2024.10.3

We identified an issue preventing the use of Fully Qualified Domain Names (FQDN) for S3 endpoints. The system uses S3 force path style, which caused SQS connection failures. As a workaround, you had to avoid providing S3 FQDN in AWS EKS-based clusters at both common and Integration Service levels. If other services needed explicit FQDN configurations, you had to specify them only in their respective configuration blocks. This issue has been fixed.