Skip to main content
Version: v3.x (DDN)

Create a Data Plane

Introduction

A Data Plane in Hasura provides dedicated infrastructure for running your GraphQL workloads. This guide walks you through the process of creating a new Data Plane for dedicated Private DDN.

Prerequisite

To create a Data Plane in Private DDN, you'll need an Enterprise contract. Reach out to sales here to get started.

How to create a new Data Plane on Dedicated Private DDN

Step 1. Create a new Data Plane

Navigate to the Private DDN section in your Hasura console.

Data Plane Management

Click the Create Data Plane button.

Data Plane Creation Pending

Step 2. Complete the Data Plane Configuration Form

  • Name: Enter a descriptive name using only letters and spaces, between 4-30 characters. This will be used to identify your Data Plane.
  • Domain: This field is automatically generated from your Data Plane name. This is the base domain for the GraphQL API on this Data Plane.
  • Cloud Provider: Select your preferred cloud provider. Currently available options: AWS.
  • Region: Select the geographical region for your Data Plane.
  • Zones: Select availability zones. For AWS, use AZ IDs (e.g., use1-az1, use1-az2) instead of AZ names (us-east-1a, us-east-1b) for your Data Plane. The maximum number of zones available to select depends on your Hasura Private DDN Subscription.
How to get AZ IDs for AWS?

Availability Zone (AZ) IDs are unique identifiers for AWS Availability Zones within a region. Using AZ IDs ensures consistency across different AWS accounts and optimizes performance by aligning your Data Plane with your database's physical location.

Why Use AZ IDs Instead of AZ Names?

  • Consistency: AZ IDs are consistent across all AWS accounts, whereas AZ Names can differ.
  • Performance: Deploying resources in the same physical AZ reduces latency.
  • Cost Efficiency: Avoids cross-zone network costs by ensuring resources are within the same AZ.

Note: When selecting AZ IDs, ensure they correspond to the AZs where your database resides to maintain low latency and avoid cross-zone network costs. It is recommended to choose at least two AZs for higher availability and fault tolerance.

Read more about AWS AZ IDs on AWS Docs

Steps to Obtain AZ IDs

You can obtain AZ IDs using either the AWS CLI or the AWS Console.

1. Using AWS CLI:

Run the following command, replacing <region> with your desired region:


aws ec2 describe-availability-zones \
--region <region> \
--output table \
--query "AvailabilityZones[?State=='available'] | [].{ZoneName: ZoneName, ZoneId: ZoneId}"

Example output for us-east-1:

-----------------------------
| DescribeAvailabilityZones |
+-----------+---------------+
| ZoneId | ZoneName |
+-----------+---------------+
| use1-az1 | us-east-1a |
| use1-az2 | us-east-1b |
| use1-az3 | us-east-1c |
+-----------+---------------+

2. Using AWS Console:

  • Log in to the AWS Console.
  • Navigate to the EC2 service.
  • Select your desired region from the top-right corner dropdown.
  • On the EC2 Dashboard page, locate the "Service health" section.
  • Under "Service health", find the "Zones" subsection. This section lists the Availability Zones along with their corresponding Zone IDs.
  • VPC CIDR: A /16 CIDR block that defines the IP address range for your Data Plane's Virtual Private Cloud (VPC). Default value: 10.0.0.0/16.
  • Kubernetes Service CIDR: A /16-/20 CIDR block used for Kubernetes service cluster IP addresses in your Data Plane. This CIDR range is used internally by Kubernetes to assign IP addresses to services running in the cluster. Default value: 172.20.0.0/16.
Important When choosing your VPC CIDR and Kubernetes Service CIDR:
  • Consider your current and future network topology, ensuring these CIDR ranges don't conflict with existing network routes or address spaces, especially for VPC peering or VPN connections.
  • Consult with your network administrator if you're unsure about potential conflicts.
  • Remember that VPC CIDR and Kubernetes Service CIDR cannot be modified once the Data Plane has been created. :::
Data Plane Creation Form

Step 3. Create and Monitor your Data Plane

Click the Create button after filling out all required fields. The creation process will begin, and you'll see your Data Plane listed with a Creating status. The creation process typically takes 60 minutes to complete.

Data Plane Page

Click on the Creating button in the status column to see detailed progress.

Data Plane Creating Status

After Creation

Once your data plane is successfully created and the status updates to Active, you and your team can begin creating projects on your Data Plane. To access more information about a specific Data Plane, simply click on its name within the Data Planes table. This action will navigate you to a detailed view page of the selected Data Plane, as illustrated below.

Data Plane Detail

Next steps

Now that you've created a Data Plane on dedicated Private DDN, learn how to add collaborators so they can create projects.