aws-network-manager

name	aws-network-manager
description	AWS Network Manager API skill. Use when working with AWS Network Manager for attachments, global-networks, connect-attachments. Covers 85 endpoints.
version	1.0.0
generator	lapsh

AWS Network Manager

API version: 2019-07-05

Auth

AWS SigV4

Base URL

Not specified.

Setup

1. Configure auth: AWS SigV4
2. GET /global-networks -- verify access
3. POST /attachments/{attachmentId}/accept -- create first accept

Endpoints

85 endpoints across 13 groups. See references/api-spec.lap for full details.

attachments

Method	Path	Description
POST	/attachments/{attachmentId}/accept	Accepts a core network attachment request. Once the attachment request is accepted by a core network owner, the attachment is created and connected to a core network.
DELETE	/attachments/{attachmentId}	Deletes an attachment. Supports all attachment types.
GET	/attachments	Returns a list of core network attachments.
POST	/attachments/{attachmentId}/reject	Rejects a core network attachment request.

global-networks

Method	Path	Description
POST	/global-networks/{globalNetworkId}/connect-peer-associations	Associates a core network Connect peer with a device and optionally, with a link. If you specify a link, it must be associated with the specified device. You can only associate core network Connect peers that have been created on a core network Connect attachment on a core network.
POST	/global-networks/{globalNetworkId}/customer-gateway-associations	Associates a customer gateway with a device and optionally, with a link. If you specify a link, it must be associated with the specified device. You can only associate customer gateways that are connected to a VPN attachment on a transit gateway or core network registered in your global network. When you register a transit gateway or core network, customer gateways that are connected to the transit gateway are automatically included in the global network. To list customer gateways that are connected to a transit gateway, use the DescribeVpnConnections EC2 API and filter by transit-gateway-id. You cannot associate a customer gateway with more than one device and link.
POST	/global-networks/{globalNetworkId}/link-associations	Associates a link to a device. A device can be associated to multiple links and a link can be associated to multiple devices. The device and link must be in the same global network and the same site.
POST	/global-networks/{globalNetworkId}/transit-gateway-connect-peer-associations	Associates a transit gateway Connect peer with a device, and optionally, with a link. If you specify a link, it must be associated with the specified device. You can only associate transit gateway Connect peers that have been created on a transit gateway that's registered in your global network. You cannot associate a transit gateway Connect peer with more than one device and link.
POST	/global-networks/{globalNetworkId}/connections	Creates a connection between two devices. The devices can be a physical or virtual appliance that connects to a third-party appliance in a VPC, or a physical appliance that connects to another physical appliance in an on-premises network.
POST	/global-networks/{globalNetworkId}/devices	Creates a new device in a global network. If you specify both a site ID and a location, the location of the site is used for visualization in the Network Manager console.
POST	/global-networks	Creates a new, empty global network.
POST	/global-networks/{globalNetworkId}/links	Creates a new link for a specified site.

connect-attachments

Method	Path	Description
POST	/connect-attachments	Creates a core network Connect attachment from a specified core network attachment. A core network Connect attachment is a GRE-based tunnel attachment that you can use to establish a connection between a core network and an appliance. A core network Connect attachment uses an existing VPC attachment as the underlying transport mechanism.
GET	/connect-attachments/{attachmentId}	Returns information about a core network Connect attachment.

connect-peers

Method	Path	Description
POST	/connect-peers	Creates a core network Connect peer for a specified core network connect attachment between a core network and an appliance. The peer address and transit gateway address must be the same IP address family (IPv4 or IPv6).
DELETE	/connect-peers/{connectPeerId}	Deletes a Connect peer.
GET	/connect-peers/{connectPeerId}	Returns information about a core network Connect peer.
GET	/connect-peers	Returns a list of core network Connect peers.

core-networks

Method	Path	Description
POST	/core-networks	Creates a core network as part of your global network, and optionally, with a core network policy.
DELETE	/core-networks/{coreNetworkId}	Deletes a core network along with all core network policies. This can only be done if there are no attachments on a core network.
DELETE	/core-networks/{coreNetworkId}/core-network-policy-versions/{policyVersionId}	Deletes a policy version from a core network. You can't delete the current LIVE policy.
POST	/core-networks/{coreNetworkId}/core-network-change-sets/{policyVersionId}/execute	Executes a change set on your core network. Deploys changes globally based on the policy submitted..
GET	/core-networks/{coreNetworkId}	Returns information about the LIVE policy for a core network.
GET	/core-networks/{coreNetworkId}/core-network-change-events/{policyVersionId}	Returns information about a core network change event.
GET	/core-networks/{coreNetworkId}/core-network-change-sets/{policyVersionId}	Returns a change set between the LIVE core network policy and a submitted policy.
GET	/core-networks/{coreNetworkId}/core-network-policy	Returns details about a core network policy. You can get details about your current live policy or any previous policy version.
GET	/core-networks/{coreNetworkId}/core-network-policy-versions	Returns a list of core network policy versions.
GET	/core-networks	Returns a list of owned and shared core networks.
POST	/core-networks/{coreNetworkId}/core-network-policy	Creates a new, immutable version of a core network policy. A subsequent change set is created showing the differences between the LIVE policy and the submitted policy.
POST	/core-networks/{coreNetworkId}/core-network-policy-versions/{policyVersionId}/restore	Restores a previous policy version as a new, immutable version of a core network policy. A subsequent change set is created showing the differences between the LIVE policy and restored policy.
PATCH	/core-networks/{coreNetworkId}	Updates the description of a core network.

site-to-site-vpn-attachments

Method	Path	Description
POST	/site-to-site-vpn-attachments	Creates an Amazon Web Services site-to-site VPN attachment on an edge location of a core network.
GET	/site-to-site-vpn-attachments/{attachmentId}	Returns information about a site-to-site VPN attachment.

transit-gateway-peerings

Method	Path	Description
POST	/transit-gateway-peerings	Creates a transit gateway peering connection.
GET	/transit-gateway-peerings/{peeringId}	Returns information about a transit gateway peer.

transit-gateway-route-table-attachments

Method	Path	Description
POST	/transit-gateway-route-table-attachments	Creates a transit gateway route table attachment.
GET	/transit-gateway-route-table-attachments/{attachmentId}	Returns information about a transit gateway route table attachment.

vpc-attachments

Method	Path	Description
POST	/vpc-attachments	Creates a VPC attachment on an edge location of a core network.
GET	/vpc-attachments/{attachmentId}	Returns information about a VPC attachment.
PATCH	/vpc-attachments/{attachmentId}	Updates a VPC attachment.

peerings

Method	Path	Description
DELETE	/peerings/{peeringId}	Deletes an existing peering connection.
GET	/peerings	Lists the peerings for a core network.

resource-policy

Method	Path	Description
DELETE	/resource-policy/{resourceArn}	Deletes a resource policy for the specified resource. This revokes the access of the principals specified in the resource policy.
GET	/resource-policy/{resourceArn}	Returns information about a resource policy.
POST	/resource-policy/{resourceArn}	Creates or updates a resource policy.

organizations

Method	Path	Description
GET	/organizations/service-access	Gets the status of the Service Linked Role (SLR) deployment for the accounts in a given Amazon Web Services Organization.
POST	/organizations/service-access	Enables the Network Manager service for an Amazon Web Services Organization. This can only be called by a management account within the organization.

tags

Method	Path	Description
GET	/tags/{resourceArn}	Lists the tags for a specified resource.
POST	/tags/{resourceArn}	Tags a specified resource.
DELETE	/tags/{resourceArn}	Removes tags from a specified resource.

Common Questions

Match user requests to endpoints in references/api-spec.lap. Key patterns:

• "Create a accept?" -> POST /attachments/{attachmentId}/accept
• "Create a connect-peer-association?" -> POST /global-networks/{globalNetworkId}/connect-peer-associations
• "Create a customer-gateway-association?" -> POST /global-networks/{globalNetworkId}/customer-gateway-associations
• "Create a link-association?" -> POST /global-networks/{globalNetworkId}/link-associations
• "Create a transit-gateway-connect-peer-association?" -> POST /global-networks/{globalNetworkId}/transit-gateway-connect-peer-associations
• "Create a connect-attachment?" -> POST /connect-attachments
• "Create a connect-peer?" -> POST /connect-peers
• "Create a connection?" -> POST /global-networks/{globalNetworkId}/connections
• "Create a core-network?" -> POST /core-networks
• "Create a device?" -> POST /global-networks/{globalNetworkId}/devices
• "Create a global-network?" -> POST /global-networks
• "Create a link?" -> POST /global-networks/{globalNetworkId}/links
• "Create a site?" -> POST /global-networks/{globalNetworkId}/sites
• "Create a site-to-site-vpn-attachment?" -> POST /site-to-site-vpn-attachments
• "Create a transit-gateway-peering?" -> POST /transit-gateway-peerings
• "Create a transit-gateway-route-table-attachment?" -> POST /transit-gateway-route-table-attachments
• "Create a vpc-attachment?" -> POST /vpc-attachments
• "Delete a attachment?" -> DELETE /attachments/{attachmentId}
• "Delete a connect-peer?" -> DELETE /connect-peers/{connectPeerId}
• "Delete a connection?" -> DELETE /global-networks/{globalNetworkId}/connections/{connectionId}
• "Delete a core-network?" -> DELETE /core-networks/{coreNetworkId}
• "Delete a core-network-policy-version?" -> DELETE /core-networks/{coreNetworkId}/core-network-policy-versions/{policyVersionId}
• "Delete a device?" -> DELETE /global-networks/{globalNetworkId}/devices/{deviceId}
• "Delete a global-network?" -> DELETE /global-networks/{globalNetworkId}
• "Delete a link?" -> DELETE /global-networks/{globalNetworkId}/links/{linkId}
• "Delete a peering?" -> DELETE /peerings/{peeringId}
• "Delete a resource-policy?" -> DELETE /resource-policy/{resourceArn}
• "Delete a site?" -> DELETE /global-networks/{globalNetworkId}/sites/{siteId}
• "Delete a transit-gateway-registration?" -> DELETE /global-networks/{globalNetworkId}/transit-gateway-registrations/{transitGatewayArn}
• "List all global-networks?" -> GET /global-networks
• "Delete a connect-peer-association?" -> DELETE /global-networks/{globalNetworkId}/connect-peer-associations/{connectPeerId}
• "Delete a customer-gateway-association?" -> DELETE /global-networks/{globalNetworkId}/customer-gateway-associations/{customerGatewayArn}

Response Tips

• Check response schemas in references/api-spec.lap for field details
• Create/update endpoints typically return the created/updated object

References

• Full spec: See references/api-spec.lap for complete endpoint details, parameter tables, and response schemas

Generated from the official API spec by LAP