docs(graphql-api): callout additional step when adding permission to …

…lambda Replaces the stale PR #5855 from @sundersc
aws-amplify · Dec 8, 2023 · 01bf11e · 01bf11e
1 parent 355710e
commit 01bf11e
Showing 1 changed file with 6 additions and 0 deletions.
diff --git a/...s/[platform]/build-a-backend/graphqlapi/customize-authorization-rules/index.mdx b/...s/[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.
 
+<Callout>
+
+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`.
+
+</Callout>
+
 </Block>
 
 <Block name="AWS CDK">