Confluent Cloud Network on AWS

Each Confluent Cloud network is a virtual network that is provisioned in your Confluent Cloud AWS account.

You can create multiple Dedicated Kafka clusters within each Confluent Cloud network.

For details on default service quotas, see Network service quotas.

Prerequisites

Before you create a Confluent Cloud network, you need the following information.

Name your Confluent Cloud network

The name you choose is used to identify your network in the Confluent Cloud Console and when using the Confluent CLI. Choose a meaningful name, but consider including the connection type in the name (for example, My-Transit-Gateway-CCN-1).

Select Region and Availability Zones

Dedicated clusters you create in your Confluent Cloud network inherit the selected Region and Availability Zones.

Select CIDR blocks and block size

Important

Limited Availability

Support for /27 CIDR blocks is in Limited Availability to a subset of Confluent customers. To be considered for access before General Availability, contact Confluent Support.

By default, you can select a /16 CIDR block for use with your VPC Peering Confluent Cloud network on AWS. With the Limited Availability feature enabled, you can select either one /16 CIDR block or multiple /27 CIDR blocks (one for each Availability Zone).

The CIDR block must be in one of the following private IP ranges:

  • RFC 1918 private address spaces:

    • 10.0.0.0/8
    • 172.16.0.0/12
    • 192.168.0.0/16
  • RFC 6598 private address space:

    • 100.64.0.0/10
  • RFC 2544 private address space:

    • 198.18.0.0/15

      This CIDR block is incompatible with Transit Gateway-to-Transit Gateway Cluster Linking.

Additional requirements for selecting a /16 CIDR block:

  • Selected CIDR block cannot overlap with existing Confluent Cloud /16 CIDR blocks.
  • The CIDR block cannot overlap with the following IP ranges:
    • 10.100.0.0/16
    • 10.255.0.0/16
    • 172.17.0.0/16
    • 172.20.0.0/16

CIDRs for the your VPCs that need to be directly routable cannot overlap with the above CIDR blocks due to routing conflicts with Confluent services.

  • You cannot switch to /27 CIDR blocks after the Confluent Cloud network is provisioned.

Create a Confluent Cloud network on AWS

Follow the procedure below to create a Confluent Cloud network on AWS.

You can host multiple clusters within one Confluent Cloud network. For details on service quotas, see Network.

  1. In the Confluent Cloud Console, go to the Network management page for your environment.

  2. Click Create your first network if this is the first network in your environment, or click + Add Network if your environment has existing networks.

  3. Select AWS as the cloud service provider and select the geographic region in Region.

  4. Select the connectivity type: Transit Gateway, VPC Peering, or PrivateLink.

    Depending on the option selected, different Zone Placement options and CIDR for Confluent Cloud fields will appear.

    • Transit Gateway: Cluster is accessible using the transit gateway endpoint.
    • VPC Peering: Cluster is accessible using the VPC peering endpoint.
    • PrivateLink: Cluster is accessible using AWS PrivateLink connections.
  5. Complete the steps for the connectivity type you selected and then click Continue.

    Important

    After provisioning your new Confluent Cloud network, you cannot change your selected Availability Zone (AZ) IDs or CIDR block size. Make sure to deploy a network based on your zonal requirements.

    Under Zone Placement, select three zones for your network.

    Depending on support for zones, you might only have three zones to choose from.

  6. Specify a Network Name, review your configuration, and click Create Network.


Your Confluent Cloud network is created and provisioned within 20 minutes.

Next steps

After successfully provisioning the Confluent Cloud network on AWS, you can add Dedicated Kafka clusters within your Confluent Cloud network by using the following options: