Luka Antolic-Soban

Gen 2

Thanks @MarlonJD I will try this later. My only worry is that if and when the Amplify team fix it, will it cause me issues since they might not move...

I am not an expert with the CDK but I guess I was worrying whether or not the LogicalIDs would be modified from moving to sub-stacks

Just wanted to pop in to say that I also am getting the same error when trying to add in event source for dynamodb streams. Same issue circular dependency between...

@jgo80 do you have a workaround by any chance for now?

Thanks @MattWlodarski I will take a look at this today and give it a try and then update this thread

I had some triggers in the auth resource. If I remove them, it removes the circular dependency. ``` triggers: { customMessage, postConfirmation, preSignUp, defineAuthChallenge, createAuthChallenge, verifyAuthChallengeResponse: verifyAuthChallenge, }, ```

@ggj0418 @MattWlodarski do you either of you have any auth triggers?

```javascript import { defineAuth, secret } from "@aws-amplify/backend"; import { customMessage } from "./custom-message/resource"; import { postConfirmation } from "./post-confirmation/resource"; import { preSignUp } from "./pre-signup/resource"; import { defineAuthChallenge }...

@AnilMaktala here is the min code required for me to reproduce ```javascript /** * @see https://docs.amplify.aws/react/build-a-backend/ to add storage, functions, and more */ const backend = defineBackend({ auth, data, dynamodbStreamPlaces,...