Is This Cloud Architecture Efficient for Production?

0
9
Asked By CloudyDay987 On

I'm looking to gather insights from anyone who uses a similar cloud architecture. Here's a rough sketch of mine: it starts with internet users connecting to an application served through a Google API, backed by CloudFront CDN. From there, it splits to an S3 bucket for a static website and a load balancer targeting an EC2 instance running a Node.js API in a Docker container on port 8001. I'm curious if this approach is sound for a production application. Are there any areas for improvement or better alternatives?

5 Answers

Answered By SavingNinja On
Answered By TechSavvy22 On

I would recommend using ECS instead of relying on EC2 with Docker. ECS simplifies management by handling the underlying infrastructure for you. Plus, consider placing a WAF in front of CloudFront for added security. Just watch out for your VPC, security groups, and subnet configurations, as those can really impact your setup's security and efficiency.

Answered By CostConsciousCoder On

I agree with the others about ECS—it reduces complexity significantly. Managing an EC2 instance just adds unnecessary latency when you could streamline it all. We've had this kind of setup at work, but it can get pricey. Have you looked into any cost-saving measures?

Answered By DevOpsFanatic On

Switching to ECS has been a game-changer for me. It reduces the hassle of updating EC2 instances for security vulnerabilities. Also, adding a WAF really helps with threat protection. It’s worth considering if you want to minimize manual maintenance.

Answered By DockerDude77 On

Honestly, I'd steer clear of EC2 in this case. Using ECS would cut down on management overhead, and it fits better for what you're doing. EKS might be better for complex setups, but for a single service, ECS is the way to go.

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.