You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.The text was updated successfully, but these errors were encountered: