#✅ - Key Management Service gen2
1 messages · Page 1 of 1 (latest)
Hey @heady stratus , Amplify Gen 2 doesnt create KMS keys for secrets, the secrets are created on AWS Systems Manager ->
Parameter Store. the KMS keys in the screenshot appears to be due to the underlying service using KMS, for example: https://aws.amazon.com/blogs/aws/amazon-s3-encrypts-new-objects-by-default/
At AWS, security is the top priority. Starting today, Amazon Simple Storage Service (Amazon S3) encrypts all new objects by default. Now, S3 automatically applies server-side encryption (SSE-S3) for each new object, unless you specify a different encryption option. SSE-S3 was first launched in 2011. As Jeff wrote at the time: “Amazon S3 server-s...
ok so if I get that correctly,
amplify gen2 could have created a s3 bucket to store some information, which by default got encrypted, therefore generating these secrets?
(I assume gen2 created it, as I have not touched s3)
CDK will create the bucket to store assets, you should be able to see the buckets in the S3 console.
I have many buckets so instead I am trying to remove the rds one
but in the same region, I don't have anything deployed for rds.
How can I remove this key?
@heady stratus AWS managed key cannot be modified or deleted,refer to
https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#aws-managed-cmk
Learn the basic terms and concepts used in AWS KMS.
✅ - Key Management Service gen2