Amplify CLI fails with Error: Cannot add S3Triggera54de6aa due to a cyclic dependency

Describe the bug I am following the aws amplify photo albums tutorial but when building a new environment the S3 trigger fails with ‘access denied’ when calling S3.getObject().

Is there a separate step required to set permission for the S3 Trigger on the S3 bucket? Perhaps I missed it.

In any event then I tried to run ‘amplify function update’ to give the function access to the S3 bucket and I then get the following error:

Error: Cannot add S3Triggera54de6aa due to a cyclic dependency
    at checkForCyclicDependencies (/usr/local/lib/node_modules/@aws-amplify/cli/lib/extensions/amplify-helpers/update-amplify-meta.js:188:15)
    at AmplifyToolkit.updateamplifyMetaAfterResourceUpdate [as _updateamplifyMetaAfterResourceUpdate] (/usr/local/lib/node_modules/@aws-amplify/cli/lib/extensions/amplify-helpers/update-amplify-meta.js:114:9)
    at updateFunctionResource (/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/amplify-category-function/lib/provider-utils/awscloudformation/index.js:144:29)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at async Object.executeAmplifyCommand (/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/amplify-category-function/lib/index.js:193:5)
    at async executePluginModuleCommand (/usr/local/lib/node_modules/@aws-amplify/cli/lib/execution-manager.js:153:5)
    at async Object.executeCommand (/usr/local/lib/node_modules/@aws-amplify/cli/lib/execution-manager.js:35:9)
    at async Object.run (/usr/local/lib/node_modules/@aws-amplify/cli/lib/index.js:82:9)

Amplify CLI Version 4.29.5

To Reproduce N/A

Expected behavior I would expect the function to work

Screenshots N/A

Desktop (please complete the following information):

• OS: macOS
• Node Version. v12.18.1

Additional context N/A

[walteh]

I just ran into this problem as well, so here is how I ran into it:

1. used amplify add function to create new function “S3Trigger”
2. while creating “S3Trigger” I set gave it full create, read, update, delete access on my amplify configured S3 Storage bucket “MyBucket”
3. used amplify update storage and attempted to make “S3Trigger” the trigger
4. Amplify CLI fails with the message “Cannot add S3Trigger due to a cyclic dependency”

[duncangroenewald]

The issue appears to be that after creating the S3Trigger I added permission to the trigger to access API by using the ‘amplify function update’.

This created a policy with the same name as the S3Trigger’s bucket access policy which clobbered the bucket access policy.

Seems like a flaw in the amplify-cli logic that allows this to happen. Eventually I had to manually rename one of the policies as a workaround but you have to watch this each time you run the amplify-cli or it might get replaced if you subsequently run ‘amplify function update’ or ‘amplify storage update’