Book Image

AWS Administration - The Definitive Guide - Second Edition

By : Yohan Wadia
Book Image

AWS Administration - The Definitive Guide - Second Edition

By: Yohan Wadia

Overview of this book

Many businesses are moving from traditional data centers to AWS because of its reliability, vast service offerings, lower costs, and high rate of innovation. AWS can be used to accomplish a variety of both simple and tedious tasks. Whether you are a seasoned system admin or a rookie, this book will help you to learn all the skills you need to work with the AWS cloud. This book guides you through some of the most popular AWS services, such as EC2, Elastic Beanstalk, EFS, CloudTrail, Redshift, EMR, Data Pipeline, and IoT using a simple, real-world, application-hosting example. This book will also enhance your application delivery skills with the latest AWS services, such as CodeCommit, CodeDeploy, and CodePipeline, to provide continuous delivery and deployment, while also securing and monitoring your environment's workflow. Each chapter is designed to provide you with maximal information about each AWS service, coupled with easy to follow, hands-on steps, best practices, tips, and recommendations. By the end of the book, you will be able to create a highly secure, fault-tolerant, and scalable environment for your applications to run on.
Table of Contents (17 chapters)
Title Page
Packt Upsell

Planning your next steps

Well, we have covered a lot of new features and services in this chapter, however, there are still a few things that I would recommend you try out on your own. First up is Elastic Beanstalk's advanced configurations.

As mentioned earlier, Beanstalk provides a lot of different ways for you to customize and extend your application with other AWS services using a variety of built-in services such as .ebextensions, which we covered in the previous section. One similar service that can be used to configure a Beanstalk environment's configuration is called the environment manifest file. This is a simple YAML file containing your environment's manifest configurations, such as the environment name, solution stack, and environment links to use when creating your environment. The file is placed in your application's root directory and is generally named env.yaml. One of the key uses of this file is to provide support for environment links that enable you to connect two application...