StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>The <a href="http://docs.amazonwebservices.com/elasticbeanstalk/latest/dg/create_deploy_NET.managing.elb.html" rel="noreferrer">AWS Elastic Beanstalk Developer Guide</a> explains how to enable an SSL certificate for your Elastic Beanstalk environment.<br> The relevant part is:</p> <blockquote> <p>Controlling the HTTPS port</p> <p>Elastic Load Balancing supports the HTTPS/TLS protocol to enable traffic encryption for client connections to the load balancer. Connections from the load balancer to the EC2 instances are done using plaintext. By default, the HTTPS port is turned off.</p> <p>To turn on the HTTPS port</p> <ul> <li><p>Create and upload a certificate and key to the AWS Access and Identity Management (AWS IAM) service. The IAM service will store the certificate and provide an Amazon Resource Name (ARN) for the SSL certificate you've uploaded. For more information creating and uploading certificates, see the <a href="http://docs.amazonwebservices.com/IAM/latest/UserGuide/ManagingServerCerts.html" rel="noreferrer">Managing Server Certificates</a> section of Using AWS Identity and Access Management.</p></li> <li><p>Specify the HTTPS port by selecting a port from the HTTPS Listener Port drop-down list.</p></li> <li><p>In the SSL Certificate ID text box, enter the Amazon Resources Name (ARN) of your SSL certificate (e.g., arn:aws:iam::123456789012:server-certificate/abc/certs/build). Use the SSL certificate that you created and uploaded in step 1. For information on viewing the certificate's ARN, see <a href="http://docs.amazonwebservices.com/IAM/latest/UserGuide/index.html?InstallCert.html" rel="noreferrer">Verify the Certificate Object</a> topic in the Creating and Uploading Server Certificates section of the Using IAM Guide.</p></li> </ul> </blockquote>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload