Tracking and Managing deployed lambda packages on S3 backup
- Dominant language
- Python
- Stars
- 6.7k
- Forks
- 1.2k
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 52
Description
Hi there,
Summary
Is there a way to 'manage' deployed layer/function packages in S3 that have been deployed via SAM?
By manage: a) view which packages are 'stale' (new versions have been deployed and the old ones are now orphaned) b) in SAM CLI, and/or AWS CLI and/or AWS UI view for a particular lambda or layer which S3 package it is using?
When using SAM, my S3 bucket is filling up with deployment packages, and I'm not sure to see which ones are safe to delete (they are orphaned) and which ones are current?
Background
I've been using SAM for a few months now to develop some lambda deployments of an existing python function, which is working fairly well.
Due to my function design (which has a single lambda spawn multiple child lambda to wait for responses, all coupled with a custom layer), plus likely my newbie'nish with SAM and AWS in general, I've been doing a lot of the dev work directly on AWS, as I can't seem to get it to run locally via SAM.
The result is my S3 bucket I'm using for the deployment packages now has many, many packages placed there by sam deploy, but never purged.
I'd like to be able to remove orphaned packages from older deploy's.
thanks,
Richard
Contributor guide
Assessment
This issue has not been assessed yet.