AWS claude-platform documentation change
Summary
Improved clarity in CloudTrail logging configuration, usage views, and cost allocation tag documentation
Security assessment
Changes are editorial improvements without security implications. CloudTrail logging clarification doesn't address vulnerabilities but maintains existing monitoring practices. No evidence of security incident remediation.
Diff
diff --git a/claude-platform/latest/userguide/monitoring.md b/claude-platform/latest/userguide/monitoring.md index 30868050b..edc7d40ec 100644 --- a//claude-platform/latest/userguide/monitoring.md +++ b//claude-platform/latest/userguide/monitoring.md @@ -11 +11 @@ Request IDsUsage metrics and dashboardsCost allocation and monitoring -AWS CloudTrail can capture all requests to Claude Platform on AWS. Workspace and vault operations are logged as Management events by default. Inference, batch, file, skill, model, user profile, and Claude Managed Agents operations (other than vaults) are classified as Data events and require explicit data event logging configuration, which incurs additional CloudTrail charges. See [IAM actions](./iam-actions.html) for the full event type classification and the [AWS CloudTrail documentation](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/) for configuration details. +AWS CloudTrail can capture all requests to Claude Platform on AWS. Workspace and vault operations are logged as Management events by default. All other operations (inference, batch, file, skill, model, user profile, and Claude Managed Agents except vaults) are Data events. Logging them requires explicit configuration and incurs additional CloudTrail charges. See [IAM actions](./iam-actions.html) for the full event type classification and the [AWS CloudTrail documentation](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/) for configuration details. @@ -169 +169 @@ Claude Platform on AWS does not publish per-workspace usage metrics to Amazon Cl - * **Claude Console usage views** — when a principal federates into the Claude Console with `aws-external-anthropic:AssumeConsole` (see [IAM policies](./iam-policies.html)), the usage dashboards show request volume, token counts, and per-model breakdowns for the workspaces the principal has access to. Account-wide usage views require admin console capability. + * **Claude Console usage views** — when a principal federates into the Claude Console with `aws-external-anthropic:AssumeConsole` (see [IAM policies](./iam-policies.html)), the usage dashboards show request volume, token counts, and per-model breakdowns for accessible workspaces. Account-wide usage views require admin console capability. @@ -191 +191 @@ Claude Platform on AWS charges appear on your AWS bill under the **Claude Platfo -Workspace tags flow through to CUR line items for all Claude Platform on AWS usage, so the same tag keys can drive both IAM-based access control and cost allocation without additional configuration. See [Cost allocation tags](https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/cost-alloc-tags.html) in the AWS Billing documentation for setup steps and activation delays. +Workspace tags flow through to CUR line items for all Claude Platform on AWS usage. The same tag keys drive both IAM-based access control and cost allocation. See [Cost allocation tags](https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/cost-alloc-tags.html) in the AWS Billing documentation for setup steps and activation delays.