AWS cloud-map medium security documentation change
Summary
Added support for service-linked roles, AWS RAM namespace sharing documentation, and new service creation account filter
Security assessment
1. Enabling service-linked roles improves least-privilege access control. 2. AWS RAM integration documentation adds secure resource sharing guidance. 3. ServiceCreatedByAccount filter enables better audit capabilities for service ownership.
Diff
diff --git a/cloud-map/latest/dg/security_iam_service-with-iam.md b/cloud-map/latest/dg/security_iam_service-with-iam.md index 7349c1bb6..fda8e2aa0 100644 --- a//cloud-map/latest/dg/security_iam_service-with-iam.md +++ b//cloud-map/latest/dg/security_iam_service-with-iam.md @@ -23 +23 @@ Service roles | No -Service-linked roles | No +Service-linked roles | Yes @@ -46,0 +47,4 @@ To enable cross-account access, you can specify an entire account or IAM entitie +###### Note + +You can use AWS Resource Access Manager (AWS RAM) to securely share a AWS Cloud Map namespace. A resource-based policy is applied to your namespace by the AWS RAM service. For more information, see [Cross-account AWS Cloud Map namespace sharing](./sharing-namespaces.html). + @@ -128,0 +133,5 @@ A filter that lets you get objects by specifying the name of the related service +**`servicediscovery:ServiceCreatedByAccount`** + + +A filter that lets you get objects by specifying the ID of the AWS account that created the service. + @@ -179 +188 @@ Changing the permissions for a service role might break AWS Cloud Map functional -**Supports service-linked roles:** No +**Supports service-linked roles:** Yes