1. Home
  2. Docs
  3. CCX
  4. How-To
  5. Deployment
  6. Deploying a database in AWS

Deploying a database in AWS

Interfacing With CCX UI

A database in CCX is called as “Data Store” for which you have to deploy, setup, and configure in order to use and interface with your application.

 

To deploy, simply hit Create data store

Create Data Store
or hit the Create drop down button as shown below:

Create Data Store

After clicked, panel view to choose your desired database as shown below will show up.

Select A Database

Select a database - MySQL

In this example, we’re picking up MySQL with supported vendor and version Percona Server 8.0 for replication. Hit Continue to proceed to Configuration as shown below.

Configuration

Create Data Store - MySQL

Configuration: Creating a MySQL 8 datastore [Summary]

Field Description
Name
  • The name of this data store. This name can NOT be changed later.
Tags
  • Specify tags to allow filtering and searching for clusters. Each cluster can have zero or many tags to help keep the clusters organized. Note that special characters like spaces, tabs and dollar signs are not supported.
  • The created tags can be filtered while looking up the clusters in the CCX dashboard page, by clicking on the magnifier glass icon on the top menu.
Configuration
  • Multi-Master. If your setup requires to have more than one active-writer nodes, then choose this configuration. It will deploy Percona XtraDB Cluster
  • Master/Replicas. If you have only one active-writer node and have secondary as your replica, then choose this configuration. It will deploy a Percona Server.
Number of Nodes
  • Allows you to choose the number of nodes that you wanted to deploy.
    • For MySQL Multi-Master, you can choose from 1 master node or 3 multi-master nodes.
    • For Master/Replicas, you can choose from 1 master node or 1 master and 2 replicas

Cloud Service

Currently, CCX supports only Amazon Web Services and Safespring. For more information about supported cloud providers and its supported regions, please go to Cloud Providers. To choose which cloud provider you have subscribed, simply pick the Cloud service provider, then choose the region you would like to deploy your data store. After that, hit Continue.

Select Cloud Service - MySQL

Cloud Service: Creating a MySQL 8 datastore [Summary]

Field Description
Cloud service provider
  • Choose the supported cloud providers.
Regions
  • Choose a region where you would want the database cluster to be deployed.

Instances

This is the section where you have to determine the resources of your database nodes to be deployed such as CPU, memory, and storage.

Configure your instance resources

Instances: Creating a MySQL 8 datastore [Summary]

Field Description
Instances
  • Pick your instance size with predefined CPU and memory.
    • Small, Medium, and Large are enabled by default
    • X-Large and 2X-Large are disabled and requires you to contact our Sales.
Storage
  • Choose the supported volume type for the selected cloud platform.
    • GP2: General Purpose SSD
    • IO1: Provisioned IOPS SSD (99.8% – 99.9% durability)
Storage Size (Gib)
  • The volume size. The minimum and maximum database sizes are depending on the volume type.
    • GP2 – 1 GiB – 16 TiB
    • IO1 – 4 GiB – 16 TiB

Network settings

This is the section where you have to define what type of accessibility does your database nodes required. Does it have to be located on a private network, or shall be access publicly or open to the world provided your security such as firewall and password are setup.

Network settings: Creating a MySQL 8 datastore [Summary]

Field Description
Network Type
  • Choose the networking type:
    • Private: All nodes will be configured with a private IP address. To connect to the data store, you need to peer with the created VPC. See VPC and VPC Peering.
    • Public: All instances will be deployed with public IP addresses. Access to the public IP addresses is controlled by a firewall.
Availability zone
  • Choose the availability zone (AZ) for every node in the cluster.
    • Single AZ
      • Allows you to assign and choose one availability zone only for which your database node will be located and deployed
    • Multi AZ
      • Allows you to assign and choose up to three availability zones. For which you can designate which AZ your database node shall be located and deployed
Select VPC
  • Choose the VPC of that particular region. Only available if you choose Private under the Network.
  • If you do not see the VPC in the drop-down, create a VPC beforehand. See VPC and VPC Peering.
Select a zone
  • Choose which AZ would you like to assign your database nodes for high availability
    • For Single AZ, you can only pick one AZ available on the region
    • For Multi-AZ, you can assign up to three AZ depending on the region you designate your database to be located.

Preview

Before deploying your data store, CCX will give you a preview of your desired selections and options you have configured for your data store. This is the section where it summarizes the value you have assigned to its designated sections before deployment.

Preview of your datastore deployment in CCX - MySQL

Preview: Creating a MySQL 8 datastore [Summary]

Field Description
Database
  • The type of database you choose. In this example, we have MySQL 8
Configuration
  • Summarizes the configuration you have set
Cloud Service
  • Shows the cloud service provider you choose and to what region your database nodes shall be deployed and located.
Instance
  • Summarizes the type of resources (CPU, memory, storage) of your database instances to be used for your data store
Network settings
  • Shows the accessibility of your data store, if it’s private or public.
  • Shows the kind of availability whether it is only assigned to be single zone or is it on a multi-zone location.
  • Shows also the availability zone to which your database nodes shall be located
Estimated cost
  • summarizes the cost for this type of database, setup, and configuration in a monthly basis. This gives you a heads up of what amount it shall cost you before deploying your database.
Was this article helpful to you? Yes No