[Explain that Architecture #1] A Highly-Available 2-Tier Web Application on AWS
ALX Gold Fellow, Cloud consultant and a Certified educator with 7 years of experience. With experience as a Cloud Consultant, I assist in migrating on-premise workloads to the cloud. I am passionate about Data, AI, and Blockchain, and expertise in the Cloud Adoption Framework and AWS Well-Architected Framework. I specialize in training on industry certifications from major technology providers and excels in co-creation, data analytics, user experience, and problem-solving. I am on a career mission to grow into Technical Program/Project Management and use these skills to lead 500 successful projects targeting the SDGs on Education and Gender Equality.
Welcome to my first post on the Explain that Architecture series, where each week I will develop an Architectural Diagram for a specific use case and provide a high-level explanation of the Diagram.
This week we are going to have a simple architectural diagram that follows High Availability best practices from the AWS Well-Architected Framework
A Highly-Available 2-Tier Web Application Architectural Diagram
Explanation
This is an architecture diagram for an Amazon Web Services (AWS) deployment. It shows how a client can access an application hosted on AWS through an internet gateway. The application is hosted on Amazon Elastic Compute Cloud (EC2) instances, which are located in two availability zones. The instances are managed by an auto-scaling group and are accessed through an application load balancer. The architecture also includes AWS Secrets Manager for managing secrets and a virtual private cloud (VPC) for isolating the application from other resources in the AWS cloud.
Extend the Diagram
Finally, here are some ways for you to extend the diagram:
Add more details about the components and their interactions.
Include more components such as security groups, and other AWS services to support high availability.
Provide more information about the client and how they interact with the system.
Include more information about the availability zones and how they are configured.
Provide more information about the auto-scaling and how it is configured.
Include other services to support other pillars of the AWS Well-Architected Framework and justify them.
Follow me for more Cloud and Cybersecurity content and feel free to share this post with the community.
