FunctionPilot
A better AWS Lambda console in your own AWS account: every function with its numbers, shared tests, code, logs, costs and per-team access.
[ P ] LATEST POSTS
Giving your team access to Lambda without handing out the AWS console
Support engineers need logs, testers need to invoke, and very few people should edit code in production. Here is how to give each of them exactly that on Lambda, with every action traced back to a person in CloudTrail.
5 min read →
What watching your Lambda functions costs in CloudWatch, and how to keep it down
Metrics, Logs Insights, Live Tail and Cost Explorer all charge per call, so a dashboard that refreshes for every viewer can quietly cost more than the functions it watches. Here is what each call costs, the API limits that bite, and how FunctionPilot keeps viewing cheap.
4 min read →
Lambda test events your whole team can use, with assertions and history
The Lambda console keeps ten private test events per function, sharing them needs schema registry permissions, and no result is kept. Here is how FunctionPilot turns test events into shared, checked tests with every run on record.
4 min read →
Finding unused Lambda functions and deprecated runtimes across every account
The Lambda console can't tell you when a function was last called, and runtime deprecation notices only look at $LATEST. Here is how to find unused functions and old runtimes from metrics you already have, by script or in FunctionPilot.
4 min read →
FunctionPilot: a better AWS Lambda console that runs in your own AWS account
The Lambda console is good at one function in one Region. Teams with hundreds of functions across several accounts need more. FunctionPilot puts every function, its numbers, its tests, its code and its logs in one place, inside your own AWS account.
4 min read →