DBaaS

DBaaS, E2E’s Database as a Service, runs MySQL, MariaDB, or PostgreSQL for you. Each database server you create is a DBaaS instance. Create one from MyAccount, and you get an endpoint and a port to connect to with the username and password you set. You manage the data, and E2E runs the server underneath it.

What you can do

• Create a DBaaS instance running MySQL, MariaDB, or PostgreSQL.
• Connect to a DBaaS instance with the client tool you already use.
• Import a database into a DBaaS instance to move an existing application’s data in, and Manage database users on a DBaaS instance to give each application its own user.
• Start, stop, and restart a DBaaS instance, and Delete a DBaaS instance when you have finished with it.
• Move a DBaaS instance to another project in the same account.
• Expand a DBaaS instance’s disk space as your data grows, or Upgrade a DBaaS instance’s plan for more vCPUs and RAM.
• Move a DBaaS instance to a newer engine version to run a newer release.
• Whitelist an IP address for a DBaaS instance to choose which addresses can connect through the Endpoint, and Attach a VPC to a DBaaS instance for private access from your own network.
• Monitor a DBaaS instance and set alerts to get an email when a metric meets a condition you set, and read its monitoring graphs and slow query log.
• Back up and restore a DBaaS instance with snapshots, or Schedule automatic snapshots, for backup and recovery.
• Export logs to Object Storage from a running DBaaS instance.
• Create a Read Replica to take read traffic off the primary DBaaS instance.
• Enable SSL on a DBaaS instance to encrypt the connection.
• Create and edit a parameter group to set engine configuration values.
• Install a PostgreSQL extension to add an extension to a PostgreSQL DBaaS instance from its Extensions tab.
• Convert a DBaaS instance to a committed plan for a lower rate over a fixed period.

Who it is for

Use DBaaS for any application that keeps its data in MySQL, MariaDB, or PostgreSQL. Common uses:

• The data layer of a web or mobile application. The application connects through the DBaaS instance’s endpoint, and you choose which addresses can reach it with the whitelist, or privately from inside an attached VPC.
• Applications that read far more than they write. Up to four Read Replicas answer read queries, such as reports and dashboards, while the primary handles every change.
• A copy of your data in a second region. DBaaS runs in Delhi and Chennai, and a Read Replica in the other one can be promoted into an independent DBaaS instance when you need it. See Read Replicas for what a replica in the other region needs.
• Teams that want managed backups. Take a snapshot while the DBaaS instance is running, or on a daily, weekly, or monthly schedule, and restore it into a new DBaaS instance.
• Applications with their own engine settings. A parameter group sets the engine configuration values once and applies them to the primary of every DBaaS instance it is attached to.

Where to start

Get started with DBaaS. For quick answers, see DBaaS FAQ, and when something goes wrong, see Troubleshooting DBaaS. For every size, count, and naming limit, see DBaaS limits.