The Relational Database (RDB) service automatically creates a database entity for your project. It is possible to create several entities within one project/region.
- Cloud Computing Service (C2S)
- Cloud Networking Service (CNS)
- Cloud Block Storage Service (CBS)
- Infrastructure Scheduling Service (CRON)
- Cloud Security Service(CS2)
- Cloud Identity Service (SSH)
- Auto Configuration Service (ACS)
- Terraform As A Service(TAS)
- Telemetry As A Service (TMS)
- Cloud Monitoring Service (CMS)
- CloudWach & SSM (SSM)
- Cloud Formation Service (CFS)
- Log Aggregation Service (LAS)
- Load Balancer Service (LBS)
- Relational Database Service (RDB)
- Docker Service (DOS)
- OpenShift as a Sevice (OSS)
- Kubernetes as a Service (KUB)
- Hybris as a Service (HAS)
- Magento as a Service (MAS)
- Jenkins as a Service (JaS)
- Gerrit as a Service (GAS)
- Sonar as a Service (SQS)
- Artifactory as a Service (AFS)
- Sitecore as a Service (SAS)
- Messaging Service (MES)
- Ambari Service (AAS)
- Cloud Support Service (CSS)
Relational Database Service (RDB)
This topic contains the following sections:
Have a Question?
The current page gives the general information on the service and the main workflows. However, while working with the services, our users encounter new questions they need assistance with. The most frequently asked questions on EPAM Cloud Services are gathered on the Cloud Services FAQ page. Visit the page to check whether we have a ready answer for your question.
Related CLI Commands
The table below provides the list of service-related commands and their descriptions:
|or2-manage-rdb --action [describe, install, remove]||or2rdb||Starts the service in the specified project and region|
Further on this page, you can find more details on the RDB service manipulation.
The service is available only in EPAM regions. Still, it is similar to AWS RDS service, and the set of the databases provided by the two platforms is the same. The table below contains the list of databases supported by EPAM Orchestrator, and their versions, as well as the host VM configurations:
|Database||PostgreSQL||MySQL||MariaDB||Oracle||MS SQL Server|
|Host VM Shape||Medium||Medium||Medium||Medium||Medium|
|Host VM Image||Ubuntu16.04 64-bit||Ubuntu16.04 64-bit||Ubuntu16.04 64-bit||OracleLinux7 64-bit||W2012R2Std (for 2012)|
Service Activation and Manipulation
The service is manipulated with the or2-manage-rdb (or2rdb) command with different --action/-a parameter values (describe, install, remove).
All you have to do to start the service is run the command with the following parameters:
or2rdb -p project -r region -a install -t type [-n db_name] -u db_username [-pwd db_password] [-d description] [-f file_path]
|-a install||Obligatory parameter; the action parameter specifying that a new database instance should be created.|
|-t type||Obligatory parameter; the type of the database to be installed (mysql, mssql, postgresql, oracle, mariadb).|
|-u db_username||Obligatory parameter; the username that will be used to login to the created database.|
|-n db_name||Optional parameter; the name of the database to be created; if not specified, will be generated automatically.|
|-pwd db_password||Optional parameter; the password to be used to login to the created database. If not specified, a random password will be generated.|
|-d description||Optional parameter; the description of the new database.|
|-f file_path||The parameter specifying the path to the initialization script used for database configuration.|
When the command is launched, Orchestrator runs a virtual machine corresponding to the selected database, attaches three 100GB volumes to it, installs the necessary database and applies all the settings.
An extended system disk can be used instead of attaching three additional 100GB storages for MySQL and MS SQL databases. The allowed system disk sizes are 100, 200, 300, and 500 GB. To use this option, add the --use-sys-disk-size parameter to the or2-manage-rdb (or2rdb) command at the service start:
or2rdb -p project -r region -a install -t type [-n db_name] -u db_username [-pwd db_password] [-d description] [-f file_path] --use-sys-disk-size 200
To deactivate the RDB service, run the same or2rdb command with the -a remove option. This command deactivates the service and terminates the virtual machine created for it:
or2rdb -p project -r region -a remove -S service_id
MS SQL with Guaranteed Capacities
In addition to databases hosted on virtual machines, EPAM Cloud offers the option of creating MS SQL instances on hardware servers. This way, the capacity of the database is always guaranteed, which may be one of the critical factors of its reliable performance. In addition, MS SQL instance deployment on a hardware server is faster and easier.
The hardware servers used for database hosting are specially configured for this purpose and have independent disk subsystems. EPAM Cloud supports guaranteed capacities for MS SQL 2014 instances which, when requested via the Orchestrator, will be deployed on a dedicated hardware DBMS server.
To order an MS SQL 2014 instance with guaranteed capacities, run the or2-manage-rdb (or2rdb) command with the following parameters:
or2rdb -p project -r EPAM-BY1 -v 2014 -s 50
- -r EPAM-BY1 - the virtualization region. The service is available only in EPAM-BY1
- -v 2014 - version number. Specify 2014 to order a MS SQL 2014 instance with guaranteed capacity. If other version is specified, the standard VM-based service will be launched
- -s 50 - database disk quota limit, in GB. Allowed values: 50, 100, 150. If not specified, the storage size will be set to 100
The default maximum memory size used for one database instance is 4GB and currently cannot be changed.
When ordering an MS SQL 2014 instance, you do not have to specify user name and password. Instance users have dbcreator rights and can access database by using their domain credentials. Still, if you do not want to use your domain credentials (Windows authorization), you can use the login and password generated during the service activation (use SQL authorization).
The instance connection information can be found in or2-manage-rdb (or2rdb) command with -a describe parameter:
or2rdb -p project -r region -a describe
Please note that the service has a specific billing approach. Typically, platform services in EPAM Cloud are billed according to the price of resources needed to run these servers.
As MS SQL 2014 database instances are based on hardware, their pricing policy differs. Their billing directly depends on the used storage volume, as it is calculated according to the following scheme:
|DB Storage Volume||Creation Fee (one-time)||Monthly Price|
Login to the DB
When the configuration is complete, you can login to your instance and start using the database with the credentials specified/generated during the service start.
Please note, that if you run the service with MSSQL, you have admin access to the whole MSSQL instance and can login to it using your domain credentials.
More information on the RDB Service can be found in the EPAM Cloud Services Guide. For detailed description of the Maestro CLI commands used to manage the RDB Service, refer to the Maestro CLI User Guide.
The service usage price is defined by the price of the VM on which the DB is hosted and all the attached storages.
For example, the parameters of a VM hosting a My SQL database are as follows:
- Shape: MEDIUM
- Image: Ubuntu16.04_64-bit
- Additional Storages: 3x100GB
Therefore, the approximate monthly cost of one RDB instance in case of 100% and 24/7 load is about $71.53 in EPAM-BY2 region (as of 08/07/2018). The price may vary depending on the region and the selected database. To get more detailed estimations, please use our Cost Estimator tool. To estimate the price of the AWS-based infrastructure you plan to create, you can use the AWS Simple Monthly Calculator.