AWS re:Invent re:Cap 행사에서 발표된 강연 자료입니다. 아마존 웹서비스의 이종남 프로페셔널 컨설턴트가 발표한 내용입니다. 내용 요약: AWS 클라우드 인프라 활용의 이점을 극대화하기 위해 취해야 할 최적화 방안과 아키텍처 설계 방법에 대해 알아보겠습니다. AWS의 성능 최적화 전문가에게서 모범 사례를 습득하고 인프라 확장 과정에서 최적의 성능을 확보하려면 어떤 서비스를 어떻게 활용해야 하는지 알아보시기 바랍니다.

1. AWS 비용최적화

2. 아키텍처

3.
이종남, AWS

4. 프로페셔널

5. 서비스

6. 컨설턴트

7.
December 8, 2014 | Seoul, Korea
re:Cap

9. Whether you're a startup getting to profitability or an enterprise
optimizing spend, it pays to run cost-efficient architectures on AWS.
Building on last year's popular foundation of how to reduce waste
and fine-tune your AWS spending, this session reviews a wide range
of cost planning, monitoring, and optimization strategies, featuring
real-world experience from AWS customer Adobe Systems. With the
massive growth of subscribers to Adobe's Creative Cloud, Adobe's
footprint in AWS continues to expand. We will discuss the techniques
used to optimize and manage costs, while maximizing performance
and improving resiliency.
When traditional application and operating practices are used in
cloud deployments, immediate benefits occur in speed of
deployment, automation, and transparency of costs. The next step is
a re-architecture of the application to be cloud-native, and significant
operating cost reductions can help justify this development work.
Cloud-native applications are dynamic and use ephemeral resources
that customers are only charged for when the resources are in use.

10. With AWS, you can reduce capital costs, lower your overall bill, and
match your expense to your usage. This session describes how to
calculate the total cost of ownership (TCO) for deploying solutions on
AWS vs. on-premises or at a colocation facility, as well as how to
address common pitfalls in building a TCO analysis. The session
presents and models customer examples.
This session is a deep dive into techniques used by successful
customers who optimized their use of AWS. Learn tricks and hear
tips you can implement right away to reduce waste, choose the most
efficient instance, and fine-tune your spending; often with improved
performance and a better end-customer experience. We showcase
innovative approaches and demonstrate easily applicable methods
to save you time and money with Amazon EC2, Amazon S3, and a
host of other services.

11. In this session, you learn how you can leverage AWS services
together with third-party storage appliances and gateways to
automate your backup and recovery processes so that they are not
only less complex and lightweight, but also easy to manage and
maintain. We demonstrate how to manage data flow from on-premises
systems to the cloud and how to leverage storage
gateways. You also learn best practices for quick implementation,
reducing TCO, and automating lifecycle management.
In the event of a disaster, you need to be able to recover lost data
quickly to ensure business continuity. For critical applications,
keeping your time to recover and data loss to a minimum as well as
optimizing your overall capital expense can be challenging. This
session presents AWS features and services along with Disaster
Recovery architectures that you can leverage when building highly
available and disaster resilient applications. We will provide
recommendations on how to improve your Disaster Recovery plan
and discuss example scenarios showing how to recover from a
disaster.

13. Mimi Jiang, Adobe
Constantin Gonzalez, AWS
November 13, 2014 | Las Vegas, NV

15. • Speed, agility, and innovation
• Focus on your business
• Go global in minutes

18. 에코시스템
글로벌 확산
신규 기능
신규 서비스
AWS 사용량
증가
인프라
추가증설
인프라 비용
절감
가격
인하
고객
인프라 혁신증가
2006년 이후
47회 가격인하 규모의 경제

20. aws.amazon.com/premiumsupport/trustedadvisor/
비즈니스, 엔터프라이즈 서포트 고객에게 33 가지 이상 체크리스트 제공
(네 가지 체크리스트는 모든 고객이 이용가능)
http://aws.amazon.com/blogs/aws/trusted-advisor-console-basic/

23. Cloud
Hosted
Cloud
Optimized
Cloud
Native

24. Cloud Enabled 1.0
• Lift and shift
• 노력

25. 소요도

26. 하( )

27.
• 기술

28. 난이도

29. 하( )

30.
• 클라우드

31. 이점은

32.
아주

33. 조금

34. 획득

35.
• 자동화로

36. 어느

37. 정도까지
는

38. 효율화

40. Cloud Enabled 2.0
• 애플리케이션

41. 현대화

42.
• 노력

43. 소요도

44. 상(

45.
• 기술

46. 난이도

47. 상(
• 클라우드

48. 이점은

49.
상당량

50. 획득

52. Cloud Enabled 3.0
• 애플리케이션을

53. 재개발

54.
완료하기까지

55. 힘

56. 많이

57. 듦

58.
• 노력

59. 소요도

60. 상(

61.
• 기술

62. 난이도

63. 상(
• 클라우드

64. 이점

65. 극대화

67. Cloud
Hosted
• Lift and shift
• 노력

68. 소요도

69. 하

70.
• 기술

71. 난이도

72. 하

73.
• 클라우드

74. 이점은

75.
아주

76. 조금

77. 획득

78.
• 자동화로

79. 어느

80. 정도까
지는

81. 효율화

82.
Cloud
Optimized
Cloud
Native
• 애플리케이션

83. 현대화

84.
• 노력

85. 소요도

86. 상

87.
• 기술

88. 난이도

89. 상

90.
• 클라우드

91. 이점은

92. 상당
량

93. 획득

94.
• 애플리케이션

95. 재개발

96. 완
료하기까지

97. 힘

98. 많이

99. 듦

100.
• 노력

101. 소요도

102. 상

103.
• 기술

104. 난이도

105. 상

106.
• 클라우드

107. 이점

108. 극대화

109.
Cloud Enabled 1.0 Cloud Enabled 2.0 Cloud Enabled 3.0

110. Cloud
scorecard As of m/d/y
Cloud
enablement
Cloud 2.0
Architecture reviewed and approved
Multitenant (common apps server, separate or single DB)
Scalability (will scale wide for all capabilities with no practical limitations)
High availability (no single point of failure)
Zero footprint client (HTML interface for all functionality and customer-facing utilities)
Supports automation of tenant lifecycle and other processes
Meets Infor cloud deployment, patching, and upgrade requirements
Supports health check monitors
No critical security code scanner findings and penetration test performed successfully
Supports customization through UI-driven configuration (no source code changes)
Required integration are using HTTPS/SFTP
No dependency on server access to local devices (example: printers)
Product support organization ready to provide cloud support
Supports Auto Scaling
Cloud 3.0
Minimized/no third-party royalty costs
Supports scalable open-source database technologies
Application is stateless (session information stored externally)
Supports a single-version deployment (upgrades are incremental, rapid, scalable)
Cloud 2.0 score / 14
Cloud 3.0 score 0 / 4

114. 월요일 금요일 휴가시즌 종료 35% 절감

118. LaunchConfig: {
Type : AWS::AutoScaling::LaunchConfiguration,
Metadata : {
AWS::CloudFormation::Init : {
config : {
… packages, sources, files, services …
}
}
},
Properties: {
ImageId : ami-149f7863,
InstanceType : m1.small,
SecurityGroups : [ {Ref : WebServerSecurityGroup} ],
KeyName : MySSHKey,
UserData : { Fn::Base64 : { Fn::Join : [, [
#!/bin/bash -vn,
… your user data script …
]]}}
}
}

119. WebServerGroup : {
Type : AWS::AutoScaling::AutoScalingGroup,
Properties : {
AvailabilityZones : [
us-east-1a,
us-east-1b,
us-east-1c,
],
LaunchConfigurationName : { Ref : LaunchConfig },
MinSize : “3,
MaxSize : “6,
DesiredCapacity : “3,
LoadBalancerNames : [ { Ref : ElasticLoadBalancer } ]
}
}

121. { adobe.io }: Adobe’s API platform
Adobe apps
© 2014 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
API Gateway
API Console
API Management
Services
3rd party apps
{adobe.io}
API services

122. { adobe.io }: AWS deployment architecture
Public Subnet
Private Subnet
© 2014 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
API Consumers
Availability Zone 1
Amazon
Route
53
Public Subnet
Private Subnet
Availability Zone 2
Auto Scaling Group
Auto Scaling Group
Region (US East, EU, AP, US West)

123. Scaling mechanisms
Event-based scaling
• Overprovision for sharp traffic increase
** Prewarm your load balancer
• Observe traffic pattern scale down
Schedule-based scaling
• Match scaling with workload at different times
• Scale down dev test environments
© 2014 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
Architect

126. • No Upfront
• Partial Upfront
• All Upfront
https://aws.amazon.com/blogs/aws/simplified-reserved-instances/

130. On-Demand:
$0.24
$0.028 (11.7%) $0.026 (10,8%)
$3.28
(1367%)

133. LaunchConfig: {
Type : AWS::AutoScaling::LaunchConfiguration,
Metadata : {
AWS::CloudFormation::Init : {
config : {
… packages, sources, files, services …
}
}
},
SpotPrice: 0.59,
Properties: {
ImageId : ami-149f7863,
InstanceType : m1.small,
SecurityGroups : [ {Ref : WebServerSecurityGroup} ],
KeyName : MySSHKey,
UserData : { Fn::Base64 : { Fn::Join : [, [
#!/bin/bash -vn,
… your user data script …
]]}}
}
}

135. 20%
64%

139. ARC313: So You Think You Can Architect?

141. DynamoDB:
20% 절감
캐싱/최적화:
80%

142. 절감
Dynamic
Cache
flush
사용량

143. 증가

144. +
신규

145. 기능

146. 도입

152. 간단하고, 더 안정적이고, 비용 낮추고

161. re:Cap