Book Image

Implementing DevOps on AWS

By : Vaselin Kantsev
Book Image

Implementing DevOps on AWS

By: Vaselin Kantsev

Overview of this book

Knowing how to adopt DevOps in your organization is becoming an increasingly important skill for developers, whether you work for a start-up, an SMB, or an enterprise. This book will help you to drastically reduce the amount of time spent on development and increase the reliability of your software deployments on AWS using popular DevOps methods of automation. To start, you will get familiar with the concept of IaC and will learn to design, deploy, and maintain AWS infrastructure. Further on, you’ll see how to design and deploy a Continuous Integration platform on AWS using either open source or AWS provided tools/services. Following on from the delivery part of the process, you will learn how to deploy a newly created, tested, and verified artefact to the AWS infrastructure without manual intervention. You will then find out what to consider in order to make the implementation of Configuration Management easier and more effective. Toward the end of the book, you will learn some tricks and tips to optimize and secure your AWS environment. By the end of the book, you will have mastered the art of implementing DevOps practices onto AWS.
Table of Contents (17 chapters)
Implementing DevOps on AWS
About the Author
About the Reviewer
Customer Feedback
Free Chapter
What is DevOps and Should You Care?
Build, Test, and Release Faster with Continuous Integration

Using Route53 ALIAS records

This is a special in-house type of DNS record specific to the Route53 service.

For an AWS user an Alias record is a great alternative to a CNAME (for supported resources).

Some of the main advantages are:

  • Aliases resolve directly to an IP address, saving the extra lookup which a CNAME would require

  • Alias records are supported at the zone apex, so you could create an alias which uses the top of a domain (for example

  • Alias records allow advanced Route53 features such as weighted/latency/geo routing and failovers

  • There is no AWS cost associated with Alias lookups


NB: A Route53 Alias record can currently only point to a limited set of AWS resources. For more information please see: