What Do You Think of My Project Architecture?

Switching to ECS or Fargate sooner rather than later could be beneficial. It allows you to maintain the ease of a single box setup while providing you with autoscaling and rolling deployments. Instead of resizing EC2 instances during traffic spikes, you can simply adjust your desired tasks. Regarding your Redis and message queue servers, consider whether using Elasticache and SQS might save you time and resources; it could be a smart move performance-wise!

Before going live, did you have a UAT environment to test your architecture? It’s a great way to evaluate security, performance, and availability. A more concrete architecture diagram would help us provide better feedback, but it seems you might want to address high availability and monitoring—both essential for production. Also, consider integrating security features like Cognito for user authentication and WAF/Shield if they're not already in place. Regarding scaling, using an Auto Scaling Group is recommended over vertical scaling due to downtime.

Your setup sounds solid! Instead of just scaling your EC2 instance vertically, consider looking into horizontal scaling with a load balancer. That way, you'll avoid downtime, and it’ll be easier to manage traffic spikes. Also, don't forget to check into using ECS to manage your Docker containers; it helps with scaling and updates without much hassle. For the database, think about implementing read replicas since you’ll be having lots of reads, which could really help offload some stress from the main database. S3 and CloudFront are definitely good choices for serving static assets, so you're on the right track there!