You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(I tried various different combinations of engines (e.g., aurora vs aurora-postgresql) and engVersions, and paramGroupNames, etc. with consistent results. It fails to deploy.)
Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. associated pull-request, stackoverflow, gitter, etc)
This is related to #929, which requests for a way to create Aurora Serverless using high-level RDS constructs.
Note: I tried it on various regions including us-west-1 and us-west-2 with the same results.
The text was updated successfully, but these errors were encountered:
I'm submitting a ...
What is the current behavior?
If the current behavior is a πͺ²bugπͺ²: Please provide the steps to reproduce
Call to
new CfnDBCluster()
withengineMode: 'serverless'
fails oncdk deploy
.For example, here's an example code:
(I tried various different combinations of engines (e.g., aurora vs aurora-postgresql) and engVersions, and paramGroupNames, etc. with consistent results. It fails to deploy.)
The error I get:
Anything that can be created via CloudFormation should be create-able using CDK, even with low level CFN constructs.
Documentation does not explicitly mention that aurora serverless cannot be created via CDK.
https://docs.aws.amazon.com/cdk/api/latest/docs/@aws-cdk_aws-rds.CfnDBCluster.html
Likewise, CloudFormation doc does not state that it cannot create aurora serverless.
Please tell us about your environment:
Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. associated pull-request, stackoverflow, gitter, etc)
This is related to #929, which requests for a way to create Aurora Serverless using high-level RDS constructs.
Note: I tried it on various regions including us-west-1 and us-west-2 with the same results.
The text was updated successfully, but these errors were encountered: