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

Security Best Practices with Inngest #487

Open
hckhanh opened this issue Feb 14, 2024 · 1 comment
Open

Security Best Practices with Inngest #487

hckhanh opened this issue Feb 14, 2024 · 1 comment

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

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

2 participants