https://docs.redhat.com/en/documentation/red_hat_jboss_enterprise_application_platform/8.0/html-single/deploying_jboss_eap_on_amazon_web_services/index#proc_providing-feedback-on-red-hat-documentation_default

Multiple references throughout the doc:
5.2 Launch one or more instances to serve as host controllers
6.1.1 Launching clustered AMIs without mod_cluster and VPC for domain controller instance
6.1.2 Launching clustered AMIs without mod_cluster and VPC for host controller

Same issue applies to JGroups S3_PING:
6.1 Launch clustered JBoss EAP AMIs without mod_cluster and VPC

The EAP domain's S3 (and JGroups S3_PING) support uses a deprecated authentication method that is no longer supported (except for grandfathered S3 buckets created before June 2024, 2020).
https://aws.amazon.com/blogs/aws/amazon-s3-update-sigv2-deprecation-period-extended-modified/

All these references to it need to either be removed, or a big red note added that it does not work unless you have an old bucket.

This applies to both EAP 7 and 8 versions of the document.
I'm not aware of any customers using this functionality, and if they were then they would already had it configured years ago, so removal is probably the simplest (especially for EAP 8).