You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Other versions of the SDK provide an option to get the region automatically when running on an EC2 instance or Lambda (for example the Java SDK)
There doesn't seem to be any good reason that the JavaScript SDK should behave differently.
Use Case
As the Java SDK's own documentation states:
When your code runs on Amazon EC2 or AWS Lambda, you might want to configure clients to use the same AWS Region that your code is running on. This decouples your code from the environment it’s running in and makes it easier to deploy your application to multiple AWS Regions for lower latency or redundancy.
Proposed Solution
Like the Java SDK, the JavaScript SDK region provider chain should try to get the region from IMDS if it's unable to get it from AWS_REGION or config files.
Other Information
No response
Acknowledgements
I may be able to implement this feature request
This feature might incur a breaking change
SDK version used
3.588
Environment details (OS name and version, etc.)
Amazon Linux 2023
The text was updated successfully, but these errors were encountered:
Describe the feature
Other versions of the SDK provide an option to get the region automatically when running on an EC2 instance or Lambda (for example the Java SDK)
There doesn't seem to be any good reason that the JavaScript SDK should behave differently.
Use Case
As the Java SDK's own documentation states:
Proposed Solution
Like the Java SDK, the JavaScript SDK region provider chain should try to get the region from IMDS if it's unable to get it from
AWS_REGION
or config files.Other Information
No response
Acknowledgements
SDK version used
3.588
Environment details (OS name and version, etc.)
Amazon Linux 2023
The text was updated successfully, but these errors were encountered: