event bridge and lambda implementation

[aidanharrisnhs]

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.