--- schema_version: "1" id: 5559a043007667f9c1057d12faef0815673af2fc6afe8e2e310df6313ce5ea09 title: Manage Transit Gateway Attachments collection: mulesoft version: current locale: en-us portal_url: https://docs.salesforce.com/mulesoft/current/en-us/cloudhub/tgw-manage-arm.md canonical_url: https://docs.mulesoft.com/cloudhub/tgw-manage-arm source_site: docs.mulesoft.com content_type: documentation content_hash: 0da16ee512015922760636ec365cd03bd7eed0273496d6b73f243490a774442c description: MuleSoft Documentation Site latest: true --- --- product: CloudHub --- # Manage Transit Gateway Attachments > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Use Anypoint Runtime Manager to manage transit gateway attachments, such as adding and removing a route from the route table or detaching an Anypoint VPN from a transit gateway. ## Rename a Transit Gateway Attachment You might want to rename a transit gateway attachment to match the attachment name in AWS. To rename a transit gateway attachment: 1. On the **Transit Gateways** page, click the Transit Gateway menu (**…​**) and select **Edit name**: ![Edit name option in the Transit Gateways menu](/mulesoft/current/en-us/cloudhub/_images/tgw-rename.png) 2. In the popup window, enter a new name and click **Save**. ## Add a Route to the Transit Gateway Route Table You might want to add a route to enable a new subnet to be accessible through the transit gateway. 1. In Anypoint Platform, navigate to **Transit Gateways** > **VPCs** and click **Add Route**. 2. In the **Add VPC Route** window, use CIDR notation to enter a single subnet for your AWS VPC: ![Add VPC route](/mulesoft/current/en-us/cloudhub/_images/tgw-add-vpc-route.png) 3. Click **Add Route**. Anypoint Platform submits the new route to AWS. > [!NOTE] When you add a new route, the platform ensures it doesn’t conflict with any existing > routes in the VPC, whether they’re static or propagated from a BGP connection. If the new route is > a duplicate, either remove the existing route or split the new route into smaller ones to avoid > any collisions. When the route addition succeeds, the **Transit Gateways** page shows the **Route added** message and the **Transit Gateways** page shows the route CIDR in the route table. In the route tables, added routes show **Transit Gateway** as the value in the **Next Hop** column. Specific routes attached to the transit gateway show under **Transit Gateway Routes**. Other routes in the VPC show under **VPC Routes**. ![Transit Gateway in the Next Hop column of the route table](/mulesoft/current/en-us/cloudhub/_images/tgw-route-added.png) ## Remove a Route from the Transit Gateway Route Table You might need to remove a route if you no longer want a subnet to be accessible through the transit gateway. To remove a route: 1. On the **Transit Gateways** page, in the **VPCs** section, click the **X** icon in the appropriate Transit Gateway route row of the route table: ![Remove route icon in the VPCs section](/mulesoft/current/en-us/cloudhub/_images/tgw-remove-vpc-route.png) 2. At the confirmation prompt, click **Remove**. ## Detach an Anypoint VPC from the Transit Gateway You might need to detach a VPC so that you can reattach it. Detaching a VPC from a transit gateway also deletes the attachment in AWS. Any apps deployed to the VPC continue to run, but they are no longer connected to your Amazon VPCs and VPNs. To detach a VPC from the transit gateway: 1. On the **Transit Gateways** page, click the VPC menu (**…​**) and select **Detach**: ![Detach VPC option in the VPC menu](/mulesoft/current/en-us/cloudhub/_images/tgw-detach-vpc.png) 2. At the confirmation prompt, click **Detach**. Detaching a VPC might take several minutes. ## Remove an Anypoint VPC from the Transit Gateway If you reject an attachment in AWS, the VPC attachment appears as `rejected` in Anypoint Platform. In this case, you must remove the attachment before trying to attach it again. To remove a VPC from the transit gateway: 1. On the **Transit Gateways** page, click the VPC menu (**…​**) and select **Remove**: 2. At the confirmation prompt, click **Remove**. Removing a VPC might take several minutes. After the VPC is removed, the **Attach VPC** button becomes available. ## Remove a Transit Gateway from Anypoint Platform You might need to remove a transit gateway if you’ve reached your entitlement limit or you want to switch the connection to a new transit gateway. If a transit gateway has no VPCs attached, you can remove it from Anypoint Platform. > [!NOTE] Removing a transit gateway deletes the resource share in AWS that Anypoint Platform uses > to access the transit gateway. To remove a transit gateway from Anypoint Platform: 1. On the **Transit Gateways** page, click the Transit Gateway menu (**…​**) and select **Remove**: ![Remove option in the Transit Gateway menu](/mulesoft/current/en-us/cloudhub/_images/tgw-remove.png) Anypoint Platform prevents you from removing a transit gateway if it has VPCs attached. If the **Transit Gateways** page doesn’t list any VPCs, but you can’t delete the transit gateway, the transit gateway might be attached to a VPC that belongs to another business group that you don’t have access to. 2. At the confirmation prompt, click **Remove**. ## See Also - [Troubleshoot Transit Gateway Attachments](https://docs.mulesoft.com/cloudhub/tgw-troubleshoot) - [Attach to Transit Gateways](https://docs.mulesoft.com/cloudhub/tgw-attach-arm) - [Transit Gateway Attachments](https://docs.mulesoft.com/cloudhub/tgw-about) - [Virtual Private Cloud](https://docs.mulesoft.com/cloudhub/virtual-private-cloud) - [Create and Update a VPC for Runtime Manager](https://docs.mulesoft.com/cloudhub/vpc-tutorial) - [Grant Permissions and Roles to Users](https://docs.mulesoft.com/access-management/users#grant-permissions-and-roles-to-users)