Skip to content

Comments

added event bridge lambda and new vault to facilitate new cross account copy job method#42

Closed
aidanharrisnhs wants to merge 7 commits intomainfrom
feature/TEX-9678-event-bridge-lambda-intermediary-vault-implementation
Closed

added event bridge lambda and new vault to facilitate new cross account copy job method#42
aidanharrisnhs wants to merge 7 commits intomainfrom
feature/TEX-9678-event-bridge-lambda-intermediary-vault-implementation

Conversation

@aidanharrisnhs
Copy link
Contributor

Description

we added a new intermediary vault and pointed the backup plans to it, this allows us to change the kms keys of the recovery points so they inherit the kms key of the intermediary vault so they have a customer managed key to enable cross account transfers. We also added an event bridge to detect new recovery points being made in the intermediary vault, which kicks off a lambda which starts another copy job to the destination vault.

Type of changes

This change allows teams to AWS managed keys on their databases and still be able to have them backed up to another account.

  • Refactoring (non-breaking change)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would change existing functionality)
  • Bug fix (non-breaking change which fixes an issue)

Checklist

  • I am familiar with the contributing guidelines
  • I have followed the code style of the project
  • I have added tests to cover my changes
  • I have updated the documentation accordingly
  • This PR is a result of pair or mob programming

Sensitive Information Declaration

To ensure the utmost confidentiality and protect your and others privacy, we kindly ask you to NOT including PII (Personal Identifiable Information) / PID (Personal Identifiable Data) or any other sensitive data in this PR (Pull Request) and the codebase changes. We will remove any PR that do contain any sensitive information. We really appreciate your cooperation in this matter.

  • I confirm that neither PII/PID nor sensitive data are included in this PR and the codebase changes.

@aidanharrisnhs aidanharrisnhs requested a review from a team as a code owner May 21, 2025 15:38
Copy link
Contributor

@pennytextures pennytextures left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It'd be nice if the documentation were updated too, but e-RS has already put this branch live and it works fine.

Happy to add documentation myself after this is in

@regularfry regularfry added enhancement New feature or request non-breaking A change that does not affect existing consumers labels Jul 9, 2025
@regularfry
Copy link
Contributor

This branch has an unsigned commit and can't be merged, so it's been redone as #50. Closing this in favour of that.

@regularfry regularfry closed this Jul 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request non-breaking A change that does not affect existing consumers

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants