NAT Gateway
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 NAT Gateway
Get data for a single AWS NAT Gateway that you know the ID or arn for:
Get data for all of the NAT Gateways in a certain AWS account:
Get data for all of the NAT Gateways that are NOT in a certain AWS account:
Get data for all of the NAT Gateways that have a connected subnet:
Use multiple filter selectors, (i.e. has, and, not, or) to get data for all of the NAT Gateways that have subnet instances AND vpc instances connected to them OR that do not have networkInterface 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, region if you want to look for a value that matches say, us- to get all NAT Gateways in us regions:
You can order the results you get back either asc or desc depending on your preference:
Only select and return the first two NAT Gateways that are found:
Only select and return the first two NAT Gateways that are found, but offset by one so gateways two & three are returned:
Count the number NAT Gateways across all scanned AWS accounts:
Count the number of NAT Gateways 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 NAT Gateways that are in the us-east-1 region across all your accounts:
Putting it all together; get all data for all NAT Gateways 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 gateways but if you want to it's easy to go from say, gateway -> vpc -> routeTable ...etc:
