Difference between revisions of "Amazon regions"
| Line 55: | Line 55: | ||
* [[AWS policy]]: <code>[[aws:RequestedRegion]]</code> (April 2018) <ref>https://aws.amazon.com/es/blogs/security/easier-way-to-control-access-to-aws-regions-using-iam-policies/</ref> | * [[AWS policy]]: <code>[[aws:RequestedRegion]]</code> (April 2018) <ref>https://aws.amazon.com/es/blogs/security/easier-way-to-control-access-to-aws-regions-using-iam-policies/</ref> | ||
* <code>[[aws configure]]</code>: <code>[[.aws/config]]</code>, <code>[[.aws/credentials]]</code> | * <code>[[aws configure]]</code>: <code>[[.aws/config]]</code>, <code>[[.aws/credentials]]</code> | ||
| + | * <code>[[aws configure get region]]</code> | ||
* [[Cross-region]]: [[Amazon S3 Cross-Region Replication (CRR)]], [[SRR]], [[EventBridge]] | * [[Cross-region]]: [[Amazon S3 Cross-Region Replication (CRR)]], [[SRR]], [[EventBridge]] | ||
* <code>[[suaws]]</code> | * <code>[[suaws]]</code> | ||
| Line 62: | Line 63: | ||
* <code>[[AWS_DEFAULT_REGION]]</code> | * <code>[[AWS_DEFAULT_REGION]]</code> | ||
* [[AWS Global Accelerator]] for instant AWS region [[failover]] | * [[AWS Global Accelerator]] for instant AWS region [[failover]] | ||
| − | + | ||
* [[Multi-Region]]: [[RDS]] | * [[Multi-Region]]: [[RDS]] | ||
* <code>[[AWS_REGION]]</code> | * <code>[[AWS_REGION]]</code> | ||
Revision as of 15:32, 2 August 2022
- https://aws.amazon.com/about-aws/global-infrastructure/regions_az/
- https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Concepts.RegionsAndAvailabilityZones.html
Contents
Regions
North America
- 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
- São Paulo:
sa-east-1
Middle East
Europe
- Frankfurt:
eu-central-1 - Dublin:
eu-west-1 - London:
eu-west-2 - Paris:
eu-west-3 - Stockholm:
eu-north-1 - Milan:
eu-south-1 - Spain (announced mid-2022)
Africa
- Cape Town:
af-south-1
Asia
- 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
- Sydney:
ap-southeast-2
aws ec2 describe-regions --query "Regions[].{Name:RegionName}" --output text
Regional tokens
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
- Learn how to enable or disable AWS regions: https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_examples_aws-enable-disable-regions.html
Related terms
- AWS policy:
aws:RequestedRegion(April 2018) [1] 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
See also
- 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:
