Skip to content
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

Closed
snayler0 opened this issue Mar 3, 2021 · 7 comments
Closed
Labels
closing-soon This issue will automatically close in 4 days unless further comments are made. feature-request A feature should be added or improved. service-api This issue is due to a problem in a service API, not the SDK implementation.

Comments

@snayler0
Copy link

snayler0 commented Mar 3, 2021

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/

@jasdel
Copy link
Contributor

jasdel commented Mar 3, 2021

Thanks for reaching out @snayler0 The SDK will support any publically released region without an API update. You should be able to use the ap-northeast-3 region now with the SDK, and shouldn't need to wait for an update.

With that said the SDKs will include the region in its metadata when the region is made available to the SDK's models.

@jasdel jasdel added feature-request A feature should be added or improved. service-api This issue is due to a problem in a service API, not the SDK implementation. and removed bug This issue is a bug. needs-triage This issue or PR still needs to be triaged. labels Mar 3, 2021
@snayler0
Copy link
Author

snayler0 commented Mar 4, 2021

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 :)

hashicorp/terraform-provider-aws#17882

@mcalhoun
Copy link

mcalhoun commented Mar 4, 2021

You should be able to use the ap-northeast-3 region now with the SDK, and shouldn't need to wait for an update.

This doesn't seem to be the case. You can see here the ap-northeast-3 region is missing from the list of regions that endpoints will be generated for.

I can confirm that it is not working for me directly in the SDK or Terraform's provider as @snayler0 stated above.

@jasdel
Copy link
Contributor

jasdel commented Mar 4, 2021

@mcalhoun correct the ap-northeast-3 region won't be enumerated in the list of regions in the SDK until the SDK's models are updated. But you should be able to use "ap-northeast-3" as a string when configuring the SDK Config, and API Clients.

Are you having issues with using the region directly in the SDK and not as a constant?

@jasdel jasdel added the response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days. label Mar 4, 2021
@bflad
Copy link
Contributor

bflad commented Mar 4, 2021

Today's AWS SDK Go release includes the ap-northeast-3 region in the endpoints model: https://github.com/aws/aws-sdk-go/pull/3809/files#diff-783c87adfc4cf462f2451c6b5dd3078c96de3e6d29526e86cb6f086b0dcea90d

@jasdel
Copy link
Contributor

jasdel commented Mar 4, 2021

Since the SDK has now been updated to include ap-northeast-3 region in release, v1.37.24 I think we can close this issue. If you have any issues using that region, or the SDK please let us know!

@jasdel jasdel added closing-soon This issue will automatically close in 4 days unless further comments are made. and removed response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days. labels Mar 4, 2021
@snayler0 snayler0 closed this as completed Mar 8, 2021
@github-actions
Copy link

github-actions bot commented Mar 8, 2021

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closing-soon This issue will automatically close in 4 days unless further comments are made. feature-request A feature should be added or improved. service-api This issue is due to a problem in a service API, not the SDK implementation.
Projects
None yet
Development

No branches or pull requests

4 participants