From 6828cf2a4e88d9a610b547d9e049169a5ebb6697 Mon Sep 17 00:00:00 2001 From: Josh Du Lac Date: Wed, 18 Sep 2019 18:41:47 -0500 Subject: [PATCH] Fixed typo Fixed typo: "assocate" -> "associate", and added clarifying word "on" --- Auth/2_ServerlessAPI/Optional-APIGateway-IAMAuth.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Auth/2_ServerlessAPI/Optional-APIGateway-IAMAuth.md b/Auth/2_ServerlessAPI/Optional-APIGateway-IAMAuth.md index e8390a45..3b908f1d 100644 --- a/Auth/2_ServerlessAPI/Optional-APIGateway-IAMAuth.md +++ b/Auth/2_ServerlessAPI/Optional-APIGateway-IAMAuth.md @@ -26,7 +26,7 @@ If you're using the latest version of the Chrome, Firefox, or Safari web browser For us to be able to use request signing and IAM-based fine-grained access control, we'll first need to associate an IAM policy that provides permissions to invoke API operations for your API Gateway deployment. For further details, you can review [controlling access to an API with IAM permissions](https://docs.aws.amazon.com/apigateway/latest/developerguide/permissions.html) documentation. #### High-Level Instructions -In the IAM console, assocate the *WildRydesAPI-StandardUserPolicy* with your Cognito Identity Pool's authenticated user role to provide all authenticated users access to invoke operations the */ride* path. +In the IAM console, associate the *WildRydesAPI-StandardUserPolicy* with your Cognito Identity Pool's authenticated user role to provide all authenticated users access to invoke operations on the */ride* path.
Step-by-step instructions (expand for details)