Scribd
Upload
15 views2 pages

AWS Architecture

The document outlines a proposed architecture for handling data workloads and a three-tier application using AWS services. It suggests using an API Gateway for request management, Amazon EMR for data processing, and various AWS tools for frontend, backend, and database management, ensuring redundancy and security. Additionally, it includes monitoring solutions like AWS Cloudtrail and Amazon Cloudwatch for tracking API calls and resource utilization.

Uploaded by

Wai Phyo Maung
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
15 views2 pages

AWS Architecture

The document outlines a proposed architecture for handling data workloads and a three-tier application using AWS services. It suggests using an API Gateway for request management, Amazon EMR for data processing, and various AWS tools for frontend, backend, and database management, ensuring redundancy and security. Additionally, it includes monitoring solutions like AWS Cloudtrail and Amazon Cloudwatch for tracking API calls and resource utilization.

Uploaded by

Wai Phyo Maung
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Architecture Diagram

*Zoom in if you are not able to view it


Explanation
1. Data Workload handling
Previous:
Data Analytics Workload is previously handled using Apache Hadoop
Proposed Solution:
We are using a API Gateway so that all requests from various sources are handled through a API gateway so that requests can be filtered, and data is processed with
the help of Amazon EMR cluster in AWS so that it can easily handle up to Peta bytes of Data Processing and no failure occurs during data processing. Data is stored
in Amazon S3 Cluster. Amazon Athena is considered for SQL query processing and Amazon Quicksight for showing the required data on dashboard
2. Three Tier Architecture:
Previous:
A three-tier architecture composed of a frontend (HTML, CSS, JavaScript), backend (Apache Web Server and a Java application), and database (MySQL). The three-
tier application hosts a dynamic website that accepts user traffic from the internet.
Proposed Solution:
Frontend: Apache Web server is handled with the help of Amazon Cloudfront to act as a caching methodology for various regions and static web server is handled
on Amazon S3.
Backend & Database : Backend & Database is handled with the help of VPC, Network gateway w.r.t Data and server security and Application Load balancer is used to
handle the requests received on the application/ database. Amazon RDS is considered as SQL database handling as mySQL DB is used on on-premises.
AWS Lambda is used for Application handling & serverless computing.
Considered Two Availability Zones so that if failure occurs in one availability zone can be handled by the resources in another availability zone.
Orchestration Tools such as EKS as used for handling Containers and there Dependencies.
Hybrid Solutions:
a. For Data Backup we have AWS Backup for data redundancy.
b. EKS everywhere has been used as a Orchestration tool to handle the Containers on-premises.
c. AWS Storage Gateway is considered as different versions of Files like NFS can be stored in Amazon S3.
d. AWS Organizations, AWS Control Tower is considered for Account Handling with service Control polocies
e. AWS Service Catalog is considered as Developers, Testers are restricted to usage of specific catalog or services to avoid cost overruns
f. AWS Systems Manager to mange different AWS services enabled in AWS Organization
Monitoring:
a.AWS Cloudtrail to have the logs of API calls and requests and to know the changes done by users.
b.Amazon Cloudwatch to monitor the resources CPU utilization, error logs and Alarms when threshold limits are met.

You might also like