Severalnines Blog
The automation and management blog for open source databases

How to configure access credentials in NinesControl

Posted in:

Once you have created an account on NinesControl, you need to configure NinesControl to access the cloud in which your databases will run. You need to define access credentials for your cloud account. In this blog post we’ll show you how to configure access to DigitalOcean and AWS.


To configure NinesControl to access DigitalOcean, you first need to be logged into your DigitalOcean account. Next, go to the API section.

Once there, click on “Generate New Token” to create a new token for NinesControl. You will be asked to pick a name for the token and scopes - make sure both read and write are included. When you are ready, click “Generate Token”.

New token will be created - it takes a form of alphanumeric string which you can copy to your clipboard.

Next, go to your NinesControl account, go to Cloud Accounts -> DigitalOcean and add your token. Save credentials afterwards.

That’s it, now you can deploy MySQL and MongoDB clusters on DigitalOcean.

Amazon Web Services

To configure NinesControl to access AWS, you first need to create an IAM user. NinesControl will use IAM to deploy your databases on AWS. When you are logged into your AWS account, you can find the IAM section under “Services”.

Next, you need to click on “Users” to create a new user. Fill the name and create it.

After you create it, you can download your credentials for further use. You can also copy the Access Key ID and Secret Access Key. You’ll need them later in NinesControl.

After we create the user, we need to grant correct privileges.The user should appear in the list. If needed, you can always use filter box as shown below to find it.

Once you found the user, click on it. Go to the “Permissions” tab and click on “Attach Policy” button. (Note: This is not the only way to grant privileges - you can also create a group with the required permissions and then assign user to such group. We won’t cover this method in this blog)

A policy that we need to attach is called “AmazonEC2FullAccess”. You can find it on the list or use the filter field to show just that policy.

Once this is done, your user is ready to be used in NinesControl. Log in to NinesControl, go to Cloud Accounts and pick Amazon AWS as provider. You will have to fill in some data like name of the credentials as showed in NinesControl, region in which the cluster should be deployed and, finally, credentials themselves - Access Key and Secret Key for your IAM.

When you accomplish this, you should be able to deploy your databases on Amazon Web Services. Deployment will be covered in a separate blog post, for now we’d like to add that, at the first deployment, you will have to create new VPC and subnet by clicking on “[Add]” next to Vpc and Subnet fields.

That’s it. You have now configured NinesControl to access AWS and will be able to deploy MySQL and MongoDB clusters on AWS.

Related Post

MySQL on Docker: Composing the Stack

Docker 1.13 introduces a long-awaited feature called Compose-file support. Compose-file defines everything about an application - services, databases, volumes, networks, and dependencies can all be defined in one place.  In this blog, we’ll show you how to use Compose-file to simplify the Docker deployment of MySQL containers.

Posted in:

How to deploy and manage MySQL multi-master replication setups with ClusterControl 1.4

MySQL replication, while simple and popular, may come in different shapes and flavors. Master slave or master master topologies can be configured to suit your environment.  ClusterControl 1.4 brings a list of enhancements to deploy and manage different types of MySQL replication setups. This blog outlines the different topologies that can be deployed, the merits of each topology, and shows how each can be managed in a live environment.

Posted in:

Automatic failover of MySQL Replication - New in ClusterControl 1.4

MySQL replication setups are inevitably related to failovers - what do you do when your master fails and your applications are not able to write to the database anymore? Automated failover is required if you need to quickly recover an environment to keep your database up 24x7. This blog post discusses this new replication feature recently introduced in ClusterControl 1.4.

Posted in:

Automating MySQL Replication with ClusterControl 1.4.0 - what’s new

This blog post will go through new replication features in ClusterControl 1.4.0, including enhanced multi-master deployment, managing replication topology changes, automated failover and handling of replication errors.

Posted in: