Скачать или смотреть Understanding Mutable vs Immutable Infrastructure in AWS CloudFormation

Dive into the difference between mutable and immutable infrastructure in AWS CloudFormation. Explore how CloudFormation manages resource updates, and what this means for your applications.
---
This video is based on the question https://stackoverflow.com/q/69140280/ asked by the user 'user10916892' ( https://stackoverflow.com/u/10916892/ ) and on the answer https://stackoverflow.com/a/69140614/ provided by the user 'LRutten' ( https://stackoverflow.com/u/12259756/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: AWS Cloudformation - Is it mutable or immutable infrastructure?

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Understanding Mutable vs Immutable Infrastructure in AWS CloudFormation

When working with cloud services, particularly with AWS (Amazon Web Services), infrastructure management can often lead to questions about the underlying mechanics of how resources are handled. One common inquiry that arises is whether AWS CloudFormation operates under a mutable or immutable infrastructure model. This guide will clarify these concepts and explain how CloudFormation functions when updating resources.

What Do Mutable and Immutable Infrastructures Mean?

Before delving into CloudFormation's behavior, let’s distinguish between mutable and immutable infrastructures:

Mutable Infrastructure: In this model, resources can be changed or modified in place. For example, if a virtual server requires additional memory or disk space, those changes can be applied directly without the need to replace the server entirely. This approach is flexible, allowing for quick changes, but it can introduce complexities and inconsistencies over time.

Immutable Infrastructure: In contrast, immutable infrastructure indicates that once a resource is created, it cannot be changed. Instead, any updates or modifications require the creation of a new resource. This approach often leads to more stable systems since the state of resources remains consistent, minimizing issues that arise from configuration changes.

Is AWS CloudFormation Mutable or Immutable?

AWS CloudFormation provides a means to automate and manage infrastructure as code. So, when it comes to updates using CloudFormation stacks, the following points should be considered:

Resource Properties Update:

CloudFormation, like many Infrastructure as Code (IaC) tools, strives to update resource properties without replacing the entire resource whenever possible.

However, the capability to do this depends on the specifics of the AWS service APIs involved. Some properties can be updated without any interruption, while others necessitate replacing the resource.

Examples of Behavior:

Consider an Application Load Balancer (ALB): Changing its scheme from public to internal requires creating a new ALB, representing a shift towards an immutable approach for that setting.

Conversely, other properties, such as updating security groups, can be altered in place, reflecting mutable behavior.

Discussion on Infrastructure Management Paradigms

Given the nuances of resource updates in AWS CloudFormation, it's crucial to recognize that the infrastructure management landscape has evolved, particularly with an emphasis on immutable structures in application layers:

Immutability in Applications:

Today's discussions about immutable infrastructure primarily focus on application layers, especially in designs that follow a three-tier architecture consisting of load balancers, application layers, and data layers.

Services like EC2, ECS, and EKS utilize autoscaling groups or container orchestration, allowing instances to be treated as transient resources without retaining state. When a change is necessary, these resources can simply be replaced, which aligns with the principles of immutable infrastructure.

Conclusion

In summary, AWS CloudFormation operates on a mutable infrastructure basis whenever feasible, attempting to update resources in place. However, it also accommodates an immutable infrastructure approach when certain modifications mandate the creation of new resources. Understanding this distinction and the implications for your application design can lead to better infrastructure management, enhanced stability, and improved deployment practices.

With continued advancements in cloud technology, knowing how tools l