-
Notifications
You must be signed in to change notification settings - Fork 3
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
[QOLDEV-908] move WAF stack to global region #557
Conversation
ThrawnCA
commented
Jul 8, 2024
•
edited
Loading
edited
- WAFv2 resources are required to be in the us-east-1 region, but CloudFormation exports cannot cross regions, so use the SSM Parameter Store to pass necessary values.
- CloudFront is meant to be managed globally, and WAFv2 resources are required to be in the us-east-1 region
…ailable in the region
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
unsure if this will work when cfn cloudfront is made in sydney.
- Move CloudFront distribution back to the original region, but pass the Web ACL ID via SSM Parameter Store so we can cross regions
CmsOrigin: "{{ CmsOrigin }}" | ||
WebACLId: "{{ Environment }}CKANWebACLId" | ||
WebACLId: "{{ lookup('aws_ssm', '/config/CKAN/' + Environment + '/common/waf_acl_id', region='us-east-1') }}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is a way to make this lookup on cfn template. But you do need to give different param string per env for it to work. See repo site-myqldgovau iam.cfn.yml file in the .GitHub/aws folder
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For now I would probably choose to keep the style consistent with other templates in this repo.
Do update the pr message per the changes |