skills.rest
bjaus
bjausCOMMUNITY
Explore all skills by this author →
GitHub

eventbridge-event

Publish AWS EventBridge events from Go with structured envelopes and metadata.

Updated Aug 27, 2026
Search Tags:#publish#AWS#Go#EventBridge#buspub#envelope
One-click install
npx skills add https://github.com/bjaus/dotfiles --skill eventbridge-event
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: eventbridge-event
Source: https://github.com/bjaus/dotfiles/tree/main/plugin/skills/eventbridge-event
Command: npx skills add https://github.com/bjaus/dotfiles --skill eventbridge-event

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables teams to publish AWS EventBridge events from a Go-based publisher following LT K conventions, ensuring consistent envelopes, traceability, and structured metadata.

Core Features & Use Cases

  • Go-based publisher integration using buspub to publish events to EventBridge
  • Enforced envelope with generated_by metadata including project, git_sha, runtime, and runtime_version
  • Supports conventional event naming and sources (e.g., consumer/profile, ProfileUpdated)

Quick Start

Initialize the publisher with awsCfg, companyEventBusName, and a RuntimeConfig containing:

  • Project, GitSHA, ContextLogger, MetricsClient
  • Runtime, RuntimeVersion, and EventSourcePrefix Then publish a sample event with PutCompanyEvent using source "consumer/profile", detail_type "ProfileUpdated", and a DataEnvelope containing user data.

Frequently Asked Questions about eventbridge-event

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I publish AWS EventBridge events from a Go application?▼

To publish AWS EventBridge events from Go, initialize a publisher with your AWS configuration, event bus name, and runtime metadata, then call PutCompanyEvent with your source, detail type, and data envelope.

What metadata should be included in an EventBridge event envelope for distributed tracing?▼

An EventBridge event envelope for tracing should include generated_by metadata containing the project name, GitSHA, runtime, runtime version, context logger, metrics client, and event source prefix.

Does this Go EventBridge publisher support conventional event naming conventions?▼

Yes, this Go EventBridge publisher supports conventional event naming and sources, allowing you to specify structured sources like consumer/profile and detail types like ProfileUpdated for domain events.

What is the best way to structure domain events requiring traceability across distributed systems in Go?▼

The best way to structure traceable domain events in Go is using a structured envelope with buspub, embedding project GitSHA, runtime metadata, and a context logger to ensure consistent traceability across distributed systems.

How do I configure RuntimeConfig for a Go EventBridge publisher?▼

Configure RuntimeConfig by providing your Project, GitSHA, ContextLogger, MetricsClient, Runtime, RuntimeVersion, and EventSourcePrefix to initialize the Go EventBridge publisher with the required structured metadata.

Related Skills

Explore More Software Engineering Skills→
wesleyegbertowesleyegberto
3

hybrid-cloud-networking

Provision and validate hybrid cloud network topologies with VPN and dedicated interconnects.

Community
Advanced
northseadlnorthseadl

eventbridge

Create custom event buses, rules, and targets on AWS EventBridge.

Community
Advanced
iludeilude
8

logging-observability

Implement structured JSON logging with trace and span IDs.

Community
Advanced
aurainfosecaurainfosec

eventbridge

Configure AWS EventBridge event buses, rules, patterns, and targets.

Official
Intermediate