MSK clusters should be encrypted with a customer-managed KMS key
このページは日本語には対応しておりません。随時翻訳に取り組んでいます。
翻訳に関してご質問やご意見ございましたら、
お気軽にご連絡ください。
Description
MSK clusters should be encrypted using a customer-managed KMS key for data volumes rather than the default AWS-managed key. Customer-managed keys provide full control over key rotation policies, access permissions via KMS key policies, and the ability to revoke or disable the key.
Create a new MSK cluster with a customer-managed KMS key specified for data volume encryption. Existing clusters cannot have their encryption key changed after creation. For guidance, refer to Amazon MSK encryption.
