| « PreviousNext » | |
![]() ![]() | Did this page help you? Yes | No | Tell us about it... |
Describes the status of one or more Amazon EC2 instances, including any scheduled events. Instance status has two main components:
System Status reports impaired functionality that stems from issues related to the
systems that support an instance, such as such as hardware failures and
network connectivity problems. The
DescribeInstanceStatus response elements report
such problems as impaired
reachability..
Instance Status reports impaired functionality that arises from problems internal to
the instance. The DescribeInstanceStatus response
elements report such problems as impaired reachability.
Instance status provides information about four types of scheduled events for an instance that may require your attention:
Scheduled Reboot: When Amazon EC2 determines that an instance must be rebooted, the
instances status will return one of two event codes:
system-reboot or instance-reboot. System
reboot commonly occurs if certain maintenance or upgrade operations require
a reboot of the underlying host that supports an instance. Instance reboot
commonly occurs if the instance must be rebooted, rather than the underlying
host. Rebooting events include a scheduled start and end time.
System Maintenance: When Amazon EC2 determines that an instance requires maintenance that
requires power or network impact, the instance's status will return an event
code called system-maintenance. System maintenance is either
power maintenance or network maintenance. For power maintenance, your
instance will be unavailable for a brief period of time and then rebooted.
For network maintenance, your instance will experience a brief loss of
network connectivity. System maintenance events include a scheduled start
and end time. You will also be notified by email if one of your instances is
set for system maintenance. The email message indicates when your instance
is scheduled for maintenance.
Scheduled Retirement: When Amazon EC2 determines that an instance must be shut down, the
instance's status returns an event code called
instance-retirement. Retirement commonly occurs when the
underlying host is degraded and must be replaced. Retirement events include
a scheduled start and end time. You will also be notified by email if one of
your instances is set to retiring. The email message indicates when your
instance will be permanently retired.
Scheduled Stop: When Amazon EC2 determines that an instance must be shut down, the
instances status returns an event code called instance-stop.
Stop events include a scheduled start and end time. You will also be
notified by email if one of your instances is set to stop. The email message
indicates when your instance will be stopped.
When your instance is retired, it will either be terminated (if its root device type is the
instance-store) or stopped (if its root device type is an EBS volume). Instances
stopped due to retirement will not be restarted, but you can do so manually. You can
also avoid retirement of EBS-backed instances by manually restarting your instance
when its event code is instance-retirement. This ensures that your
instance is started on a different underlying host.
InstanceIdThe list of instance IDs. If not specified, all instances are described.
Type: String
Default: None
Constraints: Maximum 100 explicitly specified instance IDs.
Required: No
IncludeAllInstancesWhen true, returns the health status for all instances (for example,
running, stopped, pending, shutting down). When
false, returns only the health status for
running instances.
Type: Boolean
Default: false
Required: No
MaxResultsThe maximum number of paginated instance items per response.
Type: Integer
Default: 1000
Required: No
NextTokenThe next paginated set of results to return.
Type: String
Default: None
Required: No
Filter.n.NameThe name of a filter. See the Supported Filters section for a list of supported filter names.
Type: String
Default: None
Required: No
Filter.n.Value.mA value for the filter. See the Supported Filters section for a list of supported values for each filter.
Type: String
Default: None
Required: No
You can specify filters so that the response includes information for only certain instances. For example, you can use a filter to specify that you're interested in instances in a specific Availability Zone. You can specify multiple values for a filter. The response includes information for an instance only if it matches at least one of the filter values that you specified.
You can specify multiple filters; for example, specify instances that are in a specific Availability Zone and have a status of retiring. The response includes information for an instance only if it matches all the filters that you specified. If there's no match, no special message is returned, the response is simply empty.
You can use wildcards in a filter value. An asterisk (*) matches zero or more characters, and a question mark (?) matches exactly one character. You can escape special characters using a backslash (\) before the character. For example, a value of \*amazon\?\\ searches for the literal string *amazon?\.
The following are the available filters.
availability-zoneThe Availability Zone of the instance.
Type: String
event.codeThe code identifying the type of event.
Type: String
Valid values: instance-reboot | system-reboot | system-maintenance |
instance-retirement | instance-stop
event.descriptionA description of the event.
Type: String
event.not-afterThe latest end time for the scheduled event.
Type: DateTime
event.not-beforeThe earliest start time for the scheduled event.
Type: DateTime
instance-state-nameThe state of the instance.
Type: String
Valid values: pending | running | shutting-down | terminated | stopping | stopped
instance-state-codeA code representing the state of the instance. The high byte is an opaque internal value and should be ignored. The low byte is set based on the state represented
Type: Integer (16-bit unsigned integer)
Valid values: 0 (pending) | 16 (running) | 32 (shutting-down) | 48 (terminated) |
64 (stopping) | 80 (stopped)
system-status.statusThe system status of the instance.
Type: String
Valid values: ok | impaired | initializing |
insufficient-data | not-applicable
system-status.reachabilityFilters on system status where the name is reachability.
Type: String
Valid values: passed | failed | initializing | insufficient-data
instance-status.statusThe status of the instance.
Type: String
Valid values: ok | impaired | initializing | insufficient-data | not-applicable
instance-status.reachabilityFilters on instance status where the name is reachability.
Type: String
Valid values: passed | failed |initializing | insufficient-data
The following elements are returned in a
DescribeInstanceStatusResponse element.
requestIdThe ID of the request.
Type: xsd:string
instanceStatusSetA list of instances status descriptions, each one wrapped in an item element.
Type: InstanceStatusItemType
nextTokenThe next paginated set of results to return.
Type: xsd:string
This example returns instance status descriptions for all instances.
https://ec2.amazonaws.com/? Action=DescribeInstanceStatus &Version=2013-02-01 &AuthParams
This example returns instance status descriptions for the specified instances.
https://ec2.amazonaws.com/? Action=DescribeInstanceStatus &InstanceId.0=i-1a2b3c4d &InstanceId.1=i-2a2b3c4d &Version=2013-02-01 &AuthParams
This example returns instance status descriptions for all instances specified by supported DescribeInstanceStatus filters.
https://ec2.amazonaws.com/? Action=DescribeInstanceStatus &Filter.0.Name=system-status.reachability &Filter.0.Value.failed &Version=2013-02-01 &AuthParams
<DescribeInstanceStatusResponse xmlns="http://ec2.amazonaws.com/doc/2013-02-01/">
<requestId>3be1508e-c444-4fef-89cc-0b1223c4f02fEXAMPLE</requestId>
<instanceStatusSet>
<item>
<instanceId>i-1a2b3c4d</instanceId>
<availabilityZone>us-east-1d</availabilityZone>
<instanceState>
<code>16</code>
<name>running</name>
</instanceState>
<systemStatus>
<status>impaired</status>
<details>
<item>
<name>reachability</name>
<status>failed</status>
<impairedSince>YYYY-MM-DDTHH:MM:SS.000Z</impairedSince>
</item>
</details>
</systemStatus>
<instanceStatus>
<status>impaired</status>
<details>
<item>
<name>reachability</name>
<status>failed</status>
<impairedSince>YYYY-MM-DDTHH:MM:SS.000Z</impairedSince>
</item>
</details>
</instanceStatus>
<eventsSet>
<code>instance-retirement</code>
<notBefore>YYYY-MM-DDTHH:MM:SS+0000</notBefore>
<notAfter>YYYY-MM-DDTHH:MM:SS+0000</notAfter>
<description>
The instance is running on degraded hardware
</description>
</eventsSet>
</item>
<item>
<instanceId>i-2a2b3c4d</instanceId>
<availabilityZone>us-east-1d</availabilityZone>
<instanceState>
<code>16</code>
<name>running</name>
</instanceState>
<systemStatus>
<status>ok</status>
<details>
<item>
<name>reachability</name>
<status>passed</status>
</item>
</details>
</systemStatus>
<instanceStatus>
<status>ok</status>
<details>
<item>
<name>reachability</name>
<status>passed</status>
</item>
</details>
</instanceStatus>
<eventsSet>
<code>instance-reboot</code>
<notBefore>YYYY-MM-DDTHH:MM:SS+0000</notBefore>
<notAfter>YYYY-MM-DDTHH:MM:SS+0000</notAfter>
<description>
The instance is scheduled for a reboot
</description>
</eventsSet>
</item>
<item>
<instanceId>i-3a2b3c4d</instanceId>
<availabilityZone>us-east-1c</availabilityZone>
<instanceState>
<code>16</code>
<name>running</name>
</instanceState>
<systemStatus>
<status>ok</status>
<details>
<item>
<name>reachability</name>
<status>passed</status>
</item>
</details>
</systemStatus>
<instanceStatus>
<status>ok</status>
<details>
<item>
<name>reachability</name>
<status>passed</status>
</item>
</details>
</instanceStatus>
</item>
<item>
<instanceId>i-4a2b3c4d</instanceId>
<availabilityZone>us-east-1c</availabilityZone>
<instanceState>
<code>16</code>
<name>running</name>
</instanceState>
<systemStatus>
<status>ok</status>
<details>
<item>
<name>reachability</name>
<status>passed</status>
</item>
</details>
</systemStatus>
<instanceStatus>
<status>insufficient-data</status>
<details>
<item>
<name>reachability</name>
<status>insufficient-data</status>
</item>
</details>
</instanceStatus>
</item>
</instanceStatusSet>
</DescribeInstanceStatusResponse>