We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Currently SNS topics are not encrypted and thus are flagged as a security issue.
An equivalent KMS key generated for SNS. Here is an example pulled from kms.tf to encrypt SQS.
kms.tf
// KMS key for server-side encryption (SSE) of SQS resource "aws_kms_key" "sse_sqs" { description = "BinaryAlert Server-Side Encryption - SQS" enable_key_rotation = true tags = { Name = var.tagged_name } policy = data.aws_iam_policy_document.kms_allow_s3.json } resource "aws_kms_alias" "sse_sqs_alias" { name = "alias/${var.name_prefix}_binaryalert_sse_sqs" target_key_id = aws_kms_key.sse_sqs.key_id }
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Background
Currently SNS topics are not encrypted and thus are flagged as a security issue.
Desired Change
An equivalent KMS key generated for SNS. Here is an example pulled from
kms.tf
to encrypt SQS.The text was updated successfully, but these errors were encountered: