aws-cloudformation / aws-cloudformation/cloudformation-coverage-roadmap

[AWS::Events::EventBus] - [BUG] - Missing log destinations in `LogConfig`

Open
#2,345 5 comments 9 reactions 0 assignees View on GitHub
bug
Dominant language
No language data
Stars
1.1k
Forks
62
PR merge metrics
No merged PRs in 30d

Description

### Name of the resource

AWS::Events::EventBus

### Resource Name

_No response_

### Issue Description

Following [this announcement](https://aws.amazon.com/about-aws/whats-new/2025/07/amazon-eventbridge-enhanced-logging-improved-observability/), the [`LogConfig`](https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/aws-properties-events-eventbus-logconfig.html) property was added to the [`AWS::Events::EventBus`](https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/aws-resource-events-eventbus.html) resource. The problem is that this new property only has the `IncludeDetail` and the `Level` properties:

Image

Because of this, there's no way to set and configure log destinations, as per the [EventBridge docs](https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-event-bus-logs.html):

Image

### Expected Behavior

I expected the `LogConfig` property of the `AWS::Events::EventBus` resource to be similar to the [`PipeLogConfiguration`](https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/aws-properties-pipes-pipe-pipelogconfiguration.html) property of [`AWS::Pipes::Pipe`](https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/aws-resource-pipes-pipe.html#cfn-pipes-pipe-logconfiguration):

Image

Specifically, I don't see the following properties in `LogConfig`:
- `CloudwatchLogsLogDestination`
- `FirehoseLogDestination`
- `S3LogDestination`

### Observed Behavior

It's not possible to configure logging for `AWS::Events::EventBus` resource because there are missing properties.

### Test Cases

See above.

### Other Details

_No response_

Contributor guide

Open the contributing guide

Research direction

No implementation file or test is named. Start by comparing the EventBridge LogConfig documentation with PipeLogConfiguration and the linked EventBridge logging guidance, then locate the repository's AWS::Events::EventBus resource definition. Done means the three requested log-destination properties are supported and covered by the project's validation or coverage checks.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
cloud
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.