<p>I am using an existing Security Group in <code>security-groups</code> annotation. But while creating ALB through Ingress it is attaching a default SG. Why it is not attaching the existing SG used in my annotation. And I am using <code>alb-ingress-controller</code>.</p>

<pre><code>apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: app-ingress
  annotations:
    kubernetes.io/ingress.class: alb
    alb.ingress.kubernetes.io/scheme: internet-facing
    alb.ingress.kubernetes.io/target-type: "instance"
    alb.ingress.kubernetes.io/security-groups: sg-**********
    alb.ingress.kubernetes.io/certificate-arn: arn
    alb.ingress.kubernetes.io/listen-ports: '[{"HTTP":80,"HTTPS": 443}]'
spec:
  rules:
  - host: host
    http:
      paths:
      - path: /
        backend:
          serviceName: serviceName
          servicePort: 80
</code></pre>

Parag Poddar
<p>the actual syntax for annotation is 
alb.ingress.kubernetes.io/security-groups: sg-xxxx, nameOfSg1, nameOfSg2</p>

<p>You need to create a pair of SGs. One attaching to ELB and other one attaching to worker nodes where the pods are running. </p>

<p>if sg-12345 with Name tag 'elb_sg' is attaching to ELB and 'worker_sg' is attaching to worker nodes, then the annotation should be:
alb.ingress.kubernetes.io/security-groups: sg-12345, elb_sg, worker_sg</p>

<p>And dont forget to add inbound on worker_sg to all traffic from elb_sg.</p>
