This plugin manages databases on Shuttle and connects them to your app. A shared database is in the same cluster as other user’s databases, but it is not accessible by other users. If you want a high performing and isolated database, we also offer dedicated Shuttle AWS RDS.
You can connect to any type of remotely hosted database from your code, so do not let our current database offerings limit your creativity! Got other databases you want to see on Shuttle? Let us know!
The Shuttle Shared Postgres cluster is RDS-based and uses Postgres version 16. Contact support if you want to enable common Postgres Extensions for your project.

​
Usage

Start by adding the shuttle-shared-db dependency. Each type of shareable database is behind its own feature flag and macro attribute path.
EngineFeature flagAttribute path
Postgrespostgresshuttle_shared_db::Postgres

​
Output type

By default, you can get the connection string to the database and connect to it with your preferred library. You can also specify other return types to get rid of common boilerplate. Depending on which type declaration is used as the output type in the macro, additional feature flags need to be activated: Postgres output types:
Feature flagType declarationDescription
StringThe connection string including username and password (example)
sqlx (with rustls) or sqlx-native-tlssqlx::PgPoolAn sqlx connection pool (example)
diesel-asyncdiesel_async::AsyncPgConnectionAn async diesel connection
diesel-async-bb8diesel_bb8::Pool<diesel_async::AsyncPgConnection>A bb8 connection pool
diesel-async-deadpooldiesel_deadpool::Pool<diesel_async::AsyncPgConnection>A deadpool connection pool
opendal-postgresopendal::OperatorAn OpenDAL Operator key-value storage interface
opendal-postgresshuttle_shared_db::SerdeJsonOperatorA wrapper over Operator with interface for serde types (example)
Lastly, add a macro annotation to the Shuttle main function. Here are examples for Postgres: 
// Use the connection string
#[shuttle_runtime::main]
async fn main(#[shuttle_shared_db::Postgres] conn_str: String) -> ... { ... }

// With sqlx feature flag, get a PgPool connected automatically
#[shuttle_runtime::main]
async fn main(#[shuttle_shared_db::Postgres] pool: sqlx::PgPool) -> ... { ... }
The Shuttle builder does not currently support sqlx compile-time checked macros. Use cargo sqlx prepare to enable offline building.

​
Parameters

ParameterTypeDescription
local_uri&strIf specified, on local runs, use this database instead of starting a Docker container for it
When passing in strings, you can also insert secrets from Secrets.toml using string interpolation. To insert the PASSWORD secret, pass it in like this: 
#[shuttle_runtime::main]
async fn main(
    #[shuttle_shared_db::Postgres(
        local_uri = "postgres://postgres:{secrets.PASSWORD}@localhost:16695/postgres"
    )] conn_str: String,
) -> ... { ... }
Caveat: If you are interpolating a secret from Secrets.dev.toml, you need to set the same secret in Secrets.toml to a empty string so that this step does not crash in deployment.
The URI should be formatted according to the Postgres documentation. If you do not specify a local_uri, then cargo-shuttle will attempt to spin up a Docker container and launch the database inside of it. For this to succeed, you must have Docker installed and you must also have started the Docker engine. If you have not used Docker before, the easiest way is to install the desktop app and then launch it in order to start the Docker engine.

​
Connection string

After deploying a project with a database macro, you can view the connection string with credentials with: 
shuttle resource list --show-secrets
Using the connection string, you can connect to it for manual querying, inspection, and migration.

​
Example

The Shuttle main function below uses the #[shuttle_shared_db::Postgres] attribute macro to provision a shared Postgres database, which can be accessed with an sqlx Pool.
main.rs
#[shuttle_runtime::main]
async fn main(
    #[shuttle_shared_db::Postgres] pool: PgPool,
) -> shuttle_axum::ShuttleAxum {
    sqlx::migrate!()
        .run(&pool)
        .await
        .expect("Failed to run migrations");

    let state = MyState { pool };
    let router = Router::new()
        .route("/todos", post(add))
        .route("/todos/:id", get(retrieve))
        .with_state(state);

    Ok(router.into())
}
The full example can be found on GitHub.