New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ap-northeast-3 region is no longer a local region (as of 1st March 2021) #3805
Comments
Thanks for reaching out @snayler0 The SDK will support any publically released region without an API update. You should be able to use the With that said the SDKs will include the region in its metadata when the region is made available to the SDK's models. |
Is there a chance this may be different, as the region has changed from a local to a global region? See the following issue in the terraform aws provider repo that lead me here :) |
This doesn't seem to be the case. You can see here the I can confirm that it is not working for me directly in the SDK or Terraform's provider as @snayler0 stated above. |
@mcalhoun correct the Are you having issues with using the region directly in the SDK and not as a constant? |
Today's AWS SDK Go release includes the |
Since the SDK has now been updated to include |
|
Describe the bug
ap-northeast-3 region has moved from a local region to a GA region.
The code needs to be updated to reflect this.
Version of AWS SDK for Go?
v1.37.22 (all versions will have this issue though)
Additional Context
https://aws.amazon.com/blogs/aws/aws-asia-pacific-osaka-region-now-open-to-all-with-three-azs-more-services/
The text was updated successfully, but these errors were encountered: