Patterns Factory

Web Application Hosting

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”.

WAH

Try AWS Visual Design Tool

Read more

VPC With Private Subnet

Description: This pattern depicts a scenario that customer does not want to migrate DB workload to the Public Cloud but Web and Application servers have been migrated to AWS. In this scenario Web and Application servers in AWS have private IPs. Web servers are behind ELB and they are managed by a server that we called it here Management Server . The management server will play like a jumping server to login to the Web server from Internet (By Web Admins). We assumed your Web admin have static IP address ( we set that as 100.101.102.103/32. You should change that based on your Admin IP address). On the other hand, application server’s admin will not use Jumping server/management server to administer the application server. In return, they connect to application servers from Enterprise network. We assumed that network is 10.1.0.0/16 . You should change that IP according to your requirement. In this pattern, the Logic Tier has a route to VPG and it will be connecting to a fake DB server in the enterprise premises with the IP address of 10.1.0.2/32 . Again you should change it based on your DB server IP address. You have to change the CGW IP address to your public IP address (i.e. replacing1.2.3.4 )

VPC With Private Subnet

Try AWS Visual Design Tool

NAT Pattern

Description: Instances that you launch into a private subnet in a virtual private cloud (VPC) can’t communicate with the Internet. You can optionally use a network address translation (NAT) instance in a public subnet in your VPC to enable instances in the private subnet to initiate outbound traffic to the Internet, but prevent the instances from receiving inbound traffic initiated by someone on the Internet.

NAT

Try AWS Visual Design Tool

© 2015 - DC Solution Factory Inc.