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

Enable SSL Encryption from LB to Kong Instances #12

Open
lorenzoaiello opened this issue Nov 26, 2019 · 3 comments
Open

Enable SSL Encryption from LB to Kong Instances #12

lorenzoaiello opened this issue Nov 26, 2019 · 3 comments

Comments

@lorenzoaiello
Copy link
Contributor

We need end-to-end encryption, including SSL from the ALB to the EC2 instances.

@DennoVonDiesel
Copy link
Contributor

Would it be sufficient to optionally provision an NLB or Classic ELB for passthrough SSL directly to Kong?

@lorenzoaiello
Copy link
Contributor Author

Definitely an option, we'd just need to figure out how we want to get the SSL certs on the Kong instances (assuming they can't be applied via the API once it's online - I've not looked into the possibility of doing that).

@p0pr0ck5
Copy link

Kong has a notion of a per-service certificates, so it would be wrong to assume there would be just one certificate for an ALB to establish a handshake with.

It makes sense for an NLB to front Kong, given that Kong supports more than just HTTP traffic. And the NLB can still perform HTTP healthcheck to the upstream ASG.

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