Manage VPC Peering Connections

Generate an API key to use the Atlas Cloud API.

1. In Atlas, go to the Project Access Manager page.

2. If it's not already displayed, select your desired organization from the Organizations menu in the navigation bar.

3. If it's not already displayed, select your desired project from the Projects menu in the navigation bar.

4. Do one of the following steps:

   • Select Project Access from the Access Manager menu in the navigation bar.

   • Next to the Projects menu, expand the Options menu, click Project Settings, and click Access Manager in the sidebar.

   The Project Access Manager page displays.

5. Click Applications.

6. Click Create API Key.

7. On the Create API Key page, enter your API Key information.

8. Save your API Key information.

9. Click Done.

Retrieve the Atlas Cloud AWS Account ID, the VPC ID, and the CIDR block.

A sample API request resembles the following:

curl \
-s --user "ajarafoc:a98a3a67-7400-4d6f-94b2-20a64118524d" \
--digest \
--header 'Accept: application/vnd.atlas.2024-11-13+json' \
--header 'Content-Type: application/json' \
--request GET \ "https://cloud.mongodb.com/api/atlas/v2/groups/671a86f4cfc9da7d7c31b14f/streams/accountDetails?cloudProvider=aws&regionName=US_EAST_1"

Note the following example parameter values:

A sample output resembles the following:

{
   "awsAccountId": "974404375205",
   "cidrBlock": "192.168.248.0/21",
   "vpcId": "vpc-0ef7efa5ceca36e2f"
}

Configure a network configuration.

A Confluent Network Configuration that supports VPC peering is required before you create a VPC peering connection. If a network configuration doesn't yet exist in your account, then select AWS as your cloud provider and select a region from the Add Network Configuration field in Confluent Cloud.

Click Continue and select VPC Peering in the next page.

Select three different Zones and the CIDR block for the Confluent AWS VPC.

Click Add Network Connection.

Open the Confluent VPC Peering Network Configuration, and click VPC Peering.

Provide the connection with a name, an Atlas AWS Account ID, a VPC ID, and the CIDR block from Step 2, and click Add.

The VPC peering connection request displays in Atlas after a potential delay.

To see your pending request in your Atlas account, execute an API request similar to:

curl \
-s --user "ojarafoc:1ecf4c70-98ea-4168-8e44-fd67dba0f3ba" \
--digest \
--header 'Accept: application/vnd.atlas.2023-02-01+json' \
--header 'Content-Type: application/json' \
--request GET \
"https://cloud-dev.mongodb.com/api/atlas/v2/groups/671a86f4cfc9da7d7c31b14f/streams/vpcPeeringConnections?requesterAccountId=417601102659"

Note the following example parameter values:

A sample output resembles the following:

{
   "links": [
      {
         "href": "https://cloud-dev.mongodb.com/api/atlas/v2/groups/671a86f4cfc9da7d7c31b14f/streams/vpcPeeringConnections?requesterAccountId=417601102659&pageNum=1&itemsPerPage=100",
         "rel": "self"
      }
   ],
   "results": [
      {
         "_id": "6759e61aa6cf0a5476e233d1",
         "accepterAccountId": "974404375205",
         "accepterVpcId": "vpc-0ddfd37072cc5ed61",
         "cloudStatus": "pending-acceptance",
         "expirationTime": "2024-12-18T19:20:37Z",
         "groupId": "671a86f4cfc9da7d7c31b14f",
         "localStatus": "NONE",
         "name": "pcx-09277e1e81d0751c1",
         "requesterAccountId": "417601102659",
         "requesterCidr": "10.0.0.0/16",
         "requesterVpcId": "vpc-0d13eb6a2f0377854"
      }
   ],
   "totalCount": 1
}

Accept the incoming VPC Peering connection request.

Note that the cloudStatus value is pending-acceptance.

Execute the following API request:

curl \
-s --user "ojarafoc:1ecf4c70-98ea-4168-8e44-fd67dba0f3ba" \
--digest \
--header 'Accept: application/vnd.atlas.2023-02-01+json' \
--header 'Content-Type: application/json' \
-d '{"requesterVpcId": "vpc-0d13eb6a2f0377854", "requesterAccountId":"417601102659"}' \
--request POST \
"https://cloud-dev.mongodb.com/api/atlas/v2/groups/671a86f4cfc9da7d7c31b14f/streams/vpcPeeringConnections/pcx-09277e1e81d0751c1:accept"

Note the following example parameter values:

Verify that the connection was accepted.

To do this, repeat Step 9 and observe the cloudStatus field value. When the connection is finally accepted, the value should return active.