From 01bf11ecc33c110d5ab03a27b82c614bed955fe4 Mon Sep 17 00:00:00 2001 From: Tim Schmelter Date: Fri, 8 Dec 2023 15:08:20 -0800 Subject: [PATCH] docs(graphql-api): callout additional step when adding permission to lambda Replaces the stale PR #5855 from @sundersc --- .../graphqlapi/customize-authorization-rules/index.mdx | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/src/pages/[platform]/build-a-backend/graphqlapi/customize-authorization-rules/index.mdx b/src/pages/[platform]/build-a-backend/graphqlapi/customize-authorization-rules/index.mdx index 298b6e22784..510c0677f2f 100644 --- a/src/pages/[platform]/build-a-backend/graphqlapi/customize-authorization-rules/index.mdx +++ b/src/pages/[platform]/build-a-backend/graphqlapi/customize-authorization-rules/index.mdx @@ -754,6 +754,12 @@ If you grant a Lambda function in your Amplify project access to the GraphQL API Therefore, these functions have special access privileges that are scoped based on their IAM policy instead of any particular `@auth` rule. + + +Once you grant a function access to the GraphQL API, it is required to redeploy the API to apply the permissions. To do so, run the command `amplify api gql-compile --force` before deployment via `amplify push`. + + +