2 réponses
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
The easiest way will be to use an ALB with an certificate from ACM. Other options would be to build LetsEncrypt client into your container image and script the certificate request.
Hope this helps.
0
An alternative to using Elastic Load Balancer is to use the AWS API Gateway together with AWS Cloud Map. An overview for this approach is described in this blog post Field Notes: Serverless Container-based APIs with Amazon ECS and Amazon API Gateway
Since you have relatively few requests, and since AWS API Gateway is not priced at an hourly rate like Elastic Load Balancer, it may provide a lower total cost.
répondu il y a 6 mois
Contenus pertinents
- demandé il y a 2 ans
- demandé il y a un an
- demandé il y a 2 ans
AWS OFFICIELA mis à jour il y a 2 ans- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a 3 ans
- AWS OFFICIELA mis à jour il y a un mois
Keep in mind that my application is not that big from Monday to Friday, it handles a maximum of 500 requests and a maximum of 50 people use it, so initially I did not add an ALB, however I understand that for security it is good practice that the server is only through https taking this into account if the ALB is necessary?
I certainly understand your concern given the load. I suspect you would get much better cost/value for this type of workload on a t3a/t4g EC2 instance running Docker and using LetsEncrypt.
I understand your answer and I had considered it, can you tell me, based on your experience, which is the best practice and in which the performance of my application would be better? I am very grateful in advance for your help.
Best practice and performance would both be to use ALB with ACM however you have to weigh that with the cost and importance of your solution. I use low-end instances with Docker/LetsEncrypt for some personal dashboards and self hosted stuff but I would never do this for a business critical production workload.
If I wanted to hibernate the container, that is, turn it off so that it does not charge while it is not in use and turn it on again when they make an https request from the front again, how could I do it?