1.
Architecting Enterprise Applications in the Cloud<br />Matt Tavis<br />Solutions Architect<br />

2.
What Does the Enterprise Application Demand?<br />High Availability<br />Manageability<br />Security<br />Monitoring<br />Scalability<br />Reliability<br />

3.
T<br />T<br />T<br />S3 Replicas<br />EC2 Regions<br />Availability Zone A<br />Availability Zone B<br />Availability Zone C<br />Auto Scaling<br />Amazon CloudWatch<br />Elastic Load Balancing<br />Note: Conceptual drawing only. The number of Availability Zones may vary. S3 guarantees 3 or more copies across 2 or more AZs.<br />AWS has the Tools for Enterprise Demands<br />

4.
Achieving Enterprise Needs is an Agreement between Architecture and Infrastructure<br />Leveraging a scalable, on-demand infrastructure requires an application that can take advantage of it.<br />Corollary: Fork-lifting a broken architecture into the AWS cloud will not make it any better<br />Architecture and Infrastructure Must Work Together<br />

5.
There are Many Paths into the Cloud<br />Move to the Cloud<br />Build for the Cloud<br />

6.
Design for Failure and Nothing Fails<br />Loose Coupling Sets You Free<br />Design for Dynamism<br />Security is Everywhere<br />Don’t Fear Constraints<br />Leverage a Variety of Storage Services<br />Cloud Architecture Lessons Learned<br />

7.
Never expect your systems to be stable<br />Everything fails<br />Hard disks<br />Power supplies<br />Cabling<br />Network ports<br />Switches<br />Load-balancers<br />Ethernet chips<br />IO controllers<br />Fans<br />Even software fails<br />If you can add it, it can fail<br />Design for Failure and Nothing Fails<br />

8.
Elastic IPs enable consistent endpoints and a re-mappable<br />Leverage multiple Amazon EC2 Availability Zones (AZs)<br />Replicate databases and persistence layers across AZs<br />Use real-time monitoring across key access points<br />Use Elastic Block Store (EBS) for persistent file systems<br />Snapshot EBS for disaster recovery and increased persistence<br />Auto Scaling and Elastic Load Balancing can automatically provision new resources<br />Use Amazon CloudWatch to monitor instance health<br />Designing for Failure with AWS<br />

9.
Components should not make no assumptions about the inner workings of other components<br />Design for a jumble of black boxes<br />Loosely coupled systems and AWS<br />De-coupling systems allows for hybrid models (in-cloud + in-physical data center)<br />Balancing between clusters enables easier scaling<br />Using queues (Amazon SQS) buffers against failures<br />Loose Coupling Sets You Free<br />

10.
Components should not assume the health or location of other components<br />Bootstrapping and dynamic configuration helps you scale dynamically<br />Add or build management components to enable scale-out and scale-in on-demand<br />Design for Dynamism<br />

11.
With AWS, physical security is free, network security is easy, and other security can be added<br />Building secure systems with AWS<br />Create distinct Security Groups for each Amazon EC2 cluster<br />Use group-based rules for controlling access between layers<br />Restrict external access to specific IP ranges and ports<br />Use strong passwords and certificate-based authentication<br />Encrypt data stored in Amazon S3<br />Encrypt information transmitted across the wire<br />Use encrypted file systems for sensitive data<br />Security is Everywhere<br />

12.
Having a flexible, on-demand pool of resources allows for different architectures that remove constraints<br />Don’t Fear Constraints<br /> I need more than xxGB of RAM per instance<br />Distribute load across multiple instances; use a shared distributed cache<br /> I need more than xxK IOPS on my database<br />Run multiple read-only copies; sharding; database clustering software<br /> My current server specs are better than the EC2 instances<br />Run more Amazon EC2 instances but only when you need them<br /> I need static IPs for my servers<br />Boot scripts that re-configure software from configuration database<br />

13.
AWS offers a wide variety of storage services designed for reliability, low latency, ease of access, indexing and throughput.<br />Amazon S3 is optimized for easy access to highly durable and available storage of objects<br />Store persistent data needing durability and easy access<br />Amazon CloudFront for performance<br />Push popular objects to worldwide edge locations<br />Amazon SimpleDB for indexing, speed, scale, and simplicity<br />Store small bits of data that have no dependencies, such as metadata<br />Amazon EBS acts like a disk drive for persistent storage with high throughput and basic durability<br />Store dynamic content or a traditional RDBMS<br />Amazon EC2 local disk space for transient data<br />Leverage a Variety of Storage Services<br />

14.
Deploy internal applications for greater cost savings<br />Development, test, staging and training environments<br />Hosting of quick and effective marketing campaign (micro-sites)<br />Faster time to market for new business opportunities<br />Recurring or on-demand batch data processing jobs<br />Large scale analytics (Hadoop)<br />Disaster recovery<br />Load testing applications on your own infrastructure<br />What Can an Enterprise Do on AWS?<br />

15.
Sample Architecture:Migrating Your Internal IT Applications<br />

16.
A typical enterprise application could need:<br />A secure environment that is part of the enterprises’ existing network (Amazon VPC)<br />Computing power (Amazon EC2)<br />Storage capacity for images, videos, backups, files, etc. (Amazon S3)<br />Indexed storage (Amazon SimpleDB)<br />Relational Database (Your favorite on EBS)<br />Messaging between components (Amazon SQS)<br />Load balancing for optimal performance<br />Enterprise Application Design on AWS<br />

17.
Create a secure connection between assets and applications within your corporate network and assets and applications that reside in AWS<br />Users and applications within your existing infrastructure securely interact with assets in AWS as if they were local<br />Amazon VPC Extends Your Datacenter<br />Your existing infrastructure<br />Amazon VPC<br />

18.
Customer’s isolated AWS resources<br />Amazon VPC Architecture<br />10.32.2.0/24<br />Subnets<br />10.32.3.0/24<br />10.32.1.0/24<br />VPN Gateway<br />AmazonWeb Services<br />Cloud<br />Secure VPN Connection over the Internet<br />External<br />Customers<br />YourNetwork<br />

19.
Establish subnets to control who and what can access your resources<br />Connect your isolated AWS resources and your IT infrastructure via a VPN connection<br />Launch AWS resources within the isolated network<br />Use your existing security and networking technologies to examine traffic to/from your isolated resources<br />Extend your existing security and management policies within your IT infrastructure to your isolated AWS resources as if they were running within your infrastructure<br />Amazon VPC Creates an isolated environment within AWS<br />

20.
Advantages of your on-premises infrastructure<br />Ensure network isolation<br />Works with your security tools<br />Employ your existing identity and authentication infrastructure<br />Integrates seamlessly with the rest of your infrastructure via VPN<br />Plus, the benefits of a cloud-based infrastructure<br />Don’t get trapped by CapEx<br />True company-level elasticity<br />Lower operational responsibilities and costs<br />Super-fast provisioning of on-demand resources<br />Realize the Best of Both Worlds<br />

21.
Available now<br />Amazon EBS<br />Single AZ in us-east-1<br />Amazon CloudWatch<br />On-Demand and Reserved Instances<br />Linux/UNIX and Windows<br />Upcoming features<br />Direct Internet access<br />Multiple AZs<br />Elastic IPs<br />Security groups<br />Amazon DevPay<br />Auto Scaling<br />Elastic Load Balancing<br />Amazon VPC: Supported AWS Features<br />

22.
Internal new employee provisioning application<br />A hiring manager visits an internal website<br />Enters employee information, including start date, office location, computer type, and so on<br />The website kicks off a series of workflows on existing systems already deployed within the company<br />Facilities: setup the office space<br />IT: setup the new computer<br />Hiring manager: email with forms for employee to fill out<br />…and so on…<br />Spiky usage around Summer (new interns)<br />No internal resources available for the application, so the organization has chosen to deploy in AWS<br />Our Sample Enterprise Application (Old Way)<br />

23.
Setup the Web Server in Amazon VPC<br />AWS Cloud<br />Amazon VPC<br />Existing Network<br />

24.
Flexible<br />Choose your programming model, application platform, databases, and operating system stack<br />Cost-effective, pay only for what you use<br />Scalable<br />Automatically add and delete resources as they are needed<br />Reliable<br />Built on the world-class Amazon infrastructure<br />Secure<br />Connection with Amazon VPC ensures that only users within your organization can see your AWS resources<br />Web Server Running on Amazon EC2<br />

25.
Use Amazon S3 for Raw Storage<br />AWS Cloud<br />Store persistent files in Amazon S3 for lower costs, higher reliability<br />Encrypt sensitive data<br />

26.
Use Amazon EBS to Host Databases<br />AWS Cloud<br />Configure an Amazon EBS device to host your existing relational database. Snapshots can be automatically backed up to Amazon S3.<br />

27.
Interact With Existing Corporate Systems<br />Amazon VPC provides a two-way secure connection so that applications hosted in AWS can communicate with systems hosted in our existing network.<br />

28.
Amazon SimpleDB can be used as a cost-effective, zero-administration indexed store for your application<br />Amazon CloudWatch, Elastic Load Balancing, and Auto-Scaling services enable greater fault-tolerance and scalability<br />Amazon Elastic MapReduce can be used to crunch and analyze large amounts of data<br />Amazon Flexible Payments Service can handle checkout pipelines and payment methods<br />Amazon Mechanical Turk can be used for tasks best suited for human intervention (e.g., image upload and content approval, database cleansing, etc.)<br />Additional Capabilities<br />

29.
AWS Management Console<br />Numerous cloud-based third-party providers<br />BMC, RightScale, others<br />API-based control enables existing workflow applications to manage AWS resources<br />Existing IT management systems can extend to cloud<br />Amazon VPC enables existing management and operations systems, security policies, etc. to extend to cloud resources<br />Amazon CloudWatch provides easy to use monitoring<br />Management and Operations<br />

30.
https://aws.amazon.com/console<br />AWS Management Console<br />

31.
But What if You Have What you Have?<br />But can I use Package X <br />in the AWS Cloud?<br />

32.

33.

34.
Thank You<br />aws.amazon.com<br />