Launch type: Serverless | Template: Cloudfront | Security: Low | Language: HCL

Description

• S3 bucket will share static website files with server-side encryption enables for all objects. Versioning is automatically enabled to prevent accidental deletion.
• Route 53 creates primary and secondary records to route traffic based on health checks.
• Cloudfront creates a distribution to serve static web pages from the s3 bucket. Configured with a TLS Certificate from AWS.

Build Order

Launch type: Non-serverless | Template: EC2 | Security: High | Language: HCL

Description

• I've built a resilient infrastructure with Route 53 routing to an Application Load Balancer, securely directing traffic to private instances hosting a dynamic website.
• I placed a bastion host in the public subnet enabling secure SSH access to the private instances.
• The infrastructure is designed for multi-region, multi-Availability Zone deployment and aimed at ensuring resiliency and minimizing downtime.

Build Order

Launch type: Serverless | Template: AWS containers | Security: High | Language: HCL

Use Case

• Using Fargate to host a dynamic website allows for seamless scaling based on traffic demands, enables cost-efficiency, efficient resource utilization, and removes operational overhead.
• Fargate can be employed for backend processing of on-demand tasks, such as image or document processing that allows the organization to efficiently scale resources based on variable workloads without the need for managing dedicated servers.

Description

• I created an image in docker and pushed it to the container registry in AWS in order to run it in a serverless fashion through fargate.
• The infrastructure is fuly serverless, resilient, highly available and configured to failover to a backup region with zero downtime.
• I maximized the security by placing the ECS service in private subnets which can only be accessed through the load balancer. The image runs on a container and keeps its important details in a Dynamo database.

Build Order

Launch type: Hybrid | Template: Kubernetes | Security: High | Language: HCL

Description

• I created an image in docker and pushed it to the ECR. The image is intended to host a dynamic website on managed kubernetes containers.
• The region has two availability zones available, one that runs serverless eks containers, and one that runs non-serverless containers on ec2.
• The EC2 containers are configured with a bastion host that allows SSH access into the containers virtual machines for troubleshooting purposes..
• YAML files configure Grafana and Promethues to monitor/scrape my containers and provide me with performance and health metrics.

Build Order

Launch type: EC2 | Template: Apache | Language: HCL

Description

• This architecture diagram shows a highly available AWS deployment where traffic from users flows through Route 53 DNS to a load balancer in the public subnet.
• The load balancer directs requests to EC2 instances running Red Hat and Apache in private subnets, which are managed by an auto scaling group for reliability.
• The application is backed by a PostgreSQL database with a main instance and a replica, while monitoring and security are handled by CloudWatch and SSL/TLS.