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

Use KMS multi-region keys for the default key #218

Closed
nozaq opened this issue Sep 12, 2021 · 5 comments
Closed

Use KMS multi-region keys for the default key #218

nozaq opened this issue Sep 12, 2021 · 5 comments
Labels
enhancement New feature or request

Comments

@nozaq
Copy link
Owner

nozaq commented Sep 12, 2021

Use KMS Multi-Region Keys to centralize the CMK creation, which is currently distributed among regions.

  • Replace single-region keys with the multi-region key.
  • Use the multi-region key for..
    • CloudTrail encryption
    • SNS topic encryption
  • Optionally supporting single-region keys could be helpful, but the design depends on the upstream implementation.

Current status
Waiting for the multi-region keys to be supported in terraform-aws-provider(See this issue).

Ref: #182 #216

@nozaq nozaq added the enhancement New feature or request label Sep 12, 2021
@nozaq nozaq added the blocked Waiting for other events before proceeding label Sep 24, 2021
@giovannifl
Copy link

Any update ?

@nozaq
Copy link
Owner Author

nozaq commented Oct 8, 2021

@giovannifl We need to wait the AWS provider to support multi region key resource, but it seems the upstream issue is not resolved yet.

@willfarrell
Copy link
Contributor

willfarrell commented Nov 4, 2021

@nozaq nozaq removed the blocked Waiting for other events before proceeding label Nov 22, 2021
@nozaq
Copy link
Owner Author

nozaq commented Nov 22, 2021

AWS suggests to use multi-region keys only if there is clear benefit since they introduce additional security concerns(ref).
Need to investigate more before deciding to use multi-region keys instead of having a single-region key for each region.

@nozaq
Copy link
Owner Author

nozaq commented Jan 8, 2022

After considering tradeoffs, I didn't find clear benefit over complications.
Closing it for now.

@nozaq nozaq closed this as completed Jan 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants