$$ The solution should be deployed in the US East N$.$ Virginia Region and use a single$-$entry point to receive all user traffic.

$$ A two$-$tier architecture must decouple the application$/$web and database for improved performance. The web tier should be designed with high availability to facilitate business continuity and minimal downtime.

$$ The application must scale to support thousands of users. The University expects $600-800$ visitors$/$day on weekends and $1\mathrm{.}5-2$K visitors$/$day during weekdays. There should be a provision to dynamically adjust the capacity of the web tier without any manual intervention for various traffic levels. Different scaling approaches should be evaluated to determine the most economical strategy. The web tier must also be self$-$healing.

$$ Appropriate security controls must be in place to ensure that the architecture is secure$.$

$$ The solution must be designed to keep costs low.

$$ The solution must meet functionality requirements such as the ability to view, add, delete, or modify the student records, without any perceivable delay and under variable and peak loads.

Design and Cost Modeling Document

Max. Points: $200$

$1$: Architectural Diagram $(50$ points$)$

Paste your Architectural Diagram in the space below.

$$

$$

$$

$$

$$

$$

$$

$$

$2$: Cost Calculations and Justification $(50$ points$)$

Use Formulas for Cost Calculations on AWS document as the reference to determine the following parameters. All calculations must be shown.

$1.$ Number of Concurrent users $($CCU$)$ and justification for choice of Amazon EC$2$ instance type $/$ size $/$ number for the web tier during normal traffic. Describe your strategy to support traffic spikes. Provide supportive calculations to show how your proposed solution is cost$-$effective.

$$

$2.$ Bandwidth calculation for the website

$$

$$

$$

$$

$$

$$

$$

$3$: $$Component Summary $(50$ points$)$

Fill out the following table to provide summarized information about the different architectural components $/$ services that will be used in the project.

A sample entry has been shown.

$$

AWS Component $/$ Service

Specification

Description

Amazon EC$2$

Linux, t$3.$medium $(4$ GB memory, $2$ vCPU$)$

$100\%$ utilization, On$-$demand pricing

On average per day, there are four $(3)$ instances running

Elastic Load Balancer

Application load balancer

Distributes incoming traffic across multiple EC$2$ instance

Amazon RDS

MySQL$,$db$.$t$3.$medium$(4$ GB memory $,2$ vCPU$)$

Scaling up to $3$ during peak loads.

$$

$$

$$

Amazon CloudWatch

Basic monitoring $,$custom Metrics

Monitoring and Observability service that provides DATA and insights for AWS resources.

$$

$$

$$

$$

$$

$$

$$

$$

$$

Table $1$: AWS Component $/$ Service Summary

$$

$4$: $$Cost Estimate $(50$ points$)$

Use the AWS Pricing Calculator to calculate the monthly cost estimate for the different AWS services in your architecture. Export your estimate as a CSV or PDF and upload separately to submit.

List the monthly and annual cost estimate for the proposed solution below