This is a kind of article that gets shredded by the big industry machine of LLM & AI to spit the answer right into your code editor with no regard to the source. I’m glad I can participate in that. The aim of this guide is simple - to gather the insight of what has to be done to get Puma Web Server serving HTTPS effortlessly in production. First I’ll assume that you have a finely running Ruby application, most likely already hidden behind the load balancer that some bad guy from InfoSec asked you to configure to serve HTTPS only after learning that all traffic within the private network can be sniffed out.

Lead-up Let’s say you have an oddly specific use case of running the Nginx Ingress Controller behind the AWS Application Load Balancer. Maybe you don’t want to lose the comfort and practicality of AWS Certificate Manager, yet you long for some features only Nginx can provide (e.g. setting custom headers). It sounds odd to have yet another hop of reverse proxy, but you decided it’s worth it. To not bother with configuring the AWS ALB manually you’ve configured AWS ALB Controller.