This message was deleted.

Use nginx ingress

Or use the aws lb controller to create an alb with an acm cert and a 443 listener

Hi. Should the aws lb controller be internet facing or internal facing ?

Internet facing since the vcs webhooks need to hit atlantis

I added the following ingress to values.yml and deployed the change using helm upgrade, I see a new load balancer is created.

ingress:
  enabled: true
  ingressClassName:
  annotations: 
      <http://kubernetes.io/ingress.class|kubernetes.io/ingress.class>: alb
      <http://alb.ingress.kubernetes.io/scheme|alb.ingress.kubernetes.io/scheme>: internet-facing
      <http://alb.ingress.kubernetes.io/certificate-arn|alb.ingress.kubernetes.io/certificate-arn>: "arn id"
      <http://alb.ingress.kubernetes.io/listen-ports|alb.ingress.kubernetes.io/listen-ports>: '[{"HTTP": 80}, {"HTTPS":443}]'
      <http://alb.ingress.kubernetes.io/actions.ssl-redirect|alb.ingress.kubernetes.io/actions.ssl-redirect>: '{"Type": "redirect", "RedirectConfig": { "Protocol": "HTTPS", "Port": "443", "StatusCode": "HTTP_301"}}'

I pointed the DNS for my custom domain to the above created load balancer, however, domain atlantis.abc.com is not loading securly(domain is not redirecting to https://atlantis.abc.com). Instead when I access the domain atlantis.abc.com with https , it is loading securly

Maybe redirect port 80 to 443?

I am able to make this work now, however, I am trying to do a atlantis apply on a sample null resource, however, the plan is not getting applied. When I check the webhook request logs, it gives a 200 status code, however, plan is not getting applied.