[英]When deploying a Docker container to AWS, do i need to deploy my own reverse proxy as well?
I have a rails API to handle data and server logic for other client apps. 我有一个Rails API来处理其他客户端应用程序的数据和服务器逻辑。 When dockerizing and deploying it to AWS elastic beanstalk (generic docker - single container), it fails.
在对其进行docker化并将其部署到AWS Elastic beantalk(通用docker-单个容器)时,它会失败。 Do i need to deploy multiple containers, to include my own configuration of nginx?
我是否需要部署多个容器以包括我自己的Nginx配置? or does AWS have a way to handle the reverse proxy for me?
还是AWS有办法为我处理反向代理? Just looking for a little guidance.
只是在寻找一些指导。 If I have to handle nginx myself that's fine (and any pointers there would be nice), but I'm actually trying to offload as much setup and configuration as possible onto the services AWS provides and keep a more narrow focus on the code I need to write for the API itself
如果我必须亲自处理nginx(并且任何指针都会很好),但实际上我正在尝试将尽可能多的设置和配置分担到AWS提供的服务上,并更加专注于我需要的代码为API本身编写
You can use the AWS ALB, so the application load balancer ( https://aws.amazon.com/de/elasticloadbalancing/applicationloadbalancer/ ), which you deploy in the EC section and which does understand you container configuration, thus offers you to target a container / port in your ECB stack. 您可以使用AWS ALB,因此可以在EC部分中部署并且可以理解您的容器配置的应用程序负载均衡器( https://aws.amazon.com/de/elasticloadbalancing/applicationloadbalancer/ ),从而为您提供了在您的ECB堆栈中定位一个容器/端口。 This is the way you would avoid a own nginx container as the load balancer with a configuration, ALB will handle this for you, also with the SSL interception and the promise to be really reliable ( and some limitations )
这是您避免使用自己的nginx容器作为具有配置的负载均衡器的方式,ALB会为您处理此问题,同时还会通过SSL拦截和保证确实可靠的承诺(以及某些限制)
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.