-
Notifications
You must be signed in to change notification settings - Fork 153
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
Feature request: publish Lambda layers in Malaysia, Mexico, Thailand #3200
Comments
Adding the newer Mexico region to the issue (& renamed title). We'll aim to release them at the next release which will be in 2 weeks. |
Tried to run the bootstrap script in beta for Also I think we need to onboard the Mexico region in both beta & prod still. |
The regions are all bootstrapped in the beta stage, we still need to:
cc @am29d |
@am29d I see you have bootstrapped the regions but didn't add the new regions to the workflow matrix. With today's release the layer version in the 3 new regions went out of sync again. Please balance the versions again and add open a PR as soon as you can - so they don't go out of sync again. |
Yep, wanted to finish the work before noon, but then release was out, fix incoming. |
Ran the SSM parameter script & verified that the correct layer was published in the new regions. |
This issue is now closed. Please be mindful that future comments 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. |
This is now released under v2.16.0 version! |
Use case
AWS recently launched new region:
Asia Pacific (Malaysia) - ap-southeast-5
https://aws.amazon.com/pt/blogs/aws/now-open-aws-asia-pacific-malaysia-region/
Solution/User Experience
Deploy Lambda Layers to this new region.
Alternative solutions
No response
Acknowledgment
Future readers
Please react with 👍 and your use case to help us understand customer demand.
The text was updated successfully, but these errors were encountered: