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

Static Inngest IPs #487

Open
hckhanh opened this issue Feb 14, 2024 · 4 comments
Open

Static Inngest IPs #487

hckhanh opened this issue Feb 14, 2024 · 4 comments

Comments

@hckhanh
Copy link

hckhanh commented Feb 14, 2024

Is your feature request related to a problem? Please describe.

I searched in Inngest docs but I cannot see any section about the security practices

Additionally, Are there any ip ranges just for inngest connection only. I really want to whitelist the access connection from Inngest to /api/inngest api

@JonParton
Copy link

JonParton commented Apr 23, 2024

Also interested in this answer and it being documented some where!

From Searching Discord I found there used to be some fixed IP's and now it looks like Inngest migrated to some new ones.

tonyhb @ inngest — 20/03/2024 18:18
ideal. we'll be moving to our new IP range 198.212.45.0/24 this week + next, at which point we'll be allowlisted by clouds

@tonyhb - If you confirmed if the migration happened and the Inngest server now has a set of IP's as below you will be able to close this ticket easily 🙂👍

198.212.45.0/24

@jasonroelofs
Copy link

Is this IP range active? I tried using it and it didn't seem to work yet.

@JonParton
Copy link

JonParton commented Nov 2, 2024

So, pretty sure these are not implemented yet @jasonroelofs .

However, there is an endpoint below that will provide you with the current Inngest source IP's

https://inngest.com/ips-v4

@tonyhb also confirmed that any new IP's would appear in this endoint at least 48 hours before use ... So you have that rolling window to have a cron function to keep them in sync in your white lists etc!

Don't think that these details are actually documented any where ... But if it were it could probably close this ticket!

@jasonroelofs
Copy link

Got it, thanks for the link!

@hckhanh hckhanh changed the title Security Best Practices with Inngest Whitelisting Inngest IPs list Nov 3, 2024
@hckhanh hckhanh changed the title Whitelisting Inngest IPs list Static Inngest IPs Nov 5, 2024
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

No branches or pull requests

3 participants