AWS iot-mi documentation change
Summary
Updated terminology from 'managed integrations' to 'Managed Integrations' for consistency
Security assessment
Changes are capitalization updates only. No modifications to Secrets Manager integration, OAuth security practices, or credential handling. Security implications of client ID/secret storage remain identical.
Diff
diff --git a/iot-mi/latest/devguide/secrets-manager.md b/iot-mi/latest/devguide/secrets-manager.md index eae2cd57c..310df5d55 100644 --- a//iot-mi/latest/devguide/secrets-manager.md +++ b//iot-mi/latest/devguide/secrets-manager.md @@ -15 +15 @@ Secrets Manager encrypts secrets using AWS Key Management Service keys. For more -Managed integrations for AWS IoT Device Management integrates with AWS Secrets Manager so that you can store your data in Secrets Manager and use the secret ID in your configurations. +Managed Integrations for AWS IoT Device Management integrates with AWS Secrets Manager so that you can store your data in Secrets Manager and use the secret ID in your configurations. @@ -23 +23 @@ In OAuth, a client ID and client secret are credentials that identify and authen -Managed integrations for AWS IoT Device Management uses OAuth to communicate with customers that use the C2C workflows. Customers need to provide the client ID and client secret to communicate. Managed integrations customers will store a client ID and client secret in their AWS accounts, and managed integrations reads the client ID and client secret in our customer account. +Managed Integrations for AWS IoT Device Management uses OAuth to communicate with customers that use the C2C workflows. Customers need to provide the client ID and client secret to communicate. Managed Integrations customers will store a client ID and client secret in their AWS accounts, and managed integrations reads the client ID and client secret in our customer account.