Skip to content

Bug: x86_64 Lambda layers uses the wrong name #5227

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

Closed
sthulb opened this issue Sep 24, 2024 · 3 comments · Fixed by #5226
Closed

Bug: x86_64 Lambda layers uses the wrong name #5227

sthulb opened this issue Sep 24, 2024 · 3 comments · Fixed by #5226
Assignees
Labels
bug Something isn't working layers Lambda Layers work

Comments

@sthulb
Copy link
Contributor

sthulb commented Sep 24, 2024

Expected Behaviour

AWS Lambda layers for the x86_64 architecture are currently mislabeled as "x86". This naming inconsistency may lead to confusion and potential compatibility issues. We need to update our layer naming convention to accurately reflect the x86_64 architecture.

Current Behaviour

Layers are marked as "x86" using the following ARN:

arn:aws:lambda:{region}:017000801446:layer:AWSLambdaPowertoolsPythonV3-{python_version}-x86:1

Code snippet

N/A

Possible Solution

Rename layers to arn:aws:lambda:{region}:017000801446:layer:AWSLambdaPowertoolsPythonV3-{python_version}-x86_64:1. This forces the deployment of this new x86_64 layer name that exists in version 1 as x86.

Steps to Reproduce

Read the docs

Powertools for AWS Lambda (Python) version

latest

AWS Lambda function runtime

3.8

Packaging format used

Lambda Layers

Debugging logs

No response

@leandrodamascena
Copy link
Contributor

Thanks for opening this issue @sthulb.

@leandrodamascena leandrodamascena moved this from Triage to Working on it in Powertools for AWS Lambda (Python) Sep 24, 2024
@leandrodamascena leandrodamascena added layers Lambda Layers work and removed triage Pending triage from maintainers labels Sep 24, 2024
@leandrodamascena leandrodamascena changed the title Bug: x86_64 layer uses the wrong name Bug: x86_64 Lambda layers uses the wrong name Sep 30, 2024
@github-project-automation github-project-automation bot moved this from Working on it to Coming soon in Powertools for AWS Lambda (Python) Oct 1, 2024
Copy link
Contributor

github-actions bot commented Oct 1, 2024

⚠️COMMENT VISIBILITY WARNING⚠️

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.

@github-actions github-actions bot added the pending-release Fix or implementation already in dev waiting to be released label Oct 1, 2024
This was referenced Oct 1, 2024
Copy link
Contributor

github-actions bot commented Oct 8, 2024

This is now released under 3.1.0 version!

@github-actions github-actions bot removed the pending-release Fix or implementation already in dev waiting to be released label Oct 8, 2024
@leandrodamascena leandrodamascena moved this from Coming soon to Shipped in Powertools for AWS Lambda (Python) Jan 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working layers Lambda Layers work
Projects
Status: Shipped
Development

Successfully merging a pull request may close this issue.

2 participants