Miguel Abreu
I'm still seeing this working with mlflow
we are stuck too :-(
I though there was some issue with the existing stack, I went and created a new one and the same issue happened
Error log ``` Auth/AuthRoleAttachment us-east-1:09cbad3f-99be-4caf-ab51-584475ea29d2 already exists in stack arn:aws:cloudformation:us-east-1:558378773035:stack/PerformanceDash-dev-Auth/54f4df40-310e-11ec-8546-1264d5675413 ``` Full error log ``` 11:07:43 AM | CREATE_FAILED | AWS::Cognito::IdentityPoolRoleAttachment | AuthRoleAttachment0 C8CE9CC us-east-1:09cbad3f-99be-4caf-ab51-584475ea29d2 already exists in stack arn:aws:cloudformation:us-ea...
cdk code ```typescript /** * CloudFormation parameters */ const adminEmail = new CfnParameter(this, "adminEmail", { type: "String", description: "Email address for the admin user", minLength: 5, }); const pool =...
the code above works fine for default authenticated and unauthenticated roles, but when I introduce the roleMapping the stack starts failing
In my case, we have multiple roles at the application levels (unauthenticated, public, editor, admin). I would like to map a role for each one that only have access to...
I think that all this role generation should be handled by the developer and not hidden inside the framework but anyway if we go that route this needs to be...
I tried to split the stack in AUTH vs AUTHZ trying to create the roles and the mapping later but there are other failures there too. The method to initialized...