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

EKS (L7) SSL Termination at ELB - Proxy Protocol and HTTP to HTTPS redirection #3274

Closed
vikas027 opened this issue Mar 13, 2021 · 2 comments
Closed

Comments

@vikas027
Copy link

vikas027 commented Mar 13, 2021

Describe the bug

I have a working Ambassador setup where I have terminated SSL on the Classic ELB (using ACM certificate). I have also enabled proxy protocol using the ELB annotation but when I enable HTTP to HTTPS redirection, it gets stuck in a https loop.

I also want to have HTTP to HTTPS redirection too along with the proxy protocol. I think I need some options set here but can't figure them out.

To Reproduce
Steps to reproduce the behaviour:

  1. Patch the service
---
apiVersion: getambassador.io/v2
kind:  Module
metadata:
  name:  ambassador
spec:
  config:
    use_proxy_proto: true
    use_remote_address: false
    x_forwarded_proto_redirect: true

---
apiVersion: getambassador.io/v2
kind: Host
metadata:
  name: ambassador
spec:
  hostname: "*"
  selector:
    matchLabels:
      hostname: wildcard
  acmeProvider:
    authority: none
  requestPolicy:
    insecure:
      action: Route
      # action: Redirect # Redirection loop

Expected behaviour
I would expect Ambassador to behave normally and have the HTTP to HTTPS redirection working smoothly :)

Versions (please complete the following information):

  • Ambassador: v1.12.1
  • Kubernetes environment: EKS
  • Kubernetes Version: v1.19.8

Related tickets

@vikas027 vikas027 changed the title EKS (L7) SSL Termination at ELB - HTTP to HTTPS redirection EKS (L7) SSL Termination at ELB - Proxy Protocol and HTTP to HTTPS redirection Mar 13, 2021
@EvertonSA
Copy link

please post your service definition

@vikas027
Copy link
Author

Closing the issue. I have regenerated the manifests using the official link and things worked for me.

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