A web-startup runs its very successful social news application on Amazon EC2 with an Elastic Load Balancer, an
Auto-Scaling group of Java/Tomcat application-servers, and DynamoDB as data store. The main webapplication best runs on m2 x large instances since it is highly memory- bound Each new deployment requires
semi-automated creation and testing of a new AMI for the application servers which takes quite a while ana is
therefore only done once per week.
Recently, a new chat feature has been implemented in nodejs and wails to be integrated in the architecture.
First tests show that the new component is CPU bound Because the company has some experience with using
Chef, they decided to streamline the deployment process and use AWS Ops Works as an application life cycle
tool to simplify management of the application and reduce the deployment cycles.
What configuration in AWS Ops Works is necessary to integrate the new chat module in the most cost-efficient
and flexible way?
Create one AWS Ops Works stack, create one AWS Ops Works layer, create one custom recipe
Create one AWS Ops Works stack create two AWS Ops Works layers create one custom recipe
Create two AWS Ops Works stacks create two AWS Ops Works layers create one custom recipe
Create two AWS Ops Works stacks create two AWS Ops Works layers create two custom recipe