event-bus | EventBus is a simple JavaScript library for managing events | Pub Sub library

aws.events belongs to AWS, not to you, thus you can't define it as source of your events. Only AWS can do it.

You need to use your own custom name for the source of your events, e.g. myapp.events.

I don't believe you can configure VertxOptions from code.

You could put a cluster.xml Hazelcast configuration file in the classpath instead.

Note that the Vert.x cluster managers are not supported in Quarkus yet. You can make them work in JVM mode (see this attempt with Infinispan) but not in native mode.

Artifacts use context: to reference the source locations.

I think you must be using an old version of Skaffold. Newer versions of Skaffold provide more detail:

I see there's some confusion between the various Buses and the Event Store. Before attempting to implement an Event Bus, you need to answer one important question that lies at the foundation of any Event Sourcing implementation:

• How to preserve the Event Store as the Single Source of Truth?

That is, your Event Store contains the complete state of the domain. This also means that the consumers of the Event Bus (whatever it ends up being - a message queue, a streaming platform, Redis, etc.) should only get the events that are persisted. Therefore, the goals become:

• Only deliver events on the Bus that are persisted to the Store (so if you get an error writing to the Store, or maybe a Concurrency Exception, do not deliver via bus!)
• Deliver all events to all interested consumers, without losing any events

These two goals intuitively translate to "I want atomic commit between the Event Store and the Event Bus". This is simplest to achieve when they're the same thing!

So, instead of thinking about how to connect an "Event Bus" to command handlers and send events back and forth, think about how to retrieve already persisted events from the Event Store and subscribe to that. This also removes any dependency between command handlers and event subscribers - they live on different sides of the Event Store (writer vs. reader), and could be in different processes, on different machines.

Extrapolating from the similar answers I put in the comments, this works for me:

Based on the comments,

The URI should be something like below for events:

arn:aws:apigateway:${AWS::Region}:events:action/PutEvents

In Vert.x 3, the cluster host and cluster public host default to localhost.

If you only change the cluster public host in VertxOptions, Vert.x will bind EventBus transport servers to localhost while telling other nodes to connect to the public host.

This kind of configuration is needed when running Vert.x on some cloud providers, but in most cases you only need to set the cluster host (and then the public host will default to its value):

First, if you have a consumer with dependencies and are using a container, I'd suggest following the documentation – particularly at the bottom where it shows how to configure consumers on a receive endpoint from the container.

In your case, this would look like:

According to this You should use kebab-case format to name your custom events :