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

BCDA-8360 add waf sync lambda #197

Merged
merged 28 commits into from
Jan 14, 2025
Merged

Conversation

carlpartridge
Copy link
Collaborator

🎫 Ticket

https://jira.cms.gov/browse/BCDA-8360

🛠 Changes

Add WAF auto sync lambda

ℹ️ Context

We have recently switched over to WAF to control our allowlist of IP addresses. This lambda should sync our app DB with the source of truth on IP addresses to our WAF.

🧪 Validation

Local tests and linting passing.

@carlpartridge carlpartridge requested a review from a team December 30, 2024 15:01
@carlpartridge carlpartridge changed the title Carl/bcda 8360 add waf sync lambda BCDA-8360 add waf sync lambda Dec 30, 2024
Copy link
Contributor

@laurenkrugen-navapbc laurenkrugen-navapbc left a comment

Choose a reason for hiding this comment

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

Approving, with the steps I took to validate:

  • review lambda invocation to ensure that it's running with no errors (it is)
  • review logs for success messages (they are present)

The only thing that we should do before we cutover is put some test data in our lower env to make sure it works properly. I looked in the dev WAF, and there are no IP addresses. Maybe we can coordinate with @gfreeman-navapbc on some safe-for-use IPs that we can dump in there in the interim?

@carlpartridge carlpartridge merged commit c7b5ade into main Jan 14, 2025
6 of 7 checks passed
@carlpartridge carlpartridge deleted the carl/BCDA-8360-add-waf-sync-lambda branch January 14, 2025 15:08
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.

3 participants