Skip to content
New issue

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

AWS SQS Server Side Encryption Support For Queues #911

Closed
brandongalbraith opened this issue Jun 19, 2017 · 2 comments
Closed

AWS SQS Server Side Encryption Support For Queues #911

brandongalbraith opened this issue Jun 19, 2017 · 2 comments
Labels
enhancement Requests to existing resources that expand the functionality or scope.

Comments

@brandongalbraith
Copy link
Contributor

AWS recently rolled out support of server side encryption of SQS message payloads. It would be helpful for this queue attribute to be supported for organizations where compliance requirements dictate it (encryption in flight, encryption at rest, etc).

Support of this queue attribute could follow the S3 server side encryption and KMS key id syntax.

Example SQS queue resource:

resource "aws_sqs_queue" "super_secret_queue" {
  name                      = "super_secret-example-queue"
  delay_seconds             = 90
  max_message_size          = 2048
  message_retention_seconds = 86400
  receive_wait_time_seconds = 10
  redrive_policy            = "
{\"deadLetterTargetArn\":\"${aws_sqs_queue.terraform_queue_deadletter.arn}\",\"maxReceiveCount\":4}"
  server_side_encryption = true
  sse_kms_key_id = "<AWS_KMS_CMK>" 
}

Note the deviation from the S3 SSE attribute behavior; SQS only supports KMS, therefore server_side_encryption may be a bool versus defining which encryption scheme to use.

@stack72 stack72 added the enhancement Requests to existing resources that expand the functionality or scope. label Jun 29, 2017
@stack72
Copy link
Contributor

stack72 commented Jul 7, 2017

I believe this can be closed via #962

@stack72 stack72 closed this as completed Jul 7, 2017
@ghost
Copy link

ghost commented Apr 11, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!

@ghost ghost locked and limited conversation to collaborators Apr 11, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement Requests to existing resources that expand the functionality or scope.
Projects
None yet
Development

No branches or pull requests

2 participants