Breaking AWS CloudFormation permissions changes impacting Amplify CLI?

[dthian]

Amplify CLI Version

12.8.2

Question

Hi, I just received an email from AWS CloudFormation regarding an API behaviour change that could cause disruptions.

Prior to January 31, 2024, CloudFormation actions on nested stacks were allowed if the action was part of a parent stack operation.

However, this is no longer true with the breaking change - If the user attempts to update a stack after adding a nested stack to the template, then the nested stack will also require CreateStack permissions for the operation to succeed. Similarly, if a nested stack is removed, the user will need DeleteStack permissions for the nested stack in order to successfully update the parent stack.

On April 5, 2024, AWS will remove my account from the allow-list, which will make this new behavior take effect. AWS strongly recommends that I modify or attach IAM Policies for the affected APIs by April 5, 2024, to avoid service disruption.

As it is mainly the Amplify CLI that is generating the CloudFormation templates (and therefore permissions) and deploying them, and since these permission behaviour are changing as per the AWS email - is there guidance on how to handle this CloudFormation change?

[EvanCarroll]

This framework is no good. I suggest people avoid it.

https://www.reddit.com/r/node/comments/54rueh/using_let_significantly_slower_vs_var_v8_disables/ https://gist.github.com/Salakar/6d7b84f7adf1f3bc62a754752a6e5d0e

[StevenLangbroek]

@EvanCarroll rather than bashing the project without any justification other than this bug (I followed your link, where you also don't give any other explanation), you could also help figure out what's causing this behavior.

[connor4312]

As this issue (and other issues and PRs) have been open for years without update, I've created a newer rewrite of this tool. It uses the widely-used Benchmark.js, which includes warmup.