NSX-T Data Center REST API
Update the VPC attachment
Update the VPC attachment.**IMPORTANT WARNING for Connectivity Profile Changes:** When changing the
vpc_connectivity_profile field, this operation may cause immediate traffic disruption:
• **Auto SNAT Changes**: If switching between connectivity profiles with different
"Default Outbound NAT" settings (enabled vs disabled), existing auto SNAT rules
will be deleted and new ones may be created. This can break outbound connectivity
for private subnets during the transition.
• **External IP Block Changes**: If the new connectivity profile uses different
external IP blocks, existing SNAT IP allocations will be released and new ones
allocated, potentially changing translated IP addresses.
• **Transit Gateway Changes**: Switching to a connectivity profile with a different
transit gateway will update routing paths and may cause temporary connectivity loss.
**Best Practices:**
1. Plan for potential downtime during the profile transition
2. Test connectivity profile changes in non-production environments first
Request:
Method:
PUT
URI Path(s):
/policy/api/v1/orgs/{org-id}/projects/{project-id}/vpcs/{vpc-id}/attachments/{vpc-attachment-id}
Request Headers:
n/a
Query Parameters:
n/a
Request Body:
VpcAttachment+
Example Request:
PUT https://<policy-mgr>/policy/api/v1/orgs/default/projects/project-1/vpcs/vpc-1/attachments/vpc-attachment-1 { "vpc_connectivity_profile": "/orgs/default/projects/project-1/vpc-connectivity-profiles/production_vpc1_connectivity_profile" }Successful Response:
Response Code:
200 OK
Response Headers:
Content-type: application/json
Response Body:
VpcAttachment+