-
Notifications
You must be signed in to change notification settings - Fork 429
Add public lambda layer to other regions #1183
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
Thanks for opening your first issue here! We'll come back to you as soon as we can. |
Oh we missed it - assigning to @am29d as it should be straightforward for us to add. Thanks for spotting it @rubenesp87 |
Thanks for opening your first issue here! We'll come back to you as soon as we can. |
Update: @am29d is working on migrating our internal Lambda Layers pipeline to CodePipeline in a Powertools AWS account. Once that's done (~H2), we should be able to expand to more AWS regions. You can follow progress here: github.com/orgs/awslabs/projects/51/views/11 |
We're almost there @rubenesp87 - we've just finished migrated Lambda Layer pipeline to GitHub Actions, and we're now going to test the rollout to all AWS regions. Once that's done, the only thing we'll need is automation to ensure Docs are always up to date with all version we're going to have. From there, we can expand additional Layers like ARM or Extra dependencies, etc. |
This is now released under 1.26.6 version! |
Is your feature request related to a problem?
There some missing regions on the public lambda layer, ie: me-south-1, ap-east-1, af-south-1, eu-south-1...
Describe the solution you'd like
Add the public lambda layer to the non-existing regions
Describe alternatives you've considered
Use SAR to deploy a CloudFormation stack with a copy of the Lambda Layer in all the regions, this is a bit tedious having multiple applications in multiple regions and working only in some regions.
Actual public layers

The text was updated successfully, but these errors were encountered: