ModifyTransitGatewayPeeringAttachment
Modifies the options for a transit gateway peering attachment. The peering attachment must be in the available state.
You can allow multipath resilience for your side of an inter-Region transit gateway peering attachment between
supported Regions.
Multipath resilience isn't supported for transit gateway peering attachments in the same Region. It takes
effect only when both the requester and the accepter allow it. To modify the requester side, send the
request in the Region of the requester transit gateway. To modify the accepter side, send the request in the
Region of the accepter transit gateway. To check whether multipath resilience is in effect, use
DescribeTransitGatewayPeeringAttachments and check
multipathResilienceStatus.
Request Parameters
The following parameters are for this specific action. For more information about required and optional parameters that are common to all actions, see Common Query Parameters.
- DryRun
-
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 isUnauthorizedOperation.Type: Boolean
Required: No
- Options
-
The options to modify for the transit gateway peering attachment.
Type: ModifyTransitGatewayPeeringAttachmentRequestOptions object
Required: No
- TransitGatewayAttachmentId
-
The ID of the transit gateway peering attachment.
Type: String
Required: Yes
Response Elements
The following elements are returned by the service.
- requestId
-
The ID of the request.
Type: String
- transitGatewayPeeringAttachment
-
Information about the transit gateway peering attachment.
Type: TransitGatewayPeeringAttachment object
Errors
For information about the errors that are common to all actions, see Common Error Types.
Examples
Example – Allow multipath resilience
The following example request allows multipath resilience for the requester side of the specified
transit gateway peering attachment. Because the accepter doesn't allow multipath resilience yet,
the response shows a multipathResilienceStatus of pending:
Sample Request
https://ec2.amazonaws.com/?Action=ModifyTransitGatewayPeeringAttachment
&TransitGatewayAttachmentId=tgw-attach-1234567890abcdef0
&Options.AllowMultipathResilience=true
&Options.MultipathResilienceMode=always-on
&AUTHPARAMS
Sample Response
<ModifyTransitGatewayPeeringAttachmentResponse xmlns="http://ec2.amazonaws.com/doc/2016-11-15/">
<requestId>4e9b2c7d-1a3f-4b8e-9c5d-2f6a8e1bexample</requestId>
<transitGatewayPeeringAttachment>
<accepterTgwInfo>
<ownerId>123456789012</ownerId>
<region>us-west-2</region>
<transitGatewayId>tgw-1234567890abc1234</transitGatewayId>
</accepterTgwInfo>
<creationTime>2026-11-10T11:36:30.000Z</creationTime>
<options>
<requesterAllowMultipathResilience>true</requesterAllowMultipathResilience>
<requesterMultipathResilienceMode>always-on</requesterMultipathResilienceMode>
<accepterAllowMultipathResilience>false</accepterAllowMultipathResilience>
<multipathResilienceStatus>pending</multipathResilienceStatus>
</options>
<requesterTgwInfo>
<ownerId>123456789012</ownerId>
<region>us-east-1</region>
<transitGatewayId>tgw-11223344aabbcc112</transitGatewayId>
</requesterTgwInfo>
<state>available</state>
<transitGatewayAttachmentId>tgw-attach-1234567890abcdef0</transitGatewayAttachmentId>
</transitGatewayPeeringAttachment>
</ModifyTransitGatewayPeeringAttachmentResponse>
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the following: