Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Mastering AWS CloudFormation

You're reading from   Mastering AWS CloudFormation Build resilient and production-ready infrastructure in Amazon Web Services with CloudFormation

Arrow left icon
Product type Paperback
Published in Nov 2023
Publisher Packt
ISBN-13 9781805123903
Length 310 pages
Edition 2nd Edition
Languages
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 (19) Chapters Close

Preface 1. Part 1: CloudFormation Internals FREE CHAPTER
2. Chapter 1: Working with CloudFormation 3. Chapter 2: Advanced Template Development 4. Part 2: Provisioning and Deployment at Scale
5. Chapter 3: Validation, Linting, and Deploying the Stack 6. Chapter 4: Continuous Integration and Deployment 7. Chapter 5: Deploying to Multiple Regions and Accounts Using StackSets 8. Chapter 6: Configuration Management of EC2 Instances Using cfn-init 9. Part 3: Extending CloudFormation
10. Chapter 7: Creating Resources Outside AWS Using Custom Resources 11. Chapter 8: Creating Your Own Resource Registry for CloudFormation 12. Chapter 9: Scale Your Templates Using Macros, Nested Stacks, and Modules 13. Chapter 10: Generating CloudFormation Templates Using AWS CDK 14. Chapter 11: Deploying Serverless Applications Using AWS SAM 15. Chapter 12: What’s Next? 16. Assessments 17. Index 18. Other Books You May Enjoy

Including a template in your application

You will recall from the previous chapters that we had several templates for different tiers. We had core (network and security), web (frontend), middleware (backend), and database tiers.

So far, we haven’t stored our templates in the version control system, but since we need to apply CD, we need to figure out the proper way to store them. Normally, it all depends on how you want to organize your workflow. If you have a separate operations or cloud team that is responsible for infrastructure and operations, it is wise to keep all the templates in a single repository. Developers will then supply you with any desired changes to the infrastructure or with the new version of the application.

Our flow is as follows:

  1. The developer publishes a new version of an app.
  2. The developer provides the operations team with the new version and/or changes.
  3. The operations team makes changes to parameters and/or templates.
  4. The operations...
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 €18.99/month. Cancel anytime