| Did this page help you? Yes No Tell us about it... |
The following table describes which Amazon EC2 resources are global, Regional, or Availability Zone-based.
| Resource | Type | Description |
|---|---|---|
|
AWS Account |
Global |
You use the same AWS account in all Regions. |
|
DevPay Product Codes |
Global |
You use the same DevPay product codes throughout all Regions. |
|
Amazon EC2 System Identifiers |
Regional |
Includes the AMI ID, Instance ID, EBS Volume ID, EBS Snapshot ID, and so on. |
|
Instances |
Availability Zone |
Instances are tied to Availability Zones. However, the instance ID is tied to the Region. |
|
AMIs |
Regional |
AMIs are tied to the Region where its files are located within Amazon S3. |
|
Security Groups |
Regional |
Security groups are not copied across Regions. Instances within the Region cannot communicate with instances outside the Region using group-based firewall rules. Traffic from instances in another Region is seen as WAN bandwidth. |
|
SSH Key Pairs |
Regional or Global |
The SSH key pairs that you create with
|
|
User-Supplied Identifiers |
Regional |
Includes security group names, SSH key pair names, and so on. Although you can create the same names in multiple Regions, they have no relationship to each other. |
|
Elastic IP Addresses |
Regional |
Elastic IP addresses are tied to a Region and cannot be mapped across Regions. |
|
EBS Volumes |
Availability Zone |
An Amazon EBS volume must be located within the same Availability Zone as the instance to which it attaches. |
|
EBS Snapshots |
Regional |
Snapshots are tied to Regions and can only be used for volumes within the same Region. |