Search icon
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
AWS Certified Developer - Associate Guide - Second Edition

You're reading from  AWS Certified Developer - Associate Guide - Second Edition

Product type Book
Published in Jun 2019
Publisher Packt
ISBN-13 9781789617313
Pages 812 pages
Edition 2nd Edition
Languages
Authors (2):
Vipul Tankariya Vipul Tankariya
Profile icon Vipul Tankariya
Bhavin Parmar Bhavin Parmar
Profile icon Bhavin Parmar
View More author details

Table of Contents (30) Chapters

Preface 1. Overview of AWS Certified Developer - Associate Certification 2. Understanding the Fundamentals of Amazon Web Services 3. Identity and Access Management (IAM) 4. Virtual Private Clouds 5. Getting Started with Elastic Compute Cloud (EC2) 6. Handling Application Traffic with ELB 7. Monitoring with CloudWatch 8. Simple Storage Service, Glacier, and CloudFront 9. Other AWS Storage Options 10. AWS Relational Database Service 11. AWS DynamoDB - A NoSQL Database Service 12. Amazon Simple Queue Service (SQS) 13. Simple Notification Service (SNS) 14. AWS Simple Workflow Service (SWF) 15. CloudFormation Overview 16. Understanding Elastic Beanstalk 17. Overview of AWS Lambda 18. Key Management Services 19. Working with AWS Kinesis 20. Working with AWS CodeBuild 21. Getting Started with AWS CodeDeploy 22. Working with AWS CodePipeline 23. CI/CD on AWS 24. Serverless Computing 25. Amazon Route 53 26. ElastiCache Overview 27. Mock Tests 28. Assessments 29. Another Book You May Enjoy

The 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. Consequently, 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...

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 €14.99/month. Cancel anytime}