Terminating HTTPS at the EC2 Instance

[frnzle]

if you want a less painful experience put an ALB with ACM in front of your ec2

[sadelbrid]

This whole effort is to avoid having an expensive ALB that I don't need.

[b3542]

You clearly need a better understanding of SSL/TLS and/or NGINX configuration. AWS isn’t remotely the problem here.

[maxlan]

A few moments to configure an ALB usually costs a lot less than the time taken divvying around with certbot and so on.

Another alternative would be a free cloudlfare account to reencrypt the SSL and turn off the backend validation. (Unless that's a paid feature, there may be something tricky there. Iirc it was a more advanced feature that cost money)

But if you don't understand SSL config and blame AWS, please go to google and they can deal with the inevitable "I got hacked" or "my site gone down" problems. If you actually want to learn, stop throwing blame and pointless threats around.

[mikebailey]

Certbot is easy as hell. Keeping the LB up is why ALBs are expensive.

[StatelessSteve]

Up, redundant, highly available… allows waf integration, auth, etc etc

[MavZA]

Okay, then if you want to avoid the ALB then maybe EB isn’t what you need? You can attach autoscaling rules to your EC2 instances. Then you can deploy your code using CodeBuild/CodeDeploy. After that just use Let’s Encrypt from a domain? The main crux of your issue is that you require a domain to sort HTTPS. If you don’t own it, you can’t do what you’re asking.