Difference between revisions of "Amazon regions"

From wikieduonline
Jump to navigation Jump to search
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>

Revision as of 18:32, 2 May 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: