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

EC2 security

Diving deeper into our VPC, we are now going to look at ways to enhance the security around our EC2 instances.

IAM Roles

IAM EC2 Roles are the recommended way to grant your application access to AWS services.

As an example, let us assume we had a web app running on our web server EC2 instance and it needs to be able to upload assets to S3.

A quick way of satisfying that requirement would be to create a set of IAM access keys and hardcode those into the application or its configuration. This however means that from that moment on it might not be very easy to update those keys unless we perform an app/config deployment. Furthermore, we might for one reason or another end up re-using the same set of keys with other applications.

The security implications are evident: reusing keys increases our exposure if those get compromised and having them hardcoded greatly increases our reaction time (it takes more effort to rotate such keys).

An alternative to the preceding method would be to...

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