Amazon EventBridge

[ewbankkit]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

Amazon EventBridge announced.

At the AWS API level these are additions to the existing CloudWatch Events API.

New or Affected Resource(s)

Sticking with the existing naming convention of aws_cloudwatch_event_

New Resource

• aws_cloudwatch_event_event_bus

Modified Resources

• aws_cloudwatch_event_permission
• aws_cloudwatch_event_rule
• aws_cloudwatch_event_target

Potential Terraform Configuration

# Copy-paste your Terraform configurations here - for large Terraform configs,
# please use a service like Dropbox and share a link to the ZIP file. For
# security, you can also encrypt the files using our GPG public key.

References

Requires:

• Update module aws/aws-sdk-go to v1.20.19 #9305

[ebekker]

I would just stick with the simpler aws_cloudwatch_event_bus -- the resource is a bus in the CW Events system. (Although technically, the API doesn't even reflect that it's built atop or integrated with CW.)

[ewbankkit]

@ebekker Yes, I tend to agree. Of these CloudWatch resources, only aws_cloudwatch_metric_alarm strictly conforms to the naming guidelines.

[tanmng]

@ewbankkit given the change in commit 8295926 in #10256 by @alexanderkalach, I think this issue can no longer be closed by that PR, and we will need separate effort to handle AWS partner event bus. Is that the case?
If so, can we proceed with the result of the vote and start getting an implementation on this?

[ewbankkit]

@tanmng Yes, #10256 is just the initial work needed. There will be additional PRs to complete functionality.

[breathingdust]

Hi Everyone! 👋

We recognize the significant community interest in this service area and want to provide an update about its status.

Because there is significant overlap between EventBridge and Cloudwatch we’ll need to take a step back and spend a bit of time considering design.

Once we’ve finished our research, we’ll post an update to the issue detailing the next steps.

We appreciate all the contributions and feedback thus far!

[claranet-barney]

Hey @breathingdust / @ewbankkit Any news on how this is coming along? Not hassling just wondering if there's been any movement on it or any plans in progress?

[breathingdust]

Hey @claranet-barney! 👋

Nothing to report as yet, we'll need to work through this quarters ROADMAP items first. It's still definitely on our list and I would expect to see it released sometime this summer. Thanks for your patience!

[kurtmaile]

Hi,

Is event bridge support still outstanding?

Cheers

[mwarkentin]

In the meanwhile, you can do the cloudformation hack:

resource "aws_cloudformation_stack" "eventbridge_bus" {
  name = "eventbridge-bus"

  template_body = <<EOF
Resources:
  EventBus:
    Type: AWS::Events::EventBus
    Properties:
      Name: bus-name
EOF
}

[DylanBohlender]

It looks like this has been added to the August - October ROADMAP file as the first item, which is awesome!

Is there a rough timeline for when this will be implemented? I suspect that the design research phase likely extended the timelines here, but any visibility into progress would be greatly appreciated. The CF template hack above is a useful workaround, but I suspect I'm not alone in feeling icky every time I'm writing inline CF templates in lieu of HCL.

[maryelizbeth]

Hey @DylanBohlender! Right now, we don't have a release date for EventBridge support. The team is actively researching and will begin implementation once that is complete. Once we've decided on the design of this feature, we'll begin work and you'll see it added to a release milestone. We'll come back to this issue with updates as they're available.

[smailc]

Any news on EventBridge support?

[breathingdust]

Hi all! 👋

Just an update that we have finished the service design and plan to start work this week, so we are on track to have this out by the end of October. Again, we appreciate your patience!

[breathingdust]

Initial scope of EventBridge support has been completed as of v3.14.1 🎉

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!