GetTransitGatewayPeering - AWS Global Networks for Transit Gateways


Returns information about a transit gateway peer.

Request Syntax

GET /transit-gateway-peerings/peeringId HTTP/1.1

URI Request Parameters

The request uses the following URI parameters.


The ID of the peering request.

Length Constraints: Minimum length of 0. Maximum length of 50.

Pattern: ^peering-([0-9a-f]{8,17})$

Required: Yes

Request Body

The request does not have a request body.

Response Syntax

HTTP/1.1 200 Content-type: application/json { "TransitGatewayPeering": { "Peering": { "CoreNetworkArn": "string", "CoreNetworkId": "string", "CreatedAt": number, "EdgeLocation": "string", "OwnerAccountId": "string", "PeeringId": "string", "PeeringType": "string", "ResourceArn": "string", "State": "string", "Tags": [ { "Key": "string", "Value": "string" } ] }, "TransitGatewayArn": "string", "TransitGatewayPeeringAttachmentId": "string" } }

Response Elements

If the action is successful, the service sends back an HTTP 200 response.

The following data is returned in JSON format by the service.


Returns information about a transit gateway peering.

Type: TransitGatewayPeering object


For information about the errors that are common to all actions, see Common Errors.


You do not have sufficient access to perform this action.

HTTP Status Code: 403


The request has failed due to an internal error.

HTTP Status Code: 500


The specified resource could not be found.

HTTP Status Code: 404


The request was denied due to request throttling.

HTTP Status Code: 429


The input fails to satisfy the constraints.

HTTP Status Code: 400

See Also

For more information about using this API in one of the language-specific AWS SDKs, see the following: