1. AWS Cloud Computing
Masaki

2. EC2 S3
CloudWatch
ELB
Route 53
CloudFront
AWS Service

3. Elastic compute cloud – 彈性雲端

4. Quick and easy deployment No CapEx,No initial investment
Elastic Capacity
Quick and easy deployment
No CapEx,No initial investment
Pay as you go,for what you use
Automation and Reusable components

5. www.yourdomain.com media.yourApp.com
Example 1: Web Application Architecture
media.yourApp.com
(Static data)
Amazon CloudFront
Amazon Route 53
Hosted Zone
Elastic Load
Balancer
Amazon EC2
Instances
Amazon
CloudWatch
Alarms
Web
Server
Web
Server
Amazon S3
Bucket
Amazon SNS
Notifications
Auto Scaling Group
Web
Server
Web
Server
Web
Server
Web
Server
AZ-1
Region

8. Naklab intern

9.
測試不同地區AWS的latency

10. http://aws.amazon.com/ec2/ EC2收費方式
750 HOURS OF EC2 RUNNING MICRO INSTANCE USAGE
EC2收費方式

11. Simple storage service - 簡易儲存系統

12. S3有99.99%SLA(Service Level Agreement) 用多少付多少 一個object 大小可以到5GB
大約一年故障小於53分鐘
S3有99.99%SLA(Service Level Agreement)
用多少付多少
一個object 大小可以到5GB

13. 使用一年，我的圖片用了34GB

14. 我的空間有256T ，這是真的

15. Cloudwatch – 雲端資源監控管理

16. Cloud Watch是Amazon雲端提供給用戶拿來監測EC2效能的一種服務。
讓系統管理者容易掌握到EC2的運作效能，主要有五項(Memory需要另外安裝套件):
* CPU Utilization
* Disk Reads
* Disk Writes
* Network In
* Network Out

17. Elastic Load Balancing – 彈性負載平衡

18. 要有一台以上一模一樣的 EC2
依照伺服器的健康狀態，來幫你將流量轉向其他的 EC2 上面去。
ELB 可搭配 Cloud Watch 作自動擴展

19. Route 53 – Domain Name System (DNS)

20. Highly Available and Reliable Scalable Simple Fast Cost-Effective
DNS Hosting
Highly Available and Reliable 
Scalable
Simple
Fast
Cost-Effective
Secure
Flexible
Highly Available and Reliable – Route 53 is built using AWS’s highly available and reliable infrastructure. The distributed nature of our DNS servers helps ensure a consistent ability to route your end users to your application. Route 53 is designed to provide the level of dependability required by important applications. Amazon Route 53 is backed by the Amazon Route 53 Service Level Agreement.
Scalable – Route 53 is designed to automatically scale to handle very large query volumes without any intervention from you.
Designed for use with other Amazon Web Services – Route 53 is designed to work well with other AWS features and offerings. You can use Route 53 to map domain names to your Amazon EC2 instances, Amazon S3 buckets, Amazon CloudFront distributions, and other AWS resources. By using the AWS Identity and Access Management (IAM) service with Route 53, you get fine grained control over who can update your DNS data. You can use Route 53 to map your zone apex (mydomain.com versus your Elastic Load Balancing instance using a feature called Alias record.
Simple – With self-service sign-up, Route 53 can start to answer your DNS queries within minutes. You can configure your DNS settings with the AWS Management Console or our easy-to-use API. You can also programmatically integrate the Route 53 API into your overall web application. For instance, you can use Route 53’s API to create a new DNS record whenever you create a new EC2 instance.
Fast – Using a global anycast network of DNS servers around the world, Route 53 is designed to automatically route your users to the optimal location depending on network conditions. As a result, the service offers low query latency for your end users, as well as low update latency for your DNS record management needs.
Cost-Effective – Route 53 passes on the benefits of AWS’s scale to you. You pay only for managing domains through the service and the number of queries that the service answers for each of your domains, at a low cost and without minimum usage commitments or any up-front fees.
Secure – By integrating Route 53 with AWS Identity and Access Management (IAM), you can grant unique credentials and manage permissions for every user within your AWS account and specify who has access to which parts of the Route 53 service.
Flexible – Route 53 offers Weighted Round-Robin (WRR), also known as DNS load balancing. This lets you assign weights to your DNS records that specify what portion of your traffic is routed to various endpoints.

21. Route 53收費方式 Hosted Zones Standard Queries 不用怕像菲律賓DNS被攻擊
$0.50 per hosted zone / month for the first 25 hosted zones
$0.10 per hosted zone / month for additional hosted zones
Standard Queries
$0.500 per million queries – first 1 Billion queries / month
$0.250 per million queries – over 1 Billion queries / month
管理一個網域一年只要$6.12美金
不用怕像菲律賓DNS被攻擊
Route 53收費方式

22. CloudFront – 內容傳遞網路(CDN)

23. 以前要將伺服器放到不同地點，可以減少互連的流量，進而降低頻寬成本。 現在CloudFront會找到離使用者最近的機房，並從那邊丟檔案出來。
另外一個好處在於有異地備援。當某個伺服器故障時，系統將會調用其他鄰近地區的伺服器服務，進而提供接近100%的可靠度。
加速瀏覽速度、降低傳輸費用。
Fast Using a network of edge locations around the world, Amazon CloudFront caches copies of your static content close to viewers, lowering latency when they download your objects and giving you the high, sustained data transfer rates needed to deliver large popular objects to end users at scale. Requests for your dynamic content are carried back to your origin servers running in Amazon Web Services (e.g., Amazon EC2, Elastic Load Balancing) over optimized network paths for a more reliable and consistent experience. These network paths are constantly monitored by Amazon and connections from CloudFront edge locations to the origin are reused to serve your dynamic content with the best possible performance.
Simple A single API call lets you get started distributing content from your Amazon S3 bucket or Amazon EC2 instance or other origin server through the Amazon CloudFront network. Or, interact with Amazon CloudFront through the AWS Management Console’s simple graphical user interface. There is no need to create separate domains for your static and dynamic content. With CloudFront, you can just use the same domain name to point to all of your website content. Any changes you make to your existing configuration take effect across the entire global network within minutes. Plus, since there’s no need to negotiate with a sales person, you can get started quickly and begin delivering your entire website using Amazon CloudFront.
Designed for use with other Amazon Web Services Amazon CloudFront is designed for use with other Amazon Web Services, including Amazon S3, where you can durably store the definitive versions of your static files, and Amazon EC2, where you can run your application server for dynamically generated content. Amazon CloudFront also integrates with Elastic Load Balancing. For instance, you can deploy your web application on Amazon EC2 servers behind Elastic Load Balancing and use Amazon CloudFront to deliver your entire website.
Cost-Effective Amazon CloudFront passes on the benefits of Amazon’s scale to you. You pay only for the content that you deliver through the network, without minimum commitments or up-front fees. This applies for any type of content that you deliver – static, dynamic, streaming media, or a web application with any combination of these.
Elastic With Amazon CloudFront, you don’t need to worry about maintaining expensive web-server capacity to meet the demand from potential traffic spikes for your content. The service automatically responds as demand increases or decreases without any intervention from you. Amazon CloudFront also uses multiple layers of caching at each edge location and collapses simultaneous requests for the same object before contacting your origin server. These optimizations further help reduce the need to scale your origin infrastructure as your website becomes more popular.
Reliable Amazon CloudFront is built using Amazon’s highly reliable infrastructure. The distributed nature of edge locations used by Amazon CloudFront automatically routes end users to the closest available location as required by network conditions. Origin requests from the edge locations to AWS origin servers (e.g., Amazon EC2, Amazon S3, etc.) are carried over network paths that Amazon constantly monitors and optimizes for both availability and performance.
Global Amazon CloudFront uses a global network of edge locations, located near your end users in the United States, Europe, Asia, and South America.