-
Notifications
You must be signed in to change notification settings - Fork 153
Feature request: deploy Lambda layers in ap-south-2
and me-central-1
regions
#2674
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
Comments
Will be back tomorrow and we can go thorough it 🫡 |
Access for |
I have bootstrapped the accounts but still need to run the script to align the versions. Please before running it let's talk offline. |
Access to requested regions granted. |
Putting this on hold until the next iteration (next week). |
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. |
Reopening this as we'll release the layers in these regions in a future iteration. |
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.8.0 version! |
Use case
As per issue title, we should start publishing our Lambda layers to these two regions starting from the next release. This will allow us to have the layer showing up in the Lambda console UI as well as allow customers to use the Layer in them.
Solution/User Experience
Following the process described here, we should do the following actions:
me-central-1
opt-in region in beta accountme-central-1
opt-in region in prod accountme-central-1
in beta accountme-central-1
in prod accountap-south-2
in beta accountap-south-2
in prod account.github/workflows/reusable_deploy_layer_stack.yml
listdocs/index.md
tablelayer-balancer
inap-south-2
prod accountlayer-balancer
inme-central-1
prod accountAlternative 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: