Skip to content

aj/use secret region#604

Merged
astuyve merged 4 commits intomainfrom
aj/use-secret-region
Mar 11, 2025
Merged

aj/use secret region#604
astuyve merged 4 commits intomainfrom
aj/use-secret-region

Conversation

@astuyve
Copy link
Copy Markdown
Contributor

@astuyve astuyve commented Mar 11, 2025

Fixes #594

you can verify with this function using a secret in us-east-1, while running in us-west-2.

Metrics appearing:
image

@astuyve astuyve requested a review from a team as a code owner March 11, 2025 18:33
)
.await
} else {
decrypt_aws_kms(&client, config.kms_api_key.clone(), aws_config).await
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Would KMS have the same issue? we are sending the aws_config which has the region config for the lambda

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

The KMS string doesn't contain a region, the key ID is actually embedded in the ciphertext – so the aws API has to sort it out.

Copy link
Copy Markdown
Contributor

@duncanista duncanista left a comment

Choose a reason for hiding this comment

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

LGTM – thanks for answering my comments!

@astuyve astuyve merged commit 3a029ab into main Mar 11, 2025
33 checks passed
@astuyve astuyve deleted the aj/use-secret-region branch March 11, 2025 19:20
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.

"Error decrypting key" when upgrading to recent versions of extension

2 participants