Create MySQL Cloud Service: Service Details Page

Service Details is a page in the Create MySQL Cloud Service wizard you use to create a new database deployment. For more information, see Creating a MySQL Server Deployment.

What You See on the Service Details Page

The following table describes the key information shown on the Service Details page.

Element Description

Shape

The number of Oracle Compute Units (OCPUs) and amount of memory (RAM) for each compute node of the new database deployment. MySQL Cloud Service offers several OCPU/RAM combinations, as described in Computing Power.

SSH Public Key

Edit

The SSH public key to be used for authentication when using an SSH client to connect to a compute node of the new deployment.

Click Edit to specify the public key, either by uploading a file containing the public key value or by pasting in the value of a public key.

If you paste in the value, make sure the value does not contain line breaks or end with a line break.

Usable Database Storage (GB)

The amount of storage in GB for actual database data.

Administration User

The name of the MySQL Database Server administration user. Default is root.

Administration Password

Confirm Password

The password for the MySQL Database administrative users:

The password:

  • Must be 8 to 30 characters in length.

  • Must contain at least one lowercase letter

  • Must contain at least one uppercase letter

  • Must contain at least one number

  • Must contain at least one of these symbols: _ (underscore), # (hash sign), or $ (dollar sign).

Database Schema Name

The name for the database instance. This name:

  • Must not exceed 64 characters. Can contain letters, numbers and special characters (_,$).

  • Must start with a letter.

  • Must contain only letters, numbers, or these symbols: _ (underscore), # (hash sign), or $ (dollar sign).

Server Character Set

The character set used by the server.

Timezone

Select a timezone for the MySQL server. The default is SYSTEM which sets the timezone of the MySQL server to the same value used by the compute node. See MySQL Cloud Service Supported Timezonesfor a complete list.

MySQL Port

The port on which the server listens. The range of available ports is 3200 to 3399. The default is 3306.

Configure Enterprise Monitor

Controls whether MySQL Enterprise Monitor is installed. Select Yes to install, No to decline.

Manager User

User name of the MySQL Enterprise Monitor’s manager user.

Manager Password

Confirm Manager Password

The password for the manager user.

The password you enter:

  • Must be 8 to 30 characters in length.

  • Must contain at least one lowercase letter

  • Must contain at least one uppercase letter

  • Must contain at least one number

  • Must contain at least one of these symbols: _ (underscore), # (hash sign), or $ (dollar sign).

Agent User

Name of the Agent user. This user is used by the MySQL Enterprise Agents to connect to the MySQL Service Manager and relay the information collected about the host on which the agent is installed and any MySQL instances installed on that host.

Note:

No agent installations are provided at this time. It is currently only possible to install the MySQL Enterprise Service Manager, which can monitor any MySQL instances, local or remote, using a built-in agent.. If you want to monitor MySQL instances installed on other MySQL Cloud Service instances, you can configure the MySQL Service Manager to monitor them, but cannot monitor a remote host’s operating system, file system, or network interfaces. Although agent installations are not currently possible, it is mandatory to define an Agent User and Password to properly configure the MySQL Enterprise Monitor. These parameters can be changed later.

Agent Password

Confirm Agent Password

The password for the agent user.

The password you enter:

  • Must be 8 to 30 characters in length.

  • Must contain at least one lowercase letter

  • Must contain at least one uppercase letter

  • Must contain at least one number

  • Must contain at least one of these symbols: _ (underscore), # (hash sign), or $ (dollar sign).

Backup Destination

Controls how backups for the deployment are to be configured:

  • Both Cloud Storage and Local Storage—backups are configured to be created automatically and stored both on local storage and on an Oracle Storage Cloud Service container.

  • None—backups are not configured.

  • Cloud Storage Only—backups are configured to be created automatically and stored in an Oracle Storage Cloud Service container. No local backup is created for this option.

For more information about backups and backup configurations, see About Backing Up Databases on MySQL Cloud Service.

Cloud Storage Container

The URL where backups to cloud storage are to be stored. :

  • For database deployments in Oracle Cloud Infrastructure, enter the URL of an existing Oracle Cloud Infrastructure Object Storage bucket. The URL is of the form:

    https://swiftobjectstorage.region.oraclecloud.com/v1/account/bucket

    For example:

    https://swiftobjectstorage.us-phoenix-1.oraclecloud.com/v1/mycompany/mybucket

    You must create this storage bucket before you begin creating the database deployment. See Object Storage API in Oracle Cloud Infrastructure documentation.

  • For database deployments in Oracle Cloud Infrastructure Classic, enter the URL of an Oracle Cloud Infrastructure Object Storage Classic container. The URL is of the general form:

    https://storage-instance-specifier/container

    The field is populated with the default URL of the storage associated with your ID domain and the container name MySQLCS. For example, assuming an ID domain named testDomain:

    https://testDomain.storage.oraclecloud.com/v1/Storage-testDomain/MySQLCS

    Note:

    If the account does not include an Object Storage service entitlement or if the region selected is an Oracle Cloud Infrastructure region, the container field is not autopopulated.

    The Create Cloud Storage Container checkbox is enabled by default to create the container the first time a MySQL Cloud Service instance is created on the ID domain. To use a different name, change the container string to the desired container name.

    Note:

    Do not use the storage container that you are using to back up MySQL Cloud Service deployments to cloud storage for any other purpose. For example, do not also use it to back up Oracle Java Cloud Service instances to cloud storage. Using the container for multiple purposes can result in billing errors.

    To determine the storage-instance-specifier value for your account, see About REST URLs for Oracle Storage Cloud Service Resources in Using Oracle Cloud Infrastructure Object Storage Classic.

Cloud Storage User Name

The user name of a user who has read/write access to the specified Oracle Storage Cloud Service container.

  • For database deployments in Oracle Cloud Infrastructure, enter the user name you use to sign in to the Oracle Cloud Infrastructure console.

  • For database deployments in Oracle Cloud Infrastructure Classic, enter the Oracle Cloud user name of the administrator of the Oracle Cloud Infrastructure Object Storage Classic container specified in Cloud Storage Container. Usually, this is your Oracle Cloud user name.

Cloud Storage Password
The password necessary to access the location specified in Cloud Storage Container.

  • For database deployments in Oracle Cloud Infrastructure, enter the Auth Token generated in Oracle Cloud Infrastructure for the user that you specified. For more information, see Prerequisites for Oracle Platform Services on Oracle Cloud Infrastructure in the Oracle Cloud Infrastructure documentation.

  • For database deployments in Oracle Cloud Infrastructure Classic, enter the password of the Oracle Cloud user specified in Cloud Storage User Name.

Create Cloud Storage Container

(Not available on Oracle Cloud Infrastructure) Enabled by default. Create a new Oracle Cloud Infrastructure Object Storage Classic container as part of the database deployment creation, if the container does not exist already. Specify the container name and the Cloud Storage user name and password in the preceding fields.

Create Instance from Existing Backup

If Yes is selected, enables you to populate, or initialize, the new database with the data stored in an existing backup, in cloud storage.

Backup File Cloud Storage Path

The path to the backup file.

Username

The cloud storage user name.

Password

The cloud storage password.

Cancel

Click to cancel the wizard without creating a new database deployment.

Next

Click to advance to the Confirmation page.