Configure a Virtual Private Cloud (VPC)
Amazon Virtual Private Cloud (Amazon VPC) enables you to launch Amazon Web Services (AWS) resources into a virtual network that you’ve defined. This virtual network closely resembles a traditional network that you’d operate in your own data center, with the benefits of using the scalable infrastructure of AWS.
VPC with Public and Private Subnets (NAT)
Amazon VPC enables you to launch AWS resources into a virtual network that you’ve defined, called a virtual private cloud (VPC). The configuration for this scenario includes a virtual private cloud (VPC) with a public subnet and a private subnet.
Cloud computing is fast becoming the standard method of creating scalable, manageable web application services, and Amazon is leading the way. Master the complexities of AWS and understand all of your options with this comprehensive Learning Path. Learn to make your existence in the cloud trouble-free.
A web app is any software that users access through a web browser or specialized web client. Web apps are typically structured into logical tiers. For example, a common structure uses three tiers. The first tier is the web browser, which is responsible for presenting the user interface. The middle tier is an application server, which is responsible for the application’s functionality. The third tier is a database server or file system, which is responsible for data storage.
With Amazon Web Services (AWS), you can provision compute power, storage and other resources, gaining access to a suite of elastic IT infrastructure services as your business demands them. With minimal cost and effort, you can move your application to the AWS cloud and reduce capital expenses, minimize support and administrative costs, and retain the performance, security, and reliability requirements your business demands. This blog post discusses steps, techniques and methodologies for moving your existing enterprise applications to the AWS cloud
More and more enterprises are moving applications to the cloud to modernize their current IT asset base or to prepare for future needs. They are taking the plunge, picking up a few mission-critical applications to move to the cloud and quickly realizing that there are other applications that are also a good fit for the cloud. We discuss a phase-driven step-by-step strategy for migrating applications to the cloud.
Create a source bundle, which includes the deployment scripts, and upload it to AWS CodeCommit repository
Now you can download the following sample bundle to your local repository and push the change to the central repository along with your application code hosted on AWS CodeCommit. The sample bundle includes everything you need to work AWS CodeDeploy: the Application Specification (AppSpec) file and deployment scripts.
Use AWS CodeDeploy to Deploy Amazon EC2 Instances Behind an Elastic Load Balancer and Auto Scaling
Let’s assume you have an application architecture designed for high availability that includes an Elastic Load Balancer in front of multiple application servers belonging to an Auto Scaling Group. Elastic Load Balancing enables you to distribute incoming traffic over multiple servers and Auto Scaling allows you to scale your EC2 capacity up or down automatically according to your needs In this blog post, we will show how you can use CodeDeploy to avoid downtime when updating the code running on your application servers in such an environment. We will use the CodeDeploy rolling updates feature so that there is a minimum capacity always available to serve traffic and use a simple script to take EC2 instances out of the load balancer as and when we deploy new code on it.