Difference between revisions of "Amazon regions"
Jump to navigation
Jump to search
↑ https://docs.aws.amazon.com/accounts/latest/reference/manage-acct-regions.html
↑ https://aws.amazon.com/es/blogs/security/easier-way-to-control-access-to-aws-regions-using-iam-policies/
| (4 intermediate revisions by the same user not shown) | |||
| Line 3: | Line 3: | ||
== Regions == | == Regions == | ||
| − | ===North America=== | + | === North America === |
| − | * N. Virginia: <code>[[us-east-1]]</code>: <code>[[InvalidViewerCertificate]]</code> in <code>[[AWS CloudFront]]</code>, [[AWS CloudFormation]] | + | * [[N. Virginia]]: <code>[[us-east-1]]</code>: <code>[[InvalidViewerCertificate]]</code> in <code>[[AWS CloudFront]]</code>, [[AWS CloudFormation]] |
* Ohio: <code>[[us-east-2]]</code> | * Ohio: <code>[[us-east-2]]</code> | ||
* N. California: <code>[[us-west-1]]</code> | * N. California: <code>[[us-west-1]]</code> | ||
| Line 39: | Line 39: | ||
* Sydney: <code>[[ap-southeast-2]]</code> | * Sydney: <code>[[ap-southeast-2]]</code> | ||
| − | + | ||
| + | == Commands == | ||
| + | * <code>[[aws ec2 describe-regions]] --query "Regions[].{Name:RegionName}" --output text</code> | ||
| + | * <code>[[aws account disable-region]]</code> | ||
== [[Regional tokens]] == | == [[Regional tokens]] == | ||
| Line 51: | Line 54: | ||
== Activities == | == Activities == | ||
* Learn how to enable or disable AWS regions: https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_examples_aws-enable-disable-regions.html | * Learn how to enable or disable AWS regions: https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_examples_aws-enable-disable-regions.html | ||
| + | * [[Determine region from and EC2 instance]]: <code>[[curl http://169.254.169.254/latest/meta-data/placement/region]]</code> | ||
| + | * [[AWS: Denies access to AWS based on the requested Region]] | ||
* [[Specify which AWS Regions your account can use]] <ref>https://docs.aws.amazon.com/accounts/latest/reference/manage-acct-regions.html</ref> | * [[Specify which AWS Regions your account can use]] <ref>https://docs.aws.amazon.com/accounts/latest/reference/manage-acct-regions.html</ref> | ||
| − | |||
== Related terms == | == Related terms == | ||
| Line 71: | Line 75: | ||
* <code>[[aws-all-regions]]</code> | * <code>[[aws-all-regions]]</code> | ||
* [[Amazon EC2 Global View]] | * [[Amazon EC2 Global View]] | ||
| + | * <code>[[eksctl get cluster --all-regions]]</code> | ||
== See also == | == See also == | ||
Latest revision as of 09:30, 21 June 2024
- https://aws.amazon.com/about-aws/global-infrastructure/regions_az/
- https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Concepts.RegionsAndAvailabilityZones.html
Contents
Regions[edit]
North America[edit]
- N. Virginia:
us-east-1:InvalidViewerCertificateinAWS CloudFront, AWS CloudFormation - Ohio:
us-east-2 - N. California:
us-west-1 - Oregon:
us-west-2 - Canada:
ca-central-1
South America[edit]
- São Paulo:
sa-east-1
Middle East[edit]
Europe[edit]
- Frankfurt:
eu-central-1 - Dublin:
eu-west-1 - London:
eu-west-2 - Paris:
eu-west-3 - Stockholm:
eu-north-1 - Milan:
eu-south-1(2020) - Spain (announced mid-2022)
Africa[edit]
- Cape Town:
af-south-1
Asia[edit]
- Hong Kong:
ap-east-1 - Mumbai:
ap-south-1 - Osaka:
ap-northeast-3 - Seoul:
ap-northeast-2 - Singapore:
ap-southeast-1 - Tokyo:
ap-northeast-1
Oceania[edit]
- Sydney:
ap-southeast-2
Commands[edit]
aws ec2 describe-regions --query "Regions[].{Name:RegionName}" --output textaws account disable-region
Regional tokens[edit]
AWS recommends using regional AWS Security Token Service (STS) endpoints to reduce latency. Session tokens from regional STS endpoints are valid in all AWS Regions. If you use regional STS endpoints, no action is required.
Session tokens from the global STS endpoint (https://sts.amazonaws.com) are valid only in AWS Regions that are enabled by default. If you intend to enable a new Region for your account, you can either use session tokens from regional STS endpoints or activate the global STS endpoint to issue session tokens that are valid in all AWS Regions. You can do this in Account Settings in the IAM console.
Session tokens that are valid in all AWS Regions are larger. If you store session tokens, these larger tokens might affect your systems. Learn more
Activities[edit]
- Learn how to enable or disable AWS regions: https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_examples_aws-enable-disable-regions.html
- Determine region from and EC2 instance:
curl http://169.254.169.254/latest/meta-data/placement/region - AWS: Denies access to AWS based on the requested Region
- Specify which AWS Regions your account can use [1]
Related terms[edit]
- AWS policy:
aws:RequestedRegion(April 2018) [2] aws configure:.aws/config,.aws/credentialsaws configure get region- Cross-region: Amazon S3 Cross-Region Replication (CRR), SRR, EventBridge
suaws- TaskCat CloudFormation validation tool
--regionoption inawscommand.- Terraform data source: aws region
AWS_DEFAULT_REGION- AWS Global Accelerator for instant AWS region failover
- Multi-Region: RDS
AWS_REGION- AWS partition
aws-all-regions- Amazon EC2 Global View
eksctl get cluster --all-regions
See also[edit]
- Amazon regions, Cross-region, Global View,
aws account disable-region - Region, Availability Zone (AZ), AMI, ARN, Edge Locations, CPU credits, Placement groups, AWS: Placement groups
- Amazon regions,
ibmcloud regions
Advertising:
