AWS iot-mi documentation change
Summary
Updated terminology from 'managed integrations' to 'Managed Integrations' in section headers and policy descriptions
Security assessment
Capitalization changes only. No modifications to VPC endpoint policy structure, permissions, or security controls. Policy examples remain functionally identical.
Diff
diff --git a/iot-mi/latest/devguide/vpc-endpoints-access-control.md b/iot-mi/latest/devguide/vpc-endpoints-access-control.md index adf710557..484c34439 100644 --- a//iot-mi/latest/devguide/vpc-endpoints-access-control.md +++ b//iot-mi/latest/devguide/vpc-endpoints-access-control.md @@ -15 +15 @@ Endpoint policies must be written in JSON format. For more information, see [ Co -## Example: VPC endpoint policy for AWS IoT Managed integrations actions +## Example: VPC endpoint policy for AWS IoT Managed Integrations actions @@ -17 +17 @@ Endpoint policies must be written in JSON format. For more information, see [ Co -The following is an example of an endpoint policy for AWS IoT Managed integrations. This policy allows users connecting to AWS IoT Managed integrations through the VPC endpoint to access destinations but denies access to credential lockers. +The following is an example of an endpoint policy for AWS IoT Managed Integrations. This policy allows users connecting to AWS IoT Managed Integrations through the VPC endpoint to access destinations but denies access to credential lockers. @@ -51 +51 @@ The following is an example of an endpoint policy for AWS IoT Managed integratio -The following VPC endpoint policy allows access to AWS IoT Managed integrations only for IAM principals that have the specified IAM role in their trust chain. All other IAM principals are denied access. +The following VPC endpoint policy allows access to AWS IoT Managed Integrations only for IAM principals that have the specified IAM role in their trust chain. All other IAM principals are denied access.