I just started a new job as a junior cloud platform and infrastructure officer, and my tech lead has assigned me a project that requires me to create a schema. I'm working with several AWS services including S3, Route 53, Certificate Manager, two EC2 instances, a Load Balancer, RDS (SQL), CodePipeline, and CodeBuild (with source code coming from GitHub). I'm feeling a bit lost when it comes to understanding how to put together this schema or diagram for my project. If anyone has resources or tips to help me out, I would really appreciate it! Thanks in advance for your thoughts and recommendations.
2 Answers
It sounds like you'll need three separate diagrams:
1. One for the runtime aspects like EC2 instances, load balancers, RDS, and S3.
2. A second for the DNS setup involving Route 53, S3, and the Load Balancer.
3. And a deployment diagram that includes CodePipeline, CodeBuild, and EC2.
Don't try to cram all of this into one big diagram; it usually ends up being confusing. Keeping them separate will make your life easier. Check out this article for more details on why breaking it apart is a good idea!
So, I need to create three parts all within the larger AWS setup, right?
Since I'm working on a three-tier application, I assumed I should combine everything into a single diagram, but it looks like that's not the best approach. Thanks for clarifying this for me!
Yeah, a lot of diagrams online tend to oversimplify things. Real-world systems are usually more complex. Just remember that even for the runtime diagram, representing a 3-tier architecture in the bigger system makes sense. You can find examples online that break it down nicely!
Oooo, this is a fantastic breakdown! Really helps clarify things.