Manage Cloud Environments on StreamNative Cloud

A Cloud Connection provisions a Pool that enables you to deploy BYOC instances. Within that Pool, you can create Cloud Environments, which provision Pool Members in your designated cloud region. After creating a Cloud Environment, you can create an Instance and then create a cluster within that instance.

Plan a Cloud Environment

Before you start provisioning a cloud environment, you need to plan for the required information. The information you need to provide depends on your cloud provider. Here is a summary of the required information:

Region

Select the region where the Cloud Environment will be created.

VPC

Choose between using a StreamNative-managed VPC or your own VPC (aka Bring Your Own Network, or BYON).

StreamNative-managed VPC

If you decide to use a StreamNative-managed VPC, you need to provide the CIDR value for the VPC. Below are the recommended default CIDR values for each cloud provider:

• AWS
  • Default VPC CIDR: 10.60.0.0/16 (must between /16 and /28), but we suggest using /16 to /18, otherwise there will not be enough IP addresses.
  • The subnet CIDR will be calculated by VPC CIDR.
• GCP
  • Default VPC CIDR: 10.0.0.0/16
  • Secondary ranges for pods and services:
    • Pods: 192.168.0.0/16
    • Services: 192.168.64.0/18
• Azure
  • Default VPC CIDR: 10.70.0.0/16
  • Default Subnet CIDR: 10.70.0.0/24

Bring You Own Network (BYON)

If you decide to use your own VPC, please make sure that the VPC meets the following requirements:

If you don't tag the VPC and subnets with the required tags, the Cloud Environment provisioning will fail as we don't have the permission to access the VPC and subnets.

Bring Your Own DNS

By default, all the clusters will have a StreamNative-generated DNS record. If you want to use your own DNS, you need to provide the DNS Zone ID for a public hosted zone.

Default Gateway

Select the endpoint type for the default gateway. A gateway exposes service endpoints externally and can be either public or private. If you select private, you must provide allowed IDs for creating privatelink services. The allowed IDs are the account IDs that you want to grant access to the private endpoints.

Create a Cloud Environment

After you have planned all the required information, you can then provision a cloud environment through Cloud Console, snctl, or StreamNative's Terraform provider.

Monitoring the Provisioning Process

Creating a Cloud Environment through Terraform does not immediately create the Cloud Environment, but rather kicks off a process that creates it. Provisioning a Cloud Environment takes approximately 40 minutes. You will receive an email notification when the Cloud Environment is ready or if there are any issues.

At the same time, if you want to monitor the provisioning process, you can use snctl.

snctl describe -n orgname cloudenvironment CLOUD_ENVIRONMENT_NAME

• Replace CLOUD_ENVIRONMENT_NAME with the name of the cloud environment.

Once snctl describe returns a status of True and a type of Ready your Cloud Environment has been provisioned, and you can create a Pulsar Cluster within it.

If this command returns an error state, please reach out to the StreamNative support team.

Update a Cloud Environment

It is generally not recommended to update a Cloud Environment once it has been created. If you need to update a Cloud Environment, please reach out to StreamNative support team to discuss your requirements.

Delete a Cloud Environment

Next steps

After setting up one or more Cloud Environments, you can proceed to create StreamNative instances and clusters within those environments.