AWS iot-mi documentation change
Summary
Updated service name references from 'AWS IoT Managed Integrations' to 'managed integrations for AWS IoT Device Management' or 'managed integrations' throughout the document for consistency and branding alignment
Security assessment
The changes are purely branding/terminology updates without modifying security policies, permissions, or procedures. The service-linked role name (AWSServiceRoleForIoTManagedIntegrations) and its permissions (logs:CreateLogGroup, cloudwatch:PutMetricData, etc.) remain unchanged. No new security features or vulnerabilities are addressed.
Diff
diff --git a/iot-mi/latest/devguide/using-service-linked-roles.md b/iot-mi/latest/devguide/using-service-linked-roles.md index d22802815..8aeefc3bd 100644 --- a//iot-mi/latest/devguide/using-service-linked-roles.md +++ b//iot-mi/latest/devguide/using-service-linked-roles.md @@ -5 +5 @@ -Service-linked role permissions for AWS IoT Managed IntegrationsCreating a service-linked role for AWS IoT Managed IntegrationsEditing a service-linked role for AWS IoT Managed IntegrationsDeleting a service-linked role for AWS IoT Managed IntegrationsSupported Regions for AWS IoT Managed Integrations service-linked roles +Service-linked role permissions for managed integrationsCreating a service-linked role for managed integrationsEditing a service-linked role for managed integrationsDeleting a service-linked role for managed integrationsSupported Regions for managed integrations service-linked roles @@ -9 +9 @@ Managed integrations for AWS IoT Device Management is in preview release and is -# Using service-linked roles for AWS IoT Managed Integrations +# Using service-linked roles for managed integrations @@ -11 +11 @@ Managed integrations for AWS IoT Device Management is in preview release and is -AWS IoT Managed Integrations uses AWS Identity and Access Management (IAM) [service-linked roles](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_terms-and-concepts.html#iam-term-service-linked-role). A service-linked role is a unique type of IAM role that is linked directly to AWS IoT Managed Integrations. Service-linked roles are predefined by AWS IoT Managed Integrations and include all the permissions that the service requires to call other AWS services on your behalf. +Managed integrations for AWS IoT Device Management uses AWS Identity and Access Management (IAM) [service-linked roles](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_terms-and-concepts.html#iam-term-service-linked-role). A service-linked role is a unique type of IAM role that is linked directly to managed integrations. Service-linked roles are predefined by managed integrations and include all the permissions that the service requires to call other AWS services on your behalf. @@ -13 +13 @@ AWS IoT Managed Integrations uses AWS Identity and Access Management (IAM) [serv -A service-linked role makes setting up AWS IoT Managed Integrations easier because you don’t have to manually add the necessary permissions. AWS IoT Managed Integrations defines the permissions of its service-linked roles, and unless defined otherwise, only AWS IoT Managed Integrations can assume its roles. The defined permissions include the trust policy and the permissions policy, and that permissions policy cannot be attached to any other IAM entity. +A service-linked role makes setting up managed integrations easier because you don’t have to manually add the necessary permissions. Managed integrations for AWS IoT Device Management defines the permissions of its service-linked roles, and unless defined otherwise, only managed integrations can assume its roles. The defined permissions include the trust policy and the permissions policy, and that permissions policy cannot be attached to any other IAM entity. @@ -15 +15 @@ A service-linked role makes setting up AWS IoT Managed Integrations easier becau -You can delete a service-linked role only after first deleting their related resources. This protects your AWS IoT Managed Integrations resources because you can't inadvertently remove permission to access the resources. +You can delete a service-linked role only after first deleting their related resources. This protects your managed integrations resources because you can't inadvertently remove permission to access the resources. @@ -19 +19 @@ For information about other services that support service-linked roles, see [AWS -## Service-linked role permissions for AWS IoT Managed Integrations +## Service-linked role permissions for managed integrations @@ -21 +21 @@ For information about other services that support service-linked roles, see [AWS -AWS IoT Managed Integrations uses the service-linked role named **AWSServiceRoleForIoTManagedIntegrations** – Provides AWS IoT Managed Integrations permission to publish logs and metrics on your behalf. +Managed integrations for AWS IoT Device Management uses the service-linked role named **AWSServiceRoleForIoTManagedIntegrations** – Provides managed integrations for AWS IoT Device Management permission to publish logs and metrics on your behalf. @@ -30 +30 @@ The AWSServiceRoleForIoTManagedIntegrations service-linked role trusts the follo -The role permissions policy named AWSIoTManagedIntegrationsServiceRolePolicy allows AWS IoT Managed Integrations to complete the following actions on the specified resources: +The role permissions policy named AWSIoTManagedIntegrationsServiceRolePolicy allows managed integrations to complete the following actions on the specified resources: @@ -32 +32 @@ The role permissions policy named AWSIoTManagedIntegrationsServiceRolePolicy all - * Action: `logs:CreateLogGroup, logs:DescribeLogGroups, logs:CreateLogStream, logs:PutLogEvents, logs:DescribeLogStreams, cloudwatch:PutMetricData` `on all of your AWS IoT Managed Integrations resources.` + * Action: `logs:CreateLogGroup, logs:DescribeLogGroups, logs:CreateLogStream, logs:PutLogEvents, logs:DescribeLogStreams, cloudwatch:PutMetricData` `on all of your managed integrations resources.` @@ -85 +85 @@ You must configure permissions to allow your users, groups, or roles to create, -## Creating a service-linked role for AWS IoT Managed Integrations +## Creating a service-linked role for managed integrations @@ -87 +87 @@ You must configure permissions to allow your users, groups, or roles to create, -You don't need to manually create a service-linked role. When you cause an event type such as calling the `PutRuntimeLogConfiguration`, `CreateEventLogConfiguration`, or `RegisterCustomEndpoint` API commands in the AWS Management Console, the AWS CLI, or the AWS API, AWS IoT Managed Integrations creates the service-linked role for you. For more information on `PutRuntimeLogConfiguration`, `CreateEventLogConfiguration`, or `RegisterCustomEndpoint`, see [`PutRuntimeLogConfiguration`](https://amazonaws.com/iot-mi/latest/APIReference/API_PutRuntimeLogConfiguration.html), [`CreateEventLogConfiguration`](https://amazonaws.com/iot-mi/latest/APIReference/API_CreateEventLogConfiguration.html), or [`RegisterCustomEndpoint`](https://amazonaws.com/iot-mi/latest/APIReference/API_RegisterCustomEndpoint.html). +You don't need to manually create a service-linked role. When you cause an event type such as calling the `PutRuntimeLogConfiguration`, `CreateEventLogConfiguration`, or `RegisterCustomEndpoint` API commands in the AWS Management Console, the AWS CLI, or the AWS API, managed integrations creates the service-linked role for you. For more information on `PutRuntimeLogConfiguration`, `CreateEventLogConfiguration`, or `RegisterCustomEndpoint`, see [`PutRuntimeLogConfiguration`](https://amazonaws.com/iot-mi/latest/APIReference/API_PutRuntimeLogConfiguration.html), [`CreateEventLogConfiguration`](https://amazonaws.com/iot-mi/latest/APIReference/API_CreateEventLogConfiguration.html), or [`RegisterCustomEndpoint`](https://amazonaws.com/iot-mi/latest/APIReference/API_RegisterCustomEndpoint.html). @@ -89 +89 @@ You don't need to manually create a service-linked role. When you cause an event -If you delete this service-linked role, and then need to create it again, you can use the same process to recreate the role in your account. When you cause an event type such as calling the `PutRuntimeLogConfiguration`, `CreateEventLogConfiguration`, or `RegisterCustomEndpoint` API commands, AWS IoT Managed Integrations creates the service-linked role for you again. Alternatively, you can contact AWS Customer Support via the AWS Support Center Console. For more information on AWS Support Plans, see [Compare AWS Support Plans](https://aws.amazon.com/premiumsupport/plans/). +If you delete this service-linked role, and then need to create it again, you can use the same process to recreate the role in your account. When you cause an event type such as calling the `PutRuntimeLogConfiguration`, `CreateEventLogConfiguration`, or `RegisterCustomEndpoint` API commands, managed integrations creates the service-linked role for you again. Alternatively, you can contact AWS Customer Support via the AWS Support Center Console. For more information on AWS Support Plans, see [Compare AWS Support Plans](https://aws.amazon.com/premiumsupport/plans/). @@ -93 +93 @@ You can also use the IAM console to create a service-linked role with the **IoT -## Editing a service-linked role for AWS IoT Managed Integrations +## Editing a service-linked role for managed integrations @@ -95 +95 @@ You can also use the IAM console to create a service-linked role with the **IoT -AWS IoT Managed Integrations does not allow you to edit the AWSServiceRoleForIoTManagedIntegrations service-linked role. After you create a service-linked role, you cannot change the name of the role because various entities might reference the role. However, you can edit the description of the role using IAM. For more information, see [Editing a service-linked role](https://docs.aws.amazon.com/IAM/latest/UserGuide/using-service-linked-roles.html#edit-service-linked-role) in the _IAM User Guide_. +managed integrations does not allow you to edit the AWSServiceRoleForIoTManagedIntegrations service-linked role. After you create a service-linked role, you cannot change the name of the role because various entities might reference the role. However, you can edit the description of the role using IAM. For more information, see [Editing a service-linked role](https://docs.aws.amazon.com/IAM/latest/UserGuide/using-service-linked-roles.html#edit-service-linked-role) in the _IAM User Guide_. @@ -97 +97 @@ AWS IoT Managed Integrations does not allow you to edit the AWSServiceRoleForIoT -## Deleting a service-linked role for AWS IoT Managed Integrations +## Deleting a service-linked role for managed integrations @@ -103 +103 @@ If you no longer need to use a feature or service that requires a service-linked -If the AWS IoT Managed Integrations service is using the role when you try to delete the resources, then the deletion might fail. If that happens, wait for a few minutes and try the operation again. +If managed integrations is using the role when you try to delete the resources, then the deletion might fail. If that happens, wait for a few minutes and try the operation again. @@ -109 +109 @@ Use the IAM console, the AWS CLI, or the AWS API to delete the AWSServiceRoleFor -## Supported Regions for AWS IoT Managed Integrations service-linked roles +## Supported Regions for managed integrations service-linked roles @@ -111 +111 @@ Use the IAM console, the AWS CLI, or the AWS API to delete the AWSServiceRoleFor -AWS IoT Managed Integrations supports using service-linked roles in all of the Regions where the service is available. For more information, see [AWS Regions and endpoints](https://docs.aws.amazon.com/general/latest/gr/iot-managedintegrations.html). +Managed integrations for AWS IoT Device Management supports using service-linked roles in all of the Regions where the service is available. For more information, see [AWS Regions and endpoints](https://docs.aws.amazon.com/general/latest/gr/iot-managedintegrations.html).