-
Notifications
You must be signed in to change notification settings - Fork 587
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
When using aurora dbinstance make sure certain properties aren't used #1409
Conversation
47e33f9
to
7b95ab7
Compare
Edit: I found the AWS documentation that supports this change. Where did you source this list from? According to this AWS blog, and the AWS Sample CloudFormation Template for Aurora, |
https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-rds-database-instance.html#cfn-rds-dbinstance-copytagstosnapshot While I will agree that Aurora supports |
Any advice on fixing stacks broken by this? If we update
I've checked a few times making sure no other template changes are made. Is there a practical way to go from having it in the template to not that doesn't involve rebuilding the DB and migrating data? P.s I ran in to this having followed https://aws.amazon.com/blogs/database/deploy-an-amazon-aurora-postgresql-db-cluster-with-recommended-best-practices-using-aws-cloudformation/ which still lists the property in the Aurora yaml:
|
@PatMyron I may need your opinion on this. I'm trying to replicate this issue and I cannot replicate it. @neerolyte this was the only value that changed correct? @PatMyron looks like this issue was brought up here too. aws-cloudformation/cloudformation-coverage-roadmap#211 |
Issue #, if available:
fix #1395
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.