LuigiDurso opened a new issue, #9386: URL: https://github.com/apache/seatunnel/issues/9386
### Search before asking - [x] I had searched in the [issues](https://github.com/apache/seatunnel/issues?q=is%3Aissue+label%3A%22bug%22) and found no similar issues. ### What happened When using the SeaTunnel Iceberg connector with a custom S3 endpoint (MinIO), the AWS SDK ignores the configured endpoint and attempts to connect to 127.0.0.1:9002, resulting in connection failures. Despite multiple configuration attempts with various property formats, the connector consistently tries to use the hardcoded local endpoint instead of the specified MinIO endpoint. ### SeaTunnel Version 2.3.11 ### SeaTunnel Config ```conf sink { Iceberg { catalog_name = "iceberg" // Nessie catalog properties iceberg.catalog.config = { uri = "http://nessie:19120/iceberg/main"; catalog-impl = "org.apache.iceberg.rest.RESTCatalog" warehouse = "s3://***/" s3.endpoint="http://minio:9000"; s3.region="us-east-1" s3.path-style-access=true s3.aws-access-key="***" s3.aws-secret-key="***" } namespace = "demo" table = "fake_data_table" } } ``` ### Running Command ```shell curl --location 'http://127.0.0.1:9090/submit-job/upload' --form 'config_file=@"/***/config/fake-to-iceberg-nessie.conf"' ``` ### Error Exception ```log Caused by: software.amazon.awssdk.core.exception.SdkClientException: Unable to execute HTTP request: Connect to 127.0.0.1:9002 [/127.0.0.1] failed: Connection refused (Connection refused) (SDK Attempt Count: 4) ... Caused by: java.net.ConnectException: Connection refused (Connection refused) ``` ### Zeta or Flink or Spark Version _No response_ ### Java or Scala Version _No response_ ### Screenshots _No response_ ### Are you willing to submit PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
