Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Aws::Errors::NoSuchEndpointError #71

Open
quanld1502 opened this issue Oct 8, 2024 · 0 comments
Open

Aws::Errors::NoSuchEndpointError #71

quanld1502 opened this issue Oct 8, 2024 · 0 comments

Comments

@quanld1502
Copy link

Aws::Errors::NoSuchEndpointError (Encountered a SocketError while attempting to connect to:

https://sts.us-west-2.amazonaws.com

This is typically the result of an invalid :region option or a
poorly formatted :endpoint option.

  • Avoid configuring the :endpoint option directly. Endpoints are constructed
    from the :region. The :endpoint option is reserved for certain services
    or for connecting to non-standard test endpoints.

  • Not every service is available in every region.

  • Never suffix region names with availability zones.
    Use "us-east-1", not "us-east-1a"

Known AWS regions include (not specific to this service):

af-south-1
ap-east-1
ap-northeast-1
ap-northeast-2
ap-northeast-3
ap-south-1
ap-south-2
ap-southeast-1
ap-southeast-2
ap-southeast-3
ap-southeast-4
ap-southeast-5
aws-global
ca-central-1
ca-west-1
eu-central-1
eu-central-2
eu-north-1
eu-south-1
eu-south-2
eu-west-1
eu-west-2
eu-west-3
il-central-1
me-central-1
me-south-1
sa-east-1
us-east-1
us-east-2
us-west-1
us-west-2
aws-cn-global
cn-north-1
cn-northwest-1
aws-us-gov-global
us-gov-east-1
us-gov-west-1
aws-iso-global
us-iso-east-1
us-iso-west-1
aws-iso-b-global
us-isob-east-1
eu-isoe-west-1
)

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant