Building Enterprise Cloud Apps
•
10 likes•1,288 views
Building Enterprise Applications in the Cloud - presentation by Mike Culver at the AWS Cloud for the Enterprise Event in LA on October 15, 2009
![WE THINK OF THE CLOUD AS A SET OF BUILDING BLOCK SERVICES ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Building Enterprise Cloud Apps
Similar to Building Enterprise Cloud Apps (20)
More from Amazon Web Services
More from Amazon Web Services (20)
Recently uploaded
Recently uploaded (20)
Building Enterprise Cloud Apps
- 1. BUILDING ENTERPRISE CLOUD APPS Mike Culver, Strategic Alliances Team
- 4. CONSERVE CAPITAL Infrastructure Cost $ time Large Capital Expenditure You just lost customers Predicted Demand Traditional Hardware Actual Demand Automated Virtualization
- 5. EC2 HAS AN UNPRECEDENTED DURABILITY MODEL Note: Conceptual drawing only. The number of Availability Zones may vary Amazon CloudWatch Auto Scaling Elastic Load Balancing
- 6. CLOUD COMPUTING ATTRIBUTES Abstract Resources Not tied to physical hardware and can be flexible as your needs demand. On-Demand Provisioning Ask for what you need, exactly when you need it. Pay only for what you use. Scalability Scale up or down depending on usage needs. No Up-Front Costs No contracts or long-term commitments. Pay only for what you use. Efficiency of Experts Utilize the skills, knowledge and resources of experts.
- 8. Move to the Cloud Build for the Cloud
- 13. SOA OFTEN HAS A BUS Service Bus Order Entry Credit Check Inventory Allocation Pick Ticket Generated Send Confirmation Email
- 14. ARCHITECT FOR EVERYTHING FAILS AND THEN NOTHING DOES Bus Order Entry Credit Check Bus Amazon Simple Queue Service
- 20. SAMPLE ARCHITECTURE: MIGRATING YOUR INTERNAL IT APPLICATIONS
- 23. AMAZON VPC ARCHITECTURE Your Network Amazon Web Services Cloud Secure VPN Connection over the Internet Subnets Customer’s isolated AWS resources VPN Gateway
- 28. SETUP THE WEB SERVER IN AMAZON VPC Amazon VPC Existing Network AWS Cloud
- 30. USE AMAZON S3 FOR RAW STORAGE Store persistent files in Amazon S3 for lower costs, higher reliability Encrypt sensitive data AWS Cloud
- 31. USE AMAZON EBS TO HOST DATABASES AWS Cloud Configure an Amazon EBS device to host your existing relational database. Snapshots can be automatically backed up to Amazon S3.
- 32. INTERACT WITH EXISTING CORPORATE SYSTEMS Amazon VPC provides a two-way secure connection so that applications hosted in AWS can communicate with systems hosted in our existing network.
- 35. AWS MANAGEMENT CONSOLE https://aws.amazon.com/console
- 36. BUT WHAT IF YOU HAVE WHAT YOU HAVE?
Editor's Notes
- Services Oriented Architecture is a significant step forward in terms of building scaleable and resilient applications. A typical SOA application might look something like whis, where each step in a workflow is connected to a pipeline, or Service Bus.
- Under the hood the bus actually uses Amazon Simple Queue between steps.
- Point of Slide: to explain VPC's high-level architecture, walking them through the discrete elements of a VPC, and a specific data flow to exemplify 1) data-in-transit security and continued 1) AAA control by the enterprise. AWS (”orange cloud"): What everybody knows of AWS today. Customer’s Network (“blue square”) : The customer’s internal IT infrastructure. VPC (”blue square on top of orange cloud"): Secure container for other object types; includes Border Router for external connectivity. The isolated resources that customers have in the AWS cloud. Cloud Router (“orange router surrounded by clouds”) : Lives within a VPC; anchors an AZ; presents stateful filtering. Cloud Subnet (“blue squares” inside VPC): connects instances to a Cloud Router. VPN Connection: Customer Gateway and VPN Gateway anchor both sides of the VPN Connection, and enables secure connectivity; implemented using industry standard mechanisms. Please note that we currently require whatever customer gateway device is used supports BGP. We actually terminate two (2) tunnels - one tunnel per VPN Gateway - on our side. Besides providing high availability, we can service one device while maintaining service. As such, we can either connect to one of the customer's BGP-supporting devices (preferably running JunOS or IOS).
- This slide discusses the corresponding AWS functionality that we will support at limited public beta launch. Please note that the items under "Launch ++" are other AWS capabilities that we are currently evaluating for operability within VPC, but do not have a date as yet. Direct Internet/AWS access is our most important feature.
- As you can recall, we’ve setup Amazon VPC in the AWS cloud. We’ve also configured a secure connection between our existing network and Amazon VPC. All of our activity inside our VPC and all traffic to and from our existing network and Amazon VPC can be monitored, managed, and secured by all of our existing security apparatus and procedures/policies. We will deploy our web server and full application platform stack on Amazon EC2 instances that are spawned within Amazon VPC.
- Benefits of using Amazon EC2 to host your web application.
- We will host all of our static and large files over on Amazon S3. Things like images, music, PDFs, and the like are best suited for Amazon S3. Amazon S3 provides a low-cost, highly reliable and scalable storage environment for your web applications. We will encrypt this data for security reasons.
- You can host your relational database on top of Amazon EBS. Companies like IBM and Oracle have even enabled license portability so that you can bring your existing database licenses into the AWS cloud.
- As you’ll recall, we want our application to be able to kickoff workflows with a bunch of systems we’re already running internally. While it may make sense, both economically and technically, to eventually migrate these systems into AWS as well, as of right now that isn’t the case. So, we’ll need to be able to have our Employee Provisioning application that is hosted in AWS be able to communicate with our internal systems. With Amazon VPC, this is easy.
- These are some additional AWS features that we could use as part of our application.