Document all iam permission / api action potentially used per resources type

### Name of the resource

Other

### Resource name

all

### Reference Link

_No response_

### Details

I must have missed the issue but ..

The cloudformation resource documentation should include a detailled list of the IAM permissions potentially required per resource.

The recommended way of "_[querying] the CloudTrail logs only after launching and deleting the stack in order to capture actions from both operations_" from your public [AWS Blog Implement the principle of least privilege][] post don't take into account changes from stack updates (ex instances replacement in an ASG, parameters changes on resources ....)

Links
-----

- [AWS Blog Implement the principle of least privilege]
- [AWS::AutoScaling::AutoScalingGroup]

[AWS Blog Implement the principle of least privilege]: https://aws.amazon.com/blogs/security/how-to-implement-the-principle-of-least-privilege-with-cloudformation-stacksets/
[AWS::AutoScaling::AutoScalingGroup]: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-as-group.html

Start by reviewing the CloudFormation resource documentation, the linked AWS::AutoScaling::AutoScalingGroup resource, and the AWS Blog least-privilege guidance. Define the resource types and stack operations that must be covered, including updates, and consider how IAM actions would be documented. Done means each resource type has a detailed, maintainable list of potentially required permissions.

Written by the indexing model from the issue text.