docs.aws.amazon.com Open in urlscan Pro
13.35.58.67 Public Scan

Back to summary

URL:
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/monitoring-instances-status-check_sched.html
Submission: On June 07 via manual (June 7th 2024, 12:53:23 pm UTC) from GB — Scanned from GB

Form analysis
0 forms found in the DOM

Text Content

SELECT YOUR COOKIE PREFERENCES

We use essential cookies and similar tools that are necessary to provide our
site and services. We use performance cookies to collect anonymous statistics so
we can understand how customers use our site and make improvements. Essential
cookies cannot be deactivated, but you can click “Customize cookies” to decline
performance cookies.

If you agree, AWS and approved third parties will also use cookies to provide
useful site features, remember your preferences, and display relevant content,
including relevant advertising. To continue without accepting these cookies,
click “Continue without accepting.” To make more detailed choices or learn more,
click “Customize cookies.”

Accept all cookiesContinue without acceptingCustomize cookies

CUSTOMIZE COOKIE PREFERENCES

We use cookies and similar tools (collectively, "cookies") for the following
purposes.

ESSENTIAL

Essential cookies are necessary to provide our site and services and cannot be
deactivated. They are usually set in response to your actions on the site, such
as setting your privacy preferences, signing in, or filling in forms.

PERFORMANCE

Performance cookies provide anonymous statistics about how customers navigate
our site so we can improve site experience and performance. Approved third
parties may perform analytics on our behalf, but they cannot use the data for
their own purposes.

Allow performance category
Allowed

FUNCTIONAL

Functional cookies help us provide useful site features, remember your
preferences, and display relevant content. Approved third parties may set these
cookies to provide certain site features. If you do not allow these cookies,
then some or all of these services may not function properly.

Allow functional category
Allowed

ADVERTISING

Advertising cookies may be set through our site by us or our advertising
partners and help us deliver relevant marketing content. If you do not allow
these cookies, you will experience less relevant advertising.

Allow advertising category
Allowed

Blocking some types of cookies may impact your experience of our sites. You may
review and change your choices at any time by clicking Cookie preferences in the
footer of this site. We and selected third-parties use cookies or similar
technologies as specified in the AWS Cookie Notice.

CancelSave preferences

UNABLE TO SAVE COOKIE PREFERENCES

We will only store essential cookies at this time, because we were unable to
save your cookie preferences.

If you want to change your cookie preferences, try again later using the link in
the AWS console footer, or contact support if the problem persists.

Dismiss

Create an AWS Account
1. AWS
2. ...

3. Documentation
4. Amazon EC2
5. User Guide for Linux Instances

Feedback
Preferences

AMAZON ELASTIC COMPUTE CLOUD

USER GUIDE FOR LINUX INSTANCES

* What is Amazon EC2?
* Set up
* Get started tutorial
* Best practices
* Amazon Machine Images
* AMI types
* Virtualization types
* Boot modes
* Launch an instance
* AMI boot mode parameter
* Instance type boot mode
* Instance boot mode
* Operating system boot mode
* Set AMI boot mode
* UEFI variables
* UEFI Secure Boot
* How UEFI Secure Boot works
* Launch an instance with UEFI Secure Boot support
* Verify whether an instance is enabled for UEFI Secure Boot
* Create a Linux AMI to support UEFI Secure Boot
* Create three key pairs
* Option A: Add keys to the variable store from within the instance
* Option B: Create a binary blob containing a pre-filled variable
store

* How the AWS binary blob is created

* Find a Linux AMI
* Shared AMIs
* Find shared AMIs
* Make an AMI public
* Share an AMI with organizations or OUs
* Share an AMI with specific AWS accounts
* Cancel having an AMI shared with your account
* Use bookmarks
* Guidelines for shared Linux AMIs

* Paid AMIs
* AMI lifecycle
* Create an AMI
* Create an Amazon EBS-backed Linux AMI
* Create an instance store-backed Linux AMI
* Set up the AMI tools
* Create an AMI from an instance store-backed instance
* Convert to an Amazon EBS-Backed AMI
* AMI tools reference

* Modify an AMI
* Copy an AMI
* Store and restore an AMI
* Deprecate an AMI
* Disable an AMI
* Archive AMI snapshots
* Deregister (delete) an AMI
* Automate the EBS-backed AMI lifecycle

* Use encryption with EBS-backed AMIs
* Monitor AMI events
* Understand AMI billing
* AMI billing fields
* Find AMI billing information
* Verify AMI charges on your bill

* AMI quotas

* Instances
* Instances and AMIs
* Instance types
* Find an instance type
* Get recommendations
* For new workloads
* For existing workloads

* Change the instance type
* Compatibility
* Troubleshoot
* Instance store-backed instances

* Burstable performance instances
* Key concepts
* Unlimited mode
* Concepts
* Examples

* Standard mode
* Concepts
* Examples

* Work with burstable performance instances
* Monitor your CPU credits

* Mac instances
* Launch a Mac instance
* Connect to your Mac instance
* Update the operating system and software on Mac instances
* Increase the size of an EBS volume on your Mac instance
* Stop and terminate your Mac instance
* Find supported macOS versions for Dedicated Host
* Subscribe to macOS AMI notifications
* EC2 macOS AMIs release notes

* EBS optimization
* Instance purchasing options
* On-Demand Instances
* Reserved Instances
* Regional and zonal Reserved Instances (scope)
* Types of Reserved Instances (offering classes)
* How Reserved Instances are applied
* Use your Reserved Instances
* How you are billed
* Buy Reserved Instances
* Sell in the Reserved Instance Marketplace
* Modify Reserved Instances
* Exchange Convertible Reserved Instances
* Reserved Instance quotas

* Spot Instances
* Best practices
* How Spot Instances work
* Spot Instance pricing history
* Savings
* Work with Spot Instances
* Example launch specifications

* Spot request status
* Rebalance recommendations
* Spot Instance interruptions
* Reasons for interruption
* Interruption behavior
* Stop
* Hibernate
* Terminate
* Prepare for interruptions
* Initiate an interruption
* Spot Instance interruption notices
* Find interrupted Spot Instances
* Determine whether Amazon EC2 terminated a Spot Instance
* Billing

* Spot placement score
* Spot Instance data feed
* Spot Instance quotas
* Burstable performance instances

* Dedicated Hosts
* Pricing and billing
* Burstable T3 instances on Dedicated Hosts
* Work with Dedicated Hosts
* Work with shared Dedicated Hosts
* Dedicated Hosts on AWS Outposts
* Host recovery
* Host maintenance
* Track configuration changes

* Dedicated Instances
* Work with Dedicated Instances

* Capacity Reservations
* On-Demand Capacity Reservations
* Capacity Reservation pricing and billing
* Work with Capacity Reservations
* Work with Capacity Reservation groups
* Capacity Reservations in cluster placement groups
* Capacity Reservations in Local Zones
* Capacity Reservations in Wavelength Zones
* Capacity Reservations on AWS Outposts
* Work with shared Capacity Reservations
* Capacity Reservation Fleets
* Capacity Reservation Fleet concepts
* Work with Capacity Reservation Fleets
* Example configurations
* Using service-linked roles

* Monitoring Capacity Reservations
* CloudWatch metrics
* EventBridge events
* Utilization notifications

* Capacity Blocks for ML
* Capacity Blocks pricing and billing
* Work with Capacity Blocks
* Monitor Capacity Blocks

* Instance lifecycle
* Launch
* Launch using the launch instance wizard
* Old launch instance wizard

* Launch using a launch template
* Restrictions
* Permissions
* Control launching instances
* Create
* Modify (manage versions)
* Delete
* Launch instances

* Launch an instance from an existing instance
* Use an AWS Marketplace instance

* Stop and start
* How it works
* Enable stop protection

* Hibernate
* How it works
* Prerequisites
* Configure an AMI to support hibernation
* Enable instance hibernation
* Disable KASLR on an instance (Ubuntu only)
* Hibernate an instance
* Start a hibernated instance
* Troubleshoot

* Reboot
* Terminate
* How it works
* Enable termination protection
* Change the instance initiated shutdown behavior
* Preserve data when an instance is terminated

* Retire
* Instance resiliency
* CloudWatch action based recovery
* Simplified automatic recovery

* Connect
* Connect to your Linux instance
* Connect with SSH from Linux or macOS
* Connect from Windows
* Connect with OpenSSH (Recommended)
* Connect with PuTTY
* Connect with WSL

* Connect with EC2 Instance Connect
* Tutorial
* Prerequisites
* Permissions
* Install EC2 Instance Connect
* Connect using EC2 Instance Connect
* Uninstall EC2 Instance Connect

* Connect with Session Manager

* Connect using EC2 Instance Connect Endpoint
* Permissions
* Security groups
* Create an EC2 Instance Connect Endpoint
* Connect to an instance
* Log connections
* Delete an EC2 Instance Connect Endpoint
* Service-linked role
* Quotas

* Connect your instance to a resource
* Tutorial: Connect an EC2 instance to an RDS database
* Option 1: Automatically connect – EC2 console
* Task 1: Create an RDS database – optional
* Task 2: Launch an EC2 instance – optional
* Task 3: Automatically connect your EC2 instance to your RDS
database
* Task 4: Verify the connection configuration

* Option 2: Automatically connect – RDS console
* Task 1: Launch an EC2 instance – optional
* Task 2: Create an RDS database and automatically connect it to
your EC2 instance
* Task 3: Verify the connection configuration

* Option 3: Manually connect (create security groups)
* Task 1: Launch an EC2 instance – optional
* Task 2: Create an RDS database – optional
* Task 3: Manually connect your EC2 instance to your RDS
database

* Clean up

* Configure instances
* Manage users
* Processor state control
* Set the time
* GPU instances
* Install NVIDIA drivers
* Install AMD drivers
* Activate NVIDIA GRID Virtual Applications
* Set up dual 4k displays
* Get started with P5 instances
* Optimize GPU settings

* Optimize CPU options
* Rules for specifying CPU options
* CPU cores and threads per CPU core per instance type
* Specify CPU options for your instance
* View the CPU options for your instance

* CPU features
* AMD SEV-SNP
* Requirements
* Considerations
* Concepts and terminology
* Working with AMD SEV-SNP
* Attestation with AMD SEV-SNP

* Run commands at launch
* Instance metadata and user data
* Use IMDSv2
* How IMDSv2 works
* Transition to using IMDSv2
* Supported SDKs

* Configure the instance metadata options
* For new instances
* For existing instances

* Retrieve instance metadata
* Work with instance user data
* Retrieve dynamic data
* Instance metadata categories
* Example: AMI launch index value
* Instance identity documents
* Verify using the PKCS7 signature
* Verify using the base64-encoded signature
* Verify using the RSA-2048 signature
* AWS public certificates

* Instance identity roles

* Identify instances

* Fleets
* EC2 Fleet
* EC2 Fleet request types
* EC2 Fleet 'instant' type

* EC2 Fleet configuration strategies
* Plan an EC2 Fleet
* Allocation strategies for Spot Instances
* Attribute-based instance type selection
* On-Demand backup
* Capacity Rebalancing
* Maximum price overrides
* Control spending
* Instance weighting

* Work with EC2 Fleets

* Spot Fleet
* Spot Fleet request types
* Spot Fleet configuration strategies
* Plan a Spot Fleet request
* Allocation strategies for Spot Instances
* Attribute-based instance type selection
* On-Demand in Spot Fleet
* Capacity Rebalancing
* Spot price overrides
* Control spending
* Instance weighting

* Work with Spot Fleets
* CloudWatch metrics for Spot Fleet
* Automatic scaling for Spot Fleet
* Target tracking scaling policies
* Step scaling policies
* Scheduled scaling

* Monitor fleet events
* EC2 Fleet event types
* Spot Fleet event types
* Create EventBridge rules
* For EC2 Fleet events
* For Spot Fleet events

* Tutorials
* Tutorial: Use EC2 Fleet with instance weighting
* Tutorial: Use EC2 Fleet with On-Demand as the primary capacity
* Tutorial: Launch On-Demand Instances using targeted Capacity
Reservations
* Tutorial: Launch instances into Capacity Blocks
* Tutorial: Use Spot Fleet with instance weighting

* Example configurations
* EC2 Fleet example configurations
* Spot Fleet example configurations

* Fleet quotas

* Monitor
* Automated and manual monitoring
* Best practices for monitoring
* Monitor the status of your instances
* Instance status checks
* State change events
* Scheduled events
* Define event windows for scheduled events

* Monitor your instances using CloudWatch
* Instance alarms
* Enable detailed monitoring
* List available metrics
* Install and configure the CloudWatch agent
* Get statistics for metrics
* Get statistics for a specific instance
* Aggregate statistics across instances
* Aggregate statistics by Auto Scaling group
* Aggregate statistics by AMI

* Graph metrics
* Create an alarm
* Create alarms that stop, terminate, reboot, or recover an instance

* Automate using EventBridge
* Log API calls with AWS CloudTrail

* Networking
* Regions and Zones
* Instance IP addressing
* Multiple IP addresses

* Instance hostname types
* Bring your own IP addresses
* Elastic IP addresses
* Network interfaces
* Best practices for configuring network interfaces
* Scenarios for network interfaces
* Requester-managed network interfaces
* Assign prefixes
* Work with prefixes

* Network bandwidth
* Enhanced networking
* Elastic Network Adapter (ENA)
* ENA Express
* Intel 82599 VF
* Operating system optimizations
* Network performance metrics
* Troubleshoot ENA
* Improve network latency on Linux instances
* Nitro performance considerations

* Elastic Fabric Adapter
* Get started with P5 instances and EFA
* Get started with EFA and MPI
* Get started with EFA and NCCL
* Use a base AMI
* Use an AWS Deep Learning AMI

* Work with EFA
* Monitor an EFA
* Verify the EFA installer using a checksum

* Instance topology
* How it works
* Prerequisites
* Examples

* Placement groups
* Placement strategies
* Rules and limitations
* Work with placement groups
* Share a placement group
* Placement groups on AWS Outposts

* Network MTU
* Virtual private clouds

* Security
* Infrastructure security
* Resilience
* Data protection
* Identity and access management
* IAM policies
* Policy structure
* Tag resources during creation
* Control access to EC2 resources using resource tags
* Example policies for CLI or SDK
* Example policies for the console

* AWS managed policies
* IAM roles

* Key pairs
* Create a key pair
* Tag a key pair
* Describe your key pairs
* Delete your key pair
* Add or remove a public key on your instance
* Verify the fingerprint

* Security groups
* Security group rules
* Connection tracking
* Default and custom security groups
* Work with security groups
* Security group rules for different use cases

* AWS PrivateLink
* Update management
* Compliance validation
* NitroTPM
* Considerations
* Prerequisites
* Create a Linux AMI for NitroTPM support
* Verify whether an AMI is enabled for NitroTPM
* Enable or stop using NitroTPM on an instance
* Retrieve the public endorsement key

* Storage
* Amazon EBS
* Instance store
* Add instance store volumes
* SSD instance store volumes
* Instance store swap volumes
* Optimize disk performance

* File storage
* Amazon S3
* Amazon EFS
* Amazon FSx
* Amazon File Cache

* Instance volume limits
* Root device volume
* Replace a root volume

* Device names
* Block device mappings
* Torn write prevention

* Resources and tags
* Recycle Bin
* Considerations
* Required IAM permissions
* Condition keys for Recycle Bin

* Work with retention rules
* Work with resources in the Recycle Bin
* Recover snapshots from the Recycle Bin
* Recover AMIs from the Recycle Bin

* Monitor Recycle Bin
* Monitor using EventBridge
* Monitor using CloudTrail

* Resource locations
* Resource IDs
* List and filter your resources
* Global View
* Tag your resources
* Service quotas
* Usage reports

* Troubleshoot
* Troubleshoot launch issues
* Connect to your instance
* Stop your instance
* Terminate your instance
* Failed status checks
* Troubleshoot an unreachable instance
* Boot from the wrong volume
* EC2Rescue for Linux
* Install EC2Rescue for Linux
* (Optional) Verify the signature of EC2Rescue for Linux
* Work with EC2Rescue for Linux
* Develop EC2Rescue modules

* EC2 Serial Console
* Prerequisites
* Configure access to the EC2 Serial Console
* Connect to the EC2 Serial Console
* Disconnect from the EC2 Serial Console
* Troubleshoot your instance using the EC2 Serial Console
* Troubleshoot your Linux instance using GRUB
* Troubleshoot your Linux instance using SysRq

* Send a diagnostic interrupt

* Related information
* Document history

Scheduled events for your instances - Amazon Elastic Compute Cloud
AWSDocumentationAmazon EC2User Guide for Linux Instances
Types of scheduled eventsView scheduled eventsCustomize scheduled event
notificationsWork with instances scheduled to stop or retireWork with instances
scheduled for rebootWork with instances scheduled for maintenanceReschedule a
scheduled event

SCHEDULED EVENTS FOR YOUR INSTANCES

PDFRSS

AWS can schedule events for your instances, such as a reboot, stop/start, or
retirement. These events do not occur frequently. If one of your instances will
be affected by a scheduled event, AWS sends an email to the email address that's
associated with your AWS account prior to the scheduled event. The email
provides details about the event, including the start and end date. Depending on
the event, you might be able to take action to control the timing of the event.
AWS also sends an AWS Health event, which you can monitor and manage by using
Amazon CloudWatch Events. For more information about monitoring AWS Health
events with CloudWatch, see Monitoring AWS Health events with CloudWatch Events.

Scheduled events are managed by AWS; you cannot schedule events for your
instances. You can view the events scheduled by AWS, customize scheduled event
notifications to include or remove tags from the email notification, and perform
actions when an instance is scheduled to reboot, retire, or stop.

To update the contact information for your account so that you can be sure to be
notified about scheduled events, go to the Account Settings page.

NOTE

When an instance is affected by a scheduled event, and it is part of an Auto
Scaling group, Amazon EC2 Auto Scaling eventually replaces it as part of its
health checks, with no further action necessary on your part. For more
information about the health checks performed by Amazon EC2 Auto Scaling, see
Health checks for Auto Scaling instances in the Amazon EC2 Auto Scaling User
Guide.

CONTENTS

* Types of scheduled events
* View scheduled events
* Customize scheduled event notifications
* Work with instances scheduled to stop or retire
* Work with instances scheduled for reboot
* Work with instances scheduled for maintenance
* Reschedule a scheduled event
* Define event windows for scheduled events

TYPES OF SCHEDULED EVENTS

Amazon EC2 can create the following types of events for your instances, where
the event occurs at a scheduled time:

* Instance stop: At the scheduled time, the instance is stopped. When you start
it again, it's migrated to a new host. Applies only to instances backed by
Amazon EBS.

* Instance retirement: At the scheduled time, the instance is stopped if it is
backed by Amazon EBS, or terminated if it is backed by instance store.

* Instance reboot: At the scheduled time, the instance is rebooted.

* System reboot: At the scheduled time, the host for the instance is rebooted.

* System maintenance: At the scheduled time, the instance might be temporarily
affected by network maintenance or power maintenance.

VIEW SCHEDULED EVENTS

In addition to receiving notification of scheduled events in email, you can
check for scheduled events by using one of the following methods.

Console

TO VIEW SCHEDULED EVENTS FOR YOUR INSTANCES

1. Open the Amazon EC2 console at https://console.aws.amazon.com/ec2/.

2. The dashboard displays any resources with an associated event under
Scheduled events.

3. For more detail, choose Events in the navigation pane. Any resources with an
associated event are displayed. You can filter by characteristics such as
event type, resource type, and Availability Zone.

AWS CLI

TO VIEW SCHEDULED EVENTS FOR YOUR INSTANCES

Use the describe-instance-status command.

aws ec2 describe-instance-status \
--instance-id i-1234567890abcdef0 \
--query "InstanceStatuses[].Events"

The following example output shows a reboot event.

[
"Events": [
{
"InstanceEventId": "instance-event-0d59937288b749b32",
"Code": "system-reboot",
"Description": "The instance is scheduled for a reboot",
"NotAfter": "2019-03-15T22:00:00.000Z",
"NotBefore": "2019-03-14T20:00:00.000Z",
"NotBeforeDeadline": "2019-04-05T11:00:00.000Z"
}

]
]

The following example output shows an instance retirement event.

[
"Events": [
{
"InstanceEventId": "instance-event-0e439355b779n26",
"Code": "instance-stop",
"Description": "The instance is running on degraded hardware",
"NotBefore": "2015-05-23T00:00:00.000Z"
}
]
]

PowerShell

TO VIEW SCHEDULED EVENTS FOR YOUR INSTANCES USING THE AWS TOOLS FOR WINDOWS
POWERSHELL

Use the following Get-EC2InstanceStatus command.

PS C:\> (Get-EC2InstanceStatus -InstanceId i-1234567890abcdef0).Events

The following example output shows an instance retirement event.

Code : instance-stop
Description : The instance is running on degraded hardware
NotBefore : 5/23/2015 12:00:00 AM

Instance metadata

TO VIEW SCHEDULED EVENTS FOR YOUR INSTANCES USING INSTANCE METADATA

You can retrieve information about active maintenance events for your instances
from the instance metadata by using Instance Metadata Service Version 2 or
Instance Metadata Service Version 1.

IMDSv2

[ec2-user ~]$ TOKEN=`curl -X PUT "http://169.254.169.254/latest/api/token" -H "X-aws-ec2-metadata-token-ttl-seconds: 21600"` \
&& curl -H "X-aws-ec2-metadata-token: $TOKEN" http://169.254.169.254/latest/meta-data/events/maintenance/scheduled

IMDSv1

[ec2-user ~]$ curl http://169.254.169.254/latest/meta-data/events/maintenance/scheduled

The following is example output with information about a scheduled system reboot
event, in JSON format.

[
{
"NotBefore" : "21 Jan 2019 09:00:43 GMT",
"Code" : "system-reboot",
"Description" : "scheduled reboot",
"EventId" : "instance-event-0d59937288b749b32",
"NotAfter" : "21 Jan 2019 09:17:23 GMT",
"State" : "active"
}
]

TO VIEW EVENT HISTORY ABOUT COMPLETED OR CANCELED EVENTS FOR YOUR INSTANCES
USING INSTANCE METADATA

You can retrieve information about completed or canceled events for your
instances from instance metadata by using Instance Metadata Service Version 2 or
Instance Metadata Service Version 1.

IMDSv2

IMDSv1

[ec2-user ~]$ curl http://169.254.169.254/latest/meta-data/events/maintenance/history

The following is example output with information about a system reboot event
that was canceled, and a system reboot event that was completed, in JSON format.

[
{
"NotBefore" : "21 Jan 2019 09:00:43 GMT",
"Code" : "system-reboot",
"Description" : "[Canceled] scheduled reboot",
"EventId" : "instance-event-0d59937288b749b32",
"NotAfter" : "21 Jan 2019 09:17:23 GMT",
"State" : "canceled"
},
{
"NotBefore" : "29 Jan 2019 09:00:43 GMT",
"Code" : "system-reboot",
"Description" : "[Completed] scheduled reboot",
"EventId" : "instance-event-0d59937288b749b32",
"NotAfter" : "29 Jan 2019 09:17:23 GMT",
"State" : "completed"
}
]

AWS Health

You can use the AWS Health Dashboard to learn about events that can affect your
instance. The AWS Health Dashboard organizes issues in three groups: open
issues, scheduled changes, and other notifications. The scheduled changes group
contains items that are ongoing or upcoming.

For more information, see Getting started with your AWS Health Dashboard in the
AWS Health User Guide.

anchoranchoranchoranchoranchor
* Console
* AWS CLI
* PowerShell
* Instance metadata
* AWS Health

TO VIEW SCHEDULED EVENTS FOR YOUR INSTANCES

1. Open the Amazon EC2 console at https://console.aws.amazon.com/ec2/.

2. The dashboard displays any resources with an associated event under
Scheduled events.

CUSTOMIZE SCHEDULED EVENT NOTIFICATIONS

You can customize scheduled event notifications to include tags in the email
notification. This makes it easier to identify the affected resource (instances
or Dedicated Hosts) and to prioritize actions for the upcoming event.

When you customize event notifications to include tags, you can choose to
include:

* All of the tags that are associated with the affected resource

* Only specific tags that are associated with the affected resource

For example, suppose that you assign application, costcenter, project, and owner
tags to all of your instances. You can choose to include all of the tags in
event notifications. Alternatively, if you'd like to see only the owner and
project tags in event notifications, then you can choose to include only those
tags.

After you select the tags to include, the event notifications will include the
resource ID (instance ID or Dedicated Host ID) and the tag key and value pairs
that are associated with the affected resource.

TASKS

* Include tags in event notifications
* Remove tags from event notifications
* View the tags to be included in event notifications

INCLUDE TAGS IN EVENT NOTIFICATIONS

The tags that you choose to include apply to all resources (instances and
Dedicated Hosts) in the selected Region. To customize event notifications in
other Regions, first select the required Region and then perform the following
steps.

You can include tags in event notifications by using one of the following
methods.

Console

TO INCLUDE TAGS IN EVENT NOTIFICATIONS

1. Open the Amazon EC2 console at https://console.aws.amazon.com/ec2/.

2. In the navigation pane, choose Events.

3. Choose Actions, Manage event notifications.

4. Turn on Include tags in event notifications.

5. Do one of the following, depending on the tags that you want to include in
event notifications:

* To include all tags associated with the affected instance or Dedicated
Host, select Include all tags.

* To select the tags to include, select Choose the tags to include and then
select or enter the tag keys.

6. Choose Save.

AWS CLI

TO INCLUDE ALL TAGS IN EVENT NOTIFICATIONS

Use the register-instance-event-notification-attributes AWS CLI command and set
the IncludeAllTagsOfInstance parameter to true.

aws ec2 register-instance-event-notification-attributes \
--instance-tag-attribute "IncludeAllTagsOfInstance=true"

TO INCLUDE SPECIFIC TAGS IN EVENT NOTIFICATIONS

Use the register-instance-event-notification-attributes AWS CLI command and
specify the tags to include by using the InstanceTagKeys parameter.

aws ec2 register-instance-event-notification-attributes \
--instance-tag-attribute 'InstanceTagKeys=["tag_key_1", "tag_key_2", "tag_key_3"]'

anchoranchor
* Console
* AWS CLI

TO INCLUDE TAGS IN EVENT NOTIFICATIONS

1. Open the Amazon EC2 console at https://console.aws.amazon.com/ec2/.

2. In the navigation pane, choose Events.

3. Choose Actions, Manage event notifications.

4. Turn on Include tags in event notifications.

5. Do one of the following, depending on the tags that you want to include in
event notifications:

* To include all tags associated with the affected instance or Dedicated
Host, select Include all tags.

* To select the tags to include, select Choose the tags to include and then
select or enter the tag keys.

6. Choose Save.

REMOVE TAGS FROM EVENT NOTIFICATIONS

You can remove tags from event notifications by using one of the following
methods.

Console

TO REMOVE TAGS FROM EVENT NOTIFICATIONS

1. Open the Amazon EC2 console at https://console.aws.amazon.com/ec2/.

2. In the navigation pane, choose Events.

3. Choose Actions, Manage event notifications.

4. To remove all tags from event notifications, turn off Include tags in event
notifications.

5. To remove specific tags from event notifications, choose the X) for the
corresponding tag keys.

6. Choose Save.

AWS CLI

TO REMOVE ALL TAGS FROM EVENT NOTIFICATIONS

Use the deregister-instance-event-notification-attributes AWS CLI command and
set the IncludeAllTagsOfInstance parameter to false.

aws ec2 deregister-instance-event-notification-attributes \
--instance-tag-attribute "IncludeAllTagsOfInstance=false"

TO REMOVE SPECIFIC TAGS FROM EVENT NOTIFICATIONS

Use the deregister-instance-event-notification-attributes AWS CLI command and
specify the tags to remove by using the InstanceTagKeys parameter.

aws ec2 deregister-instance-event-notification-attributes \
--instance-tag-attribute 'InstanceTagKeys=["tag_key_1", "tag_key_2", "tag_key_3"]'

anchoranchor
* Console
* AWS CLI

TO REMOVE TAGS FROM EVENT NOTIFICATIONS

1. Open the Amazon EC2 console at https://console.aws.amazon.com/ec2/.

2. In the navigation pane, choose Events.

3. Choose Actions, Manage event notifications.

4. To remove all tags from event notifications, turn off Include tags in event
notifications.

5. To remove specific tags from event notifications, choose the X) for the
corresponding tag keys.

6. Choose Save.

VIEW THE TAGS TO BE INCLUDED IN EVENT NOTIFICATIONS

You can view the tags that are to be included in event notifications by using
one of the following methods.

Console

TO VIEW THE TAGS THAT ARE TO BE INCLUDED IN EVENT NOTIFICATIONS

1. Open the Amazon EC2 console at https://console.aws.amazon.com/ec2/.

2. In the navigation pane, choose Events.

3. Choose Actions, Manage event notifications.

AWS CLI

TO VIEW THE TAGS THAT ARE TO BE INCLUDED IN EVENT NOTIFICATIONS

Use the describe-instance-event-notification-attributes AWS CLI command.

aws ec2 describe-instance-event-notification-attributes

anchoranchor
* Console
* AWS CLI

TO VIEW THE TAGS THAT ARE TO BE INCLUDED IN EVENT NOTIFICATIONS

1. Open the Amazon EC2 console at https://console.aws.amazon.com/ec2/.

2. In the navigation pane, choose Events.

3. Choose Actions, Manage event notifications.

WORK WITH INSTANCES SCHEDULED TO STOP OR RETIRE

When AWS detects irreparable failure of the underlying host for your instance,
it schedules the instance to stop or terminate, depending on the type of root
device for the instance. If the root device is an EBS volume, the instance is
scheduled to stop. If the root device is an instance store volume, the instance
is scheduled to terminate. For more information, see Instance retirement.

IMPORTANT

Any data stored on instance store volumes is lost when an instance is stopped,
hibernated, or terminated. This includes instance store volumes that are
attached to an instance that has an EBS volume as the root device. Be sure to
save data from your instance store volumes that you might need later before the
instance is stopped, hibernated, or terminated.

ACTIONS FOR INSTANCES BACKED BY AMAZON EBS

You can wait for the instance to stop as scheduled. Alternatively, you can stop
and start the instance yourself, which migrates it to a new host. For more
information about stopping your instance, in addition to information about the
changes to your instance configuration when it's stopped, see Stop and start
Amazon EC2 instances.

You can automate an immediate stop and start in response to a scheduled instance
stop event. For more information, see Automating actions for Amazon EC2
instances in the AWS Health User Guide.

ACTIONS FOR INSTANCES BACKED BY INSTANCE STORE

We recommend that you launch a replacement instance from your most recent AMI
and migrate all necessary data to the replacement instance before the instance
is scheduled to terminate. Then, you can terminate the original instance, or
wait for it to terminate as scheduled.

WORK WITH INSTANCES SCHEDULED FOR REBOOT

When AWS must perform tasks such as installing updates or maintaining the
underlying host, it can schedule the instance or the underlying host for a
reboot. You can reschedule most reboot events so that your instance is rebooted
at a specific date and time that suits you.

VIEW THE REBOOT EVENT TYPE

You can view whether a reboot event is an instance reboot or a system reboot by
using one of the following methods.

Console

TO VIEW THE TYPE OF SCHEDULED REBOOT EVENT

1. Open the Amazon EC2 console at https://console.aws.amazon.com/ec2/.

2. In the navigation pane, choose Events.

3. Choose Resource type: instance from the filter list.

4. For each instance, view the value in the Event type column. The value is
either system-reboot or instance-reboot.

AWS CLI

TO VIEW THE TYPE OF SCHEDULED REBOOT EVENT

Use the describe-instance-status command.

aws ec2 describe-instance-status \
--instance-id i-1234567890abcdef0

For scheduled reboot events, the value for Code is either system-reboot or
instance-reboot. The following example output shows a system-reboot event.

[
"Events": [
{
"InstanceEventId": "instance-event-0d59937288b749b32",
"Code": "system-reboot",
"Description": "The instance is scheduled for a reboot",
"NotAfter": "2019-03-14T22:00:00.000Z",
"NotBefore": "2019-03-14T20:00:00.000Z",
"NotBeforeDeadline": "2019-04-05T11:00:00.000Z"
}
]
]

anchoranchor
* Console
* AWS CLI

TO VIEW THE TYPE OF SCHEDULED REBOOT EVENT

1. Open the Amazon EC2 console at https://console.aws.amazon.com/ec2/.

2. In the navigation pane, choose Events.

3. Choose Resource type: instance from the filter list.

4. For each instance, view the value in the Event type column. The value is
either system-reboot or instance-reboot.

ACTIONS FOR INSTANCE REBOOT

You can wait for the instance reboot to occur within its scheduled maintenance
window, reschedule the instance reboot to a date and time that suits you, or
reboot the instance yourself at a time that is convenient for you.

After your instance is rebooted, the scheduled event is cleared and the event's
description is updated. The pending maintenance to the underlying host is
completed, and you can begin using your instance again after it has fully
booted.

ACTIONS FOR SYSTEM REBOOT

It is not possible for you to reboot the system yourself. You can wait for the
system reboot to occur during its scheduled maintenance window, or you can
reschedule the system reboot to a date and time that suits you. A system reboot
typically completes in a matter of minutes. After the system reboot has
occurred, the instance retains its IP address and DNS name, and any data on
local instance store volumes is preserved. After the system reboot is complete,
the scheduled event for the instance is cleared, and you can verify that the
software on your instance is operating as expected.

Alternatively, if it is necessary to maintain the instance at a different time
and you can't reschedule the system reboot, then you can stop and start an
Amazon EBS-backed instance, which migrates it to a new host. However, the data
on the local instance store volumes is not preserved. You can also automate an
immediate instance stop and start in response to a scheduled system reboot
event. For more information, see Automating Actions for EC2 Instances in the AWS
Health User Guide. For an instance store-backed instance, if you can't
reschedule the system reboot, then you can launch a replacement instance from
your most recent AMI, migrate all necessary data to the replacement instance
before the scheduled maintenance window, and then terminate the original
instance.

WORK WITH INSTANCES SCHEDULED FOR MAINTENANCE

When AWS must maintain the underlying host for an instance, it schedules the
instance for maintenance. There are two types of maintenance events: network
maintenance and power maintenance.

During network maintenance, scheduled instances lose network connectivity for a
brief period of time. Normal network connectivity to your instance is restored
after maintenance is complete.

During power maintenance, scheduled instances are taken offline for a brief
period, and then rebooted. When a reboot is performed, all of your instance's
configuration settings are retained.

After your instance has rebooted (this normally takes a few minutes), verify
that your application is working as expected. At this point, your instance
should no longer have a scheduled event associated with it, or if it does, the
description of the scheduled event begins with [Completed]. It sometimes takes
up to 1 hour for the instance status description to refresh. Completed
maintenance events are displayed on the Amazon EC2 console dashboard for up to a
week.

ACTIONS FOR INSTANCES BACKED BY AMAZON EBS

You can wait for the maintenance to occur as scheduled. Alternatively, you can
stop and start the instance, which migrates it to a new host. For more
information about stopping your instance, in addition to information about the
changes to your instance configuration when it's stopped, see Stop and start
Amazon EC2 instances.

You can automate an immediate stop and start in response to a scheduled
maintenance event. For more information, see Automating Actions for EC2
Instances in the AWS Health User Guide.

ACTIONS FOR INSTANCES BACKED BY INSTANCE STORE

You can wait for the maintenance to occur as scheduled. Alternatively, if you
want to maintain normal operation during a scheduled maintenance window, you can
launch a replacement instance from your most recent AMI, migrate all necessary
data to the replacement instance before the scheduled maintenance window, and
then terminate the original instance.

RESCHEDULE A SCHEDULED EVENT

You can reschedule an event so that it occurs at a specific date and time that
suits you. Only events that have a deadline date can be rescheduled. There are
other limitations for rescheduling an event.

You can reschedule an event by using one of the following methods.

Console

TO RESCHEDULE AN EVENT

1. Open the Amazon EC2 console at https://console.aws.amazon.com/ec2/.

2. In the navigation pane, choose Events.

3. Choose Resource type: instance from the filter list.

4. Select one or more instances, and then choose Actions, Schedule event.

Only events that have an event deadline date, indicated by a value for
Deadline, can be rescheduled. If one of the selected events does not have a
deadline date, Actions, Schedule event is disabled.

5. For New start time, enter a new date and time for the event. The new date
and time must occur before the Event deadline.

6. Choose Save.

It might take a minute or two for the updated event start time to be
reflected in the console.

AWS CLI

TO RESCHEDULE AN EVENT

1. Only events that have an event deadline date, indicated by a value for
NotBeforeDeadline, can be rescheduled. Use the describe-instance-status
command to view the NotBeforeDeadline parameter value.

aws ec2 describe-instance-status \
--instance-id i-1234567890abcdef0

The following example output shows a system-reboot event that can be
rescheduled because NotBeforeDeadline contains a value.

[
"Events": [
{
"InstanceEventId": "instance-event-0d59937288b749b32",
"Code": "system-reboot",
"Description": "The instance is scheduled for a reboot",
"NotAfter": "2019-03-14T22:00:00.000Z",
"NotBefore": "2019-03-14T20:00:00.000Z",
"NotBeforeDeadline": "2019-04-05T11:00:00.000Z"
}
]
]

2. To reschedule the event, use the modify-instance-event-start-time command.
Specify the new event start time by using the not-before parameter. The new
event start time must fall before the NotBeforeDeadline.

aws ec2 modify-instance-event-start-time \
--instance-id i-1234567890abcdef0 \
--instance-event-id instance-event-0d59937288b749b32 \
--not-before 2019-03-25T10:00:00.000

It might take a minute or two before the describe-instance-status command
returns the updated not-before parameter value.

anchoranchor
* Console
* AWS CLI

TO RESCHEDULE AN EVENT

1. Open the Amazon EC2 console at https://console.aws.amazon.com/ec2/.

2. In the navigation pane, choose Events.

3. Choose Resource type: instance from the filter list.

4. Select one or more instances, and then choose Actions, Schedule event.

Only events that have an event deadline date, indicated by a value for
Deadline, can be rescheduled. If one of the selected events does not have a
deadline date, Actions, Schedule event is disabled.

5. For New start time, enter a new date and time for the event. The new date
and time must occur before the Event deadline.

6. Choose Save.

It might take a minute or two for the updated event start time to be
reflected in the console.

LIMITATIONS

* Only events with an event deadline date can be rescheduled. The event can be
rescheduled up to the event deadline date. The Deadline column in the console
and the NotBeforeDeadline field in the AWS CLI indicate if the event has a
deadline date.

* Only events that have not yet started can be rescheduled. The Start time
column in the console and the NotBefore field in the AWS CLI indicate the
event start time. Events that are scheduled to start in the next 5 minutes
cannot be rescheduled.

* The new event start time must be at least 60 minutes from the current time.

* If you reschedule multiple events using the console, the event deadline date
is determined by the event with the earliest event deadline date.

Javascript is disabled or is unavailable in your browser.

To use the Amazon Web Services Documentation, Javascript must be enabled. Please
refer to your browser's Help pages for instructions.

Document Conventions
State change events
Define event windows for scheduled events
Did this page help you? - Yes

Thanks for letting us know we're doing a good job!

If you've got a moment, please tell us what we did right so we can do more of
it.

Did this page help you? - No

Thanks for letting us know this page needs work. We're sorry we let you down.

If you've got a moment, please tell us how we can make the documentation better.

DID THIS PAGE HELP YOU?

Yes
No
Provide feedback

NEXT TOPIC:

Define event windows for scheduled events

PREVIOUS TOPIC:

State change events

NEED HELP?

* Try AWS re:Post
* Connect with an AWS IQ expert

ON THIS PAGE

VIEWING EVENTS USING THE DASHBOARD.

VIEWING EVENTS USING THE EVENTS PAGE.

docs.aws.amazon.com Open in urlscan Pro 13.35.58.67 Public Scan

Form analysis 0 forms found in the DOM

Text Content

docs.aws.amazon.com Open in urlscan Pro
13.35.58.67 Public Scan

Form analysis
0 forms found in the DOM