DatabaseCluster: writers and readers not taking publiclyAccessible flag

[mdesousa]

Describe the bug

We are defining an Aurora Postgres Serverless V2 cluster as follows:

    const cluster = new DatabaseCluster(this, `${id}-serverless-db`, {
      engine: DatabaseClusterEngine.auroraPostgres({
        version: AuroraPostgresEngineVersion.VER_15_2,
      }),
      credentials: Credentials.fromGeneratedSecret("serverless"),
      vpc,
      securityGroups: [dbSecurityGroup],
      vpcSubnets: vpc.selectSubnets({ subnetType: SubnetType.PUBLIC }),
      writer: ClusterInstance.serverlessV2(`${id}-serverless-writer`, {
        publiclyAccessible: true,
      }),
      readers: [
        ClusterInstance.serverlessV2(`${id}-serverless-reader`, {
          publiclyAccessible: true,
          scaleWithWriter: true,
        }),
      ],
    });

however, the new writer and reader instances show in the console with "Publicly Accessible: No", and they are not reachable

Expected Behavior

Configuring publiclyAccessible: true should set the expected accessibility value, and the database should be reachable

Current Behavior

the new writer and reader instances show in the console with "Publicly Accessible: No", and they are not reachable

Reproduction Steps

Use the cdk to deploy as shown in the snippet

Possible Solution

No response

Additional Information/Context

No response

CDK CLI Version

2.83.1

Framework Version

No response

Node.js Version

18.15.0

OS

macOS

Language

Typescript

Language Version

TypeScript 5.1.3

Other information

No response

[pahud]

According to this logic:

aws-cdk/packages/aws-cdk-lib/aws-rds/lib/aurora-cluster-instance.ts

Line 447 in a79794e

publiclyAccessible = ownedCluster.vpcSubnets && ownedCluster.vpcSubnets.subnetType === ec2.SubnetType.PUBLIC;

I guess you should use subnetSelection for vpcSubnets instead.

vpcSubnets: { subnetType: ec2.SubnetType.PUBLIC },

It works for me:

% npx cdk synth | grep PubliclyAccessible
PubliclyAccessible: true
PubliclyAccessible: true

[github-actions]

This issue has not received a response in a while. If you want to keep this issue open, please leave a comment below and auto-close will be canceled.