AWS RDS and Aurora
Connect Hyperdrive to an AWS RDS or Aurora Postgres database instance.
This example shows you how to connect Hyperdrive to an Amazon Relational Database Service (Amazon RDS) Postgres or Amazon Aurora database instance.
To allow Hyperdrive to connect to your database, you will need to ensure that Hyperdrive has valid user credentials and network access.
When creating or modifying an instance in the AWS console:
- Configure a DB cluster identifier and other settings you wish to customize.
- Under Settings > Credential settings, note down the Master username and Master password (Aurora only).
- Under the Connectivity header, ensure Public access is set to Yes.
- Select an Existing VPC security group that allows public Internet access from
0.0.0.0/0
to the port your database instance is configured to listen on (default:5432
for PostgreSQL instances). - Select Create database.
To retrieve the database endpoint (hostname) for Hyperdrive to connect to:
- Go to Databases view under RDS in the AWS console.
- Select the database you want Hyperdrive to connect to.
- Under the Endpoints header, note down the Endpoint name with the type
Writer
and the Port.
For regular RDS instances (non-Aurora), you will need to fetch the endpoint and port of the database:
- Go to Databases view under RDS in the AWS console.
- Select the database you want Hyperdrive to connect to.
- Under the Connectivity & security header, note down the Endpoint and the Port.
The endpoint will resemble YOUR_DATABASE_NAME.cpuo5rlli58m.AWS_REGION.rds.amazonaws.com
and the port will default to 5432
.
Once your database is created, you will need to create a user for Hyperdrive to connect as. Although you can use the Master username configured during initial database creation, best practice is to create a less privileged user.
To create a new user, log in to the database and use the CREATE ROLE
command:
# Log in to the databasepsql postgresql://MASTER_USERNAME:MASTER_PASSWORD@ENDPOINT_NAME:PORT/database_name
Run the following SQL statements:
-- Create a role for HyperdriveCREATE ROLE hyperdrive;
-- Allow Hyperdrive to connectGRANT CONNECT ON DATABASE postgres TO hyperdrive;
-- Grant database privileges to the hyperdrive roleGRANT ALL PRIVILEGES ON DATABASE postgres to hyperdrive;
-- Create a specific user for Hyperdrive to log in asCREATE ROLE hyperdrive_user LOGIN PASSWORD 'sufficientlyRandomPassword';
-- Grant this new user the hyperdrive role privilegesGRANT hyperdrive to hyperdrive_user;
Refer to AWS' documentation on user roles in PostgreSQL ↗ for more details.
With a database user, password, database endpoint (hostname and port) and database name (default: postgres
), you can now set up Hyperdrive.
To configure Hyperdrive, you will need:
- The IP address (or hostname) and port of your database.
- The database username (for example,
hyperdrive-demo
) you configured in a previous step. - The password associated with that username.
- The name of the database you want Hyperdrive to connect to. For example,
postgres
.
Hyperdrive accepts the combination of these parameters in the common connection string format used by database drivers:
postgres://USERNAME:PASSWORD@HOSTNAME_OR_IP_ADDRESS:PORT/database_name
Most database providers will provide a connection string you can directly copy-and-paste directly into Hyperdrive.
To create a Hyperdrive configuration with the Wrangler CLI, open your terminal and run the following command. Replace <NAME_OF_HYPERDRIVE_CONFIG> with a name for your Hyperdrive configuration and paste the connection string provided from your database host, or replace user
, password
, HOSTNAME_OR_IP_ADDRESS
, port
, and database_name
placeholders with those specific to your database:
npx wrangler hyperdrive create <NAME_OF_HYPERDRIVE_CONFIG> --connection-string="postgres://user:password@HOSTNAME_OR_IP_ADDRESS:PORT/database_name"
This command outputs a binding for the Wrangler configuration file:
{ "name": "hyperdrive-example", "main": "src/index.ts", "compatibility_date": "2024-08-21", "compatibility_flags": [ "nodejs_compat" ], "hyperdrive": [ { "binding": "HYPERDRIVE", "id": "<ID OF THE CREATED HYPERDRIVE CONFIGURATION>" } ]}
name = "hyperdrive-example"main = "src/index.ts"compatibility_date = "2024-08-21"compatibility_flags = ["nodejs_compat"]
# Pasted from the output of `wrangler hyperdrive create <NAME_OF_HYPERDRIVE_CONFIG> --connection-string=[...]` above.[[hyperdrive]]binding = "HYPERDRIVE"id = "<ID OF THE CREATED HYPERDRIVE CONFIGURATION>"
Install the node-postgres
driver:
npm i pg@>8.13.0
yarn add pg@>8.13.0
pnpm add pg@>8.13.0
If using TypeScript, install the types package:
npm i -D @types/pg
yarn add -D @types/pg
pnpm add -D @types/pg
Add the required Node.js compatibility flags and Hyperdrive binding to your wrangler.jsonc
file:
{ "compatibility_flags": [ "nodejs_compat" ], "compatibility_date": "2024-09-23", "hyperdrive": [ { "binding": "HYPERDRIVE", "id": "<your-hyperdrive-id-here>" } ]}
# required for database drivers to functioncompatibility_flags = ["nodejs_compat"]compatibility_date = "2024-09-23"
[[hyperdrive]]binding = "HYPERDRIVE"id = "<your-hyperdrive-id-here>"
Create a new Client
instance and pass the Hyperdrive connectionString
:
// filepath: src/index.tsimport { Client } from "pg";
export default { async fetch( request: Request, env: Env, ctx: ExecutionContext, ): Promise<Response> { // Create a new client instance for each request. const client = new Client({ connectionString: env.HYPERDRIVE.connectionString, });
try { // Connect to the database await client.connect(); console.log("Connected to PostgreSQL database");
// Perform a simple query const result = await client.query("SELECT * FROM pg_tables");
// Clean up the client after the response is returned, before the Worker is killed env.waitUntil(client.end());
return Response.json({ success: true, result: result.rows, }); } catch (error: any) { console.error("Database error:", error.message);
return Response.error(); } },};
- Learn more about How Hyperdrive Works.
- Refer to the troubleshooting guide to debug common issues.
- Understand more about other storage options available to Cloudflare Workers.
Was this helpful?
- Resources
- API
- New to Cloudflare?
- Products
- Sponsorships
- Open Source
- Support
- Help Center
- System Status
- Compliance
- GDPR
- Company
- cloudflare.com
- Our team
- Careers
- 2025 Cloudflare, Inc.
- Privacy Policy
- Terms of Use
- Report Security Issues
- Trademark