Select a Web Application Idea:
Choose a type of simple web application your group would like to hypothetically deploy
(e.g., a personal blog, a photo gallery, or an online portfolio).
Identify AWS Services Needed:
Consider the components necessary to build and host the application. List which AWS
services you would use for each task:
o Compute: Which service(s) would handle processing and hosting the app?
o Storage: How will you store data (e.g., S3 for static files, database options)?
o Networking: How would you control traffic and secure access (e.g., Security
Groups, VPC)?
o User Access and Permissions: How would you manage access for different
users?
Draw Your Architecture:
Use pen and paper to sketch your web application’s architecture. Include and label the
AWS services involved, showing the relationships between each component.
For example:
o EC2 for hosting
o S3 for storing images or static files
o RDS or DynamoDB for managing application data
o IAM roles for user access control
Define Security Measures:
Discuss and note down which security settings you would use.
Example: Security Groups to restrict HTTP/HTTPS access, IAM roles to manage
permissions.
Reflection and Discussion:
Present your architecture to the class, explaining:
o The chosen AWS services and their roles.
o Key security measures and why they’re necessary.
o How this architecture would scale if the application became more popular.
Submission:
Each group will submit a diagram of their architecture along with a summary describing:
The purpose of each AWS service used
Security configurations and justifications
Scalability potential and potential improvements
