Add source IP conditions to SSB-services

GSA / notifications-api

The API powering Notify.gov

Other

10 stars 2 forks source link

Add source IP conditions to SSB-services #223

Open rahearn opened 1 year ago

rahearn commented 1 year ago

Todo:

[x] https://github.com/GSA/ttsnotify-brokerpak-sms/pull/3
[x] bump sms pak version
[x] https://github.com/GSA-TTS/datagov-brokerpak-smtp/pull/25
[x] bump smtp pak version
[x] https://github.com/GSA/usnotify-ssb/pull/11
[x] https://github.com/GSA/notifications-api/pull/225
[x] wait for authoritative answer on VPN/Zscaler egress IP addresses
[x] wait for GSA-wide zscaler rollout (should be by end of May)
[ ] lock down development service keys

rahearn commented 1 year ago

Instructions for determining ZScaler egress IPs

rahearn commented 1 year ago

Once zscaler is deployed to all GFE being used on the project, follow the above instructions to use nslookup to determine which set of zscaler egress IPs to default to. Include instructions in the onboarding/setup docs for how any non-GFE can supply their own IP address to override the zscaler list.

rahearn commented 1 year ago

@stvnrlly since this will likely be blocked until after I'm gone, let me know if you have any questions about it

tdlowden commented 1 year ago

This requires rollout of Zscaler in order to pursue.

tdlowden commented 1 year ago

I think we are clear to pursue this now?

ecayer commented 2 months ago

locking down dev service keys sounds like a potentially important thing to do to finish this... should someone pick this up, @ccostino ?