AWS vpc-lattice documentation change
Summary
Fixed typo from 'course-grained' to 'coarse-grained' in authorization policy description
Security assessment
The change is a minor typo correction without any security implications or modifications to security guidance
Diff
diff --git a/vpc-lattice/latest/ug/service-network-access.md b/vpc-lattice/latest/ug/service-network-access.md index 79b7a9f26..f9f85ddc6 100644 --- a//vpc-lattice/latest/ug/service-network-access.md +++ b//vpc-lattice/latest/ug/service-network-access.md @@ -9 +9 @@ Access settings enable you to configure and manage client access to a service ne -You can apply auth policies at the service network level, the service level, or both. Typically, auth policies are applied by the network owners or cloud administrators. They can implement course-grained authorization, for example, allowing authenticated calls from within the organization, or allowing anonymous GET requests that match a certain condition. At the service level, service owners can apply fine-grained controls, which can be more restrictive. For more information, see [Control access to VPC Lattice services using auth policies](./auth-policies.html). +You can apply auth policies at the service network level, the service level, or both. Typically, auth policies are applied by the network owners or cloud administrators. They can implement coarse-grained authorization, for example, allowing authenticated calls from within the organization, or allowing anonymous GET requests that match a certain condition. At the service level, service owners can apply fine-grained controls, which can be more restrictive. For more information, see [Control access to VPC Lattice services using auth policies](./auth-policies.html).