Resources created in cloud information can be manipulated independently of cloud information once created.
As some urgent action was needed, I believe that temporarily changing the state of the resource only on the spot (with the assumption that it will be returned later) could occur during the operation.
I wanted to make sure that the target resource was returned to the cloud information template state after making changes to that resource or undo operations.
I can't check the tools, but I think the idea is to compare them with CloudFormation designers using configuration visualization tools.
Another option might be to get a list of stack resources from the API to see the difference.
As a supplement, CloudFormation does not recommend manual changes as described in Best Practices.
After you boot up the stack, use the AWS CloudFormation console, API, or AWS CLI to update the resources in the stack.Do not change the resources in the stack in any other way than AWS CloudFormation.Changes can cause a mismatch between the template in the stack and the current state of the stack resources, and may result in an error updating or deleting the stack.
Some sets of changes are substantial dry-runs, and I personally think that even small changes through templates are less risky considering the possibility of stack update/deletion errors.
With AWS Config, you can use SNS to notify when resources are changed, and you can view the history from the management console, so I think it's close to what you want.You can also describe AWS Config settings in the CloudFormation template.
© 2024 OneMinuteCode. All rights reserved.