Skip to main content

Getting started with Civo Database

We do all the heavy lifting as our database service significantly lowers the administrative burden, allowing you to focus on developing applications.

Launching a database on Civo has a few specific requirements depending on if you are using MySQL or PostgreSQL. The documentation below covers the main options available for database launch.

Launch your first database on the dashboard

Begin by selecting the database section in the left-hand navigation & click the "Launch my first database" button.

Databases screen

This will take you to the "Create a new database" page:

Create a new database

The numbered sections give you options for the specifications of your new database.

1. Name

Add your database name here. This is a reference and must be unique within the Civo region you are using.

2. Network

When you create a database, you can assign it to a specific network. For more information, refer to the documentation on private networks.

3. Firewall

To set your database firewall, we give you 2 options:

  • Choose an existing firewall from a dropdown list.

  • Create a new firewall directly in the Database UI:

Database firewall creation options


By taking the second option, you acknowledge you will have to configure the firewall yourself and open all ports to all traffic until you do so.

In the example above, Civo Database gives you 2 options between processing opening a network port for MySQL traffic in a firewall or security group configuration:

  • Open port 3306 for MySQL traffic: open port 3306 to all incoming traffic, allowing any IP address to connect to the MySQL or PostgreSQL service running on the server. This is useful when you need to allow connections from multiple IP addresses, such as when running a public-facing service.
  • Open port 3306 for MySQL access from my IP only: would restrict access to port 3306 to a specific IP address, by default the address you are connecting from. This is useful when you want to limit access to the MySQL or PostgreSQL services to a specific machine or network, such as for security reasons or when testing connectivity from a specific location.

4. Software

Currently, we offer two different types of database software: MySQL and PostgreSQL.

Database software

5. Size and pricing

Choose the RAM, CPU, and NVMe storage size needed for your new database.

Database sizing options screen


Best practices

  • Consider the size and complexity of your data.
  • Evaluate the expected workload on your database.
  • Keep in mind that you can easily scale horizontally by adding new nodes.
  • Start with a size that you think will work well for your current needs.
  • Adjust resources as necessary based on performance metrics and workload changes.

By choosing your RAM, CPU, and NVMe storage size, you will have full transparency on the cost of your database displayed hourly or monthly. For more information on our pricing, visit Civo’s pricing page. For billing information, refer to billing documentation.

6. Additional nodes

Civo Database provides scalable managed PostgreSQL and MySQL databases that are automatically backed up nightly. They are always-on, and for further peace of mind, you can choose to run additional nodes for your databases.

Select if you would like to add additional nodes to your database. We give you the option to add 2 or 4 additional nodes. Note that this will impact the price charged for your database.

Additional nodes dropdown


Why add nodes?

There are several reasons why one might add additional nodes to a database:

  • Scalability: As a database grows in size and complexity, it may become necessary to add more nodes to ensure that it can handle an increasing amount of data and traffic. Adding more nodes allows for the workload to be distributed across the cluster, which can increase performance and reduce the risk of bottlenecks.

  • Fault tolerance: By adding additional nodes, a database can be made more resilient to hardware failures, network outages, and other issues that can impact availability. With multiple nodes, the database can continue to operate even if one or more nodes fail.

  • Improved analytics: In some cases, adding more nodes can help to support advanced analytics and data processing tasks, such as machine learning and predictive modeling. With more nodes, data can be processed faster, enabling more sophisticated analysis and modeling.

Finally, click on "Create database" to make the magic happen!

Create database

Once your database is created, see the following links for connecting to your database:

7. (OPTIONAL) Connecting your Database to Kubernetes

PREREQUISITE: In order to proceed, you must have your Database connection details in order to proceed (e.g. hostname, port, database name, username, password)

Create a Secret in Kubernetes for Database Credentials: To securely store your database credentials, create a Kubernetes secret.

Create a YAML file for the secret:

apiVersion: v1
kind: Secret
name: db-credentials
type: Opaque
username: <base64_encoded_username>
password: <base64_encoded_password>
hostname: <base64_encoded_hostname>
port: <base64_encoded_port>
dbname: <base64_encoded_dbname>

NOTE: Replace the placeholders with your actual credentials encoded in base64. You can encode your credentials using echo -n 'your_value' | base64

Apply the secret to your cluster:

kubectl apply -f db-credentials.yaml

Configure Your Application to Use the Database Now, you need to update your Kubernetes deployment or pod configuration to use the database credentials stored in the secret.

Modify your deployment YAML file to include the environment variables:

apiVersion: apps/v1
kind: Deployment
name: your-app
replicas: 1
app: your-app
app: your-app
- name: your-container
image: your-image
name: db-credentials
key: username
name: db-credentials
key: password
name: db-credentials
key: hostname
- name: DB_PORT
name: db-credentials
key: port
- name: DB_NAME
name: db-credentials
key: dbname

Apply the updated deployment to your cluster:

kubectl apply -f your-deployment.yaml

After deploying your application, ensure that it can connect to the managed database. You can check the logs of your application pods to verify the connection.

kubectl logs -l app=your-app

Look for any error messages related to database connectivity. If everything is configured correctly, your application should be able to communicate with the managed database.