AWS evs documentation change
Summary
Updated placeholder {evws} to 'Amazon EVS' in service-linked role documentation
Security assessment
Change fixes a documentation placeholder but does not address security vulnerabilities or introduce security features. It clarifies the service name for accuracy.
Diff
diff --git a/evs/latest/userguide/security-iam-awsmanpol.md b/evs/latest/userguide/security-iam-awsmanpol.md index dbd16e476..c86b2df95 100644 --- a//evs/latest/userguide/security-iam-awsmanpol.md +++ b//evs/latest/userguide/security-iam-awsmanpol.md @@ -17 +17 @@ You cannot change the permissions defined in AWS managed policies. If AWS update -You can’t attach `AmazonEVSServiceRolePolicy` to your IAM entities. This policy is attached to a service-linked role that allows Amazon EVS to perform actions on your behalf. For more information, see [Using service-linked roles for {evws}](./using-service-linked-roles.html). When you create an environment using an IAM principal that has the `iam:CreateServiceLinkedRole` permission, the `AWSServiceRoleforAmazonEVS` service-linked role is automatically created for you with this policy attached to it. +You can’t attach `AmazonEVSServiceRolePolicy` to your IAM entities. This policy is attached to a service-linked role that allows Amazon EVS to perform actions on your behalf. For more information, see [Using service-linked roles for Amazon EVS](./using-service-linked-roles.html). When you create an environment using an IAM principal that has the `iam:CreateServiceLinkedRole` permission, the `AWSServiceRoleforAmazonEVS` service-linked role is automatically created for you with this policy attached to it.