This pattern is a realization of the AWS published pattern called Web Application Hosting
This AWS pattern it is used for “web hosting highly available and scalable applications with complex architecture. Dense peak periods and wild swings in traffic patterns result in low utilization of expensive hardware. AWS provides the reliable, scalable, secure and high performance infrastructure required for web applications while enabling an elastic scale out and scale down infrastructure to match IT costs in real time as customer traffic fluctuates”.
In this pattern the users’ DNS requests are served by Amazon Route53 service.
This pattern uses CloudFront to enable greater fault tolerance in your applications and to provide best possible performance.
At the same time, web server has been offloaded parts of its content to Amazon S3 to be pushed to each newly launched server by Autoscaling.
The S3 has a Bucket Policy to allow access to its bucket content. You will need to setup up permission on your bucket to allow your web server access to your content and also users publicly access to S3 content.
The content that is served through S3 has higher availability due to the fact that S3 has nine “11s ” durability. The web servers need public IP to access S3 buckets.
NOTE: In a normal configuration, you do not need to connect users to ELBs if they are served by CloudFront. It is best practice to serve all static content from CF if you have chosen to use CF. So this pattern shows you specific scenario that you may only need it in specific cases.
Web servers and application servers are deployed in an AutoScaling group. Auto Scaling automatically adjusts your capacity up or down, according to conditions you define. You will need to set Min and Max values for your AutoScaling policies. This pattern just has desired value=1.
The RDS has been setup as multi-AZ deployment to provide high availability in database level. In this pattern we set DBA to have direct access to the DB server with its fake static IP. We assumed DBA IP as 1.2.3.4/32. You need to change it as per your requirements.
We have setup CNAMEs of CloudFront to two fake CNAMEs: dscf.com and wah.com. we have also added www.wah.com to this list. Please consider that AWS and so we do not check whether you own these doamins or no. If those domains are not owned by you, you may see error messages about existing CNAMEs or you will be asked later to remove those CNAMEs if the domain owner understands you are using CNAMEs for their domains. So please change them as per your real requirements.
Disclaimer: D.C. Solution Factory Inc has provided these domain CNAMEs just as examples and you do not have to use them as they are. You have to change them according to your domain ownership.
We also have added Route53 Alias to those CloudFront endpoints for those CNAMEs.
Know more about AWS Visual Design Tool
The post Web Application Hosting appeared first on DC Solution Factory.
