- Más nuevo
- Más votos
- Más comentarios
Hello,
As seen in the following AWS documentations You can't give an Aurora Serverless v1 DB cluster a public IP address. You can access an Aurora Serverless v1 DB cluster only from within a VPC[1]. Hence giving public access to serverlesss v2 cluster is not supported. That being said Aurora Serverless v2 does support public ip address as seen in the following AWS document which also compares differences between an Aurora Serverless v1 V/S Aurora Serverless v2 cluster[2].
References:
Thanks for that info. The doc doesn't state that ServerlessCluster launches v1 by default, and it wasn't my intention to do so, how can I launch a v2 cluster, and allow public access?
The user guide doc is your friend. Do note, however, that you'll have to run engine_version 13.6 or newer for v2; if you select e.g. 10.21 as your version, only serverless v1 is an option (I assume that's what you did). Thus, either create a new database with the right version (easiest, especially if you don't have a lot of data) or follow the upgrade instructions in the user guide (which takes a few steps, but may be a good learning experience).
https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-serverless-v2.upgrade.html
Thanks for your answer, but still no luck. I've changed the engine version to 13.6 (but see the same results with 13.7) as follows, but now it tells me
8:36:21 AM | CREATE_FAILED | AWS::RDS::DBCluster | AnotherCluster9D7C9369 The engine mode serverless you requested is currently unavailable. (Service: AmazonRDS; Status Code: 400; Error Code: InvalidParameterValue; Request ID: 4e3e0d67-2055-48a6-aa9a-6cfcbc92e27b; Proxy: null)
const cluster = new rds.ServerlessCluster(this, 'AnotherCluster', {
engine: rds.DatabaseClusterEngine.auroraPostgres({ version: rds.AuroraPostgresEngineVersion.of('13.6', '13', { s3Import: false, s3Export: false }) }),
vpc: env.getVpc(),
vpcSubnets: {
subnetType: ec2.SubnetType.PUBLIC,
},
credentials: rds.Credentials.fromGeneratedSecret('postgres'),
enableDataApi: true,
defaultDatabaseName: 'defaultDatabase'
});
Any further suggestions?
Is it mandatory for you to use the CDK for this? It appears that there's still no proper support in CDK for creating serverless v2 clusters, see e.g. https://github.com/aws/aws-cdk/issues/20197 which hasn't been marked as resolved yet. Some workarounds have been presented in the comments to that issue, so maybe you can get around the limitation that way if creating the cluster using e.g. the console is not an option.
Thanks. It is mandatory that we use the CDK - all our infrastructure is automated and stood up using it. I have since found a work around though.
Contenido relevante
- OFICIAL DE AWSActualizada hace 3 años
- OFICIAL DE AWSActualizada hace un año