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 now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Implementing DevOps on AWS

You're reading from   Implementing DevOps on AWS Engineering DevOps for modern businesses

Arrow left icon
Product type Paperback
Published in Jan 2017
Publisher Packt
ISBN-13 9781786460141
Length 258 pages
Edition 1st Edition
Tools
Concepts
Arrow right icon
Author (1):
Arrow left icon
Vaselin Kantsev Vaselin Kantsev
Author Profile Icon Vaselin Kantsev
Vaselin Kantsev
Arrow right icon
View More author details
Toc

Table of Contents (11) Chapters Close

Preface 1. What is DevOps and Should You Care? FREE CHAPTER 2. Start Treating Your Infrastructure as Code 3. Bringing Your Infrastructure Under Configuration Management 4. Build, Test, and Release Faster with Continuous Integration 5. Ever-Ready to Deploy Using Continuous Delivery 6. Continuous Deployment - A Fully Automated Workflow 7. Metrics, Log Collection, and Monitoring 8. Optimize for Scale and Cost 9. Secure Your AWS Environment 10. AWS Tips and Tricks

The frontend layer

With the subnets in place, we can start thinking about our VPC inhabitants.

The frontend or application layer consists of our Auto Scaling Groups and the first decision that we'll face would be that of an EC2 instance type.

The profile of the frontend application would very much dictate the choice between a memory, compute or a storage optimized instance. With some help from fellow developers (in the case of an in-house application) and a suitable performance testing tool (or service) you should be able to ascertain which system resource does the given application make most use of.

Let us assume we have picked the C4 Compute Optimized instance class which AWS suggests for webservers. The next question will be - what size?

Well, one way to guess our way through, is to take the average number of requests per second that we would like to be able to support, deploy the minimum number of instances we can afford (two for resilience) of the smallest size available in the chosen...

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 $19.99/month. Cancel anytime