Add `Dsql` AWS component by DamienPace15 · Pull Request #6496 · anomalyco/sst

DamienPace15 · 2026-02-27T11:12:16Z

Built off the back of PR #5969, with testing and additional code suggested by @natac13. Also merged in latest dev with the latest 4.x version.

This adds the sst.aws.Dsql component for Amazon Aurora DSQL.

What's included

Single-region

Creates an Aurora DSQL cluster in the current region. Linked functions get endpoint and region via Resource.

Multi-region

Creates a primary cluster in the current region and a peer cluster in another region. An AWS provider for the peer region is created automatically so you don't need to configure one yourself. The two-way ClusterPeering handshake that DSQL requires is also handled automatically. Linked functions get endpoint and region for the primary cluster and peer.endpoint and peer.region for the peer. The peer cluster is accessed via its public endpoint which is secured by short-lived IAM auth tokens and TLS.

VPC endpoints

You can optionally create AWS PrivateLink interface endpoints inside a VPC. Two types are supported: management for control plane operations and connection for PostgreSQL client connections. Both default to false since they cost money and need to be explicitly enabled. A security group is created automatically that allows inbound TCP/5432 from within the VPC CIDR. When a connection endpoint is created, Resource.MyCluster.endpoint automatically resolves to the private hostname instead of the public one, so your function code doesn't need to change.

Note: Multi-region VPC endpoint support is not included yet. It has some nuances around cross-region VPC creation and routing that are better handled separately.

`Dsql.get`

Reference an existing cluster by its identifier, useful for sharing a cluster across stages. Supports both single-region and multi-region clusters via peerIdentifier and peerRegion.

Tested

Single region deployment
Multi region deployment
Single region connection within Lambda
Multi region connection within Lambda connecting to both clusters
Remove single region cluster
Remove multi region cluster

This commit introduces the new component, providing a high-level construct for provisioning and managing Amazon Aurora DSQL clusters. The component supports both single-region and multi-region active-active deployments. For multi-region setups, it automatically handles the creation and peering of clusters across regions. The integration has been configured to provide functions with all necessary connection details for both primary and peer clusters, including ARNs, endpoints, and regions, accessible via the type-safe object. Two new examples have been added to demonstrate usage: - : A basic single-region cluster setup. - : A more advanced example showcasing how to connect to both the primary and peer clusters from a single Lambda function. Additionally, this commit updates the pulumi/aws dependency to v6.83.0

This commit refactors the DSQL component to resolve a critical deletion deadlock in multi-region deployments. The architecture is separated into two components: `Dsql` for single-region cluster management and `DsqlPeering` for coordinating multi-region connections. This new design leverages a Pulumi dynamic provider to orchestrate the simultaneous deletion of peered clusters, which is required by AWS and was the root cause of the deadlock. Key changes: - `Dsql` component is now simplified for single-region clusters. - New `DsqlPeering` component manages the lifecycle of multi-region peering. - A dynamic provider in TypeScript handles the complex creation and deletion logic, ensuring clusters are deleted in a coordinated manner. - The `aws-dsql-multiregion` example is updated to reflect the new, more robust usage pattern.

platform/src/components/aws/dsql.ts

vimtor

thanks for your contribution @DamienPace15

i've left a bunch of comments and suggestions

thanks again for taking a look at this

pkg/project/provider/aws.go

examples/aws-dsql-multiregion/README.md

examples/aws-dsql/README.md

www/src/content/docs/docs/examples.mdx

vimtor · 2026-02-27T13:14:24Z

platform/src/components/aws/dsql.ts

+  private static publicEndpointFromArn(clusterArn: Output<string>) {
+    return clusterArn.apply((arn) => {
+      const parts = arn.split(":");
+      const region = parts[3];
+      const clusterId = parts[5].split("/")[1];
+      return `${clusterId}.dsql.${region}.on.aws`;
+    });
+  }
+
+  private static regionFromArn(clusterArn: Output<string>) {
+    return clusterArn.apply((arn) => {
+      const parts = arn.split(":");
+      const region = parts[3];
+      return region;
+    });
+  }


there are several ARN utilities in the codebase. we should check if any of the existing ones cover this use case

if this is sql specific, the existing code is fine

I can't find any generic region from arn like utility that works with Output from what I can see. The existing utilities are all service specific parsers for example parseQueueArn, parseLambdaEdgeArn and have some specific logic around that.

probably it still makes sense to extract service-specific arn functions so we can test them. if you update the branch with origin-dev, you'll see new tests for those functions

you can keep them working with regular strings and just do the apply on the component side.

bumping this

platform/src/components/aws/dsql.ts

examples/aws-dsql/src/lambda.ts

vimtor · 2026-02-27T13:39:08Z

examples/aws-dsql-multiregion/README.md

+```typescript
+// sst.config.ts
+const cluster = new sst.aws.Dsql('MyCluster', {
+  multiRegion: {


this property doesn't exist in the component

vimtor · 2026-02-27T13:39:56Z

platform/src/components/aws/dsql-peering.ts

+import type { Dsql } from "./dsql";
+import { DsqlPeeringProvider } from "./providers/dsql-peering";
+
+export interface DsqlPeeringArgs {


i believe we no longer need the custom provider since pulumi has a resource for this: https://www.pulumi.com/registry/packages/aws-v6/api-docs/dsql/clusterpeering/

Should I be removing the dsql peering component completely?

Using the native pulumi peering component means that I would have to do something like this.

`
const witnessRegion = 'us-west-2';

const primary = new sst.aws.Dsql('Primary', { witnessRegion: witnessRegion, }); const peerProvider = new aws.Provider('PeerRegion', { region: 'us-east-2', }); const peer = new sst.aws.Dsql( 'Peer', { witnessRegion: witnessRegion }, { provider: peerProvider } ); // Create peering between clusters new aws.dsql.ClusterPeering('PrimaryPeering', { identifier: primary.identifier, clusters: [peer.arn], witnessRegion, }); new aws.dsql.ClusterPeering( 'PeerPeering', { identifier: peer.identifier, clusters: [primary.arn], witnessRegion, }, { provider: peerProvider } );`

Or should we be keeping the peering component so some of this is abstracted?

i believe we can remove the custom peering component and either provide this as an example or abstract this logic inside the existing DSQL component

an example of the latter would be:

const primary = new sst.aws.Dsql('Primary', { witness: { region: 'us-east-1' }, peers: [ { region: 'us-east-2' }, { region: 'eu-west-1' }, ], });

i'm not super familiar with dsql but this latter approach feels very clean

platform/src/components/aws/dsql.ts

platform/package.json

vimtor · 2026-03-05T09:45:18Z

bun.lock

don't worry i will fix these before merging the pr.

if you want to fix it deleting it and running bun install should work (in fact if you remove the unnecessary dep no bun changes should appear)

vimtor · 2026-03-05T09:47:49Z

platform/src/auto/run.ts

        [
          "aws:dynamodb/table:Table",
          "aws:rds/instance:Instance",
+          "aws:dsql/cluster:Cluster",


i wonder if we should also add the peering stuff here? can you confirm?

If you want to keep the peering resource then yes. It doesn't contain any data.

Currently what it will do in multi region is the following

Before Delete [Cluster 1] -> [Peering relationship] -> [Cluster 2] After Delete [Cluster 1] [Cluster 2]

The peering relationship is easy to recreate if needed.

If we add it then it will keep the multi region relationship.

Is this function strictly for resources that hold data? If so Cluster peering isn't the right spot for this imo.

vimtor · 2026-03-05T09:59:28Z

examples/aws-dsql/sst.config.ts

+/* # AWS Aurora DSQL Example
+## How to use
+
+1. **Deploy the stack**
+
+   ```bash
+   npm install
+   sst deploy
+   ```
+
+2. **Test the connection**
+   The Lambda function when invoked will connect to the DSQL cluster and run a test query.
+
+3. **View the results**
+   Check the Lambda function logs to see the successful connection and query results.
+
+## Clean up
+
+```bash


can we restructure these docs to follow the pattern of the others?

if you don't want to bother i will do it before merging

examples/aws-dsql-multiregion/sst.config.ts

platform/src/components/aws/dsql.ts

examples/aws-dsql-multiregion/sst.config.ts

platform/src/components/aws/dsql.ts

chrisfowles and others added 15 commits July 14, 2025 17:53

dsql merge dev

78ea896

merged latest dev

7ba2c97

renamed variables for multi region

479f66e

Merge branch 'dev' into chrisfowles/dev

5c6bc30

merges

ba797a7

removed qoutes

6075541

quotes

ff7a3bc

updated docs

3d7f427

quotes

b3b550a

tested DSQL with new pakcages

746ab2b

removed local ignore

c1e32f2

reverted to dev, didn't touch these files

d6e656b

reverted these ones as well

73ffc26

DamienPace15 commented Feb 27, 2026

View reviewed changes

platform/src/components/aws/dsql.ts Show resolved Hide resolved

revert function file that I didn't change to dev file

112c398

vimtor self-assigned this Feb 27, 2026

vimtor requested changes Feb 27, 2026

View reviewed changes

vimtor changed the title ~~Damienpace/dsql~~ Add Dsql AWS component Feb 27, 2026

vimtor mentioned this pull request Feb 27, 2026

feat(aws): Add Dsql component and examples #5969

Closed

DamienPace15 added 3 commits March 4, 2026 12:59

Merge branch 'dev' into damienpace/dsql addressed comments

fc3e145

addressed minor comments and removed lock files that were left over

13c0ff0

removed DSQL peering component and abstracted away peering creation

a88fd37

DamienPace15 commented Mar 5, 2026

View reviewed changes

platform/src/components/aws/dsql.ts Outdated Show resolved Hide resolved

vimtor requested changes Mar 5, 2026

View reviewed changes

DamienPace15 added 3 commits March 6, 2026 11:38

addressed minor comments, before testing big comments

ecabed4

added vpc support for single region

6dc5a88

reworked get to allow to get both clusters in cross region peering

4b76bd9

Conversation

DamienPace15 commented Feb 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What's included

Single-region

Multi-region

VPC endpoints

Dsql.get

Tested

Uh oh!

Uh oh!

vimtor left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

DamienPace15 Mar 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

DamienPace15 Mar 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

DamienPace15 commented Feb 27, 2026 •

edited

Loading

`Dsql.get`

DamienPace15 Mar 4, 2026 •

edited

Loading

DamienPace15 Mar 5, 2026 •

edited

Loading