E3030 case sensitivity caused DB instance destruction!
See original GitHub issuecfn-lint version: (cfn-lint --version
) 0.29.0
Description of issue.
E3030 told me that “Postgres” was not an allowed engine name, so I changed it to “postgres”. This caused cloudformation to rebuild my database instance, aka complete data loss. Luckily only discovered this on staging environment.
I think since CloudFormation / RDS seems to allow it, this check should be made case insensitive 😃
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
E3030 case sensitivity caused DB instance destruction!
This caused cloudformation to rebuild my database instance, aka complete data loss. Luckily only discovered this on staging environment. I think ...
Read more >Databases - Why case insensitive?
I understand the interest of case insensitive searches on text values for example. But why would we use case-insensitive database names, tables ...
Read more >Estimates of Japanese Encephalitis mortality and morbidity
Japanese Encephalitis (JE) is known for its high case fatality ratio (CFR) and ... indicating a permanent damage caused by JE infection.
Read more >Can database objects be made case insensitive while ...
In Microsoft SQL Server (2014) it is possible to choose between a case insensitive and case sensitive collation.
Read more >Post-COVID-19 human memory impairment: A PRISMA- ...
Thus, it is possible for COVID-19 infection to cause brain damage and subsequent ... For example, Savino et al. noted a case of...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I think this is also a CloudFormation bug, in that it compares the strings in a case-sensitive manner, when RDS underneath compares them in a case-insensitive manner. If you could file a bug there too that would be great.
@PatMyron @rjlohan can you two provide some thoughts here? I can confirm that it looks like the RDS resource takes any casing on the Engine… mysql, MYSQL, mySql, etc. However it looks like as you change the casing it causes the service to recreate the resource?