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 Transit Gateway Attachment
query{
queryawsTransitGatewayAttachment {
id
accountId
arn
region
transitGatewayId
transitGatewayOwnerId
resourceOwnerId
resourceType
resourceId
state
transitGatewayRouteTableId
creationTime
tags {
id
key
value
}
routeTable {
arn
}
transitGateway {
arn
}
vpc {
arn
}
vpnConnection {
arn
}
}
}
Get data for a single AWS Transit Gateway Attachment that you know the ID or arn for:
query {
getawsTransitGatewayAttachment(id: "12345") {
arn
}
}
query {
getawsTransitGatewayAttachment(arn: "arn:aws:ec2:us-east-1:111122223333:transit-gateway-attachment/tgw-attach-11122223333f466ec") {
arn
}
}
Get data for all of the Transit Gateway Attachments in a certain AWS account:
query {
queryawsTransitGatewayAttachment(filter: { accountId: { eq: "12345" } }) {
arn
}
}
Get data for all of the Transit Gateway Attachments that are NOT in a certain AWS account:
query {
queryawsTransitGatewayAttachment(filter: { not: { accountId: { eq: "12345" } } }) {
arn
}
}
Get data for all of the Transit Gateway Attachments that have a connected vpnConnection:
query {
queryawsTransitGatewayAttachment(filter: { has: vpnConnection }) {
arn
}
}
Use multiple filter selectors, (i.e. has, and, not, or) to get data for all of the Transit Gateway Attachments that have vpnConnection instances AND vpc instances connected to them OR that do not have routeTable instances connected to them. Note that you can use has, and, not, or completely independently of each other:
query {
queryawsTransitGatewayAttachment(
filter: {
has: vpnConnection
and: { has: vpc }
or: { not: { has: routeTable } }
}
) {
arn
}
}
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 Transit Gateway Attachments in us regions:
query {
queryawsTransitGatewayAttachment(filter: { region: { regexp: "/.*us-*/" } }) {
arn
}
}
You can order the results you get back either asc or desc depending on your preference:
query {
queryawsTransitGatewayAttachment(order: { desc: region }) {
arn
}
}
Only select and return the first two Transit Gateway Attachments that are found:
query {
queryawsTransitGatewayAttachment(first: 2, order: { desc: region }) {
arn
}
}
Only select and return the first two Transit Gateway Attachments that are found, but offset by one so Transit Gateway Attachments two & three are returned:
query {
queryawsTransitGatewayAttachment(first: 2, order: { desc: region }, offset: 1) {
arn
}
}
Count the number Transit Gateway Attachments across all scanned AWS accounts:
query {
aggregateawsTransitGatewayAttachment {
count
}
}
Count the number of Transit Gateway Attachments in a single account. Note that you can apply all of the same filters that are listed above to aggregate queries:
query {
aggregateawsTransitGatewayAttachment(filter: { accountId: { eq: "12345" } }) {
count
}
}
Find all of the Transit Gateway Attachments that are in the us-east-1 region across all your accounts:
query {
queryawsTransitGatewayAttachment(filter: { region: { eq: "us-east-1" } }) {
arn
}
}
Putting it all together; get all data for all Transit Gateway Attachments 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 transit gateway attachments but if you want to it's easy to go from say, transitGatewayAttachment -> transitGateway -> routeTable ...etc:
query{
queryawsTransitGatewayAttachment {
id
accountId
arn
region
transitGatewayId
transitGatewayOwnerId
resourceOwnerId
resourceType
resourceId
state
transitGatewayRouteTableId
creationTime
tags {
id
key
value
}
routeTable {
id
accountId
arn
region
vpcId
routes {
id
}
mainRouteTable
explicitlyAssociatedWithSubnets
explicitlyAssociatedWithSubnets
tags {
id
key
value
}
subnet {
arn
}
vpc {
arn
}
transitGateway {
arn
}
transitGatewayAttachment {
arn
}
}
transitGateway {
id
accountId
arn
region
ownerId
description
dnsSupport
vpnEcmpSupport
amazonSideAsn
autoAcceptSharedAttachments
defaultRouteTableAssociation
associationDefaultRouteTableId
defaultRouteTableAssociation
propagationDefaultRouteTableId
tags {
id
key
value
}
routeTable {
arn
}
transitGatewayAttachment {
arn
}
vpnConnection {
arn
}
}
vpc {
accountId
arn
defaultVpc
dhcpOptionsSet
enableDnsHostnames
enableDnsSupport
id
instanceTenancy
ipV4Cidr
ipV6Cidr
state
alb {
arn
}
eip {
arn
}
elb {
arn
}
igw {
arn
}
tags {
id
key
value
}
nacl {
arn
}
lambda {
arn
}
subnet {
arn
}
natGateway {
arn
}
routeTable {
arn
}
rdsDbInstance {
arn
}
route53HostedZone {
arn
}
}
vpnConnection {
id
accountId
arn
region
category
customerGatewayId
state
type
vpnGatewayId
transitGatewayId
options {
id
enableAcceleration
staticRoutesOnly
localIpv4NetworkCidr
remoteIpv4NetworkCidr
tunnelInsideIpVersion
type
tunnelOptions {
id
outsideIpAddress
tunnelInsideCidr
preSharedKey
}
}
routes {
id
destinationCidrBlock
source
state
}
vgwTelemetry {
id
acceptedRouteCount
lastStatusChange
certificateArn
outsideIpAddress
status
statusMessage
}
tags {
id
key
value
}
transitGateway {
arn
}
customerGateway {
arn
}
vpnGateway {
arn
}
transitGatewayAttachment {
arn
}
}
}
}
