GET /#Action=CreateTransitGatewayPeeringAttachment

Requests a transit gateway peering attachment between the specified transit gateway (requester) and a peer transit gateway (accepter). The peer transit gateway can be in your account or a different Amazon Web Services account.

After you create the peering attachment, the owner of the accepter transit gateway must accept the attachment request.

Servers

https://ec2.{region}.amazonaws.com
https://ec2.amazonaws.com
https://ec2.{region}.amazonaws.com.cn

Request headers

Name	Type	Required
`X-Amz-Content-Sha256`	String	No
`X-Amz-Credential`	String	No
`X-Amz-Date`	String	No
`X-Amz-Algorithm`	String	No
`X-Amz-SignedHeaders`	String	No
`X-Amz-Security-Token`	String	No
`X-Amz-Signature`	String	No

Query parameters

Name	Type	Required	Description
`Version`	String	Yes	Possible values: `"2016-11-15"`
`PeerRegion`	String	Yes	The Region where the peer transit gateway is located.
`PeerAccountId`	String	Yes	The ID of the Amazon Web Services account that owns the peer transit gateway.
`TagSpecification[]`	Array	No	The tags to apply to the transit gateway peering attachment.
`Options`	Object	No	Requests a transit gateway peering attachment.
`DryRun`	Boolean	No	Checks whether you have the required permissions for the action, without actually making the request, and provides an error response. If you have the required permissions, the error response is `DryRunOperation`. Otherwise, it is `UnauthorizedOperation`.
`TransitGatewayId`	String	Yes	The ID of the transit gateway.
`PeerTransitGatewayId`	String	Yes	The ID of the peer transit gateway with which to create the peering attachment.
`Action`	String	Yes	Possible values: `"CreateTransitGatewayPeeringAttachment"`

How to start integrating

Add HTTP Task to your workflow definition.
Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
Click Test request to test run your request to the API and see the API's response.