DevOps | AWS Loft Architecture Week | Wednesday, August 17

1. AWS OpsWorks
Amir Golan
Senior Product Manager

2. Operations using
AWS OpsWorks

3. Why do you need OpsWorks?
 Model and group your applications
 Manage the life-cycle of your instances
 Control Access Management
 Monitor the health of your resources
 Analyze logging information
 Mitigate operational problems

4. Configure your instances using AWS OpsWorks
 Uses Chef to configure the software on the instances
 Chef provides a DSL abstraction for common OS operations
 Associates pre-defined scripts (i.e. Chef cookbooks) with your instances
 Applies cookbooks configuration changes using life-cycle events

5. Model your applications using
AWS OpsWorks

9. Resource organization

10. Manage the life-cycle of your
instances

11. Lifecycle events
Setup Configure Deploy

12. Setup event
 Triggered every time an instance boots
 Used for initial installation of software packages

13. Configure event
 Triggered on all instances upon state changes
 Used to assure the configuration is up-to-date

14. Deploy event
 Triggered when deploying a new software version
 Allows for customizable software deployments

15. My new OpsWorks App!

20. Configure event triggered

23. Configure event triggered

26. Configure event triggered

27. Control Access Management

28. OpsWorks Access Management
 Provide IAM users full SSH / RDP and sudo / admin privileges
 Provided limited access on a group level (i.e. OpsWorks stack)

29. SSH / RDP session management
 AWS OpsWorks grants SSH / RDP access to IAM users

30. Temporary RDP session management
 AWS OpsWorks grants temporary RDP access to IAM users

31. Monitor the Health Your Resources

32. Configure your instances using AWS OpsWorks
 14 free one minute metrics (CPU, Memory, load, process count, etc.)
 Aggregation on the group level (OpsWorks stack, layer)
 CloudWatch optimized dashboards (contextual dashboards)

33. Analyze Logging Information

34. Configure your instances using AWS OpsWorks
 Troubleshoot Chef run results
 Track application logs using CloudWatch Logs

35. Create a CI/DE Pipeline with
AWS CodePipeline

36.  Continuous delivery service for fast and
reliable application updates
 Model and visualize your software release
process
 Builds, tests, and deploys your code every
time there is a code change
 Integrates with 3rd party tools and AWS
AWS CodePipeline

37. Source
Source
GitHub
Build
JenkinsOnEC2
Jenkins
Deploy
JavaApp
AWS OpsWorks
PipelineStage
Action
Transition
CodePipeline
MyApplication

38. Source
Source
GitHub
Build
JenkinsOnEC2
Jenkins
Deploy
JavaApp
AWS OpsWorks
NotifyDevelopers
Lambda
CodePipeline
MyApplication
Parallel actions

39. Source
Source
GitHub
Build
JenkinsOnEC2
Jenkins
Deploy
JavaApp
AWS OpsWorks
NotifyDevelopers
Lambda
TestAPI
Runscope
CodePipeline
MyApplication
Sequential actions

40. We have a strong partner list, and it’s growing
Source Build Test Deploy

41. AWS service integrations
Source Invoke Logic Deploy
AWS Elastic Beanstalk
Amazon S3
AWS CodeDeploy
AWS Lambda
AWS CodeCommit
AWS OpsWorks

42. AWS OpsWorks and
AWS CodePipeline

43. Configure your AWS Pipeline
 Update and apply AWS
OpsWorks cookbooks
 Deploy apps to AWS
OpsWorks stacks
Build
JenkinsOnEC2
Jenkins
NotifyDevelopers
Lambda
My AWS Application: App1
Source
App1
GitHub
Cookbooks
Amazon S3
Beta Stage
Deploy App1
AWS OpsWorks
Apply Cookbooks
AWS OpsWorks

44. Update your Chef cookbooks and deploy your applications
Streamline your CI/CD processes with
AWS OpsWorks & AWS CodePipeline

45. How do I Get Started with OpsWorks?
 Grab some community cookbooks
https://supermarket.chef.io/
 Learn more
https://aws.amazon.com/opsworks/
 Get started
https://aws.amazon.com/opsworks/
https://aws.amazon.com/codepipeline/

46. Questions?

47. Thank You!