AWS eventbridge: Clarify AWS RAM managed permission scope for shared event buses
Summary
Adds an introductory sentence for the managed-permission table, expands what AWSRAMEventBridgeEventBusV2PublishOnly and AWSRAMEventBridgeEventBusV2SubscribeOnly allow (describe the bus, update subscriber filters), and clarifies that ListResourcePolicies does not act on the default policy.
Security assessment
The diff documents exactly what a consumer account can do under each AWS RAM managed permission for a shared event bus, including the added ability to describe the bus and update subscriber filters. This is cross-account authorization guidance that helps administrators reason about shared-bus access scope, but no specific vulnerability or CVE is referenced.
Evidence
+`AWSRAMEventBridgeEventBusV2PublishOnly`| Publish to the bus, and describe the bus
Diff
diff --git a/eventbridge/latest/userguide/eb-custom-bus-sharing.md b/eventbridge/latest/userguide/eb-custom-bus-sharing.md index 66ade6f..4ada2b4 100644 --- a//eventbridge/latest/userguide/eb-custom-bus-sharing.md +++ b//eventbridge/latest/userguide/eb-custom-bus-sharing.md @@ -27,0 +28,2 @@ We recommend AWS RAM over a resource policy that you write yourself. AWS RAM giv +The following table lists what the consumer account can do with each managed permission. + @@ -30,2 +32,2 @@ Managed permission| What the consumer account can do -`AWSRAMEventBridgeEventBusV2PublishOnly`| Publish to the bus -`AWSRAMEventBridgeEventBusV2SubscribeOnly`| Attach subscribers to the bus +`AWSRAMEventBridgeEventBusV2PublishOnly`| Publish to the bus, and describe the bus +`AWSRAMEventBridgeEventBusV2SubscribeOnly`| Attach subscribers to the bus, update their filters, and describe the bus @@ -79 +81 @@ The following `default` policy on the `orders` bus lets account `444455556666` a -Manage the policies with `PutResourcePolicy`, `GetResourcePolicy`, `DeleteResourcePolicy`, and `ListResourcePolicies`. Each takes the bus ARN in `--resource-arn`, and each acts on `default` when you omit `--policy-name`. You cannot write or delete `AWS_RAM`: naming it fails with `AccessDeniedException`. `GetResourcePolicy` fails with `ResourceNotFoundException` when the named policy does not exist, rather than returning an empty document, so treat that as no policy. A bus that you shared only through AWS RAM has no `default` policy, so `get-resource-policy` without `--policy-name` returns that error; pass `--policy-name AWS_RAM` to read the policy AWS RAM wrote. `ListResourcePolicies` returns policy names and revision IDs only, never documents. To make a write or delete conditional, pass the policy's current revision in `--expected-revision-id`; on a mismatch the operation fails with `ConflictException`. A `default` policy document can be up to 20 KB; a larger policy fails with `PolicyLengthExceededException`. This quota is adjustable in Service Quotas. +Manage the policies with `PutResourcePolicy`, `GetResourcePolicy`, `DeleteResourcePolicy`, and `ListResourcePolicies`. Each takes the bus ARN in `--resource-arn`. The first three act on `default` when you omit `--policy-name`. You cannot write or delete `AWS_RAM`: naming it fails with `AccessDeniedException`. `GetResourcePolicy` fails with `ResourceNotFoundException` when the named policy does not exist, rather than returning an empty document, so treat that as no policy. A bus that you shared only through AWS RAM has no `default` policy, so `get-resource-policy` without `--policy-name` returns that error; pass `--policy-name AWS_RAM` to read the policy AWS RAM wrote. `ListResourcePolicies` returns policy names and revision IDs only, never documents. To make a write or delete conditional, pass the policy's current revision in `--expected-revision-id`; on a mismatch the operation fails with `ConflictException`. A `default` policy document can be up to 20 KB; a larger policy fails with `PolicyLengthExceededException`. This quota is adjustable in Service Quotas.