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

Configuring Envoy as a Forward Proxy with AWS API Gateway IAM Authorization #38111

Open
njeddi opened this issue Jan 20, 2025 · 0 comments
Open
Labels
triage Issue requires triage

Comments

@njeddi
Copy link

njeddi commented Jan 20, 2025

Hello,

We are working on a use case where we want to configure Envoy as a forward proxy to intercept all egress traffic with external authentication using AWS API Gateway (IAM authorization). However, when attempting to use the External Authorization (ExtAuthz) filter, we encounter a 403 error without any logs being traced in API Gateway’s CloudWatch logs.

Here’s the flow we are trying to achieve:

1- Incoming request (to access an external URL)
2- Envoy (acting as the forward proxy)
3- External Authorization (ExtAuthz) with AWS API Gateway IAM Authorizer
4- If authentication is successful, the request is forwarded to the internet.

Could you confirm if Envoy is capable of handling this scenario? Additionally, if anyone has experience with this configuration, could you please share any example setups or guidance?

Thank you for your help!

Best regards,

@njeddi njeddi added the triage Issue requires triage label Jan 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage Issue requires triage
Projects
None yet
Development

No branches or pull requests

1 participant