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

Feature request: Lambda Layer support for new regions eu-central-2 & eu-south-2 #1169

Closed
2 tasks done
dreamorosi opened this issue Nov 16, 2022 · 6 comments · Fixed by #1322 or #1327
Closed
2 tasks done

Feature request: Lambda Layer support for new regions eu-central-2 & eu-south-2 #1169

dreamorosi opened this issue Nov 16, 2022 · 6 comments · Fixed by #1322 or #1327
Assignees
Labels
automation This item relates to automation completed This item is complete and has been merged/shipped feature-request This item refers to a feature request for an existing or new utility
Milestone

Comments

@dreamorosi
Copy link
Contributor

Use case

Over the past days AWS has launched two new regions: eu-central-2 (link) and eu-south-2 (link).

Both regions are opt-in but they both launched with AWS Lambda support, which means Layers should be available.

Solution/User Experience

Over the next releases we should make an effort to publish Powertools Layers in those new regions similar to what we do currently in all other commercial ones.

Before start working on this, we should agree on the version strategy. For example, Powertools for Python keeps versions aligned also on newer regions, they have developed a script that does that automatically and that we could leverage.

Alternative solutions

No response

Acknowledgment

@dreamorosi dreamorosi added the triage This item has not been triaged by a maintainer, please wait label Nov 16, 2022
@dreamorosi dreamorosi added this to the Lambda layer milestone Nov 16, 2022
@dreamorosi dreamorosi added feature-request This item refers to a feature request for an existing or new utility discussing The issue needs to be discussed, elaborated, or refined automation This item relates to automation and removed triage This item has not been triaged by a maintainer, please wait labels Nov 16, 2022
@caioquirino
Copy link

Hi @dreamorosi, how do you generate the layers listed in https://github.com/awslabs/aws-lambda-powertools-typescript/blob/main/docs/index.md ?

I see they are all pointed to arn:aws:lambda::094274105915:layer:AWSLambdaPowertoolsTypeScript:6, so I am interested in knowing how the version (last token) is published, if it's possible to extract for example from github actions.

Thanks!

@dreamorosi
Copy link
Contributor Author

Hi @caioquirino the layers are published with this workflows, which uses a CDK app to do the job.

However at the moment the we manually update the version number in the docs after each release. We have an open issue to automate this (#1124) but we haven't gotten around implementing it yet.

From your question I'm assuming you'd like to get the latest version available in a programmatic way, is that the case? I would love to hear more about your use case/need and see if there's something that we can do to help you onboard the layers.

@dreamorosi
Copy link
Contributor Author

@am29d offered to tackle this one.

As part of this item we should include also:

  • any other region that was launched since the issue creation (i.e. ap-southeast-4)
  • making sure the the layer version in the new regions is aligned with the existing ones

@dreamorosi dreamorosi added confirmed The scope is clear, ready for implementation and removed discussing The issue needs to be discussed, elaborated, or refined labels Feb 17, 2023
@dreamorosi dreamorosi linked a pull request Feb 22, 2023 that will close this issue
13 tasks
@github-actions
Copy link
Contributor

⚠️ 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.

@github-actions github-actions bot added the pending-release This item has been merged and will be released soon label Feb 23, 2023
@dreamorosi
Copy link
Contributor Author

The workflow that we merged has a missing comma here.

I missed this during the review and got notified only when merging.

@dreamorosi dreamorosi reopened this Feb 23, 2023
@dreamorosi dreamorosi removed the pending-release This item has been merged and will be released soon label Feb 23, 2023
@github-actions github-actions bot added the pending-release This item has been merged and will be released soon label Feb 23, 2023
@dreamorosi dreamorosi linked a pull request Feb 23, 2023 that will close this issue
13 tasks
@github-actions
Copy link
Contributor

⚠️ 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.

@dreamorosi dreamorosi added completed This item is complete and has been merged/shipped and removed pending-release This item has been merged and will be released soon confirmed The scope is clear, ready for implementation labels Feb 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automation This item relates to automation completed This item is complete and has been merged/shipped feature-request This item refers to a feature request for an existing or new utility
Projects
None yet
3 participants