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.

Sign up for GitHub

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

Jump to bottom

Allow creation of mult-region KMS keys #5919

Open
keeganwitt opened this issue Mar 4, 2025 · 2 comments
Open

Allow creation of mult-region KMS keys #5919

keeganwitt opened this issue Mar 4, 2025 · 2 comments
Assignees
@amartinezfayo
Labels
priority/backlog Issue is approved and in the backlog unscoped The issue needs more design or understanding in order for the work to progress

Comments

@keeganwitt
Copy link
Contributor

keeganwitt commented Mar 4, 2025 •
edited
Loading

Multi-region KMS keys can be used in conjunction global load balancers and global Aurora databases to achieve automated failover between regions, for example for SPIRE upstream servers.
@sorindumitru sorindumitru added the triage/in-progress Issue triage is in progress label Mar 4, 2025
@sorindumitru sorindumitru added priority/backlog Issue is approved and in the backlog unscoped The issue needs more design or understanding in order for the work to progress and removed triage/in-progress Issue triage is in progress labels Mar 4, 2025
@sorindumitru
Copy link
Collaborator

We discussed this during the contributors sync yesterday. We're ok in principle with supporting so we moved it to priority/backlog. We also added the unscoped tag while we consider how we can best support multi-region keys. They are handled as primary and replica keys, so we need to see how to support them in the configuration as well as handling the lifecycle of them.

@keeganwitt
Copy link
Contributor Author

One particular call out regarding the lifecycle was if we always make a replicate-key API call every time we do a create-key call, how do we handle if one API call fails?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@amartinezfayo amartinezfayo

Labels
priority/backlog Issue is approved and in the backlog unscoped The issue needs more design or understanding in order for the work to progress
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@keeganwitt @sorindumitru @amartinezfayo