该网站工作完全正常的HTTP，但不会对HTTPS工作。 我跟着这个页面上的所有步骤来创建自签名证书并将其添加到我的弹性魔豆环境。 http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/configuring-https.html

The site works perfectly fine on HTTP, however, does not work on HTTPS. I've followed all the steps on this page to create a self-signed certificate and add it to my Elastic Beanstalk environment. http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/configuring-https.html

我还使用下面的命令得到一个成功的证书响应回从IAM： AWS IAM获得服务器证书--server证书名称

I'm also getting a successful certificate response back from IAM using the following command: aws iam get-server-certificate --server-certificate-name

在更新弹性魔豆与证书，我还添加规则添加到安全组中，它允许入站流量从0.0.0.0/0到443端口。 最后，我也验证了我的负载均衡器监听器HTTPS设置正确。

After updating Elastic Beanstalk with the certificate, I've also added add a rule to the security group that allows inbound traffic from 0.0.0.0/0 to port 443. Finally, I've also validated that my load-balancer listener has HTTPS set up correctly.

尽管一切，我的电话到https没有解决，而HTTP是工作完全正常。 任何其他的想法吗？任何帮助将是非常美联社preciated。

In spite of all that, my calls to https is not resolving, while http is working perfectly fine. Any other thoughts on this? Any help would be much appreciated.

请让我知道如果你需要任何更多的信息。拼命找一些见解/帮助到这一点。

Please let me know if you need any more information. Desperately looking for some insight/help into this.

无论如何，不​​能够解决这个问题，我的网站/ code，我试图建立HTTPS上提供弹性魔豆样品的网站。有趣的是，即使不工作。

Anyway, not being able to resolve this issue with my site/code, I tried to set up HTTPS on the sample site provided on Elastic Beanstalk. Interestingly enough, even that is not working.

推荐答案

我想提供一个更新，我终于能够解决这个问题。 根本原因是因为我错过了设置入站规则的负载均衡器的安全组。

I want to provide an update that I was finally able to resolve the issue. The root-cause was because I missed to set up an Inbound Rule for the Security Group of the Load Balancer.

无论出于何种原因，当我阅读文档，我理解的是，入站规则需要被设置为实例的安全组（而不是负载均衡）。只有当我开始跟踪负载平衡器，我才意识到，我也许应该尝试建立规则的负载均衡器的安全组。所以，问题得到解决。下面是我使用的设置。

For whatever reason, when I read the documentation, I understood that the Inbound Rule needed to be set up for the Security Group of the Instance (and not the Load Balancer). Only after I started tracing the Load Balancer did I realize that I should perhaps try setting up the Rule for the Security Group of the Load Balancer. So, the problem is resolved. Below is the setting I used.

HTTPS           443     HTTP        80      <name of the certificate>

我不得不说，文件可能会更清楚一点清楚地确定所需的负载均衡器的安全组（而不是实例）的变化。

I'd have to say that the documentation could be a bit more clear to clearly identify the change required to the Security Group of the Load Balancer (and not the Instance).