When managing your Windows infrastructure on AWS, you can automate operational tasks, like service discovery, software installation and configuration management. Using AWS OpsWorks, you can deploy, manage, and scale your applications running on Windows Server. This webinar will show you how to use Chef recipes with OpsWorks to install or update software packages and security updates. You will also learn how to use OpsWorks to react to lifecycle events, such as running launch and shutdown scripts, or adapting your application's configurations. Learning Objectives: Understand the benefits of using OpsWorks on Windows Server applications

1. AWS OpsWorks
Introducing AWS OpsWorks
for Windows Server

2. AWS OpsWorks
 Model, control and automate infrastructure of
any scale or complexity
 Application Management Service
 No additional cost running on AWS

3. Infrastructure as code
 Reusable
 Documented
 Versioned
 Tested

4. Mark Rambow
Software Development Manager
for AWS OpsWorks

5. Deployment & Management
Services

6. Deployment & Management Services
AWS Elastic Beanstalk AWS OpsWorks AWS CloudFormation
AWS CodeDeploy AWS CodePipeline AWS CodeCommit

7. Deployment & Management Services
Convenience Control
AWS Elastic Beanstalk AWS OpsWorks AWS CloudFormation

8. AWS Elastic Beanstalk and
AWS OpsWorks can be
controlled via
AWS CloudFormation.
AWS CloudFormation integration
OpsWorks Elastic Beanstalk
CloudFormation

9. AWS CloudFormation integration
OpsWorks SQS VPC S3
CloudFormation

10. OpsWorks
Core Concepts

11. Stack

14. Demo 1
Organizing your infrastructure

15. Deep service integration with
 Elastic Load Balancing
 Amazon RDS
 AWS CloudFormation
 AWS IAM (users and profiles)

16. OpsWorks apps and deployments
 You define the source of your application
 Apps can be deployed manually
 Apps are deployed automatically on instance boot
 Set environment variables

17. Operational tooling
 Streamlined provisioning
 Continuous configuration
 Manage users and permissions
 Manage remote desktop access (RDP)
 Time-based instances to manage load
 OpsWorks auto heals unhealthy instances

18. Demo II
User management and remote desktop access

19. Technical Deep Dive

20. OpsWorks architecture
OpsWorks
Backend
OpsWorks
Agent
EC2, EBS, EIP, VPC, ELB,
Auto-Scaling, Auto-Healing On-instance execution via
Command
JSON
Command
Log+Status

21. Lifecycle Events
setup configure deploy undeploy shutdown

22. Setup event
• Sent when instance boots
• Includes the deploy event
• Use for initial installation of
software & services

23. Configure event
• Sent to all instances when
any instance enters or
leaves online state
• Used for making sure the
configuration is up-to-date

24. Deploy event
• Sent when you deploy via
UI/API; part of each setup.
• Used for custom
deployment

25. Undeploy event
• Sent via UI/API when apps
are deleted
• Used to remove apps from
running instances

26. Shutdown event
• Sent when an instance
is shut down
• Specify shutdown timeout
• Used for clean shutdown

27. Example event on a Stack
Setup Configure Deploy Undeploy Shutdown
Reverse
Proxy
(cache)
Install and
configure
IIS
Sync app
server IPs
- -
Drain
connections
.Net App
Server
Install app
server
Updates DB
IP
& restart
Updates
app
Removes
app
Ship logs
Database
Install
database
Sync DB
ACLs
- - Make backup

28. Demo 3
Configure Lifecycle Events

29. Configuration Management

30. Chef
 Open Source
 Cookbooks & recipes
 Ruby DSL
 Many tutorials and
resources on the web

31. Recipe setup.rb
windows_feature 'Web-FTP-Server'
windows_package '7zip' do
source 'http://www.7-zip.org/a/7z938-x64.msi'
checksum '7c8e873991c82ad9cfc123415254ea6101e9a645e12977dcd518979e50fdedf3'
action :install
end

32. Chef resources
 Resources describe the desired state
 Resources have attributes and actions
registry_key "set background color" do
key "HKCUControl PanelColors”
values [{ name: "Background",
type: :string,
data: "86 63 127" }]
action :create
end

33. Chef resources
#apt_package, #bash, #batch, #chef_gem, #chef_handler,
#cookbook_file, #cron, #csh, #deploy, #directory, #dpkg_package,
#dsc_resource, #dsc_script, #env, #erl_call, #execute, #file,
#gem_package, #git, #group, #http_request, #ifconfig,
#ips_package, #link, #log, #mount, #ohai, #perl, #portage_package,
#powershell_script, #python, #reboot, #registry_key,
#remote_directory, #remote_file, #route, #ruby, #ruby_block, #script,
#subversion, #template, #user, #windows_package,
#windows_service

34. OpsWorks Chef integration

35. Lifecycle Events trigger Chef runs
 The OpsWorks agents controls the Chef client on
the instance
 The agent keeps your Cookbooks on the instance
up to date
 Each Lifecycle event contains list of recipes to run
 All Lifecycle Events can be triggered manually
 You can also run single recipes

36. Stack information
 OpsWorks tracks the Stack state
 This information is accessible in your recipes
 Use Chef search to access information like the list
of all nodes (instances) in your Stack or Layer
nodes = search(:aws_opsworks_instance, "hostname:db-slave*")
nodes.each do |node|
... node[:private_dns]
end

37. Demo 4
IIS + Node.JS Application Example

38. Conclusion
 OpsWorks let you group your projects in logical
units (Stacks and Layers)
 It automates setup of instances through Chef and
Lifecycle Events
 It gives you operational tooling like user
management

39. Keep in touch
@AWSOpsWorks on twitter
blogs.aws.amazon.com/application-management

40. Send us feedback

41. Send us feedback

42. Thank you very much for joining
the webinar today
Please give us feedback
@AWSOpsWorks