Lambda waste check
Lambda ARM64 Migration
lambda_arm64_migration
What it finds
Finds Lambda functions that could run on cheaper Arm processors with little or no change.
One of the Lambda checks, in the compute optimization group.
How it is detected
x86_64 function with ARM64-compatible runtime
Detection confidence: LOW. This is the criterion from our public docs. It runs in a local scan with your own read-only credentials.
- Signal
- ListFunctions architecture and runtime, with CloudWatch Invocations and Duration to size the compute
- Statistic
- Sum of Invocations and Average of Duration
- Window
- 30 days
- Monthly figure
- The function's monthly GB-seconds (memory times duration times invocations) priced at the x86_64 rate, minus the same GB-seconds at the lower arm64 rate. Functions below a small minimum monthly compute cost are skipped.
- How to fix
- Switch the function's architecture to arm64 with update-function-configuration after testing its dependencies on arm64.
- In the docs
- This check in the detector reference
AWS's own tools
None of Trusted Advisor, Cost Optimization Hub or Compute Optimizer flags this.
Checked against the AWS documentation.
Run it yourself
Nothing leaves your machine unless you choose to share a summary at the end.