Summary

Currently we are manually verifying the output of the SSM Parameters GitHub action that deploys the SSM Parameters. The validation steps are as follows:

Verify SSM Parameters (Beta): Use the AWS CLI to verify that the SSM parameters were updated correctly. Run the following command: aws ssm get-parameter --name=/aws/service/powertools/beta/typescript/generic/all/latest and aws ssm get-parameter --name=/aws/service/powertools/beta/typescript/generic/all/ to verify that the SSM parameters were updated correctly.

Verify SSM Parameters (Prod): Use the AWS CLI to verify that the SSM parameters were updated correctly. Run the following command: aws ssm get-parameter --name=/aws/service/powertools/typescript/generic/all/latest and aws ssm get-parameter --name=/aws/service/powertools/typescript/generic/all/ to verify that the SSM parameters were updated correctly.

We could automate this validation as part of the GitHub action and fail the action if the validation fails.

Why is this needed?

This will remove two manual steps from our release process

Which area does this relate to?

Automation

Solution

No response

Acknowledgment

• This request meets Powertools for AWS Lambda (TypeScript) Tenets
• Should this be considered in other Powertools for AWS Lambda languages? i.e. Python, Java, and .NET

Future readers

Please react with 👍 and your use case to help us understand customer demand.