20min

Lambda

Note: if you are running CloudGraph locally you can view the interactive, automatically generated documentation in either GraphQL Playground or Altair by clicking the docs button on the right-hand side of the screen. After reading the below information we highly suggest you use one of these tools to test your queries as they will autocomplete fields for you and let you know if your queries are valid before you even submit them.

Overview

You can currently query the following attributes and connections on an AWS Lambda:

GraphQL
|

Filtering

Get data for a single AWS Lambda that you know the ARN for:

GraphQL
|

Get data for all of the Lambdas in a certain AWS account:

GraphQL
|

Get data for all of the Lambdas that are NOT in a certain AWS account:

GraphQL
|

Advanced Filtering

Get data for all of the Lambda triggers for Cognito Userpools:

GraphQL
|

Use multiple filter selectors, (i.e. has, and, not, or) to get data for all of the Lambdas that have Cognito Userpools AND Tags OR that don't leverage VPC Networking Note that you can use has, and, not, or completely independently of each other:

GraphQL
|

You may also filter using a regex when filtering on a string field like, runtime if you want to look for a value that matches say, nodejs12.x:

GraphQL
|

Ordering

You can order the results you get back either asc or desc depending on your preference:

GraphQL
|

Only select and return the first two Lambdas that are found:

GraphQL
|

Only select and return the first two Lambdas that are found, but offset by one so Lambdas two & three are returned:

GraphQL
|

Aggregation

Count the number of Lambdas across all scanned AWS accounts:

GraphQL
|

Count the number of Lambdas in a single account. Note that you can apply all of the same filters that are listed above to aggregate queries:

GraphQL
|

Examples

Find all of the Lambdas that are using node 12 or node 14 as a runtime:

GraphQL
|

Find all of the Lambdas that have a tag of Environment:Production for a single AWS Account:

GraphQL
|

With CloudGraph you can run multiple queries at the same time so you can combine the above two queries if you like:

GraphQL
|

When you think, "in terms of a graph", you can do almost anything with CloudGraph. Say for example that you want to know what Lamba functions don't belong to a VPC (i.e. they don't leverage VPC networking). Because CloudGraph connects all resources that have relationships, such as VPC parents to their Lambda children, you are able to answer this question easily. Simply check to see what lambda functions the VPC is "connected" to, and compare that against the list of all lambda functions like so:

GraphQL
|

Kitchen Sink

Putting it all together; get all data for all Lambdas across all regions for all scanned AWS accounts in a single query. For the purposes of this example we will only get direct children of the Lambdas but if you want to it's easy to go from say, Lambda -> Subnet -> VPC...etc:

GraphQL
|

References



Updated 04 Mar 2022
Did this page help?
Yes
No