aws re:invent re:cap - 비용 최적화: 모범사례와 아키텍처 설계 기초편 - 이종남

December 8, 2014 | Seoul, Korea

AWS 비용최적화�� 아키텍처��

이종남, AWS�� 프로페셔널�� 서비스�� 컨설턴트��

re:Cap

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.

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.

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.

November 13, 2014 | Las Vegas, NV

Mimi Jiang, Adobe Constantin Gonzalez, AWS

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

에코시스템 글로벌 확산 신규 기능 신규 서비스

AWS 사용량 증가

인프라 추가증설

인프라 비용 절감

가격 인하

고객 증가 인프라 혁신

2006년 이후 47회 가격인하 규모의 경제

aws.amazon.com/premiumsupport/trustedadvisor/

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

Cloud Hosted

Cloud Optimized

Cloud Native

Cloud Enabled 1.0 • Lift and shift • 노력�� 소요도�� 하( )�� • 기술�� 난이도�� 하( )�� • 클라우드�� 이점은�� 아주�� 조금�� 획득��

• 자동화로�� 어느�� 정도까지는�� 효율화��

Cloud Enabled 2.0 • 애플리케이션�� 현대화�� • 노력�� 소요도�� 상( ��

• 기술�� 난이도�� 상(• 클라우드�� 이점은�� 상당량�� 획득��

Cloud Enabled 3.0 • 애플리케이션을�� 재개발�� 완료하기까지�� 힘�� 많이�� 듦��

• 노력�� 소요도�� 상( ��

• 기술�� 난이도�� 상(• 클라우드�� 이점�� 극대화��

•  Lift and shift •  노력�� 소요도�� 하�� •  기술�� 난이도�� 하�� •  클라우드�� 이점은�� 아주�� 조금�� 획득��

•  자동화로�� 어느�� 정도까지는�� 효율화��

Cloud Hosted

Cloud Optimized

Cloud Native

•  애플리케이션�� 현대화�� •  노력�� 소요도�� 상�� •  기술�� 난이도�� 상�� •  클라우드�� 이점은�� 상당량�� 획득��

•  애플리케이션�� 재개발�� 완료하기까지�� 힘�� 많이�� 듦��

•  노력�� 소요도�� 상�� •  기술�� 난이도�� 상�� •  클라우드�� 이점�� 극대화��

Cloud Enabled 1.0 Cloud Enabled 2.0 Cloud Enabled 3.0

Cloud scorecard As of m/d/y

Cloud enablement

Clo

ud 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

Clo

ud 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

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

"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 -v\n",

… your user data script …

]]}}

}

}

"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" } ]

}

}

© 2014 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.

API Gateway

API Management Services

API Console

{ adobe.io }: Adobe’s API platform

3rd party apps

Adobe apps

{adobe.io}

API services


{ adobe.io }: AWS deployment architecture API Consumers

Availability Zone 1

Private Subnet

Availability Zone 2

Public Subnet

Private Subnet

Auto Scaling Group

Auto Scaling Group

Region (US East, EU, AP, US West)

Amazon Route

53

Public Subnet


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

Architect

•  No Upfront

•  Partial Upfront

•  All Upfront

https://aws.amazon.com/blogs/aws/simplified-reserved-instances/

On-Demand: $0.24

$0.028 (11.7%) $0.026 (10,8%)

$3.28 (1367%)

"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 -v\n", … your user data script … ]]}} } }

20%

64%

ARC313: So You Think You Can Architect?

캐싱/최적화: 80%�� 절감

Cache flush

Dynamic DynamoDB:

20% 절감

사용량�� 증가�� + 신규�� 기능�� 도입

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

re:Cap

aws re:invent re:cap - 비용 최적화: 모범사례와 아키텍처 설계 기초편 - 이종남

Technology