6. EC2
EC2-Elastic Cloud Compute
Available in 8
Regions(Tokyo, Singapore, Sydney, Ireland, Sao
Paulo, Virginia, N.California, Origon)
Highly Available Virtual Machines
Durable Persistent disk image
Customizable AMIs
Low-cost, pay-as-you-go basis
No up-front cost
Auto scaling
OS Platforms
Programmable APIs
7. RDS
RDS – Relational Database Service
Oracle, MySQL, SQL Server
Easy provisioning thru AWS management console
Ability to connect using favorite database tools
Pay only for the resource you actually consume
Designed for use with other Amazon Services
Features
Monitoring and metrics
Automated Software Patching
Automated Backup
Snapshot
Provisioned IOPS (1K to 10K for Oracle, MySQL; 7K SQL Server)
Automatic Host Replacement
Isolation and Security
8. S3
S3 – Simple Storage Service
Easy provisioning using AWS Management
Console or API
Easy accessible end points
9. Why use Cloud Storage?
Highly Available with Strong Consistency
Provide access to data in face of failures/partitioning
Durability
Replicate data several times within and across data
centers
Scalability
Need to scale to Exabyte's and beyond
Provide a global namespace to access data around
the world
Automatically load balance data to meet peak traffic
demands
13. CloudFormation
Declaration of the AWS resource
JSON-compliant text file
Start from scratch or from the initial template
Create your AWS Stack from recipe
Automated Provisioning using CloudFormation
Simplifying IT
Operations – Create/Update/Delete
Update with no interruption
reconfiguration with some interruption
Replacement
14. Elastic Beanstalk
Application Container /PaaS (Platform as a Service)
Easy to deploy and manage applications in the
cloud
Ability to deploy thru Visual Studio or Microsoft
Web Package
Beanstalk provides
Capacity provisioning
Elastic Load balancing
Auto-scaling
Health Monitoring
Slide Objectives:Explain the differences and relationship between IaaS, PaaS, and SaaS in more detail.Speaker Notes:Here’s another way to look at the cloud services taxonomy and how this taxonomy maps to the components in an IT infrastructure. Packaged SoftwareWith packaged software a customer would be responsible for managing the entire stack – ranging from the network connectivity to the applications. IaaSWith Infrastructure as a Service, the lower levels of the stack are managed by a vendor. Some of these components can be provided by traditional hosters – in fact most of them have moved to having a virtualized offering. Very few actually provide an OSThe customer is still responsible for managing the OS through the Applications. For the developer, an obvious benefit with IaaS is that it frees the developer from many concerns when provisioning physical or virtual machines. This was one of the earliest and primary use cases for Amazon Web Services Elastic Cloud Compute (EC2). Developers were able to readily provision virtual machines (AMIs) on EC2, develop and test solutions and, often, run the results ‘in production’. The only requirement was a credit card to pay for the services.PaaSWith Platform as a Service, everything from the network connectivity through the runtime is provided and managed by the platform vendor. The Windows Azure best fits in this category today. In fact because we don’t provide access to the underlying virtualization or operating system today, we’re often referred to as not providing IaaS.PaaS offerings further reduce the developer burden by additionally supporting the platform runtime and related application services. With PaaS, the developer can, almost immediately, begin creating the business logic for an application. Potentially, the increases in productivity are considerable and, because the hardware and operational aspects of the cloud platform are also managed by the cloud platform provider, applications can quickly be taken from an idea to reality very quickly.SaaSFinally, with SaaS, a vendor provides the application and abstracts you from all of the underlying components.