Expected Behaviour

According to the Lambda Layer documentation, the SSM parameter path format is:

/aws/service/powertools/python/{arch}/{python_version}/{version}
Where {version} is "the semantic version number (e.g. 3.1.0) for a release or latest"

For version 3.23.0 (published to PyPI on Nov 13), the following SSM parameter should exist:
/aws/service/powertools/python/x86_64/python3.13/3.23.0

This follows the pattern of all previous releases (3.22.1, 3.22.0, 3.21.0, etc.).

Current Behaviour

The SSM parameter /aws/service/powertools/python/x86_64/python3.13/3.23.0 returns ParameterNotFound.

However:

• ✓ Package exists on PyPI: 3.23.0
• ✓ Lambda layer exists: arn:aws:lambda:us-east-1:017000801446:layer:AWSLambdaPowertoolsPythonV3-python313-x86_64:27 (created Nov 13, 17:32 UTC)
• ✓ SSM parameter /aws/service/powertools/python/x86_64/python3.13/latest correctly points to layer version 27

Impact:

Users pinning to specific versions in CloudFormation (using {{resolve:ssm:/aws/service/powertools/python/x86_64/python3.13/3.23.0}}) cannot upgrade until this parameter is created.

Code snippet

N/A

Possible Solution

Add parameter.

Steps to Reproduce

Verify previous version parameter exists:

aws ssm get-parameter \
  --name /aws/service/powertools/python/x86_64/python3.13/3.22.1 \
  --region us-east-1

Result: Returns layer ARN ✓

Check for 3.23.0 parameter:

aws ssm get-parameter \
  --name /aws/service/powertools/python/x86_64/python3.13/3.23.0 \
  --region us-east-1

Result: ParameterNotFound ✗

Verify layer exists:

  --layer-name arn:aws:lambda:us-east-1:017000801446:layer:AWSLambdaPowertoolsPythonV3-python313-x86_64 \
  --version-number 27 \
  --region us-east-1

Result: Returns "version 3.23.0" ✓

Powertools for AWS Lambda (Python) version

latest

AWS Lambda function runtime

3.9

Packaging format used

Lambda Layers

Debugging logs