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

Private invocation #141

Open
ghost opened this issue Dec 18, 2021 · 1 comment
Open

Private invocation #141

ghost opened this issue Dec 18, 2021 · 1 comment

Comments

@ghost
Copy link

ghost commented Dec 18, 2021

It would be nice to restrict invocation to requests containing a secret in a header (X-Invocation-Token). This can be implemented in the deployment's code instead, but unauthorized public requests would still result in invocations (that have a cost).

@vwkd
Copy link

vwkd commented Dec 23, 2021

Sounds like a use case for a „private“ FaaS which is only accessible within the Deno Deploy network from other FaaS in your account. The benefit over a „public“ FaaS which is accessible through the open Internet is that it doesn’t need authentication which would complicate your code. Also it is safer because a door can’t be breached if there is no door.

See proposal #88 for more details on a single-instance private FAAS and a multi-instance private FAAS in the “Future” section.

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

1 participant