AWS Tech Summit, London 9th November An introduction to how the Cloud can help with the development lifecycle, from dev to test to production.

1. Architecting
Applications
Matt Wood
Technology Evangelist

2. Hello.

3. Thank you.

4. AGENDA
9th November, 2010
Application lifecycle
Environments
Testing
Mo ving to Production
Summar y

5. There Will Be Code

6. 1
Application
lifecycle

7. Developing
Applications

8. Development Test Staging Production

9. Development Test Staging Production

10. Flexibility

11. Quality

12. Ship it!

13. Unpredictable
Time consuming
Bursty
Development Test Staging Production
Resource
Collaborative
intensive
Costly

14. Focus on
productivity

15. Toolkit for
productivity

16. EC2
Elastic Compute Cloud

17. Virtual servers

18. Launch
On demand

19. $
Pay as you go

20. Pay for
what you use

21. Rapid
provisioning

22. Elastic capacity

23. Administrator
access

24. Global

25. aws.amazon.com/security

26. Network security
Metrics
Hadoop
Tagging
Placement
EC2 HPC
Auto-scaling
MySQL
Idempotency

27. HOWTO:
Development in
the Cloud

28. 2
Environments

29. Dev
Test / QA
Staging
Production

30. Dev
Test / QA
Staging
Production

31. Environmental
separation

32. ges m ade Dev
C han
here
Test / QA
Staging
Shouldn’t
Production affect
this!

33. Environmental
consistency

34. Dev
Test / QA
Same s ervices,
versio ns, OS,
configs Staging
Production

35. Separation
+
Consistency

36. Variable
resources

37. Dev
l-in- one
Al
Test / QA
Staging Multi-tier,
high availa
bility,
managed
Production

38. Dev
l-in- one
Al
Test / QA
ulti- tier
M
tier, Multi-tier,
M ulti- Staging
aila bility high availa
bility,
hig h av managed
Production

39. Dev

40. ➊ Spin up new instance
> ec2-run-instances ami-2938699
$
<credentials>
➋ Log in to instance
> ssh <credentials>
root@ec2-174-129-123-206.compute-1.amazonaws.com
➌ Install and launch services
> yum install apache, apache-devel, ruby, rails

41. console.aws.amazon.com

52. ploy, go!
Inst all, de

53. Aq uick
not e ab out
stor age

54. Storage options

55. Instance storage

56. Elastic Block Store

57. Simple Storage Service

58. Data, config,
code...

59. EC2
EBS

60. ➊ Create new volume
> ec2-create-vol -s 10G
<credentials>
➋ Attach to instance
> ec2-attach-volume vol-1238797ah -i <instance>
-d <device> <credentials>
$
➌ Format and mount
$ mkfs.xfs /dev/sdh;
$ <add mount point>
$ mkdir /vol; mount /vol

61. Encapsulate
environments

62. Code
Data Configuration
OS State
ami-12398712
+
snap-986854a

63. ➊ Bundle instance
> ec2-bundle-vol -d /mnt
<credentials>
➋ Upload bundle
> ec2-upload-bundle -b <bucket> -m /mnt/manifest.xml
<credentials>
$
➌ Register bundle
> ec2-register <bucket>/manifest.xml

64. ➊ Snapshot volume
> ec2-create-snapshot vol-123981a
$
<credentials>

65. Sandboxing

66. Dev #1 Dev #2 Dev #2
AMI and
snapshot:
same base
versions,

67. Environmental
rollback

68. Only pay for
what you use

69. Pause &
terminate

71. Toolbox for
development

72. Freedom to
innovate

73. Freedom to
innovate
ew services New
architectures
New tools
New models

74. 3
Testing

75. Test on
production
architecture

76. Change
management

77. AMI + Volumes

78. ami-ha9034a
Web frontend
snap-er37a9x
ami-ha9034a
App server
snap-er37a9x
ami-ha9034a
Database
snap-er37a9x

79. Environmental
description

80. include_recipe "apache2"
include_recipe "php::php5"
apache_site "php_server.conf" do
enable :true
end

81. Puppet, Chef

82. Version control

83. Load testing
Continuous integration
Cost reduction
Webinar
aws.amazon.com
Automation
Multi-layer
System Integration

84. 4
Moving to
Production

85. Production

86. ai lab ilit Fail o
ver
Av
y
Production
Monitorin
g Scale

87. “”
Everything fails,
all the time
Werner Vogels, CTO

88. Architect for
failure

89. Address with
Elastic IPs

90. ec2-174-129-123-206.compute-1.amazonaws.com

91. ec2-174-129-123-206.compute-1.amazonaws.com
:-(

92. Elastic IP

93. Elastic IP
:-(

94. Elastic IP
:-(

95. ➊ Allocate Elastic IP Free
when
alloc
> ec2-allocate-address ated!
ADDRESS
174.129.200.110
➋ Associate Elastic IP to instance
> ec2-associate-address 174.129.200.110
-i i-7044821d
➌ Address service via Elastic IP

96. ➊ Spin up new instance
> ec2-run-instances -t m1.small
$
ami-192871
➋ Dis-associate Elastic IP
> ec2-disassociate-address
174.129.200.110
➌ Re-associate to new instance
> ec2-associate-address 174.129.200.110
-i i-23987423

97. Provide
redundancy

98. Web tier
Application tier
Database tier

99. Web tier
Application tier :-(
Database tier

100. Web tier
Application tier
Database tier

101. Web tier
Application tier :-(
Database tier

102. Remove state

103. Horizontal
layers

106. :-(

108. ➊ Allocate Elastic Load Balancer (ELB)
> ec2-allocate-address
ADDRESS
174.129.200.110
➋ Assign instances to ELB
> ec2-associate-address 174.129.200.110
-i i-7044821d
➌ Address service via ELB CNAME

109. Toolkit for
availability

110. Toolkit for
scale

111. AGENDA
9th November, 2010
Application lifecycle
Environments
Testing
Mo ving to Production
Summar y

112. On demand Development
PAYG Testing
Security Production
Architecture Easy to use

113. Questions, comments:
mawood@amazon.com
@mza
on Twitter

114. Thank you!