Kethan sai

thank you for the confirmation on the gitignore. On a quick check with Amplify team, they suggest verifying your version control system as while the file maybe gitignored for any...

hey folks, wanted to provide an update. if the repository currently does not contain a `amplify-meta.json`, could you try adding `AMPLIFY_BACKEND_PULL_ONLY` as true as the environment variables on the frontend...

Amplify CLI version 12.13.1 has been released providing this fix. To upgrade amplify CLI run `amplify upgrade` locally and set to latest on Amplify console build settings. Could you add...

thanks for raising this! I'm going to transfer this over to our CLI repository as this appears to be Gen 1 CLI issue.

Hey @GenGraphic, thank you for reaching out. It appears the `eu-central-1_K3YXJVKQN_Full-access` role is trying to perform a `GetGroup` on a Cognito userpool resource. To mitigate the issue, you should be...

@GenGraphic since the new resource name would contain a random hash value, adding the inline policy may not be idea. but you could try adding the `cognito-idp:GetGroup` action similar to...

Hey, thanks for raising this! I'm going to transfer this over to our API repository for better assistance 🙂

Hey @dhruvbansal2, thank you for reaching out. Tested the following API override in my amplify application. added the following code in my application ```ts resources.opensearch.OpenSearchStreamingLambdaFunction.functionName = "tstname"; var lambdaRole =...

Hey @dhruvbansal2, I did observe this behaviour in my application. Marking this as bug for further investigation.

Hey @fistofzen, this appears to be similar to https://github.com/aws-amplify/amplify-cli/issues/7582, currently being tracked as bug. The comment provides a workaround in using the `custom-policies.json` to add the permissions: https://github.com/aws-amplify/amplify-cli/issues/7582#issuecomment-1062437331