AWS iot-mi documentation change
Summary
Updated terminology from 'managed integrations' to 'Managed Integrations' throughout the document for consistent capitalization
Security assessment
The changes are purely cosmetic capitalization updates ('managed integrations' → 'Managed Integrations'). No security vulnerabilities, policies, permissions, or configurations were modified. The documentation still covers the same IAM policy concepts without substantive security content changes.
Diff
diff --git a/iot-mi/latest/devguide/security_iam_id-based-policy-examples.md b/iot-mi/latest/devguide/security_iam_id-based-policy-examples.md index a9f803119..0a0e6ab85 100644 --- a//iot-mi/latest/devguide/security_iam_id-based-policy-examples.md +++ b//iot-mi/latest/devguide/security_iam_id-based-policy-examples.md @@ -9 +9 @@ Policy best practicesUsing the consoleAllow users to view their own permissions -# Identity-based policy examples for managed integrations +# Identity-based policy examples for Managed Integrations @@ -11 +11 @@ Policy best practicesUsing the consoleAllow users to view their own permissions -By default, users and roles don't have permission to create or modify managed integrations resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies. +By default, users and roles don't have permission to create or modify Managed Integrations resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies. @@ -15 +15 @@ To learn how to create an IAM identity-based policy by using these example JSON -For details about actions and resource types defined by managed integrations, including the format of the ARNs for each of the resource types, see [Actions, Resources, and Condition Keys for Managed integrations ](https://docs.aws.amazon.com/IAM/latest/UserGuide/list_your_service.html) in the _Service Authorization Reference_. +For details about actions and resource types defined by Managed Integrations, including the format of the ARNs for each of the resource types, see [Actions, Resources, and Condition Keys for Managed Integrations ](https://docs.aws.amazon.com/IAM/latest/UserGuide/list_your_service.html) in the _Service Authorization Reference_. @@ -21 +21 @@ For details about actions and resource types defined by managed integrations, in - * Using the managed integrations console + * Using the Managed Integrations console @@ -30 +30 @@ For details about actions and resource types defined by managed integrations, in -Identity-based policies determine whether someone can create, access, or delete managed integrations resources in your account. These actions can incur costs for your AWS account. When you create or edit identity-based policies, follow these guidelines and recommendations: +Identity-based policies determine whether someone can create, access, or delete Managed Integrations resources in your account. These actions can incur costs for your AWS account. When you create or edit identity-based policies, follow these guidelines and recommendations: @@ -47 +47 @@ For more information about best practices in IAM, see [Security best practices i -## Using the managed integrations console +## Using the Managed Integrations console @@ -49 +49 @@ For more information about best practices in IAM, see [Security best practices i -To access the Managed integrations console, you must have a minimum set of permissions. These permissions must allow you to list and view details about the managed integrations resources in your AWS account. If you create an identity-based policy that is more restrictive than the minimum required permissions, the console won't function as intended for entities (users or roles) with that policy. +To access the Managed Integrations console, you must have a minimum set of permissions. These permissions must allow you to list and view details about the Managed Integrations resources in your AWS account. If you create an identity-based policy that is more restrictive than the minimum required permissions, the console won't function as intended for entities (users or roles) with that policy. @@ -53 +53 @@ You don't need to allow minimum console permissions for users that are making ca -To ensure that users and roles can still use the managed integrations console, also attach the managed integrations ``ConsoleAccess`` or ``ReadOnly`` AWS managed policy to the entities. For more information, see [Adding permissions to a user](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_users_change-permissions.html#users_change_permissions-add-console) in the _IAM User Guide_. +To ensure that users and roles can still use the Managed Integrations console, also attach the Managed Integrations ``ConsoleAccess`` or ``ReadOnly`` AWS managed policy to the entities. For more information, see [Adding permissions to a user](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_users_change-permissions.html#users_change_permissions-add-console) in the _IAM User Guide_. @@ -99 +99 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -How managed integrations works with IAM +How Managed Integrations works with IAM