Update static outbound IPs and remove stale entries#226
Merged
Conversation
The /32 IPs listed under IP-based whitelisting were stale CloudFront snapshots from when api.fliplet.com was not CloudFront-fronted. Since all Fliplet API/CDN domains now resolve through CloudFront (dynamic IPs), those specific IPs no longer point to Fliplet infrastructure. Changes: - Add new "Static outbound IPs" section with verified NAT Gateway EIPs for all three regions (EU, US, CA) — these are the IPs that Fliplet servers use when making outbound calls (OAuth2, App Actions, webhooks) - Remove stale /32 IPs from the general IP whitelisting section - Keep S3 CIDR ranges (still valid for CDN asset access) - Strengthen recommendation for URL-based whitelisting - Keep App Actions and Email sections unchanged (already correct)
This file contains hidden or 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
1 participant
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.
Summary
The
/32IPs listed under "IP-based whitelisting" were stale — they no longer resolve to any Fliplet infrastructure. All Fliplet API/CDN domains are now CloudFront-fronted with dynamic IPs.Verified current NAT Gateway Elastic IPs across all three regions by querying AWS directly (
describe-nat-gateways+describe-vpcs+ ECS service network configs + route tables).Changes
/32IPs —52.19.68.87,63.32.114.158,63.32.146.94(EU),54.193.126.209,54.67.74.6(US),3.98.17.196,3.98.43.103(CA) are no longer allocated as Elastic IPsVerified IPs
34.253.89.20052.212.7.11954.215.18.14054.151.38.6252.60.161.2443.98.9.146Context
Triggered by a client request (Orrick) — they use
Fliplet.OAuth2with Azure AD behind a VNet firewall and couldn't create firewall rules because the documented IPs were stale. The OAuth2 proxy (/v1/communicate/proxy/*) runs on the API service, so outbound calls use the production-vpc NAT Gateway EIP.🤖 Generated with Claude Code