AWS eventbridge: Clarify EventBridge custom bus IAM and KMS permission grants
Summary
Rewrites the Custom Event Bus permissions page: adds an intro sentence about replacing ARN placeholders, fixes the table header, and rewords each scenario row (publish, schema registry, cross-account publish, subscribers, delivery role, event sources, administration, KMS encryption) for clarity. No permission semantics are changed; the same IAM actions, iam:PassRole, resource-policy/RAM sharing, and KMS key-policy requirements are restated.
Security assessment
The diff is editorial: it restates existing least-privilege guidance for EventBridge custom buses, including iam:PassRole on the delivery role, resource-policy/AWS RAM grants for cross-account publishing, and scoped KMS key-policy actions (kms:Decrypt/Encrypt/GenerateDataKeyWithoutPlaintext/ReEncrypt*) with the aws:events:event-busv2:arn encryption context. It documents security configuration but shows no evidence of addressing a specific vulnerability or incident, so it is security documentation rather than a fix.
Evidence
+Encrypt a bus with your own key| The key policy| The bus creator's identity needs `kms:DescribeKey`. That identity, all producers, all subscriber owners, and the `events.amazonaws.com` principal need `kms:Decrypt`, `kms:Encrypt`, `kms:GenerateDataKeyWithoutPlaintext`, `kms:ReEncryptFrom`, and `kms:ReEncryptTo`, scoped to the bus with the `aws:events:event-busv2:arn` encryption context. See [Configuring permissions to use a Customer Managed KMS Key](./eb-custom-bus-encryption.html#eb-custom-bus-encryption-key-policy).
Diff
diff --git a/eventbridge/latest/userguide/eb-custom-bus-permissions.md b/eventbridge/latest/userguide/eb-custom-bus-permissions.md index a44156a..b500d63 100644 --- a//eventbridge/latest/userguide/eb-custom-bus-permissions.md +++ b//eventbridge/latest/userguide/eb-custom-bus-permissions.md @@ -9 +9 @@ -Each role in a Custom Event Bus deployment needs a small, specific set of grants. This page lists them by scenario so that you can copy the set for the role you are creating. For example, a producer's role needs `events:PutRawEvents` on the bus ARN and, if the bus uses a customer managed key, the key's policy must allow the `events.amazonaws.com` principal. +Each role in a Custom Event Bus deployment needs a small, specific set of grants. This page lists them by scenario so that you can copy the set for the role you are creating. For example, a producer's role needs `events:PutEvents` or `events:PutRawEvents` on the bus ARN. If the bus uses a customer managed key, the key's policy must also allow the `events.amazonaws.com` principal. @@ -11 +11,3 @@ Each role in a Custom Event Bus deployment needs a small, specific set of grants -Scenario| Who needs the grant| Grants +The following table lists the permission grants for each scenario. In the ARN patterns, replace `region`, `account`, and `name` with your own values. + +Permission grants by scenarioScenario| Who needs the grant| Grants @@ -13,8 +15,8 @@ Scenario| Who needs the grant| Grants -Publish to a bus| The producer's identity| `events:PutEvents` or `events:PutRawEvents` on the bus ARN; `events:DescribeEventBus` to confirm the bus is `ACTIVE` -Publish Avro or Protobuf with a schema registry| The role in `PutRawEvents` `RoleArn`| Read access to the schema in the registry: the Glue Schema Registry read actions for a Glue registry, or the secret and network access your Confluent registry requires. The role trusts `events.amazonaws.com`. See [Supported content types: JSON, Avro, Protobuf, and raw bytes](./eb-custom-bus-open-formats.html) -Publish to a bus in another account| The producer's identity, and the bus| The publish action in the producer's identity policy, and the same action granted to the producer's account by an AWS RAM share or the bus resource policy -Create and manage subscribers| The subscriber owner's identity| `events:CreateSubscriber` on the bus and on `arn:aws:events:`region`:`account`:subscriber/`name`/*`; `iam:PassRole` on the delivery role; `events:DescribeSubscriber`, `events:UpdateSubscriber`, `events:DeleteSubscriber` on the subscriber; `events:UpdateSubscriber` on the bus for an update that includes a `FilterConfiguration`; `events:TagResource` if the create carries tags -Deliver to a target| The delivery role| Trust for `events.amazonaws.com`; the target's action; `sqs:SendMessage` on the dead-letter queue; the target's key actions if the target is encrypted. See [The delivery role](./eb-custom-bus-subscribers.html#eb-custom-bus-subscribers-role) -Attach an event source| The event source owner's identity, the dead-letter queue, and the key| `events:CreateEventSource` on the bus and on the event source; a queue policy allowing `events.amazonaws.com` `sqs:SendMessage` on the dead-letter queue; if the bus is encrypted, the key policy allows `events.amazonaws.com`. See [Event sources for a Custom Event Bus](./eb-custom-bus-event-sources.html) -Administer a bus| The bus owner's identity| `events:CreateEventBus`, `events:UpdateEventBus`, `events:DeleteEventBus`, `events:PutResourcePolicy`, `events:GetResourcePolicy`, `events:DeleteResourcePolicy`, `events:ListResourcePolicies`, `events:RevokeResource`; `ram:CreateResourceShare` and related AWS RAM actions to share it -Encrypt a bus with your own key| The key policy| The bus creator's identity needs `kms:DescribeKey`; that identity, every producer and subscriber owner, and the `events.amazonaws.com` principal need `kms:Decrypt`, `kms:Encrypt`, `kms:GenerateDataKeyWithoutPlaintext`, `kms:ReEncryptFrom`, and `kms:ReEncryptTo`, scoped to the bus with the `aws:events:event-busv2:arn` encryption context. See [Configuring permissions to use a Customer Managed KMS Key](./eb-custom-bus-encryption.html#eb-custom-bus-encryption-key-policy) +Publish to a bus| The producer's identity| `events:PutEvents` or `events:PutRawEvents` on the bus ARN. `events:DescribeEventBus` to confirm the bus is `ACTIVE`. +Publish Avro or Protobuf with a schema registry| The role in `PutRawEvents` `RoleArn`| Read access to the schema in the registry. For a Glue registry, grant the Glue Schema Registry read actions. For a Confluent registry, grant the secret and network access it requires. The role trusts `events.amazonaws.com`. See [Supported content types: JSON, Avro, Protobuf, and raw bytes](./eb-custom-bus-open-formats.html). +Publish to a bus in another account| The producer's identity, and the bus| The publish action in the producer's identity policy. The bus must also grant the same action to the producer's account through an AWS RAM share or the bus resource policy. +Create and manage subscribers| The subscriber owner's identity| `events:CreateSubscriber` on the bus and on `arn:aws:events:`region`:`account`:subscriber/`name`/*`. `iam:PassRole` on the delivery role. `events:DescribeSubscriber`, `events:UpdateSubscriber`, and `events:DeleteSubscriber` on the subscriber. `events:UpdateSubscriber` on the bus if the update includes a `FilterConfiguration`. `events:TagResource` if the create carries tags. +Deliver to a target| The delivery role| Trust for `events.amazonaws.com`. The target's action. `sqs:SendMessage` on the dead-letter queue. The target's key actions if the target is encrypted. See [The delivery role](./eb-custom-bus-subscribers.html#eb-custom-bus-subscribers-role). +Attach an event source| The event source owner's identity, the dead-letter queue, and the key| `events:CreateEventSource` on the bus and on the event source. A queue policy must allow `events.amazonaws.com` to call `sqs:SendMessage` on the dead-letter queue. If the bus is encrypted, the key policy must allow `events.amazonaws.com`. See [Event sources for a Custom Event Bus](./eb-custom-bus-event-sources.html). +Administer a bus| The bus owner's identity| `events:CreateEventBus`, `events:UpdateEventBus`, `events:DeleteEventBus`, `events:PutResourcePolicy`, `events:GetResourcePolicy`, `events:DeleteResourcePolicy`, `events:ListResourcePolicies`, and `events:RevokeResource`. `ram:CreateResourceShare` and related AWS RAM actions to share it. +Encrypt a bus with your own key| The key policy| The bus creator's identity needs `kms:DescribeKey`. That identity, all producers, all subscriber owners, and the `events.amazonaws.com` principal need `kms:Decrypt`, `kms:Encrypt`, `kms:GenerateDataKeyWithoutPlaintext`, `kms:ReEncryptFrom`, and `kms:ReEncryptTo`, scoped to the bus with the `aws:events:event-busv2:arn` encryption context. See [Configuring permissions to use a Customer Managed KMS Key](./eb-custom-bus-encryption.html#eb-custom-bus-encryption-key-policy).