0% found this document useful (0 votes)
44 views1 page

Web Application Architecture On Aws Ra

Route traffic from web clients based on the request path for static and dynamic contents using Amazon Route 53. Protect the web application from common exploits with AWS WAF. Use Amazon CloudFront to reduce latency when delivering static contents. Use services like Amazon S3, ACM, EC2, RDS, EFS, and ElastiCache to host, secure, and optimize the web application architecture on AWS.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
44 views1 page

Web Application Architecture On Aws Ra

Route traffic from web clients based on the request path for static and dynamic contents using Amazon Route 53. Protect the web application from common exploits with AWS WAF. Use Amazon CloudFront to reduce latency when delivering static contents. Use services like Amazon S3, ACM, EC2, RDS, EFS, and ElastiCache to host, secure, and optimize the web application architecture on AWS.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

Route traffic from web client based on the

1
request path for static and dynamic

Web Application Architecture on AWS contents using Amazon Route 53.


Protect your web application from
This architecture shows how you can host a classic web application on AWS. 2 common web exploits with a web
application firewall like AWS WAF.
AWS Cloud Use a content delivery network (CDN),
VPC 3 like Amazon CloudFront, to reduce
11 10
latency of delivering your static.
1
Use Amazon Simple Storage Service
Amazon EFS Amazon ElastiCache 4
(Amazon S3) to store static contents and
shared storage caching service
Web Amazon Route 53 backups.
Client DNS service Availability Zone 1
Simplify your SSL certificates
Public subnet Web subnet Application subnet Database subnet 5 management using ACM.
2

7 9 Use an internet-facing Application Load


AWS WAF
6 Balancer to distribute web traffic to your
web servers spread across multiple
NAT gateway EC2 Instances EC2 Instances Amazon RDS
web servers application servers
availability zones.
primary database
3 Use NAT gateways in each public subnet
7 enable Amazon Elastic Compute Cloud
6 8 (Amazon EC2) instances in private
Database subnet subnets to access the internet.
Application Auto Scaling group Application Auto Scaling group group Use an internal Application Load
Amazon CloudFront 8
content delivery network 5 Load Balancer Web tier Load Balancer Application tier Balancer to distribute traffic to your
Availability Zone 2
application servers spread across
multiple Availability Zones.
4 Public subnet Web subnet Application subnet Database subnet
Simplify your database administration by
AWS Certificate 9 running your database layer in Amazon
Manager (ACM)
Relational Database Service (Amazon
RDS).
Amazon RDS
NAT gateway EC2 Instances EC2 Instances
standby database If database access patterns are read-
Amazon S3 web servers application servers 10 heavy, consider taking advantage of a
static storage
and backup caching layer like Amazon ElastiCache.
Consider using a shared storage service,
11 like Amazon Elastic File System
Reviewed for technical accuracy November 19, 2021 (Amazon EFS), if your servers have
© 2021, Amazon Web Services, Inc. or its affiliates. All rights reserved. AWS Reference Architecture
access to shared files.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy