---
title: "Drush and Databases on Cloud Platform"
date: "2024-02-14T06:18:38+00:00"
summary: "Optimize your Drush commands for Cloud Platform databases with our expert guide. Learn correct syntax, avoid common errors, and ensure seamless database management across environments."
image:
type: "page"
url: "/acquia-cloud-platform/drush-and-databases-cloud-platform"
id: "52f065c7-5c85-4b02-beff-860d3c0d46d0"
---

Table of contents will be added

Note

The [current Drupal version](/service-offerings/guide/software-life-cycle#supported-drupal-version) requires Drush version 11 or later. Newer versions of Drush, that is, version 11 and later, must be installed via Composer. Acquia does not manage the update to the newer versions. For more information, see [About Drush on Cloud Platform](/acquia-cloud-platform/manage-apps/command-line/drush).

When referencing an environment-specific database in an [Cloud Platform Drush command](/acquia-cloud-platform/help/92096-acquia-cloud-drush-and-database-reference "Acquia Cloud Drush and Database Reference") you must not add your [sitename’s](/definitions/sitename) environment (for example, `stg`) to the database name, as shown in the following example:

    drush @mysitegroup.test ac-database-instance-backup mysitegroupstg

Using the previous command will give you the following error, because no database named `mysitegroupstg` exists:

    message : Resource not found
    API status code 404

The error occurs because Cloud Platform uses the same database name regardless of the environment. Appending the environment to the database name changes the database named in the command to a database that does not exist in your subscription, resulting in a 404 error.

The following command is an example of a correctly-formatted command:

    drush @mysitegroup.test ac-database-instance-backup mysitegroup