PLT-504: Add BCDA dev environment to WAF configuration #129
+4
−1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🎫 Ticket
https://jira.cms.gov/browse/PLT-504
🛠 Changes
This adds the BCDA dev environment to the apply workflow of the new WAF configuration.
ℹ️ Context
We're moving all apps to WAF for IP filtering. This should alleviate some of the issues we have with security groups and maintaining our CIDR whitelists.
🧪 Validation
BCDA dev should be able to be reached on the VPN, but no other traffic should be let through. The BCDA team may need to add CIDR ranges to the new IP-set that will be created. We'll also need to remove the association to the dev WAF and security group in place in the bcda-ops repo: https://github.com/CMSgov/bcda-ops/pull/1114