Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletter Hub
Free Learning
Arrow right icon
timer SALE ENDS IN
0 Days
:
00 Hours
:
00 Minutes
:
00 Seconds
Arrow up icon
GO TO TOP
Learning AWS

You're reading from   Learning AWS Design, build, and deploy responsive applications using AWS cloud components

Arrow left icon
Product type Paperback
Published in Jul 2015
Publisher
ISBN-13 9781784394639
Length 236 pages
Edition 1st Edition
Tools
Arrow right icon
Toc

Table of Contents (14) Chapters Close

Learning AWS
Credits
About the Authors
About the Reviewers
www.PacktPub.com
Preface
1. Cloud 101 – Understanding the Basics FREE CHAPTER 2. Designing Cloud Applications – An Architect's Perspective 3. AWS Components, Cost Model, and Application Development Environments 4. Designing for and Implementing Scalability 5. Designing for and Implementing High Availability 6. Designing for and Implementing Security 7. Deploying to Production and Going Live Index

Setting up high availability


This section introduces configuring AWS infrastructure to support high availability for our application. Most of Amazon's high-level services are designed for high availability and fault tolerance such as Elastic Load Balancer (ELB), Simple Storage Service (S3), Simple Queue Service (SQS), Simple Notification Service (SNS), Relation Database Service (RDS), Route 53 a dynamic DNS service, and CloudWatch. The infrastructure services such as Elastic Cloud Compute (EC2) and Elastic Block Storage (EBS) provide constructs such as availability zones, elastic IP addresses, and snapshots to design high availability and fault tolerant applications. Remember hosting an application on the cloud does not make it fault-tolerant or highly available.

Note

We will be architecting for high availability and not for fault tolerance. The difference between them is that there is no service interruption in the case of fault-tolerant services; whereas, there is minimal service interruption...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at £13.99/month. Cancel anytime
Visually different images