overview-of-deployment-options-on-aws

More documents

Recommendations

Info

Amazon Web Services – Deployment Options on AWS March 2015more so that you can easily identify a resource. When you use tags during yourdeployment steps, the tools automatically propagate the tags to underlyingresources such as Amazon EC2 instances, Auto Scaling groups, or Amazon RDS.Appropriate use of tagging can provide a better way to manage your costs withcost allocation reports. 34 Cost allocation reports aggregate costs based on tags.This way, you can determine how much you are spending for each application ora particular project.Strategies for Updating Your StacksDepending on your choice of deployment service, the strategy for updating yourapplication code could vary a fair amount. AWS deployment services bring agilityand improve the speed of your application deployment cycle, but using a propertool and the right strategy is key for building a robust environment.The following section looks at how the deployment service can help whileperforming application updates. The approaches mentioned below will start withprebaking machine images and then move to performing in-place and disposableupgrades.Prebaking AMIsAn Amazon Machine Image (AMI) is an image consisting of a base operatingsystem or an application server in the cloud. 35 In order to launch an EC2instance, you need to choose which AMI you will use for installing yourapplication. A common practice to install an application is during instance boot.This process is called bootstrapping an instance. AWS CloudFormation providesmultiple options for bootstrapping an application. To review the options in detail,see Bootstrapping Applications via AWS CloudFormation . 36Note that the bootstrapping process can be slower if you have a complexapplication or multiple applications to install. Managing a fleet of applicationswith several build tools and dependencies can be a challenging task duringrollouts. Furthermore, your deployment service should be designed to do fasterrollouts to take advantage of Auto Scaling.Page 12 of 23
Amazon Web Services – Deployment Options on AWS March 2015Prebaking is a process of embedding a significant portion of your applicationartifacts within your base AMI. During the deployment process you cancustomize application installations by using EC2 instance artifacts such asinstance tags, instance metadata, and Auto Scaling groups.For example, let’s say you are managing a Ruby application that needs Nginx forthe front end; Elasticsearch, Logstash, and Kibana for log processing; andMongoDB for document management. You can have logical grouping of your baseAMIs that can take 80% of application binaries loaded on these AMI sets. Youcan choose to install most applications during the bootstrapping process andalter the installation based on configuration sets grouped by instance tags, AutoScaling groups, or other instance artifacts. You can set a tag on your Nginxinstances (such as Nginx-v-1.6.2). Your update process can query for the instancetag, validate whether it’s the most current version of Nginx, and then proceedwith the installation. When it’s time to update the prebaked AMI, you can simplyswap your existing AMI with the most recent version in the underlyingdeployment service and update the tag.Deployment services like AWS CloudFormation and AWS OpsWorks are bettersuited for the prebaked AMI approach. You can also find multiple third-partytools for prebaking AMIs. Some well-known ones are packer.io 37 and aminator(built by Netflix). 38 You can also choose third-party tools for your configurationmanagement such as Chef, Puppet, Salt, Ansible, and Capistrano.In-place vs Disposable MethodThe deployment services offer two methods to help you update your applicationstack, namely in-place and disposable. An in-place upgrade involves performingapplication updates on live Amazon EC2 instances. A disposable upgrade, on theother hand, involves rolling out a new set of EC2 instances by terminating olderinstances.An in-place upgrade is typically useful in a rapid deployment with a consistentrollout schedule. It is designed for sessionless applications. You can still use thein-place upgrade method for stateful applications by implementing a rollingdeployment schedule and by following the guidelines mentioned in the section onblue-green deployments.Page 13 of 23
Page 1 and 2: Overview of DeploymentOptions on AW
Page 3 and 4: Amazon Web Services - Deployment Op
Page 11: Amazon Web Services - Deployment Op
Page 23: Amazon Web Services - Deployment Op

overview-of-deployment-options-on-aws

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?