AWS eventbridge: Editorial rewrite of EventBridge custom bus sharing guide
Summary
A copy-editing pass across the 'Sharing a Custom Event Bus' page: sentences are split and rephrased for readability (e.g., AWS RAM managed permissions, accepting share invitations, unsharing behavior, resource policy handling, public-access rejection, and event source authorization). No new permissions, actions, quotas, defaults, or security controls are introduced or changed; the same technical facts (e.g., EventBridge rejects wildcard-principal `default` policies with `PublicPolicyException`, `AWS_RAM` policies cannot be written, both policies are evaluated with `Deny` overriding `Allow`) are restated in different wording.
Security assessment
The changed lines are stylistic rewrites of pre-existing security-relevant prose (resource-policy public-access rejection, cross-account authorization, unshare/revoke semantics). The diff only re-splits sentences and adjusts wording; no vulnerability is fixed, no new control is documented, and no CVE/advisory is referenced, so this is a low-severity editorial change.
Evidence
+EventBridge rejects a `default` policy that would grant public access, with `PublicPolicyException`. It does not attach the policy. This check is always on. A statement grants public access when its principal is a wildcard and no condition limits the callers to specific accounts or principals. A condition on event content, such as `events:source`, does not identify the caller. A condition such as `aws:PrincipalOrgID` does. A policy you write is invisible to AWS RAM, so you own tracking it.
Diff
diff --git a/eventbridge/latest/userguide/eb-custom-bus-sharing.md b/eventbridge/latest/userguide/eb-custom-bus-sharing.md index fcfea9a..7a34193 100644 --- a//eventbridge/latest/userguide/eb-custom-bus-sharing.md +++ b//eventbridge/latest/userguide/eb-custom-bus-sharing.md @@ -11 +11 @@ Prerequisites for sharing a busSharing a busUnsharing a busWorking with a bus th -To let another account publish to your bus, attach subscribers to it, or attach event sources to it, share the bus with AWS Resource Access Manager (AWS RAM). Then choose one of the four managed permissions. For example, share the `orders` bus with account `444455556666` using `AWSRAMEventBridgeEventBusV2SubscribeOnly`, and that account can create subscribers on it. Write a resource policy on the bus instead when you need an explicit `Deny`, a condition key, or a grant that no managed permission expresses. The other account still needs the same actions in its own identity policies, because both sides must allow. +Amazon EventBridge lets you share a Custom Event Bus with other accounts. To let another account publish to your bus, attach subscribers to it, or attach event sources to it, share the bus with AWS Resource Access Manager (AWS RAM). Then choose one of the four managed permissions. For example, share the `orders` bus with account `444455556666` using `AWSRAMEventBridgeEventBusV2SubscribeOnly`. That account can then create subscribers on it. Write a resource policy on the bus instead when you need an explicit `Deny`, a condition key, or a grant that no managed permission expresses. The other account still needs the same actions in its own identity policies, because both sides must allow it. @@ -19 +19 @@ To let another account publish to your bus, attach subscribers to it, or attach - * To share with accounts in your organization without an invitation, enable sharing with AWS Organizations in AWS RAM. To share with an account outside your organization, the account must accept the resource share invitation before it can use the bus. + * To share with accounts in your organization without an invitation, enable sharing with AWS Organizations in AWS RAM. To share with an account outside your organization, the account must first accept the resource share invitation. Only then can it use the bus. @@ -28 +28 @@ To let another account publish to your bus, attach subscribers to it, or attach -We recommend AWS RAM over a resource policy that you write yourself. With AWS RAM, you have one place to see and revoke what you have shared. AWS RAM also works with AWS Organizations and writes the bus's `AWS_RAM` resource policy for you. Create a resource share that names the bus ARN, the consumer accounts or organizational units, and one of the four AWS managed permissions for the bus resource type, each at `arn:aws:ram::aws:permission/`name``. +We recommend AWS RAM over a resource policy that you write yourself. With AWS RAM, you have one place to see and revoke what you have shared. AWS RAM also works with AWS Organizations and writes the bus's `AWS_RAM` resource policy for you. Create a resource share. It names the bus ARN, the consumer accounts or organizational units, and one of the four AWS managed permissions for the bus resource type. Each permission has the form `arn:aws:ram::aws:permission/`name``. @@ -46 +46 @@ Managed permission| What the consumer account can do -To grant less than a managed permission, or to add a condition key, author an AWS RAM customer managed permission. AWS RAM rejects one that names a bus owner only action. Read a permission back with the AWS RAM `GetPermission` operation rather than assume its exact action list. +To grant less than a managed permission, or to add a condition key, author an AWS RAM customer managed permission. AWS RAM rejects one that names an action that only the bus owner can take. Read a permission back with the AWS RAM `GetPermission` operation rather than assume its exact action list. @@ -50 +50 @@ To grant less than a managed permission, or to add a condition key, author an AW -To stop sharing, remove the bus or the principal from the resource share, or delete the share. EventBridge authorizes a subscriber or event source when it is created, so a subscriber the consumer created while the share was active keeps delivering after you unshare. To stop it, revoke it with `RevokeResource`. For more information about revoking a subscriber or an event source, see [Revoking a subscriber or an event source](./eb-custom-bus-access-revoke.html). The consumer can no longer publish or create new subscribers once the share is gone. +To stop sharing, remove the bus or the principal from the resource share, or delete the share. EventBridge authorizes a subscriber or event source when it is created. A subscriber the consumer created while the share was active keeps delivering after you unshare. To stop it, revoke it with `RevokeResource`. For more information about revoking a subscriber or an event source, see [Revoking a subscriber or an event source](./eb-custom-bus-access-revoke.html). The consumer can no longer publish or create new subscribers once the share is gone. @@ -54 +54 @@ To stop sharing, remove the bus or the principal from the resource share, or del -A bus shared with your account appears in your `ListEventBuses` results with the owner's account in its ARN, and you use it by that ARN, in the bus's Region. What you create on it belongs to you: when you list subscribers on the shared bus you see only your own subscribers, while the bus owner sees all of them. Sharing one bus exposes only that bus; you never see the owner's other buses. You cannot update or delete the bus, change its resource policy, or share it onward, and you cannot act on a subscriber that another account owns. The bus owner can withdraw any of your subscribers or event sources with `RevokeResource`; a revoked resource stops permanently and you can only delete it. +A bus shared with your account appears in your `ListEventBuses` results with the owner's account in its ARN. You use it by that ARN, in the bus's Region. What you create on it belongs to you. When you list subscribers on the shared bus, you see only your own. The bus owner sees all of them. Sharing one bus exposes only that bus. You never see the owner's other buses. You cannot update or delete the bus, change its resource policy, or share it onward. You also cannot act on a subscriber that another account owns. The bus owner can withdraw any of your subscribers or event sources with `RevokeResource`. A revoked resource stops permanently, and you can only delete it. @@ -58 +58 @@ A bus shared with your account appears in your `ListEventBuses` results with the -Sharing a bus has no charge of its own. Publishing, delivery, and retention are billed as described on the [Amazon EventBridge pricing](https://aws.amazon.com/eventbridge/pricing/) page. The bus owner can see delivery volume per consumer account in the `EventsDelivered` and `EgressBytes` metrics with the `SubscriberAccount` dimension. For more information about observability, see [Observability for the Custom Event Bus: metrics, logs, and CloudTrail](./eb-custom-bus-observability.html). +Sharing a bus has no charge of its own. Publishing, delivery, and retention are billed as described on the [Amazon EventBridge pricing](https://aws.amazon.com/eventbridge/pricing/) page on the AWS website. The bus owner can see delivery volume per consumer account in the `EventsDelivered` and `EgressBytes` metrics with the `SubscriberAccount` dimension. For more information about observability, see [Observability for the Custom Event Bus: metrics, logs, and CloudTrail](./eb-custom-bus-observability.html). @@ -62 +62 @@ Sharing a bus has no charge of its own. Publishing, delivery, and retention are -An event bus is the only Custom Event Bus resource that takes a resource policy; EventBridge rejects any other resource ARN. A bus holds two named policies. The `default` policy is the one you write, in full IAM policy language, including `Deny` statements. `AWS_RAM` is written only by AWS RAM and reflects your resource shares. +An event bus is the only Custom Event Bus resource that takes a resource policy. EventBridge rejects any other resource ARN. A bus holds two named policies. The `default` policy is the one you write, in full IAM policy language, including `Deny` statements. `AWS_RAM` is written only by AWS RAM and reflects your resource shares. @@ -64 +64 @@ An event bus is the only Custom Event Bus resource that takes a resource policy; -EventBridge evaluates both when it authorizes a caller from another account, and an explicit `Deny` in either overrides an `Allow` in the other. When a cross-account caller is denied and the policy you wrote appears to allow them, read the other policy. +EventBridge evaluates both when it authorizes a caller from another account. An explicit `Deny` in either overrides an `Allow` in the other. When a cross-account caller is denied and the policy you wrote appears to allow them, read the other policy. @@ -85 +85 @@ 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`. 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. +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. Treat that as no policy. A bus that you shared only through AWS RAM has no `default` policy. In that case, `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`. You can adjust this quota in Service Quotas. @@ -87 +87 @@ Manage the policies with `PutResourcePolicy`, `GetResourcePolicy`, `DeleteResour -EventBridge rejects a `default` policy that would grant public access, with `PublicPolicyException`, and does not attach it. This check is always on. A statement grants public access when its principal is a wildcard and no condition limits the callers to specific accounts or principals. A condition on event content, such as `events:source`, does not identify the caller. A condition such as `aws:PrincipalOrgID` does. A policy you write is invisible to AWS RAM, so you own tracking it. +EventBridge rejects a `default` policy that would grant public access, with `PublicPolicyException`. It does not attach the policy. This check is always on. A statement grants public access when its principal is a wildcard and no condition limits the callers to specific accounts or principals. A condition on event content, such as `events:source`, does not identify the caller. A condition such as `aws:PrincipalOrgID` does. A policy you write is invisible to AWS RAM, so you own tracking it. @@ -91 +91 @@ EventBridge rejects a `default` policy that would grant public access, with `Pub -Events also arrive on a bus without a direct `PutEvents` or `PutRawEvents` call: from an event source, or from a rule or a subscriber on another bus whose target is this bus. EventBridge authorizes an event source once, when you create it. It checks nothing again as events arrive, so a bus policy cannot filter that traffic afterwards. For more information about event sources, see [Event sources for a Custom Event Bus](./eb-custom-bus-event-sources.html). A rule or subscriber that you point at a bus yourself is authorized at ingestion, under the role you supplied, once for every event. EventBridge chooses the action per event: `events:PutEvents` for a genuine AWS service or partner event, and `events:PutRawEvents` for an event you originated. You cannot choose the action used. A forwarder carrying both kinds of events through one path must be granted both actions, in the role's identity policy and in the destination bus's resource policy. Granting only one denies half the stream. +Events also arrive on a bus without a direct `PutEvents` or `PutRawEvents` call. They can arrive from an event source, or from a rule or a subscriber on another bus whose target is this bus. EventBridge authorizes an event source once, when you create it. It checks nothing again as events arrive. A bus policy cannot filter that traffic afterward. For more information about event sources, see [Event sources for a Custom Event Bus](./eb-custom-bus-event-sources.html). A rule or subscriber that you point at a bus yourself is authorized at ingestion, under the role you supplied, once for every event. EventBridge chooses the action per event: `events:PutEvents` for a genuine AWS service or partner event, and `events:PutRawEvents` for an event you originated. You cannot choose the action used. A forwarder carrying both kinds of events through one path must be granted both actions. Grant them in the role's identity policy and in the destination bus's resource policy. Granting only one denies half the stream.