--- name: databases-for-elasticsearch-howto-provisioning title: Provisioning description: Provision a IBM Cloud® Databases for Elasticsearch deployment through the catalog, the Cloud Databases CLI plug-in, the Cloud Databases API, through Terraform, or through pre-built, open-source, and enterprise-ready Terraform IBM Modules (TIM). last-updated: 2026-06-15 --- > ## Documentation Index > The table of contents for this documentation set is at https://cloud.ibm.com/docs/databases-for-elasticsearch?format=markdown > The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt > Use these files to discover more information as needed. # Provisioning {: #provisioning} Provision a IBM Cloud® Databases for Elasticsearch deployment through the [catalog](https://cloud.ibm.com/databases/databases-for-elasticsearch/create){: external}, the [Cloud Databases CLI plug-in](https://cloud.ibm.com/docs/databases-cli-plugin?topic=databases-cli-plugin-cdb-reference&format=markdown){: external}, the [Cloud Databases API](https://cloud.ibm.com/apidocs/cloud-databases-api){: external}, through [Terraform](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/database){: external}, or through pre-built, open-source, and enterprise-ready [Terraform IBM Modules (TIM)](https://registry.terraform.io/modules/terraform-ibm-modules/icd-elasticsearch/ibm/latest){: external}. ## Provisioning through the IBM Cloud console {: #catalog} {: ui} Provision from the console by specifying the following parameters. ### Service details {: #service_details} {: ui} - **Service name** - The name can be any string and is the name that is used on the web and in the CLI to identify the new deployment. - **Resource group** - If you are organizing your services into [resource groups](https://cloud.ibm.com/docs/account?topic=account-account_setup&format=markdown), specify the resource group in this field. Otherwise, you can leave it at default. For more information, see [Managing resource groups](https://cloud.ibm.com/docs/account?topic=account-rgs&format=markdown). - **Location** - The deployment's public cloud region. ### Hosting model {: #hosting_model} {: ui} - **Isolated:** Secure single-tenant offering for complex, highly-performant enterprise workloads. - **Shared:** Flexible multi-tenant offering for dynamic, fine-tuned, and decoupled capacity selections. Databases for Elasticsearch Platinum features are only available on Isolated Compute. {: note} For more information, see [Hosting models](https://cloud.ibm.com/docs/cloud-databases?topic=cloud-databases-hosting-models&format=markdown) and [Databases for Elasticsearch plans](https://cloud.ibm.com/docs/databases-for-elasticsearch?topic=databases-for-elasticsearch-elastic-offerings&format=markdown). ### Resource allocation {: #resource_allocation} {: ui} Fine tune your resource allocation. The available options differ based on your selected hosting model. - **Isolated:** Use the table to choose the machine size for each member of your deployment, and specify the disk size. - **Shared:** By default, the smallest possible resource allocation is selected. This is ideal for small applications or testing. For larger allocations, select the *Custom* tile, which allows flexible resource configuration with 2+ cores. The Shared Compute hosting model supports more fine-grained resource allocations that are not shown in the UI to maintain clarity. For more information, see [Hosting models](https://cloud.ibm.com/docs/cloud-databases?topic=cloud-databases-hosting-models&format=markdown). {: note} Specify the disk size depending on your requirements. It can be increased after provisioning but cannot be decreased to prevent data loss. {: note} ### Service configuration {: #service_configuration} {: ui} - **Database version:** [Set only at deployment]{: tag-red} The deployment version of your database. To ensure optimal performance, run the preferred version. The latest minor version is used automatically. For more information, see [Versioning policy](https://cloud.ibm.com/docs/cloud-databases?topic=cloud-databases-versioning-policy&format=markdown){: external}. - **Database edition:** [Set only at deployment]{: tag-red} Select the edition that you want to deploy. Choose from Enterprise or Platinum. Note that Platinum is only available on the Isolated hosting model. - **Encryption:** [Set only at deployment]{: tag-red} If you use [Key Protect](https://cloud.ibm.com/docs/cloud-databases?topic=cloud-databases-key-protect&interface=ui&format=markdown), an instance and key can be selected to encrypt the deployment's disk. If you do not use your own key, the deployment automatically creates and manages its own disk encryption key. - **Endpoints:** [Set only at deployment]{: tag-red} Configure the [Service endpoints](https://cloud.ibm.com/docs/cloud-databases?topic=cloud-databases-service-endpoints&format=markdown) on your deployment. The default setting is *private*. After you select the appropriate settings, click **Create** to start the provisioning process. ## Provisioning through the CLI {: #use-cli} {: cli} ### Create a service instance through the CLI {: #create-service-instance-cli} {: cli} Before provisioning, follow the instructions provided in the documentation to install the [IBM Cloud CLI tool](https://cloud.ibm.com/docs/cli?topic=cli-install-ibmcloud-cli&format=markdown){: external}. 1. 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](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_cli&format=markdown#ibmcloud_login){: external} under `ibmcloud login`. ```sh ibmcloud login ``` {: pre} 2. Select the [hosting model](https://cloud.ibm.com/docs/cloud-databases?topic=cloud-databases-hosting-models&interface=cli&format=markdown) you want your database to be provisioned on. You can change this later. 3. Provision your database with the following command: ```sh ibmcloud resource service-instance-create -p '{"members_host_flavor": ""}' --service-endpoints="" ``` {: pre} For example, to provision a Databases for Elasticsearch Shared Compute hosting model instance, use a command like: ```sh ibmcloud resource service-instance-create test-database databases-for-elasticsearch enterprise us-south -p '{ "backup_id": "", "version": "", "members_memory_allocation_mb": "4096" }' --service-endpoints="private" ``` {: pre} Provision a Databases for Elasticsearch Isolated instance with the same `"members_host_flavor"` -p parameter, setting it to the desired Isolated size. Available hosting sizes and their `members_host_flavor value` parameters are listed in [Table 2](#members-host-flavor-parameter-cli). For example, `{"members_host_flavor": "b3c.4x16.encrypted"}`. Note that since the host flavor selection includes CPU and RAM sizes (`b3c.4x16.encrypted` is 4 CPU and 16 RAM), this request does not accept both, an Isolated size selection and separate CPU and RAM allocation selections. ```sh ibmcloud resource service-instance-create test-database databases-for-elasticsearch enterprise us-south -p '{"members_host_flavor": "b3c.4x16.encrypted"}' --service-endpoints="private" ``` {: pre} The fields in the command are described in the table that follows. | Field | Description | Flag | |-------|------------|------------| | `INSTANCE_NAME` [Required]{: tag-red} | The instance name can be any string and is the name that is used on the web and in the CLI to identify the new deployment. | | | `SERVICE_NAME` [Required]{: tag-red} | Name or ID of the service. For Databases for Elasticsearch, use `databases-for-elasticsearch`. | | | `SERVICE_PLAN_NAME` [Required]{: tag-red} | `enterprise` or `platinum`. Note that `platinum` requires an `isolated` host flavor. | | | `LOCATION` [Required]{: tag-red} | The location where you want to deploy. To retrieve a list of regions, use the `ibmcloud regions` command. | | | `RESOURCE_GROUP` | The Resource group name. The default value is `default`. | -g | | `--parameters` | JSON file or JSON string of parameters to create service instance | -p | | `members_host_flavor` | To provision an Isolated or Shared Compute instance, use `{"members_host_flavor": ""}`. For Shared Compute, specify a value of `multitenant`. For Isolated Compute, select desired CPU and RAM configuration. For more information, see the following table or [Hosting models](https://cloud.ibm.com/docs/cloud-databases?topic=cloud-databases-hosting-models&format=markdown).| | | `--service-endpoints` [Required]{: tag-red} | Configure the [Service endpoints](https://cloud.ibm.com/docs/cloud-databases?topic=cloud-databases-service-endpoints&format=markdown){: external} of your deployment, either `public`, `private` or `public-and-private`. | | {: caption="Basic command format fields" caption-side="top"} In the CLI, `service-endpoints` is a flag, not a parameter. {: note} ### The `members host flavor` parameter {: #members-host-flavor-parameter-cli} {: cli} The `members_host_flavor` parameter defines your Compute sizing. To provision a Shared Compute instance, specify `multitenant`. To provision an Isolated Compute instance, input the appropriate value for your desired CPU and RAM configuration. | **Members Host flavor** | **members_host_flavor value** | |:-------------------------:|:---------------------:| | Shared Compute | `multitenant` | | 4 CPU x 16 RAM | `b3c.4x16.encrypted` | | 8 CPU x 32 RAM | `b3c.8x32.encrypted` | | 8 CPU x 64 RAM | `m3c.8x64.encrypted` | | 16 CPU x 64 RAM | `b3c.16x64.encrypted` | | 32 CPU x 128 RAM | `b3c.32x128.encrypted` | | 30 CPU x 240 RAM | `m3c.30x240.encrypted` | {: caption="Host flavor sizing parameter" caption-side="bottom"} You will see a response like: ```text Creating service instance INSTANCE_NAME in resource group default of account USER... OK Service instance INSTANCE_NAME was created. Name: INSTANCE_NAME ID: crn:v1:bluemix:public:databases-for-elasticsearch:us-south:a/ 40ddc34a846383BGB5b60e:dd13152c-fe15-4bb6-af94-fde0af5303f4:: GUID: dd13152c-fe15-4bb6-af94-fde0af56897 Location: LOCATION State: provisioning Type: service_instance Sub Type: Public Service Endpoints: private Allow Cleanup: false Locked: false Created at: 2023-06-26T19:42:07Z Updated at: 2023-06-26T19:42:07Z Last Operation: Status create in progress Message Started create instance operation ``` {: codeblock} - To check provisioning status, use the following command: ```sh ibmcloud resource service-instance ``` {: pre} When complete, you will see a response like: ```text Retrieving service instance INSTANCE_NAME in resource group default under account USER's Account as USER... OK Name: INSTANCE_NAME ID: crn:v1:bluemix:public:databases-for-elasticsearch:us-south:a/40ddc34a953a8c02f109835656860e:dd13152c-fe15-4bb6-af94-fde0af5303f4:: GUID: dd13152c-fe15-4bb6-af94-fde5654765 Location: Service Name: databases-for-elasticsearch Service Plan Name: standard Resource Group Name: default State: active Type: service_instance Sub Type: Public Locked: false Service Endpoints: private Created at: 2023-06-26T19:42:07Z Created by: USER Updated at: 2023-06-26T19:53:25Z Last Operation: Status create succeeded Message Provisioning elasticsearch with version 7.17 (100%) ``` {: codeblock} - Optional: To delete a service instance, run the following command: ```sh ibmcloud resource service-instance-delete ``` {: pre} CPU and RAM autoscaling is not supported on Cloud Databases Isolated Compute. Disk autoscaling is available. If you have provisioned an Isolated instance or switched over from a deployment with autoscaling, keep an eye on your resources using [IBM Cloud® Monitoring integration](https://cloud.ibm.com/docs/cloud-databases?topic=cloud-databases-monitoring&format=markdown), which provides metrics for memory, disk space, and disk I/O utilization. To add resources to your instance, manually scale your deployment. {: note} ### The `--parameters` parameter {: #flags-params-service-endpoints} {: cli} The `service-instance-create` command supports a `-p` parameter, which allows JSON-formatted parameters to be passed to the provisioning process. For example, you can pass Cloud Resource Names (CRNs) as parameter values, which uniquely identify a resource in the cloud. All parameter names and values are passed as strings. For example, if a database is being provisioned from a particular backup and the new database deployment needs a total of 12 GB of memory across three members, then the command to provision 4 GBs per member looks like: ```sh ibmcloud resource service-instance-create databases-for-elasticsearch enterprise us-south \ -p \ '{ "backup_id": "crn:v1:blue:public:databases-for-elasticsearch:us-south:a/54e8ffe85dcedf470db5b5ee6ac4a8d8:1b8f53db-fc2d-4e24-8470-f82b15c71717:backup:06392e97-df90-46d8-98e8-cb67e9e0a8e6", "members_memory_allocation_mb": "4096" }' --service-endpoints="private" ``` {: pre} ## Provisioning through the Resource Controller API {: #provision-controller-api} {: api} Follow these steps to provision by using the [Resource Controller API](https://cloud.ibm.com/apidocs/resource-controller/resource-controller){: external}. 1. Obtain an [IAM token from your API token](https://cloud.ibm.com/apidocs/resource-controller/resource-controller#authentication){: external}. 2. You need to know the ID of the resource group that you would like to deploy to. This information is available through the [IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_commands_resource&format=markdown#ibmcloud_resource_groups). Use a command like: ```sh ibmcloud resource groups ``` {: pre} 3. You need to know the region you want to deploy to. To list all of the regions that deployments can be provisioned into from the current region, use the [Cloud Databases CLI plug-in](https://cloud.ibm.com/docs/databases-cli-plugin?topic=databases-cli-plugin-cdb-reference&format=markdown){: external}. The command looks like: ```sh ibmcloud cdb regions --json ``` {: pre} 4. Select the [hosting model](https://cloud.ibm.com/docs/cloud-databases?topic=cloud-databases-hosting-models&interface=api&format=markdown) you want your database to be provisioned on. You can change this later. A host flavor represents fixed sizes of guaranteed resource allocations. To see which host flavors are available in your region, call the [host flavors capability endpoint](https://cloud.ibm.com/apidocs/cloud-databases-api/cloud-databases-api-v5#capability) like this: ```sh curl -X POST https://api.{region}.databases.cloud.ibm.com/v5/ibm/capability/flavors \ -H 'Authorization: Bearer <>' \ -H 'ContentType: application/json' \ -d '{ "deployment": { "type": "elasticsearch", "location": "us-south" } }' ``` {: pre} This returns: ```sh { "deployment": { "type": "elasticsearch", "location": "us-south", "platform": "classic" }, "capability": { "flavors": [ { "id": "b3c.4x16.encrypted", "name": "4x16", "cpu": { "allocation_count": 4 }, "memory": { "allocation_mb": 16384 }, "hosting_size": "xs" }, { "id": "b3c.8x32.encrypted", "name": "8x32", "cpu": { "allocation_count": 8 }, "memory": { "allocation_mb": 32768 }, "hosting_size": "s" }, { "id": "m3c.8x64.encrypted", "name": "8x64", "cpu": { "allocation_count": 8 }, "memory": { "allocation_mb": 65536 }, "hosting_size": "s+" }, { "id": "b3c.16x64.encrypted", "name": "16x64", "cpu": { "allocation_count": 16 }, "memory": { "allocation_mb": 65536 }, "hosting_size": "m" }, { "id": "b3c.32x128.encrypted", "name": "32x128", "cpu": { "allocation_count": 32 }, "memory": { "allocation_mb": 131072 }, "hosting_size": "l" }, { "id": "m3c.30x240.encrypted", "name": "30x240", "cpu": { "allocation_count": 30 }, "memory": { "allocation_mb": 245760 }, "hosting_size": "xl" }, { "id": "multitenant", "name": "multitenant", "cpu": { "allocation_count": 0 }, "memory": { "allocation_mb": 0 }, "hosting_size": "" } ] } } ``` {: pre} As shown, the Isolated Compute host flavors available to a Databases for Elasticsearch instance in the `us-south` region are: - `b3c.4x16.encrypted` - `b3c.8x32.encrypted` - `m3c.8x64.encrypted` - `b3c.16x64.encrypted` - `b3c.32x128.encrypted` - `m3c.30x240.encrypted` To provision or scale your instance to 4 CPUs and `16384` megabytes or RAM, submit the following command: ```sh { "parameters": { "members_host_flavor": "`b3c.4x16.encrypted`" } } ``` {: pre} To scale your instance up to 8 CPUs and `32768` megabytes of RAM, submit the following command: ```sh { "parameters": { "members_host_flavor": "b3c.8x32.encrypted" } } ``` {: pre} 5. Once you have all the information, [provision a new resource instance](https://cloud.ibm.com/apidocs/resource-controller/resource-controller#create-resource-instance){: external} with the IBM Cloud Resource Controller. ```sh curl -X POST \ https://resource-controller.cloud.ibm.com/v2/resource_instances \ -H "Authorization: Bearer " \ -H 'Content-Type: application/json' \ -d '{ "name": "", "target": "", "resource_group": "RESOURCE_GROUP_ID", "resource_plan_id": "" "parameters": { "members_host_flavor": "", "service_endpoints":" ", "version":"" } }' ``` {: pre} To make a Shared Compute instance, follow the following example. Please note that Premium verisons of Elasticsearch are not available on Shared Compute. ```sh curl -X POST \ https://resource-controller.cloud.ibm.com/v2/resource_instances \ -H "Authorization: Bearer " \ -H 'Content-Type: application/json' \ -d '{ \ "name": "my-instance", \ "target": "us-south", \ "resource_group": "", \ "resource_plan_id": "", \ "parameters": { "members_host_flavor": "multitenant", "service_endpoints": "private", "members_memory_allocation_mb": 16384, "members_cpu_allocation_count": 4 } \ }' \ ``` {: pre} Provision a Databases for Elasticsearch Isolated instance with the same `"members_host_flavor"` parameter, setting it to the desired Isolated size. Available hosting sizes and their `members_host_flavor value` parameters are listed in [Table 2](#members_host-flavor-parameter-api). For example, `{"members_host_flavor": "b3c.4x16.encrypted"}`. Note that since the host flavor selection includes CPU and RAM sizes (`b3c.4x16.encrypted` is 4 CPU and 16 RAM), this request does not accept both, an Isolated size selection and separate CPU and RAM allocation selections. ```sh curl -X POST \ https://resource-controller.cloud.ibm.com/v2/resource_instances \ -H "Authorization: Bearer " \ -H 'Content-Type: application/json' \ -d '{ \ "name": "my-instance", \ "target": "us-south", \ "resource_group": "5g9f447903254bb58972a2f3f5a4c711", \ "resource_plan_id": "", \ "parameters": { "members_host_flavor": "b3c.4x16.encrypted", "service_endpoints": "private" } \ }' \ ``` {: pre} The parameters `name`, `target`, `resource_group`, `resource_plan_id`, and `service_endpoints` are all required. {: required} The fields in the command are described in the table that follows. | Field | Description | Flag | |-------|------------|------------| | `NAME` [Required]{: tag-red} | The instance name can be any string and is the name that is used on the web and in the CLI to identify the new deployment. | | | `SERVICE_NAME` [Required]{: tag-red} | Name or ID of the service. For Databases for Elasticsearch, use `databases-for-elasticsearch`. | | | `SERVICE_PLAN_NAME` [Required]{: tag-red} | `enterprise` or `platinum` | | | `TARGET` [Required]{: tag-red} | The region where you want to deploy. To retrieve a list of regions, use the `ibmcloud regions` command. | | | `SERVICE_ENDPOINTS_TYPE` | Configure the [Service endpoints](https://cloud.ibm.com/docs/cloud-databases?topic=cloud-databases-service-endpoints&format=markdown) of your deployment, either `public` or `private`. The default value is `public`. | | | `RESOURCE_GROUP` | The Resource group name. The default value is `default`. | -g | | `--parameters` | JSON file or JSON string of parameters to create service instance | -p | | `members_host_flavor` | To provision an Isolated or Shared Compute instance, use `{"members_host_flavor": ""}`. For Shared Compute, specify a value of `multitenant`. For Isolated Compute, select desired CPU and RAM configuration. For more information, see the table below, or [Hosting models](https://cloud.ibm.com/docs/cloud-databases?topic=cloud-databases-hosting-models&format=markdown).| | | `service-endpoints` [Required]{: tag-red} | Configure the [Service endpoints](https://cloud.ibm.com/docs/cloud-databases?topic=cloud-databases-service-endpoints&format=markdown){: external} of your deployment, either `public`, `private` or `public-and-private`. | | {: caption="Basic command format fields" caption-side="top"} ### The `members host flavor` parameter {: #members_host-flavor-parameter-api} {: api} The `members_host_flavor` parameter defines your Compute sizing. To provision a Shared Compute instance, specify `multitenant`. To provision an Isolated Compute instance, input the appropriate value for your desired CPU and RAM configuration. | **Members host flavor** | **members_host_flavor value** | |:-------------------------:|:---------------------:| | Shared Compute | `multitenant` | | 4 CPU x 16 RAM | `b3c.4x16.encrypted` | | 8 CPU x 32 RAM | `b3c.8x32.encrypted` | | 8 CPU x 64 RAM | `m3c.8x64.encrypted` | | 16 CPU x 64 RAM | `b3c.16x64.encrypted` | | 32 CPU x 128 RAM | `b3c.32x128.encrypted` | | 30 CPU x 240 RAM | `m3c.30x240.encrypted` | {: caption="Host flavor sizing parameter" caption-side="bottom"} CPU and RAM autoscaling is not supported on Cloud Databases Isolated Compute. Disk autoscaling is available. If you have provisioned an Isolated instance or switched over from a deployment with autoscaling, keep an eye on your resources using [IBM Cloud® Monitoring integration](https://cloud.ibm.com/docs/cloud-databases?topic=cloud-databases-monitoring&format=markdown), which provides metrics for memory, disk space, and disk I/O utilization. To add resources to your instance, manually scale your deployment. {: note} ## List of additional parameters {: #provisioning-parameters-api} {: api} In the `--parameters` object you can provide additional information to create your service instance, including: - `backup_id` - A CRN of a backup resource to restore from. The backup must be created by a database deployment with the same service ID. The backup is loaded after provisioning and the new deployment starts up that uses that data. A backup CRN is in the format `crn:v1:<...>:backup:`. If omitted, the database is provisioned empty. - `version` - The version of the database to be provisioned. If omitted, the database is created with the most recent major and minor version. - `disk_encryption_key_crn` - The CRN of a KMS key (for example, [Key Protect](https://cloud.ibm.com/docs/key-protect?topic=key-protect-about&format=markdown)), which is then used for disk encryption. A KMS key CRN is in the format `crn:v1:<...>:key:`. - `backup_encryption_key_crn` - The CRN of a KMS key (for example, [Key Protect](https://cloud.ibm.com/docs/key-protect?topic=key-protect-about&format=markdown)), which is then used for backup encryption. A KMS key CRN is in the format `crn:v1:<...>:key:`. To use a key for your backups, you must first [enable the service-to-service delegation](https://cloud.ibm.com/docs/cloud-databases?topic=cloud-databases-key-protect&interface=api&format=markdown#key-byok). {: note} - `members_memory_allocation_mb` - Total amount of memory to be shared between the database members within the database. For example, if the value is "12288", and there are three database members, then the deployment gets 12 GB of RAM total, giving 4 GB of RAM per member. If omitted, the default value is used for the database type is used. This parameter only applies to `multitenant'. - `members_disk_allocation_mb` - Total amount of disk to be shared between the database members within the database. For example, if the value is "30720", and there are three members, then the deployment gets 30 GB of disk total, giving 10 GB of disk per member. If omitted, the default value for the database type is used. This parameter only applies to `multitenant'. - `members_cpu_allocation_count` - Enables and allocates the number of specified cores to your deployment. For example, to use two dedicated cores per member, use `"members_cpu_allocation_count":"2"`. If omitted, the default Shared Compute CPU:RAM ratios will be applied. This parameter only applies to `multitenant'. ## Provisioning with Terraform {: #provisioning-terraform} {: terraform} Use Terraform to manage your infrastructure through the [`ibm_database` Resource for Terraform](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/database) supports provisioning Cloud Databases deployments. Alternatively, you can use Terraform IBM Modules to manage your infrastructure through [Terraform IBM Modules for Databases for Elasticsearch](https://registry.terraform.io/modules/terraform-ibm-modules/icd-elasticsearch/ibm/latest){: external}. Select the [hosting model](https://cloud.ibm.com/docs/cloud-databases?topic=cloud-databases-hosting-models&interface=terraform&format=markdown) you want your database to be provisioned on. You can change this later. ### Provisioning Shared Compute with Terraform {: #provisioning-shared-compute-terraform} {: terraform} Provision a Databases for Elasticsearch Shared hosting model instance with the `"host_flavor"` parameter set to `multitenant`. See the following example: ```terraform data "ibm_resource_group" "group" { name = "" } resource "ibm_database" "" { name = "" plan = "standard" location = "eu-gb" service = "databases-for-elasticsearch" resource_group_id = data.ibm_resource_group.group.id service_endpoints = "private" tags = ["tag1", "tag2"] adminpassword = "password12" # Pin the database version at provision time. # If omitted, the newest available major/minor is selected (per service behavior). version = "" # e.g. "8.19" for Elasticsearch preferred major group { group_id = "member" host_flavor { id = "multitenant" }, cpu { allocation_count = 6 } memory { allocation_mb = 24576 } disk { allocation_mb = 256000 } } users { name = "user123" password = "password12" } allowlist { address = "172.168.1.1/32" description = "desc" } } output "ICD Elasticsearch database connection string" { value = "http://${ibm_database.test_acc.ibm_database_connection.icd_conn}" } ``` {: codeblock} ### Provisioning Isolated Compute with Terraform {: #provisioning-isolated-computer-terraform} {: terraform} Provision a Databases for Elasticsearch Isolated instance with the same `"host_flavor"` parameter, setting it to the desired Isolated size. Available hosting sizes and their `host_flavor value` parameters are listed in [Table 1](#host-flavor-parameter-terraform). For example, `{"host_flavor": "b3c.4x16.encrypted"}`. Note that since the host flavor selection includes CPU and RAM sizes (`b3c.4x16.encrypted` is 4 CPU and 16 RAM), this request does not accept both, an Isolated size selection and separate CPU and RAM allocation selections. ```terraform data "ibm_resource_group" "group" { name = "" } resource "ibm_database" "" { name = "" plan = "standard" location = "eu-gb" service = "databases-for-elasticsearch" resource_group_id = data.ibm_resource_group.group.id service_endpoints = "private" tags = ["tag1", "tag2"] adminpassword = "password12" # Pin the database version at provision time. # If omitted, the newest available major/minor is selected (per service behavior). version = "" # e.g. "8.19" for Elasticsearch preferred major group { group_id = "member" host_flavor { id = "b3c.8x32.encrypted" } disk { allocation_mb = 256000 } } users { name = "user123" password = "password12" } allowlist { address = "172.168.1.1/32" description = "desc" } } output "ICD Elasticsearch database connection string" { value = "http://${ibm_database.test_acc.ibm_database_connection.icd_conn}" } ``` {: codeblock} ### The `host flavor` parameter {: #host-flavor-parameter-terraform} {: terraform} The `host_flavor` parameter defines your Compute sizing. - **Shared compute** - To provision a Shared Compute instance, specify `multitenant`. - **Isolated compute** - To provision an Isolated Compute instance, input the appropriate value for your desired CPU and RAM configuration. See the values in the following table. | **Host flavor** | **host_flavor value** | |:-------------------------:|:---------------------:| | Shared compute | `multitenant` | | 4 CPU x 16 RAM | `b3c.4x16.encrypted` | | 8 CPU x 32 RAM | `b3c.8x32.encrypted` | | 8 CPU x 64 RAM | `m3c.8x64.encrypted` | | 16 CPU x 64 RAM | `b3c.16x64.encrypted` | | 32 CPU x 128 RAM | `b3c.32x128.encrypted` | | 30 CPU x 240 RAM | `m3c.30x240.encrypted` | {: caption="Host flavor sizing parameter" caption-side="bottom"} CPU and RAM autoscaling is not supported on Cloud Databases Isolated Compute. Disk autoscaling is available. If you have provisioned an Isolated instance or switched over from a deployment with autoscaling, keep an eye on your resources using [IBM Cloud® Monitoring integration](https://cloud.ibm.com/docs/cloud-databases?topic=cloud-databases-monitoring&format=markdown), which provides metrics for memory, disk space, and disk I/O utilization. To add resources to your instance, manually scale your deployment. {: note}