Difference between revisions of "Amazon regions"

From wikieduonline
Jump to navigation Jump to search
(40 intermediate revisions by 3 users not shown)
Line 3: Line 3:
  
 
== Regions ==
 
== Regions ==
===North America===
+
=== North America ===
* N. Virginia: <code>[[us-east-1]]</code>  
+
* [[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>
* Oregon: <code>[[us-west-2]]</code>
+
* [[Oregon]]: <code>[[us-west-2]]</code>
 
* Canada: <code>[[ca-central-1]]</code>
 
* Canada: <code>[[ca-central-1]]</code>
  
Line 21: Line 21:
 
* [[London]]: <code>[[eu-west-2 ]]</code>
 
* [[London]]: <code>[[eu-west-2 ]]</code>
 
* [[Paris]]: <code>[[eu-west-3]]</code>
 
* [[Paris]]: <code>[[eu-west-3]]</code>
* [[Stockholm]]: <code>[[eu-north-1]]</code>
+
* [[Stockholm]]: <code>[[eu-north-1]]</code>  
* [[Milan]]: <code>[[eu-south-1]]</code>
+
* [[Milan]]: <code>[[eu-south-1]]</code> (2020)
* [[Spain]] (announced)
+
* [[Spain]] (announced mid-2022)
  
 
===Africa===
 
===Africa===
Line 30: Line 30:
 
===Asia===
 
===Asia===
 
* Hong Kong: <code>[[ap-east-1]]</code>
 
* Hong Kong: <code>[[ap-east-1]]</code>
* Mumbai: <code>[[ap-south-1]]</code>
+
* [[Mumbai]]: <code>[[ap-south-1]]</code>
 
* Osaka: <code>[[ap-northeast-3]]</code>
 
* Osaka: <code>[[ap-northeast-3]]</code>
 
* Seoul: <code>[[ap-northeast-2]]</code>
 
* Seoul: <code>[[ap-northeast-2]]</code>
Line 38: Line 38:
 
===Oceania===
 
===Oceania===
 
* 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]] ==
 +
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
 +
* [[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>
  
 
== Related terms ==
 
== Related terms ==
 
* [[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>
* [[Amazon S3 Cross-Region Replication (CRR)]], [[SRR]]
+
* <code>[[aws configure get region]]</code>
 +
* [[Cross-region]]: [[Amazon S3 Cross-Region Replication (CRR)]], [[SRR]], [[EventBridge]]
 
* <code>[[suaws]]</code>
 
* <code>[[suaws]]</code>
* [[ibmcloud regions]]
 
 
* [[TaskCat]] [[CloudFormation]] validation tool
 
* [[TaskCat]] [[CloudFormation]] validation tool
* <code>[[--region]]</code>
+
* <code>[[--region]]</code> option in <code>[[aws]]</code> command.
 +
* [[Terraform data source: aws region]]
 +
* <code>[[AWS_DEFAULT_REGION]]</code>
 +
* [[AWS Global Accelerator]] for instant AWS region [[failover]]
 +
 
 +
* [[Multi-Region]]: [[RDS]]
 +
* <code>[[AWS_REGION]]</code>
 +
* [[AWS partition]]
 +
* <code>[[aws-all-regions]]</code>
 +
* [[Amazon EC2 Global View]]
 +
* <code>[[eksctl get cluster --all-regions]]</code>
  
 
== See also ==
 
== See also ==
 +
* {{Amazon regions}}
 
* {{AWS terms}}
 
* {{AWS terms}}
* {{AWS}}
+
* {{Cloud regions}}
  
 
[[Category:AWS]]
 
[[Category:AWS]]

Revision as of 09:30, 21 June 2024

Regions

North America

South America

Middle East

Europe

Africa

Asia

Oceania


Commands

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

Related terms

See also

  • 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/
  • Advertising: