OpenDXL in AWS/Public cloud

  • Great question. We don't have any specific guidelines posted currently.


    However, a fairly basic approach would be to have a hub and spoke topology. The central hub would consist of two brokers, and spoke brokers could be added as necessary. Clients would connect to the brokers through a load balancer (maybe restrict connections to spoke brokers only). Also, with the latest version of the Open Broker and related clients, you could limit connections to web sockets.


    Thanks,

    Chris

  • It is really based on your preference, the brokers will work with either distribution model. I think it would make a lot of sense for us to put together a basic guide to walk through both scenarios. Would that be useful?


    Thanks,

    Chris

  • I think that would be very useful for anyone trying to implement in AWS. Getting a stand alone broker running was not too difficult but trying to understand the best way to handle deployment and configuration of a fabric of multiple brokers is challenging.

  • On this topic, we are also interested in the creation of Helm charts / Operators and/or other methodologies for deployment of OpenDXL brokers into Kubernetes clusters (which could be used inside AWS or any other cloud).


    If anyone else is interested in this area please reach out...