I'm seeking guidance on implementing an AWS ACM wildcard certificate for the domain .*example.com within a Kubernetes cluster, specifically on an EKS instance. My objective is to set up SSL termination for each application within the cluster, ensuring each application has its output on the corresponding host, such as app1.example.com or app2.example.com.
Currently, I have these hosts configured to route through an ELB linked to an Nginx Ingress controller within the cluster. However, I need to determine the best practice for integrating the SSL certificate in this scenario.
Is it advisable to attach the SSL certificate to the Nginx load balancer, or is there a better way to achieve this within the Kubernetes context?
I attempted to attach the ACM certificate to the ELB linked to the Nginx Ingress controller. I expected the SSL termination to work smoothly for my applications with domains like app1.example.com or app2.example.com. However, despite my efforts, I have not been successful.
