Skip to content

Fix: [AEA-5931] - Unique SQS KMS Key per Stack#358

Merged
bencegadanyi1-nhs merged 1 commit intomainfrom
AEA-5931-update-sqs-kms-key-name
Feb 5, 2026
Merged

Fix: [AEA-5931] - Unique SQS KMS Key per Stack#358
bencegadanyi1-nhs merged 1 commit intomainfrom
AEA-5931-update-sqs-kms-key-name

Conversation

@kieran-wilkinson-4
Copy link
Copy Markdown
Contributor

Summary

Updates the SQS KMS key to be unique per stack

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Feb 5, 2026

This PR is linked to a ticket in an NHS Digital JIRA Project. Here's a handy link to the ticket:

AEA-5931

@bencegadanyi1-nhs bencegadanyi1-nhs enabled auto-merge (squash) February 5, 2026 10:00
@sonarqubecloud
Copy link
Copy Markdown

sonarqubecloud bot commented Feb 5, 2026

@kieran-wilkinson-4 kieran-wilkinson-4 changed the title Fix: [AEA-5931] - Unique SQS KMS Key per Stacj Fix: [AEA-5931] - Unique SQS KMS Key per Stack Feb 5, 2026
@bencegadanyi1-nhs bencegadanyi1-nhs merged commit 96455e9 into main Feb 5, 2026
14 checks passed
@bencegadanyi1-nhs bencegadanyi1-nhs deleted the AEA-5931-update-sqs-kms-key-name branch February 5, 2026 10:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants