Kethan sai

Closing the issue as stale. Please feel free in reopening the issue and tagging us or create a new issue linking this issue. We would be happy in diving deeper.

Closing this in favor of https://github.com/aws-amplify/docs/issues/3971. Please feel free in adding additional information on your use case to the issue.

closing the issue as this page has been deprecated.

Hey @wvidana @jtweeks @renschler , following is the functions `custom-policies.json` example to grant access to SSM. ``` [ { "Action": ["ssm:GetParameters"], "Resource": [ "arn:aws:ssm:us-east-1:*:parameter/amplify/amplifydiscordbot/${env}/*" ] } ] ``` Ref: https://github.com/aws-amplify/discord-bot/blob/10549c302a9588c911743180e21ed50f2c025fea/amplify/backend/function/discordcommands/custom-policies.json

Closing the issue as the PR has been merged. https://github.com/aws-amplify/docs/pull/5113

@adamtester was the unauthenticated access enabled by running 1. `amplify update auth` 2. select `Walkthrough all the auth configurations` 3. On `Allow unauthenticated logins` select `Yes` 4. then run `amplify...

@adamtester interesting, could you try running `amplify push --force`? the walkthrough is expected to update the `cli-inputs.json` file present at the `amplify/auth/`

Closing the issue due to inactivity. Do reach out to us if you require any assistance.

@rexwreyes thank you for reaching out. This is currently an unsupported workflow, as Amplify CLI does not maintain the lifecycle of an imported auth resource. Did notice the [documentation](https://docs.amplify.aws/react/build-a-backend/auth/admin-actions/#pageMain) provides...

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