-
Notifications
You must be signed in to change notification settings - Fork 4k
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
aws_rds: unable to use per-instance parameters #27035
Labels
@aws-cdk/aws-rds
Related to Amazon Relational Database
bug
This issue is a bug.
effort/small
Small work item – less than a day of effort
p1
Comments
This is my current work-around to be compatible with how it was created using
|
Makes sense, thanks for the report |
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
@aws-cdk/aws-rds
Related to Amazon Relational Database
bug
This issue is a bug.
effort/small
Small work item – less than a day of effort
p1
Describe the bug
When trying to use the
parameters
property duringClusterInstance.provisioned
, it will try to create a ParameterGroup for you using the idInstanceParameterGroup
.If you try to have multiple instances (ie multiple readers) in a DatabaseCluster, this will throw error:
Here's the specific line of code:
https://github.com/aws/aws-cdk/blob/v2.94.0/packages/aws-cdk-lib/aws-rds/lib/aurora-cluster-instance.ts#L457-L464
Expected Behavior
I should be able to provide a simple parameters object and a parameter group to be created for each unique instance.
Current Behavior
Throws an error
Reproduction Steps
Create a
DatabaseCluster
with multiple readers with theparameters: {}
property set:Possible Solution
The ParameterGroup scope is the cluster, either the scope should be specific to the ClusterInstance, or the ParameterGroup should have a unique ID.
Additional Information/Context
No response
CDK CLI Version
2.94.0
Framework Version
No response
Node.js Version
18
OS
mac osx latest
Language
Typescript
Language Version
No response
Other information
No response
The text was updated successfully, but these errors were encountered: