Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Mastering AWS CloudFormation

You're reading from   Mastering AWS CloudFormation Plan, develop, and deploy your cloud infrastructure effectively using AWS CloudFormation

Arrow left icon
Product type Paperback
Published in May 2020
Publisher Packt
ISBN-13 9781789130935
Length 300 pages
Edition 1st Edition
Tools
Arrow right icon
Author (1):
Arrow left icon
Karen Tovmasyan Karen Tovmasyan
Author Profile Icon Karen Tovmasyan
Karen Tovmasyan
Arrow right icon
View More author details
Toc

Table of Contents (17) Chapters Close

Preface 1. Section 1: CloudFormation Internals
2. CloudFormation Refresher FREE CHAPTER 3. Advanced Template Development 4. Section 2: Provisioning and Deployment at Scale
5. Validation, Linting, and Deployment of the Stack 6. Continuous Integration and Deployment 7. Deploying to Multiple Regions and Accounts Using StackSets 8. Configuration Management of the EC2 Instances Using cfn-init 9. Section 3: Extending CloudFormation
10. Creating Resources outside AWS Using Custom Resources 11. Dynamically Rendering the Template Using Template Macros 12. Generating CloudFormation Templates Using AWS CDK 13. Deploying Serverless Applications Using AWS SAM 14. What's Next? 15. Assessments 16. Other Books You May Enjoy

Running smoke tests on your stack

How do we know whether our application is healthy once it is deployed?

In addition to monitoring, logging, and alerting, there is a method called smoke testing.

Smoke testing is a method of testing that is applied during or after an application's release. It helps us to understand whether the current release is functional or whether it contains several bugs or failures that require immediate rollback.

CloudFormation has an out-of-the-box rollback feature. As we know, it will roll back our stack to the previous healthy state if at least one of the changes could not be applied or a resource cannot be created. From the perspective of AWS, it is usually an AWS service that reports that the resource creation has failed and that the error we are seeing is actually an error message from AWS' API. However, some resources are not reported on if they have failed to create by design.

Smoke testing for EC2 auto scaling groups

For example...

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
Banner background image