Book Image

AWS Certified Developer - Associate Guide

By : Vipul Tankariya, Bhavin Parmar
Book Image

AWS Certified Developer - Associate Guide

By: Vipul Tankariya, Bhavin Parmar

Overview of this book

AWS Certified Developer - Associate Guide starts with a quick introduction to AWS and the prerequisites to get you started. Then, this book gives you a fair understanding of core AWS services and basic architecture. Next, this book will describe about getting familiar with Identity and Access Management (IAM) along with Virtual private cloud (VPC). Moving ahead you will learn about Elastic Compute cloud (EC2) and handling application traffic with Elastic Load Balancing (ELB). Going ahead you we will talk about Monitoring with CloudWatch, Simple storage service (S3) and Glacier and CloudFront along with other AWS storage options. Next we will take you through AWS DynamoDB – A NoSQL Database Service, Amazon Simple Queue Service (SQS) and CloudFormation Overview. Finally, this book covers understanding Elastic Beanstalk and overview of AWS lambda. At the end of this book, we will cover enough topics, tips and tricks along with mock tests for you to be able to pass the AWS Certified Developer - Associate exam and develop as well as manage your applications on the AWS platform.
Table of Contents (29 chapters)
Title Page
Credits
About the Author
Acknowledgments
About the Author
About the Reviewer
www.PacktPub.com
Customer Feedback
Dedication
Preface
Index

Version life cycle


Elastic Beanstalk creates a newer application version upon uploading a newer source code bundle. Creating a newer version and not deleting the old unwanted application version leads to hitting the application version limit. As a result, it does not allow us to create any newer web application versions.

The default Elastic Beanstalk limits are as follows:

Resource

Default limit

Applications

75

Application versions

1,000

Environments

200

With the help of the application version life cycle policy for an application, hitting an application version limit can be avoided. Consistently, it will manage the number of available application versions at any given time. Once the life cycle policy is enabled, it will keep either the total count of recent versions (that is, the last 200 versions of the application) or the versions that are not older than the specified age in terms of days (that is, 180 days). The application life cycle can be configured using the web console, CLI, or API.