AWS OpsWorks is an application management service that makes it easy for DevOps users to model and manage the entire application from load balancers to databases. Start from templates for common technologies like Ruby, Node.JS, PHP, and Java, or build your own using Chef recipes to install software packages and perform any task that you can script. AWS OpsWorks can scale your application using automatic load-based or time-based scaling and maintain the health of your application by detecting failed instances and replacing them. You have full control of deployments and automation of each component.
The tutorial includes topics like success stories of OpsWork, application challenges faced by OpsWork, details about OpsWork, why use OpsWork, competitors (beanstalk vs opswork vs CF vs DIY), types of layers, static application, adding a data store, auto-scaling, monitoring. The tutorial begins with a section about the success stories which took place using opswork like wooga, artsy and also the challenges faced by it. It is followed by a brief introduction to opswork and how a user can manage applications using opswork. Next comes a section about the benefits of using opswork. It gives pointers on why a user should use opswork and also about the many benefits of using opswork.
The subsequent section covers the competitors in the market like beanstalk, CF, DIY and gives details about the features of opswork which are lacking in the other competitors. Then comes the types of layers opswork uses. It includes the types of layers like app servers, My SQLDB, others and also shows opswork in action. It is further followed by a section about static applications like the architecture, the setup, creating a stack, adding a server layer, adding instances to the server layer, the states of instances, creating an application, deploying an application which are present in opswork.
Another section similar to this section is about adding a data store. It consists of the architecture, adding a layer and instance, application/DB configuration, deploying and running an application using opswork. Directly after this comes a section about auto scaling. It involves auto scaling and updating architecture, adding a LB layer, enabling load based auto scaling, adding load based instances, take action like start firing on servers. The last section of this tutorial is about monitoring. It includes monitoring like default monitoring, monitoring layer, individual default monitoring and also consists of the summary of the whole tutorial.
3. Agenda
1. Success Stories
2. Application Challenges
3. What isOpsWorks
4. Why OpsWorks
5. BeanStalk vs OpsWorks vs CF vsDIY
6. OpsWorks
7. OpsWorks in Action
8. Monitoring
9. Summary
4. Success Stories
Wooga
• Monster World runs entirely on the AWS Cloud.
• Wooga’s Monster World has approximately two million players per day.
• 15,000 requests per second at its peak.
"AWS OpsWorks gives us the tools we need to automate operations, We can scale
Monster World to millions of users without ever needing more than two back-end
developers.”
5. Success Stories
Artsy
• Marketplace and database for fine arts.
• Application based on Rails and backed by a MongoDB, Memcached,CloudFront and S3.
• Takes advantage of load-based and time-based scaling built into OpsWorks.
“OpsWorks gives us a lot more control. We have to be aware of the infrastructure and make
decisions accordingly, but the gains have been well worth it.”
Application Challenges
• Reliability
• Scalability
• Operational
Tasks o
Deployment o
Configuration o
Monitoring
o Security
6. What is OpsWorks
• AWS OpsWorks isan application management service that makes it easy for DevOps users to
model and manage the entire application from load balancers to databases.
Easy to use
Quickly get
Started and
productive
Reduces
Errorswith
Conventions
and scripted
configuration
Simplifies
Deployment
of any
Scale and
complexity
Reduce cost
And time with
automation
Enables
control
With finegrained
permissions
SIMPLE PRODUCTIVE FLEXIBLE POWERFUL SECURE
7. Why OpsWorks
• Full control of components
• Automation
• Inbuiltscalability
• Auto Healing
• Repeatable Architecture
• Fully customizable
• Permissions
• Detailed Monitoring
• Version control integration (Git/SVN)
• Resource Management
• Free, pay only for the resources that you use
8. BeanStalk vs OpsWorks vs CF vs DIY
AWSElastic
Beanstalk
“Web Apps
Made Easy”
AWS
OpsWorks
“DevOps
Automation”
AWS
CloudFormation
“Template-Driven
Provisioning”
Amazon EC2 +
Cloud Watch +
Auto Scaling +
CustomAMIs
Do ityourselfHigher-LevelServices
Convenience Control
19. Instance States
create theEC2 Requested -OpsWorks has calledthe Amazon EC2 service to
instance.
Pending -AWS OpsWorks iswaiting for the EC2 instance to start.
Booting -The EC2 instance isbooting.
Runningsetup-The AWS OpsWorks agent isrunning the layer's Setup recipes,
which handle tasks such as configuring and installing packages, and the Deploy
recipes, which deploy any apps to the instance.
Online -The instance isready for use.
21. Static Application Setup: Deploy App
lDeploy multiple apps
lA new server in same layer would have all existing appsdeployed
lA new app needs to be deployed on all servers.
39. Contact us
Here’s how TOTHENEW
uses AWS for better
infrastructure management
for your customers.
Click Here To Know More!
Have more queries on
AWS?
Talk to our AWS
experts Now!
Talk To Our Experts!
Our Offices
Client Location