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.

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

fix for cross region s3 template processing #1221

Merged
merged 1 commit into from
Apr 11, 2024

Conversation

rjjaegeraws
Copy link
Contributor

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

This fixes the S3 API cross-region call when trying to provision 3rd party firewalls that use a configuration file. If the 3rd party firewalls are being deployed in ca-west-1, but the configuration files are in ca-central-1 (home region) this error will be encountered: Error: Unable to get S3 object s3://asea-management-phase0-configcacentral1-1g9ucir5s5ry0/firewall/firewall-example-A-A-multitunnel.txt: IllegalLocationConstraintException: The ca-central-1 location constraint is incompatible for the region specific endpoint this request was sent to.

The fix below uses the config bucket's home region as a parameter to the locationconstraint in the S3 API.

@rjjaegeraws rjjaegeraws changed the title s3 template update fix for cross region s3 template processing Mar 14, 2024
@rjjaegeraws rjjaegeraws marked this pull request as ready for review April 1, 2024 19:21
Copy link
Collaborator

@archikierstead archikierstead left a comment

Choose a reason for hiding this comment

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

LGTM

@archikierstead archikierstead merged commit b59818b into aws-samples:main Apr 11, 2024
6 checks passed
@rjjaegeraws rjjaegeraws deleted the s3-template-region-fix branch April 11, 2024 16:07
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