---
title: "Discussion on \"Deployment of a Dockerized Application with AWS EC2, Nginx, Docker, and Automated SSL via Certbot\" | Hashnode"
description: "Discussion on \"Deployment of a Dockerized Application with AWS EC2, Nginx, Docker, and Automated SSL via Certbot\". INTRODUCTION\nIn this project, I worked on deploying a web application on AWS EC2. I used Docker to containerize the app, Nginx to manage traffic as a reverse proxy, and Certbot to set up SSL for secure connections. The project's goal was to create a ..."
url: "https://hashnode.com/posts/deployment-of-a-dockerized-application-with-aws-ec2-nginx-docker-and-automated-ssl-via-certbot/673dd636b20978f27f9a7c90"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Deployment of a Dockerized Application with AWS EC2, Nginx, Docker, and Automated SSL via Certbot](https://ronke.hashnode.dev/deployment-of-a-dockerized-application-with-aws-ec2-nginx-docker-and-automated-ssl-via-certbot?utm_source=hashnode&utm_medium=feed)

INTRODUCTION In this project, I worked on deploying a web application on AWS EC2. I used Docker to containerize the app, Nginx to manage traffic as a reverse proxy, and Certbot to set up SSL for secure connections. The project's goal was to create a ...

Nov 20, 2024 · 3 min read · ronke.hashnode.dev  
Read the article

-   [#devops](https://hashnode.com/tag/devops)
-   [#docker](https://hashnode.com/tag/docker)
-   [#aws](https://hashnode.com/tag/aws)
-   [#nginx](https://hashnode.com/tag/nginx)
-   [#ec2](https://hashnode.com/tag/ec2)

## Written by

[Ronke Akinyemi](https://hashnode.com/@Ronke03)

@Ronke03 · Ibadan,Nigeria

  
[View profile](https://hashnode.com/@Ronke03)

DevOps

DevOps Engineer

## Responses 1

Markdown supported · ⌘↵ to post

[CDN Edge Ops](https://hashnode.com/@cdnedgeops)

[Oct 31](https://hashnode.com/posts/deployment-of-a-dockerized-application-with-aws-ec2-nginx-docker-and-automated-ssl-via-certbot/673dd636b20978f27f9a7c90/comment/6ae53b49e6bf8b25f54d7441)

On EC2 I put Certbot renew on a timer and run nginx -t before reloading. I also pin the proxy\_pass upstream by private IP or docker network name so a container recreate does not leave nginx pointing at a dead address until the next restart.
