Closed romanglovahs closed 1 year ago
@markpeek Hello Mark, can you please look into this
We also just ran into this issue. However the storage size limit for specifying the Iops is different per DB engine as can be seen in this table: (for example Oracle Iops cannot be specified is storage size < 200) https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_Storage.html#gp3-storage So either the validation can be removed or take DB engine and storage size into consideration.
I have a PR in here that adds additional validator logic, but this would also fix our deployment issues we are experiencing as well.
https://github.com/cloudtools/troposphere/pull/2164
Note: this PR was also attempting to update refspec, but failed.
Tagging Mr @markpeek , Hi Mark is this something we can look at trying to get into the next release or some variation of it?
@tnielsen2 Looks like Mark is not interested in this tool, I'd recommend to migrate to something else or fork it for full access
@tnielsen2 was this resolved via 0faace5?
@tnielsen2 was this resolved via 0faace5?
Yep!
Excellent. Thanks!
Cloudformation does not allow to set Iops for storage GP3 < 400Gib, example error: Resource handler returned message: "You can't specify IOPS or storage throughput for engine mysql and a storage size less than 400. (Service: Rds, Status Code: 400 For <400Gib it's set automatically to 3000 and >=400 Gib is set to 12000