KMS
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.
You can currently query the following attributes and connections on an AWS KMS
Get data for a single AWS KMS key that you know the ID or arn for:
Get data for all of the KMS keys in a certain AWS account:
Get data for all of the KMS keys that are NOT in a certain AWS account:
Get data for all of the KMS keys that have a connected cloudtrail:
Use multiple filter selectors, (i.e. has, and, not, or) to get data for all of the KMS keys that have cloudtrail instances AND lambda instances connected to them OR that do not have sns instances connected to them. Note that you can use has, and, not, or completely independently of each other:
You may also filter using a regex when filtering on a string field like, description if you want to look for a value that matches say, important:
You can order the results you get back either asc or desc depending on your preference:
Only select and return the first two KMS keys that are found:
Only select and return the first two KMS keys that are found, but offset by one so keys two & three are returned:
Count the number KMS keys across all scanned AWS accounts:
Count the number of KMS keys in a single account. Note that you can apply all of the same filters that are listed above to aggregate queries:
Find all of the KMS keys that are in the us-east-1 region across all your accounts:
Find all of the KMS keys that have a tag of Environment:Production for a single AWS Account:
With CloudGraph you can run multiple queries at the same time so you can combine the above two queries if you like:
Putting it all together; get all data for all KMS keys 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 keys but if you want to it's easy to go from say, kms -> lambda -> vpc ...etc:
