I noticed this while upgrading the module from v0.4.0 to v.0.6.0.
On RDS, if the database exists, it tries to replace the existing KMS key with a new key.
I resolved the problem setting the enable_kms to false, which didn't disable KMS encryption on my database, it just didn't try to replace the existing key.
I noticed this while upgrading the module from v0.4.0 to v.0.6.0.
On RDS, if the database exists, it tries to replace the existing KMS key with a new key.
I resolved the problem setting the
enable_kmsto false, which didn't disable KMS encryption on my database, it just didn't try to replace the existing key.