AWS CLI Tips for Working with Lambda

Sometimes you need to confirm that a Lambda function was updated after your CI/CD pipeline ran, or simply verify that the function exists with the correct name and configuration.

Logging into the AWS Management Console, completing two-factor authentication, and scrolling through a long list of functions can be slow and tedious. Instead, use the AWS CLI to pull the same information straight from your terminal.

1. Choose exactly which fields to display

The option lets you select and format the data you care about. Separate multiple fields with a comma inside square brackets:

2. Handle large fleets with pagination

If your account hosts many Lambdas, add --max-items to control page size and let the CLI fetch results in manageable chunks:

3. Filter by part of the function name

You can also use a JMESPath filter inside to find functions whose names contain a specific substring:

This returns only the Lambdas whose names include pricing, along with their last-modified timestamps—a quick way to verify that the correct deployments have reached production.