Deleting a Net Peering

You can delete a Net peering to disable communication between two peered Nets.

Permission to delete the connection depends on the state of the connection:

  • If the connection is in the active state, it can be deleted either by the owner of the requester Net or the owner of the peer Net.

  • If it is in the pending-acceptance state, it can be deleted only by the owner of the requester Net.

  • It if is in the rejected, failed, or expired states, it cannot be deleted.

For more information, see About Net Peerings > Lifecycle.

Deleting a Net Peering Using Cockpit v2

  1. In the Net Peerings dashboard, check the box of the Net peering you want to delete.

    Multiselection is available.

    The Net peering is selected.

  2. Click IconTerminate Delete.
    A confirmation dialog box appears.

  3. Click Delete.
    The Net peering is deleted.

    Deleted resources remain visible for 1 hour.

Deleting a Net Peering Using OSC CLI

The DeleteNetPeering command deletes a Net peering.
If the Net peering is in the active state, it can be deleted either by the owner of the requester Net or the owner of the peer Net.
If it is in the pending-acceptance state, it can be deleted only by the owner of the requester Net.
If it is in the rejected, failed, or expired states, it cannot be deleted.

Request sample
$ osc-cli api DeleteNetPeering --profile "default" \
    --NetPeeringId "pcx-12345678"

This command contains the following attributes that you need to specify:

  • DryRun: (optional) If true, checks whether you have the required permissions to perform the action.

  • NetPeeringId: The ID of the Net peering you want to delete.

The DeleteNetPeering command returns the following elements:

  • ResponseContext: Information about the context of the response.

    • RequestId: The ID of the request.

Result sample
{
  "ResponseContext": {
    "RequestId": "0475ca1e-d0c5-441d-712a-da55a4175157"
  }
}

Deleting a Net Peering Using oapi-cli

The DeleteNetPeering command deletes a Net peering.
If the Net peering is in the active state, it can be deleted either by the owner of the requester Net or the owner of the peer Net.
If it is in the pending-acceptance state, it can be deleted only by the owner of the requester Net.
If it is in the rejected, failed, or expired states, it cannot be deleted.

Request sample
$ oapi-cli --profile "default" DeleteNetPeering \
    --NetPeeringId "pcx-12345678"

This command contains the following attributes that you need to specify:

  • DryRun: (optional) If true, checks whether you have the required permissions to perform the action.

  • NetPeeringId: The ID of the Net peering you want to delete.

The DeleteNetPeering command returns the following elements:

  • ResponseContext: Information about the context of the response.

    • RequestId: The ID of the request.

Result sample
{
  "ResponseContext": {
    "RequestId": "0475ca1e-d0c5-441d-712a-da55a4175157"
  }
}

Deleting a VPC Peering Connection Using AWS CLI

Before you begin: Install and configure AWS CLI. For more information, see Installing and Configuring AWS CLI.

To delete a VPC peering connection, use the delete-vpc-peering-connection command following this syntax:

Request sample
 $ aws ec2 delete-vpc-peering-connection \
    --profile YOUR_PROFILE \
    --vpc-peering-connection-id pcx-111aaa11 \
    --endpoint https://fcu.eu-west-2.outscale.com

This command contains the following attributes that you need to specify:

  • (optional) profile: The named profile you want to use, created when configuring AWS CLI. For more information, see Installing and Configuring AWS CLI.

  • vpc-peering-connection-id: The ID of the VPC peering connection you want to delete.

  • endpoint: The endpoint corresponding to the Region you want to send the request to. For more information, see Installing and Configuring AWS CLI.

The specified VPC peering connection is deleted.

Deleted resources remain visible for 1 hour.

Related Pages

Corresponding API Methods

AWS™ and Amazon Web Services™ are trademarks of Amazon Technologies, Inc or its affiliates in the United States and/or other countries.

Export to PDF