Provisioning

Service details

• 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, specify the resource group in this field. Otherwise, you can leave it at default. For more information, see Managing resource groups.
• Location: The deployment's public cloud region or Satellite location.

Hosting model

• 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 EnterpriseDB is only available on Isolated Compute.

For more information, see Hosting models.

Resource allocation

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.

Specify the disk size depending on your requirements. It can be increased after provisioning but cannot be decreased to prevent data loss.

Service configuration

• Database Version: Set only at deployment 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 Database Versioning Policy.
• Encryption: If you use Key Protect, 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 Configure the Service endpoints on your deployment. The default setting is private.

After you select the appropriate settings, click Create to start the provisioning process.

Create a service instance through the CLI

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

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 ke(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
   

2. Provision your database with the following command:

   ibmcloud resource service-instance-create <INSTANCE_NAME> <SERVICE_NAME> <SERVICE_PLAN_NAME> <LOCATION> <RESOURCE_GROUP> -p '{"members_host_flavor": "<members_host_flavor value>"}' --service-endpoints="<endpoint>"
   

   With EnterpriseDB, the Shared Compute host flavor is not available. Provision a {{site.data.keyword.databases-for-enterpriseDB}} 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.
   

   ibmcloud resource service-instance-create test-database databases-for-enterprisedb standard us-south -p `{"members_host_flavor": "<host_flavor value>"}` --service-endpoints="<endpoint>"
   

   The fields in the command are described in the table that follows.

   Basic command format fields

   Field	Description	Flag
   NAME Required	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	Name or ID of the service. For Databases for EnterpriseDB, use databases-for-enterprisedb.
   SERVICE_PLAN_NAME Required	Standard plan (standard).
   LOCATION Required	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
   host_flavor	For Shared Compute, specify multitenant. To provision an Isolated Compute instance, use {"members_host_flavor": "<host_flavor value>"}. The host_flavor value parameter defines your Isolated Compute sizing. For more information, see Hosting models.
   --service-endpoints Required	Configure the Service endpoints of your deployment, either public, private or public-and-private.

The host_flavor parameter defines your Compute sizing. Input the appropriate value for your desired size.

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, which provides metrics for memory, disk space, and disk I/O utilization. To add resources to your instance, manually scale your deployment.

You will see a response like:

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-enterprisedb:us-east: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

1. To check provisioning status, use the following command:

   ibmcloud resource service-instance <INSTANCE_NAME>
   

   When complete, you will see a response like:

   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-enterprisedb:us-east:a/40ddc34a953a8c02f109835656860e:dd13152c-fe15-4bb6-af94-fde0af5303f4::
   GUID:                  dd13152c-fe15-4bb6-af94-fde5654765
   Location:              <LOCATION>
   Service Name:          databases-for-enterprisedb
   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 enterprisedb with version 12 (100%)
   

2. (Optional) Deleting a service instance. Delete an instance by running a command like this one:

   ibmcloud resource service-instance-delete <INSTANCE_NAME>
   

The --parameters parameter

The service-instance-create command supports a -p flag, which allows JSON-formatted parameters to be passed to the provisioning process. Some parameter values are Cloud Resource Names (CRNs), 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 9 GB of memory across three members, then the command to provision 3 GBs per member looks like:

ibmcloud resource service-instance-create databases-for-enterprisedb <SERVICE_NAME> standard us-south \
-p \ '{
  "backup_id": "crn:v1:blue:public:databases-for-enterprisedb:us-south:a/54e8ffe85dcedf470db5b5ee6ac4a8d8:1b8f53db-fc2d-4e24-8470-f82b15c71717:backup:06392e97-df90-46d8-98e8-cb67e9e0a8e6",
  "members_memory_allocation_mb": "3072"
}' --service-endpoints="private"