VPC peering allows you to connect two VPCs together, enabling bi-directional network communication between instances in different VPCs. This page explains how to manage VPC peering connections using nico-admin-cli.
VPC Peering Commands
The nico-admin-cli vpc-peering command provides three main operations:
Creating VPC Peering Connections
To create a new VPC peering connection between two VPCs:
Example:
Notes:
- The operator should confirm with both VPC owners (VPC tenant org) that they approve the peering before creating the connection
- The VPC IDs can be provided in any order
- The system will automatically enforce canonical ordering (smaller ID becomes
vpc1_id)
- If a peering connection already exists between the two VPCs, the command will return an error indicating a peering connection already exists
- Both VPCs must exist before creating the peering connection
Listing VPC Peering Connections
To view VPC peering connections, you can either show all connections or filter by a specific VPC:
Show all peering connections:
Show peering connections for a specific VPC:
Example:
The output will display:
- Peering connection ID
- VPC1 ID (smaller UUID)
- VPC2 ID (larger UUID)
- Connection status
- Creation timestamp
Deleting VPC Peering Connections
To delete an existing VPC peering connection:
Example:
Notes:
- You need the peering connection ID (not the VPC IDs) to delete a connection
- Use the
show command to find the peering connection ID
