Open bigbenbeer opened 4 months ago
Hey @bigbenbeer, thank you for reaching out. Amplify CLI currently does not support modifying the deployment bucket created on a amplify init
. Marking this as feature-request for further evaluation.
Is there any workaround for now besides disabling the security rules inside Control Tower? The issue is currently blocking us from using Amplify at all. We are unable to start a new project.
@bigbenbeer curious if Amplify Gen 2 maybe ideal for your use case here as it utilizes CDK. Refer to https://docs.amplify.aws/gen2/ for additional information. As CDK bootstrap allows customizing the asset bucket: https://docs.aws.amazon.com/cdk/v2/guide/bootstrapping.html#bootstrapping-customizing
My app is built on Flutter which Gen 2 does not seem to support yet. Is there an ETA on when Gen 2 will become available for Flutter?
How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
20.11.1
Amplify CLI Version
12.10.1
What operating system are you using?
Ubuntu & Windows
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No manual changes made.
Describe the bug
When using
amplify init
to create a new project, the process fails because ofControlTower::Guard::Hook
failure. This failure is caused by Control Tower enforcing pre-provisioning rules on the creation of S3 buckets. The result is that Cloudformation is unable to create the S3 deployment bucket needed, which results in the entire Stack breaking.As a result, the
amplify init
process fails before it creates a local backend folder. Since it never creates a local back-end folder, I am unable to manually make changes to the backend configuration as recommended in #8894.Below is the Hook Status Message that causes the failure:
Expected behavior
Generate the configuration for
amplify init
locally to allow for customization of the settings. Alternatively, provide a mechanism by which I can override the default S3 configuration to deal with the error. For reasons outside of my control, I am unable to change the ControlTower settings.Reproduction steps
amplify init
Project Identifier
Cannot run
amplify diagnose
because there was no backend created.Log output
Additional information
No response
Before submitting, please confirm: