AWS iot-mi documentation change
Summary
Capitalized 'Managed Integrations' and clarified API authentication requirements.
Security assessment
Formatting changes don't alter security content. SigV4 authentication requirements were already documented; no new security features or vulnerabilities addressed.
Diff
diff --git a/iot-mi/latest/devguide/adding-permissions-to-iam-role.md b/iot-mi/latest/devguide/adding-permissions-to-iam-role.md index 96d56492a..ba3deb035 100644 --- a//iot-mi/latest/devguide/adding-permissions-to-iam-role.md +++ b//iot-mi/latest/devguide/adding-permissions-to-iam-role.md @@ -9 +9 @@ -All managed integrations APIs require AWS sigV4 authentication to invoke. SigV4 is signing protocol to authenticate AWS API requests using your AWS account credentials. The IAM role you use to invoke the managed integrations APIs must have the following permissions to be able to successfully invoke the APIs: +All Managed Integrations APIs require AWS sigV4 authentication to invoke. SigV4 is signing protocol to authenticate AWS API requests using your AWS account credentials. The IAM role you use to invoke the Managed Integrations APIs must have the following permissions to be able to successfully invoke the APIs: