AWS Summit Auckland 2014 | Running your First Application on AWS

1. © 2014 Amazon.com, Inc. and its affiliates. All rights reserved. May not be copied, modified, or distributed in whole or in part without the express consent of Amazon.com, Inc. Running your First Application on AWS Clayton Brown Solution Architect, Amazon Web Services

2. Build an AWS based, Scalable Mobile application that is location aware by connecting with the user’s mobile device. The Vision….

3. The Reality…. Minimum Viable Product (MVP) = Fixed amount of time* to build it and to demonstrate key AWS concepts… services … and squeeze into a 45 minute presentation *Approx: 2.5 <interrupted> days of coding effort, YMMV

4. Amazon Global Physical Infrastructure (10 Geographic Regions, Multiple Availability Zones, 51 Edge Locations) Parallel Processing Amazon Elastic MapReduce Content Delivery Amazon Cloud Front Messaging Amazon SNS Amazon SQS Email Amazon Simple Email Service (SES) Payments Amazon DevPay Amazon Flexible Payment System (FPS) Workforce Amazon Mechanical Turk High Level Building Blocks Compute Amazon EC2 Auto Scaling VM Import/Export Storage Amazon S3 EBS, Glacier, Import/Export Network Amazon VPC Elastic Load Balancer Route 53 Database Amazon RDS Simple DB, Dynamo DB, ElastiCache Low Level Building Blocks Authentication & Authorization Amazon IAM (inc MFA) Monitoring Amazon CloudWatch Deployment & Automation Amazon Elastic Beanstalk Amazon CloudFormation Cross Service Features Libraries and SDKs .Net / Java etc Web Interface Management Console Tools Visual Studio .Net / Eclipse Plugin Command Line Interface Tools to Access Services Your Application We’ll Use these Services Today

5. Reasoning Behind Service Usage Solution Requirement AWS Service(s) DNS Resolution Route 53 Networking Virtual Private Cloud (VPC by default) Load Balancing to Meet Demand Elastic Load Balancer (ELB) Auto Scaling Groups (ASG) CloudWatch Metrics Windows Servers for ASP.Net Elastic Compute Cloud (EC2) Instances Application Deployment Directly from Dev Tools Elastic Beanstalk (also helps with auto-scaling) Content Delivery Network CloudFront Reliable Storage Elastic Block Store (EBS) for Instances & Simple Storage Service (S3) Database (for Session Store) DynamoDB (No SQL) Security Identity and Access Management (IAM) Push Uploaded Content into a future backend system yet to be specified Simple Queue Service (SQS)

6. The Application User Experience

7. The Core Architecture

8. on AWS The Overall Solution Architecture API Mobile Web Site

9. Now how to build this….

10. AWS Elastic Beanstalk •  AWS Elastic Beanstalk allows for automated deployment of applications by configuring its run-time environment (inside the AMI) –  Upload your application package –  Beanstalk handles the deployment details of capacity provisioning, load balancing, auto-scaling, application health monitoring, and DNS CNAME •  Environment is available in minutes at a customized URL (e.g. http://myapp.elasticbeanstalk.com/) •  Elastic Beanstalk supports ASP.Net, Java, Node.Js, PHP, Python & Ruby •  Think about it as a managed runtime or “Container as a Service”

11. AWS SDKs & Toolkits Java .NET nodeJS Node JS Ruby RubyPython PHP iOS IOS Android AWS CLI PowershellVisual Studio Eclipse

12. AWS SDKs & Toolkits .NET Visual Studio

15. Visual Studio Add-In Toolkit from AWS Custom AWS Projects Cloud Formation Aware Editor Available from http://aws.amazon.com/visualstudio/

16. Explore, Code and Publish Directly To AWS

17. Explore, Code and Publish Directly To AWS

18. Explore, Code and Publish Directly to AWS

19. Demo Publish to Beanstalk

20. …. And Elastic Beanstalk will create you something like this! Visual Studio http://lunchandlearn.elasticbeanstalk.com

21. Development Route 53 summit2014-dev.stanski.me (A Record to IP 123.123.123.123) Development Server on AWS DNS Setup For Application Route 53 summit2014.stanski.me (CNAME to) summit2014.elasticbeanstalk.com (CNAME to) PublicELB-143817XX.ap- southeast-2.elb.amazonaws.com Production

22. Web Application Session State

23. Session State Considerations for Scaling Out •  ASP.Net uses a provider model to enable pluggable providers (DLLs) and settings in the Web.Config file •  In-Proc : in memory on the web server (default OOBE) •  Out-of-Proc : on another server ß Need this for “Scale Out” –  Usually Microsoft SQL Server on a dedicated server •  AWS provides additional Session State Options: 1.  MySQL data provider via RDS (3rd party on Codeplex) 2.  MemcacheD (aka ElastiCache) 3.  AWS DynamoDB AWS Blog Managing ASP.Net Session State With DynamoDB : http://bit.ly/1k0DeVz

24. Dynamo DB •  DynamoDB is a very fast, managed NoSQL database as a service •  Designed to store and retrieve any amount of data, and serve virtually any level of traffic with automatic sharding it linearly scalable –  Dial in the number of read and writes per second as needed by application •  All data items are stored on Solid State Drives (SSDs), replicated across 3 Availability Zones for high availability and high durability •  DynamoDB offloads the administrative burden of operating and scaling a highly available distributed database cluster

25. AWS SDK via NuGet in Visual Studio "  Pre-packaged NuGet AWS tools can be installed to provide DynamoDB Session State Support

26. Changes to Web.Config file to enable AWS DynamoDB Session State "   Security Tip: Create a custom IAM user to only allow access to DynamoDB

27. Static Content

28. Static Web Content Management Strategy •  Static Content usually resides on the same web server as dynamic web content –  E.g.. Jpegs, CSS, JS, GIFs etc •  Moving static content to dedicated “static content servers” can reduce server loads •  On AWS this means smaller instances for EC2 and lower hourly cost and using Simple Storage Service (S3) •  By using Route 53 DNS this can be changed without web application disruption

29. Application HTML References to Static Assets •  Edit HTML content directly to reference fully qualified domain name to let DNS resolve origin servers; OR •  Use Content Rewrites in the web server –  E.g. ASP.Net Content/HTTP Handlers

30. Amazon Simple Storage Service (S3) •  Amazon S3 provides a simple web services interface that can be used to store and retrieve any amount of data, at any time, from anywhere on the web •  It is designed to make web-scale computing easier for developers by allowing storage of Web accessible static content "   Allows for easy static website hosting (No EC2 Servers required) "   Designed for 99.999999999% durability and 99.99% availability of objects over a given year •  Gives developers access to the same highly scalable, reliable, secure, fast, inexpensive infrastructure that Amazon uses to run its own global network of web sites

31. S3 Bucket Setup – Static Web Hosting Enabled •  DNS abstracts the actual storage location from web browser

32. S3 DNS Setup Route 53 cdn.stanski.me (A Record to IP) Development Server on AWS Development Route 53 cdn.stanski.me (CNAME to) cdn.stanski.me.s3-website-ap- southeast-2.amazonaws.com Production "  DNS changes the underlying content origin systems Static Content Copy to S3

33. Content Delivery Acceleration

34. CloudFront : Content Delivery Network (CDN) •  CloudFront can be used to deliver your entire website, including dynamic, static as well as streaming content using a global network of edge locations •  Requests for your content can be automatically routed to the nearest edge location, so content is delivered with the best possible performance •  It integrates with Amazon Web Services like EC2 & S3 to give developers an easy way to distribute content to end users with low latency, high data transfer speeds, and no commitments

35. CloudFront Distribution "   CF responds on its Domain Name and Alternative CNAMES

36. CloudFront Origin "   CF Origin points to the S3 Bucket containing static content

37. CloudFront DNS Setup Route 53 cdn.stanski.me (A Record to IP) Development Server on AWS Development "  DNS abstracts the actual storage location from the web browser Route 53 cdn.stanski.me (CNAME to) CloudFront Name: dx21lojdjnvls.cloudfront.net Production S3 Origin: cdn.stanski.me.s3- website-ap- southeast-2.amazonaws.com Static Content Copy to S3

38. API Integration Twilio Google Maps Amazon SQS

39. Google API C# Snippet "   Using the Google API to convert GPS to Street information

40. Twilio API C# Snippet •  Using the Twilio .Net SDK to send a Text Message and make a Phone Call

41. Amazon Simple Queue Service (SQS) •  Amazon Simple Queue Service (SQS) is a fast, reliable, scalable, fully managed queue service – think MSMQ, RabbitMQ, JMS etc •  SQS makes it simple to decouple the components of a cloud application •  You can use SQS to transmit any volume of data, at any level of throughput, without losing messages or requiring other services to be always available •  With SQS you can offload the administrative burden of operating and scaling a highly available messaging cluster •  Used here to future proof your application: thumbnail images are pushed in the Summit2014Q –  This is to address the requirement of a “future application back-end-system”

42. SQS C# AWS SDK Snippet •  Create an SQS queue and send a Message into it…

43. Polling SQS in the Web Console •  Queues can be managed from the web console

44. Now lets see the app… summit2014.stanski.me

45. How could we iterate next ? •  Mobile SDKs for additional Mobile Platforms iOS, Android •  Geo Library for Amazon Dynamo DB for geospatial queries •  Amazon SQS, Amazon SNS push notifications, and more •  IAM to provide more fine-grained access control •  Or use restricted temporary AWS Credentials •  Web Social Sign In with Amazon, Google & Facebook •  Row level segregation of user data in DynamoDB

46. Key Takeaways & Next Steps •  There are a lots more services to learn & leverage •  Classroom based training & certification is available •  We offer elastic and comprehensive support •  We listen to our customers and iterate rapidly •  Available for chalk talks, workshops and other sessions