Presentation describes usage of Amazon Web Services to build a complex modern project. Also covers differences between AWS and Microsoft Azure.

1. Amazon Clouds in Action by Zenyk Matchyshyn

2. Agenda Amazon Web Services introduction. Amazon Elastic Computing Cloud (EC2). Usage of AWS on real project. AWS as a platform. Amazon vs Azure 2

3. Amazon Web Services introduction 3

4. Common AWS aspects Pay only for what you’ve used. Everything has an API. API is simple, available for most modern languages. Easy to get started – only credit card needed. Infrastructure-as-a-Service – no local deployments. Closed source implementation – open source ideas. Tight integration between the services. 4

5. Amazon EC2 Provides resizable compute capacity. In most simple case – dedicated hosting, in most complex case – scalable cloud. Available Linux and Windows instances (AMIs). Multiple locations available. Scalability build-in (Auto Scaling, Load Balancing, Monitoring). 5

6. Amazon S3 Provides storage interface to data. Used to serve static traffic, when serving from server is not enough but CDN is too much. From 1 byte to 5 TB. Simple API with lots of clients. Both public and private. Encrypted and not. Somewhat reliable  6

7. Amazon SQS Scalable messaging. Durable, queue based. Message up to 64k. Secure, if needed. Simple locking and expiration. Pull based. 7

8. Amazon SNS For notifications “from the cloud”. Has different options than Amazon SQS. More topic than queue oriented. Publisher/subscriber model. Push based. Lots of notification options. 8

9. Amazon Elastic MapReduce Hadoop in the cloud. Very easy to use. Hadoop it tough to setup. Based on EC2 and S3. Possible to tune. Possible to monitor. 9

10. Amazon EC2 10

11. Main terms AMI – Amazon Machine Image – image of OS. Instance – Running AMI. Instance Type – hardware configuration for instance. EBS - Elastic Block Store – persistent store. Location – physical location, not possible to change. Elastic IP – IP assigned to any Instance. Elastic Load Balancing – Load balancing on top of instances. 11

12. Typical flow Select instance type (e.g. hardware configuration) Select or upload AMI (e.g. operation system) Decide whether to use EBS (e.g. with hard-drive or not) Run! (e.g. power on) Stop/Terminate (e.g. reset or erase) 12

13. Available AMIs, Instance Types AMIs: Linux based Windows based With special software (e.g. Flash Media Server) Instances: From small to big From High-CPU to High-Memory Clusters, CPU and GPU 13

14. Usage of AWS on Real project 14

15. AWS Services Used Not for public audience... 15

16. Architecture Not for public audience... 16

17. AWS as a platform 17

18. Services and sites using AWS Heroku – scalable Ruby on Rails PAAS hosting. U.S. Department of State. Alexa – search and information services. Yelp – local reviews. PlayFish – social games. 18

19. Practical usage Test environments, especially automations. Staging environments. Demo environments. Production environments. Easy to set up, easy to use. 19

20. AMAzonvs Azure 20

21. Ideology comparison 21

22. Feature comparison 22

23. Community http://jug-lviv.blogspot.com/ http://dotnetug-lviv.blogspot.com/ http://www.rozrobka.com/ 23

24. Q/A 24 ?