AWS solutions documentation change
Summary
Updated apostrophe characters to curly quotes and minor punctuation fixes in policy management documentation
Security assessment
Changes are typographical improvements to documentation describing existing authorization mechanisms. No new security features added or vulnerabilities addressed.
Diff
diff --git a/solutions/latest/generative-ai-application-builder-on-aws/deployment-dashboard-1.md index ceb94ee30..ac2a55bcd 100644 --- a/solutions/latest/generative-ai-application-builder-on-aws/deployment-dashboard-1.md +++ b/solutions/latest/generative-ai-application-builder-on-aws/deployment-dashboard-1.md @@ -13 +13 @@ Beneath the surface, Lambda custom authorizers for API Gateway are used for all -On every new use case deployment, the admin policy is updated to store a new statement allowing the **execute-api:Invoke** action on that use case's API. When use cases are deleted, the corresponding statement is removed from the policy. +On every new use case deployment, the admin policy is updated to store a new statement allowing the **execute-api:Invoke** action on that use case’s API. When use cases are deleted, the corresponding statement is removed from the policy. @@ -15 +15 @@ On every new use case deployment, the admin policy is updated to store a new sta -For the groups created for an individual use case, only a single statement is present in the policy, allowing the **execute-api:Invoke** action on only that use case's API. +For the groups created for an individual use case, only a single statement is present in the policy, allowing the **execute-api:Invoke** action on only that use case’s API. @@ -17 +17 @@ For the groups created for an individual use case, only a single statement is pr -Due to this structure, any user belonging to a use case's group can access that use case's API. A single user can also be manually added to multiple groups to allow that user to use multiple use cases. +Due to this structure, any user belonging to a use case’s group can access that use case’s API. A single user can also be manually added to multiple groups to allow that user to use multiple use cases. @@ -23 +23 @@ You can also manually edit the policies for a given group in the policy table if -In the case where a use case stack is deployed standalone (without the use of the Deployment dashboard), an [Amazon Cognito user pool](https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-identity-pools.html) is created for that deployment containing a single user with access to that use case's API. This user pool belongs only to this use case and is not shared across other standalone deployments. +In the case where a use case stack is deployed standalone (without the use of the Deployment dashboard), an [Amazon Cognito user pool](https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-identity-pools.html) is created for that deployment containing a single user with access to that use case’s API. This user pool belongs only to this use case and is not shared across other standalone deployments.