AWS resource-explorer documentation change
Summary
Updated service branding (S3 Glacier to Amazon Glacier) and added details about automatic resource discovery permissions
Security assessment
While the change mentions IAM permissions, this is in the context of feature functionality rather than introducing new security documentation. The service name change is a branding update without security implications. The permission references are reiterations of existing policy requirements rather than new security guidance.
Diff
diff --git a/resource-explorer/latest/userguide/supported-resource-types.md b/resource-explorer/latest/userguide/supported-resource-types.md index 851094b3b..c2e540ff4 100644 --- a//resource-explorer/latest/userguide/supported-resource-types.md +++ b//resource-explorer/latest/userguide/supported-resource-types.md @@ -6,0 +7,2 @@ Supported services and resource typesProgrammatically accessing the list of supp +AWS Resource Explorer now provides immediate access to resource search and discovery capabilities in a Region. With this launch, you no longer need to activate Resource Explorer to discover your resources. [Learn more](https://docs.aws.amazon.com/resource-explorer/latest/userguide/manage-immediate-resource-discovery-experience.html) + @@ -9 +11 @@ Supported services and resource typesProgrammatically accessing the list of supp -Resource Explorer supports resource types across numerous AWS services. +Resource Explorer supports resource types across numerous AWS services. Resource discovery happens automatically when you access Resource Explorer with appropriate permissions. If you have, at minimum, the permissions in the `[AWSResourceExplorerReadOnlyAccess](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AWSResourceExplorerReadOnlyAccess.html)` managed policy, you can immediately search all tagged resources and supported untagged resources created after the [immediate resource discovery](https://docs.aws.amazon.com/resource-explorer/latest/userguide/manage-immediate-resource-discovery-experience.html) release. For complete resource discovery with automatic updates, you'll also need the `iam:CreateServiceLinkedRole` permission (included in the [AWSResourceExplorerFullAccess](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AWSResourceExplorerFullAccess.html) managed policy). After the service-linked role is created in your account by any user, subsequent users need only the permissions in the `[AWSResourceExplorerReadOnlyAccess](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AWSResourceExplorerReadOnlyAccess.html)` managed policy to get complete results. @@ -350 +352 @@ You can still use these resource types in their own services, but they are no lo - * Amazon S3 Glacier + * Amazon Glacier @@ -2141 +2143 @@ You can still use these resource types in their own services, but they are no lo -### Amazon S3 Glacier +### Amazon Glacier