<p>We are using EKS and Nginx-ingress(NLB). I'm trying to configure multiple AWS ACM certificates in the AWS-load-balancer-SSL-cert annotation for NLB. But with no luck. Could someone help if it possible at all? Thanks</p>
<p>If that not possible, Please guide me any other way on how to use multiple ACM cert in the ingress object-level if possible.</p>
<p><strong>My EXACT Scenario:-</strong></p>
<p>I am using an NLB (FYI)</p>
<p>If we able to add multiple ACM certificate at controller level that also works for me (I am using a single certificate  in my NLB currently see below annotations)</p>
<p>At the controller level, these flags help me to add a single certificate:-</p>
<pre class="lang-yaml prettyprint-override"><code>service.beta.kubernetes.io/aws-load-balancer-ssl-cert: arn:aws:acm:ap-south-1:1234556677:certificate/3a1d5a-469b-dffe4bad3182
service.beta.kubernetes.io/aws-load-balancer-type: nlb
</code></pre>
<p>or</p>
<p>I am maintaining an ingress object as per NameSpace. if we are able to attach a Certificate at the ingress object level, which also solves my problem.</p>

<p>Good question.</p>
<p>There is no support for multiple ACM certificates on an ALB/NLB that points to an nginx ingress controller (or any other ingress controller AFAIK).</p>
<p>The dirty hack from Kubernetes is to create another <code>Service</code> that points to the same nginx ingress controller (same selectors) but in this case, it will just create another ALB/NLB and you may not want that.</p>
<p>The non-Kubernetes way which is the way might work better for you is just to do it from AWS itself and modify the ALB/NLB that sends traffic to your nginx ingress.</p>
<p><a href="https://i.stack.imgur.com/ft3P2.png" rel="noreferrer"><img src="https://i.stack.imgur.com/ft3P2.png" alt="Image1" /></a>
<a href="https://i.stack.imgur.com/IiFNt.png" rel="noreferrer"><img src="https://i.stack.imgur.com/IiFNt.png" alt="Image2" /></a></p>
<p>✌️</p>
