Provisioning

Gen 2

Provision an Event Streams deployment through the catalog, the CLI or through Terraform.

Step 1: Select your plan

Event Streams offers different plans according to the generation of the platform, see Choosing your plan. For the Gen2 platform, the Enterprise Gen 2 plan can be selected.

The Enterprise Gen 2 plan offers pay-as-you-go access to an isolated single-tenant Event Streams service running on the Gen2 (VPC) platform. In addition to a selection of throughput and storage options, this plan also offers user-managed encryption private endpoints and meets a higher number of regulatory compliance standards. The Enterprise Gen2 plan is the best choice if data isolation, scalability, security, guaranteed performance, and increased retention are important considerations.

Step 2: Provision using the console

Log in to the IBM Cloud console.
In the Catalog,, search for Event Streams, then click the Event Streams tile to go to the provisioning page.
Select a Location that supports the Gen 2 platform.
From the Select a pricing plan section, select the Enterprise Gen 2 plan .
Enter a name for your service. You can use the default value.
Click Create. The Event Streams Resource list page opens.
When your instance is created, click on the instance name to view more information.

Step 3: Create a service credential using the console

To allow you to connect to your Event Streams instance, create a service key by using the IBM Cloud console:

In the Resource list, select your Event Streams service.
Click Service credentials.
Click New credential.
Complete the details for your new credential, such as a name and role and click Add. A new credential appears in the credentials list.
Expand the new credential's section to reveal the details in JSON format.

Step 2: Provisioning using the CLI

Before provisioning, follow the instructions provided in the documentation to install the IBM Cloud CLI tool.

Log in to IBM Cloud. If you use a federated user ID, it's important that you switch to a one-time passcode (ibmcloud login --sso), or use an API key (ibmcloud --apikey key or @key_file) to authenticate. For more information about how to log in by using the CLI, see General CLI (ibmcloud) commands under ibmcloud login.
```
ibmcloud login
```

You can create an instance by using the following command:

ibmcloud resource service-instance-create <NAME> <SERVICE_NAME> <SERVICE_PLAN_NAME> <LOCATION> -g <RESOURCE_GROUP>

Example command for Event Streams:

ibmcloud resource service-instance-create <NAME> messagehub enterprise-gen2 ca-mon -g Default -p '{
   "dataservices":{
      "kafka": {
        "throughput_mb_s": 100,
        "storage_gb": 2000
      },
      "encryption": {
         "disk": "crn:v1..."
      },
      "$schema": {
         "version": "1.0.0"
      }
   }
}'

Step 3: Create a service credential using the CLI

To create a service credential:

ibmcloud resource service-key-create NAME [ROLE_NAME] --instance-name SERVICE_INSTANCE_NAME

Replace the variables with your own values:

NAME - replace with the name to use for the service credential.
ROLE_NAME - replace with the name of the IAM role for the service credential (MANAGER, WRITER, or READER].
SERVICE_INSTANCE_NAME - replace with the name of the service instance the service credential is to be associated with.

For more information, see using the CLI.

Step 2: Provisioning using Terraform

To create an Event Streams instance with default provisioning parameters:

resource "ibm_resource_instance" "es_instance_1" {
  name              = "my_es_instance_1"
  service           = "messagehub"
  plan              = "enterprise-gen2"
  location          = "ca-mon"

  timeouts {
    create = "15m"
    update = "15m"
    delete = "15m"
  }

Step 3: Create a service credential using Terraform

To create a service credential:

resource "ibm_resource_key" "serviceKey" {
  name                  = "NAME"
  role                  = "ROLE_NAME"
  resource_instance_id  = "${ibm_resource_instance.es_instance_1.id}"
}

Replace the variables with your own values:

NAME - replace with the name to use for the service credential.
ROLE_NAME - replace with the name of the IAM role for the service credential (MANAGER, WRITER, or READER].

For more information, see using Terraform.