AWS iot-mi documentation change
Summary
Updated terminology from 'managed integrations' to 'Managed Integrations' in prerequisites and testing steps
Security assessment
Purely editorial capitalization changes. Testing procedures and security requirements remain unchanged with no impact on security configurations.
Diff
diff --git a/iot-mi/latest/devguide/vpc-endpoints-testing.md b/iot-mi/latest/devguide/vpc-endpoints-testing.md index 03efc6f64..68b87924f 100644 --- a//iot-mi/latest/devguide/vpc-endpoints-testing.md +++ b//iot-mi/latest/devguide/vpc-endpoints-testing.md @@ -11 +11 @@ PrerequisitesConnection Testing -After you create your VPC endpoint, you can test the connection by making API calls to AWS IoT Managed integrations from an EC2 instance in your VPC. +After you create your VPC endpoint, you can test the connection by making API calls to AWS IoT Managed Integrations from an EC2 instance in your VPC. @@ -17 +17 @@ After you create your VPC endpoint, you can test the connection by making API ca - * Appropriate IAM permissions for AWS IoT Managed integrations operations + * Appropriate IAM permissions for AWS IoT Managed Integrations operations @@ -36 +36 @@ After you create your VPC endpoint, you can test the connection by making API ca - 4. Make an AWS IoT Managed integrations API call: + 4. Make an AWS IoT Managed Integrations API call: