英文:
SSL with docker elastic beastalk intance
问题
我有一个使用Docker部署在Elastik Beanstalk服务上的Nestjs应用程序。
在我的安全组的入站规则中,我有80端口和443端口。
我创建了一个子域名,并使用CNAME将其重定向到我的应用程序URL。
我使用ACM生成了一个SSL证书,并使用提供的CNAME进行验证,验证通过。
我的应用程序在HTTP中的URL上工作,但在HTTPS中不工作。
我知道如何在Node.js应用程序中做到这一点,我只需要进入我的环境配置并转到负载均衡器,但是使用Docker,我没有直接在环境中进行操作的可能性。
我创建了一个应用程序负载均衡器,并在规则和目标组中添加了80端口和443端口,并在我的应用程序中监听80端口(状态为健康绿色)。
我的安全组允许443端口。
我的子域名在HTTP上工作,但在HTTPS上不工作。
英文:
I have a Nestjs application which is deployed with Docker on an Elastik beanstalk service.
Among the incoming rules of my security group I have port 80 and 443.
I created a subdomain and redirected to my application url with CNAME.
I generated an SSL certificate with ACM and validated with the provided CNAME and it validated fine.
My application works with the url in HTTP but not in HTTPS.
I know how to do it with a nodejs application, I just have to go to my environment configuration and go to load balancer but with Docker, I don't have the possibility to do it directly in the environment.
I have create a Application load balancer and i have add port 80 and 443 with rules and target group listen port 80 in my application (status healthy green)
My subdomain http work but my https not working.
答案1
得分: 3
我认为应用负载均衡器的安全组如果没有允许,将会阻止HTTPS流量。我建议检查与负载均衡器关联的安全组。
英文:
I think application load balancer security group will block the HTTPS traffic if not allowed. I suggest to check Security Group which is attached to Load balancer.
通过集体智慧和协作来改善编程学习和解决问题的方式。致力于成为全球开发者共同参与的知识库,让每个人都能够通过互相帮助和分享经验来进步。
评论