website logo
HomeGithubSlack
⌘K
Overview
Quick Start
Supported Services
Running CloudGraph in EKS
Compliance
Rules Engine
AWS
Querying AWS Data
AWS Policy Packs
Billing Data
Services
Azure
Querying Azure Data
Azure Policy Packs
Services
GCP
Querying GCP Data
GCP Policy Packs
Services
K8s
Querying Kubernetes Data
Services
Docs powered by archbee 

Lambda

19min

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
|
query {
  queryawsLambda {
    id
    accountId
    arn
    description
    handler
    kmsKeyArn
    lastModified
    memorySize
    reservedConcurrentExecutions
    role
    runtime
    sourceCodeSize
    timeout
    tracingConfig
    version
    environmentVariables {
      id
      key
      value
    }
    tags {
      id
      key
      value
    }
    kms {
      arn
      # Other fields and connections here...
    }
    securityGroups {
      arn
      # Other fields and connections here...
    }
    subnet {
      arn
      # Other fields and connections here...
    }
    vpc {
      arn
      # Other fields and connections here...
    }
    cognitoUserPool {
      arn
      # Other fields and connections here...
    }
  }
}


Filtering

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

GraphQL
|
query {
  getawsLambda(arn: "12345") {
    arn
    # Other fields and connections here...
  }
}


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

GraphQL
|
query {
  queryawsLambda(filter: { accountId: { eq: "12345" } }) {
    arn
    # Other fields and connections here...
  }
}

# Note that in addition to "accountId" you can
# Filter based on any of the following attributes:

# id
# accountId
# arn
# description // can use fulltext filters
# handler
# kmsKeyArn
# lastModified
# memorySize
# reservedConcurrentExecutions
# role
# runtime
# sourceCodeSize
# timeout
# tracingConfig
# version

# And the following Dgraph filters can also be applied:

# has
# and
# or
# not
# regexp (regular expressions)

# fulltext filters

# alloftext
# anyoftext


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

GraphQL
|
query {
  queryawsLambda(filter: { not: { accountId: { eq: "12345" } } }) {
    arn
    # Other fields and connections here...
  }
}


Advanced Filtering

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

GraphQL
|
query {
  queryawsLambda(filter: { has: cognitoUserPool }) {
    arn
    # Other fields and connections here...
  }
}

# Note that in addition to "cognitoUserPool" you can filter
# Using "has" based on any of the following attributes:

# id
# accountId
# arn
# description
# handler
# kmsKeyArn
# lastModified
# memorySize
# reservedConcurrentExecutions
# role
# runtime
# sourceCodeSize
# timeout
# tracingConfig
# version
# environmentVariables
# tags
# kms
# securityGroups
# subnet
# vpc


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
|
query {
  queryawsLambda(
    filter: {
      has: cognitoUserPool
      and: { has: tags }
      or: { not: { has: vpc } }
    }
  ) {
    arn
    # Other fields and connections here...
  }
}


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
|
query {
  queryawsLambda(filter: { runtime: { regexp: "/.*nodejs12.x.*/" } }) {
    arn
    # Other fields and connections here...
  }
}


Ordering

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

GraphQL
|
query {
  queryawsLambda(order: { desc: runtime }) {
    runtime
    # Other fields and connections here...
  }
}

# Note that in addition to "runtime" you can filter
# Using "asc" or "desc" based on any of the following attributes:

# id
# accountId
# arn
# description
# handler
# kmsKeyArn
# lastModified
# memorySize
# reservedConcurrentExecutions
# role
# sourceCodeSize
# timeout
# tracingConfig
# version


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

GraphQL
|
query {
  queryawsLambda(first: 2, order: { desc: runtime }) {
    runtime
    # Other fields and connections here...
  }
}


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

GraphQL
|
query {
  queryawsLambda(first: 2, order: { desc: runtime }, offset: 1) {
    arn
    # Other fields and connections here...
  }
}


Aggregation

Count the number of Lambdas across all scanned AWS accounts:

GraphQL
|
query {
  aggregateawsLambda {
    count
    # Other fields and connections here...
  }
}

# Note that in addition to "count" you can request the
# Following min and max values based on attributes of your Lambdas:

# idMin
# idMax
# accountIdMin
# accountIdMax
# arnMin
# arnMax
# descriptionMin
# descriptionMax
# handlerMin
# handlerMax
# kmsKeyArnMin
# kmsKeyArnMax
# lastModifiedMin
# lastModifiedMax
# memorySizeMin
# memorySizeMax
# memorySizeSum
# memorySizeAvg
# reservedConcurrentExecutionsMin
# reservedConcurrentExecutionsMax
# reservedConcurrentExecutionsSum
# reservedConcurrentExecutionsAvg
# roleMin
# roleMax
# runtimeMin
# runtimeMax
# sourceCodeSizeMin
# sourceCodeSizeMax
# timeoutMin
# timeoutMax
# timeoutSum
# timeoutAvg
# tracingConfigMin
# tracingConfigMax
# versionMin
# versionMax


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
|
query {
  aggregateawsLambda(filter: { accountId: { eq: "12345" } }) {
    count
    # Other fields and connections here...
  }
}


Examples

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

GraphQL
|
query {
  queryawsLambda(
    filter: {
      runtime: { regexp: "/.*nodejs12.*/" }
      or: { runtime: { regexp: "/.*nodejs14.*/" } }
    }
  ) {
    arn
    runtime
    # Other fields and connections here...
  }
}


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

GraphQL
|
query {
  queryawsTag(
    filter: { key: { eq: "Environment" }, value: { eq: "Production" } }
  ) {
    lambda(filter: { accountId: { eq: "12345" } }) {
      arn
      # Other fields and connections here...
    }
  }
}


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

GraphQL
|
query {
  queryawsLambda(
    filter: {
      runtime: { regexp: "/.*nodejs12.*/" }
      or: { runtime: { regexp: "/.*nodejs14.*/" } }
    }
  ) {
    arn
    runtime
    # Other fields and connections here...
  }
  queryawsTag(
    filter: { key: { eq: "Environment" }, value: { eq: "Production" } }
  ) {
    lambda(filter: { accountId: { eq: "12345" } }) {
      arn
      # Other fields and connections here...
    }
  }
}


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
|
query {
  queryawsVpc(filter: { arn: { eq: "arn:12345" } }) {
    arn
    lambda {
      arn
    }
  }
  queryawsLambda {
    arn
  }
}

# To be fair you could just query lambda directly and
# See which functions don't return the `ARN` of a VPC:

# query {
#   queryawsLambda {
#     arn
#     vpc {
#       arn
#     }
#   }
# }


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
|
query {
  queryawsLambda {
    id
    accountId
    arn
    description
    handler
    kmsKeyArn
    lastModified
    memorySize
    reservedConcurrentExecutions
    role
    runtime
    sourceCodeSize
    timeout
    tracingConfig
    version
    environmentVariables {
      id
      key
      value
    }
    tags {
      id
      key
      value
    }
    kms {
      accountId
      arn
      id
      description
      keyRotationEnabled
      usage
      policy {
        id
        # Other fields and connections here...
      }
      enabled
      keyState
      customerMasterKeySpec
      tags {
        id
        key
        value
      }
      creationDate
      keyManager
      origin
      deletionDate
      validTo
      lambda {
        arn
        # Other fields and connections here...
      }
      cloudtrail {
        arn
        # Other fields and connections here...
      }
    }
    securityGroups {
      id
      accountId
      arn
      name
      vpcId
      description
      tags {
        id
        key
        value
      }
      owner
      default
      inboundRules {
        id
        # Other fields and connections here...
      }
      outboundRules {
        id
        # Other fields and connections here...
      }
      inboundRuleCount
      outboundRuleCount
      alb {
        arn
        # Other fields and connections here...
      }
      lambda {
        arn
        # Other fields and connections here...
      }
      elb {
        arn
        # Other fields and connections here...
      }
      ec2Instance {
        arn
        # Other fields and connections here...
      }
      asg {
        arn
        # Other fields and connections here...
      }
      rdsCluster {
        arn
        # Other fields and connections here...
      }
      rdsDbInstance {
        arn
        # Other fields and connections here...
      }
    }
    subnet {
      id
      accountId
      arn
      autoAssignPublicIpv4Address
      autoAssignPublicIpv6Address
      availabilityZone
      availableIpV4Addresses
      defaultForAz
      ipV4Cidr
      ipV6Cidr
      state
      tags {
        id
        key
        value
      }
      alb {
        arn
        # Other fields and connections here...
      }
      asg {
        arn
        # Other fields and connections here...
      }
      ec2Instance {
        arn
        # Other fields and connections here...
      }
      elb {
        arn
        # Other fields and connections here...
      }
      lambda {
        arn
        # Other fields and connections here...
      }
      natGateway {
        arn
        # Other fields and connections here...
      }
      networkInterface {
        arn
        # Other fields and connections here...
      }
      routeTable {
        arn
        # Other fields and connections here...
      }
      vpc {
        arn
        # Other fields and connections here...
      }
      rdsDbInstance {
        arn
        # Other fields and connections here...
      }
    }
    vpc {
      accountId
      arn
      defaultVpc
      dhcpOptionsSet
      enableDnsHostnames
      enableDnsSupport
      id
      instanceTenancy
      ipV4Cidr
      ipV6Cidr
      state
      alb {
        arn
        # Other fields and connections here...
      }
      eip {
        arn
        # Other fields and connections here...
      }
      elb {
        arn
        # Other fields and connections here...
      }
      igw {
        arn
        # Other fields and connections here...
      }
      tags {
        id
        key
        value
      }
      nacl {
        arn
        # Other fields and connections here...
      }
      lambda {
        arn
        # Other fields and connections here...
      }
      subnet {
        arn
        # Other fields and connections here...
      }
      natGateway {
        arn
        # Other fields and connections here...
      }
      routeTable {
        arn
        # Other fields and connections here...
      }
      rdsDbInstance {
        # Other fields and connections here...
        arn
      }
      route53HostedZone {
        # Other fields and connections here...
        arn
      }
    }
    cognitoUserPool {
      id
      accountId
      arn
      name
      policies {
        id
        # Other fields and connections here...
      }
      lambdaConfig {
        id
        # Other fields and connections here...
      }
      status
      lastModifiedDate
      creationDate
      schemaAttributes {
        id
        # Other fields and connections here...
      }
      autoVerifiedAttributes
      aliasAttributes
      usernameAttributes
      smsVerificationMessage
      emailVerificationMessage
      emailVerificationSubject
      verificationMessageTemplateSmsMessage
      verificationMessageTemplateEmailMessage
      verificationMessageTemplateEmailSubject
      verificationMessageTemplateEmailMessageByLink
      verificationMessageTemplateEmailSubjectByLink
      verificationMessageTemplateDefaultEmailOption
      smsAuthenticationMessage
      mfaConfiguration
      deviceConfigChallengeRequiredOnNewDevice
      deviceConfigDeviceOnlyRememberedOnUserPrompt
      estimatedNumberOfUsers
      emailConfigSourceArn
      emailConfigReplyToEmailAddress
      emailConfigEmailSendingAccount
      emailConfigFrom
      emailConfigConfigurationSet
      smsConfigurationSnsCallerArn
      smsConfigurationExternalId
      smsConfigurationFailure
      emailConfigurationFailure
      domain
      customDomain
      adminCreateUserConfigAllowAdminCreateUserOnly
      adminCreateUserConfigUnusedAccountValidityDays
      adminCreateUserConfigInviteMessageTemplateSMSMessage
      adminCreateUserConfigInviteMessageTemplateEmailMessage
      adminCreateUserConfigInviteMessageTemplateEmailSubject
      userPoolAddOnsAdvancedSecurityMode
      usernameConfigurationCaseSensitive
      accountRecoverySettings {
        id
        # Other fields and connections here...
      }
      region
      tags {
        id
        key
        value
      }
      lambda {
        arn
        # Other fields and connections here...
      }
    }
  }
}


References

Dgraph documentation on querying

AWS Lambda documentation

Updated 03 Mar 2023
Did this page help you?
Yes
No
PREVIOUS
KMS
NEXT
NAT Gateway
Docs powered by archbee 
TABLE OF CONTENTS
Overview
Filtering
Advanced Filtering
Ordering
Aggregation
Examples
Kitchen Sink
References