-
Notifications
You must be signed in to change notification settings - Fork 43
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
Comments
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 - 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 🙂👍
|
Is this IP range active? I tried using it and it didn't seem to work yet. |
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 @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! |
Got it, thanks for the link! |
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
apiThe text was updated successfully, but these errors were encountered: