EAP Domain mode on Amazon can use as an alternative to the static discovery option the S3 Discovery. This discovery internally uses an S3 Bucket to store the information to where locate the Domain Controller.

Until EAP 7.4, the Domain Controller stores the S3 metadata under the following path:

/S3/master/jboss-domain-master-data

and uses the following keys to store the host IP, name, and protocol:

master_host, master_port, and master_protocol

However, for EAP 8 as part of the work to replace problematic language in our code, documentation, and web properties, the Domain Controller running on EAP 8.0 is going to use the following path and keys for the S3 Discovery metadata:

/S3/primary/jboss-domain-primary-data

and uses the following keys to store the host IP, name, and protocol:

primary_host, primary_port, and primary_protocol

We have to continue giving support for mixed domains under this scenario. Our policy for mixed domain support is we are keeping N-1 major backward compatibility when the lower EAP version runs on the latest minor.

In order to be able to remove the problematic language, we need to allow EAP 7.4.x (being x the latest minor) to discover a Domain Controller (running on EAP 8.x) by using the new updated S3 path and keys. It means we need to adapt EAP on a CP to add this capability.