5 ms·
Just a few days ago I spent $200 to purchase a multi-domain wildcard certificate so that I could host multiple secure domains, with multiple subdomains, on a si
by ttcbj 11y ago
Just a few days ago I spent $200 to purchase a multi-domain wildcard certificate so that I could host multiple secure domains, with multiple subdomains, on a single elastic beanstalk app. It was such a headache to figure out that I needed the multi-domain wildcard cert, then to find one to purchase for a reasonable price.
Now, 5 days later, AWS lets me create one for free in 3 minutes, with zero hassles. I cannot select it in beanstalk yet, but I am sure that will come. I am consistently amazed by how frequently AWS satisfies needs I barely knew (or didn't know) I had.
- dexterdog 11y agoI don't think you configure the LB in EB. Go into Load Balancers in your EC2 section and you can select the cert there. It's a quick switch.
- 15155 11y agoIf EB decides to tear down and rebuild an ELB, it won't have the correct cert settings.
- mentat 11y agoYou can probably manually specify in EB config files for ELB. Haven't touched that in a couple years but support should be able to help. If not reach out and I'll try to reconstruct.
- arcdigital 11y agoI just made this post about enabling beanstalk: https://medium.com/@arcdigital/enabling-ssl-via-aws-certificate-manager-on-elastic-beanstalk-b953571ef4f8 https://medium.com/@arcdigital/enabling-ssl-via-aws-certific...
- derFunk 11y agoI'm feeling the same. Just send a bunch of personal data to an Israeli CA. With having ACM earlier that would have been obsolete.
- Human_USB 11y agoSomething like this should help: option_settings: aws:elb:listener:80: ListenerEnabled: false aws:elb:listener:443: InstancePort: "80" InstanceProtocol: "HTTP" ListenerProtocol: "HTTPS" SSLCertificateID: "<replace with ACM cert ARN>"