Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot specify an Aurora engine version #2212

Closed
zrfr opened this issue Apr 10, 2019 · 0 comments · Fixed by #2698 or MechanicalRock/tech-radar#14 · May be fixed by MechanicalRock/cdk-constructs#5, MechanicalRock/cdk-constructs#6 or MechanicalRock/cdk-constructs#7

Comments

@zrfr
Copy link
Member

zrfr commented Apr 10, 2019

It is currently not possible to specify an engine version when creating a DB cluster using the DatabaseCluster construct without overriding the underlying cfn resource. DatabaseCluster does not specify an engine version, which results in a cluster being created using the engine's default version, which may not be what the user expects as this version is not necessarily the latest. (The RDS Console does not expose the default version at all, and instead requires the user to choose from the list of available engine versions.)

joehillen pushed a commit to joehillen/aws-cdk that referenced this issue May 30, 2019
Without this change, CDK's RDS DatabaseCluster is not very useful
because you can only deploy the default versions
of the given database engine.

This change adds an optional prop `engineVersion`

fixes aws#2212
joehillen pushed a commit to joehillen/aws-cdk that referenced this issue May 31, 2019
Without this change, CDK's RDS DatabaseCluster is not very useful
because you can only deploy the default versions
of the given database engine.

This change adds an optional prop `engineVersion`

fixes aws#2212
joehillen pushed a commit to joehillen/aws-cdk that referenced this issue May 31, 2019
Without this change, CDK's RDS DatabaseCluster is not very useful
because you can only deploy the default versions
of the given database engine.

This change adds an optional prop `engineVersion`

fixes aws#2212
joehillen pushed a commit to joehillen/aws-cdk that referenced this issue May 31, 2019
Without this change, CDK's RDS DatabaseCluster is not very useful
because you can only deploy the default versions
of the given database engine.

This change adds an optional prop `engineVersion`

fixes aws#2212
eladb pushed a commit that referenced this issue Jun 3, 2019
Without this change, CDK's RDS DatabaseCluster is not very useful
because you can only deploy the default versions
of the given database engine.

This change adds an optional prop `engineVersion`

Fixes #2212
This was referenced Dec 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment