S3 Connector Works in Local Environment but Fails in Mendix Cloud (ACCP)

0
Hi everyone, I’m trying to integrate Amazon S3 using the Amazon S3 Connector module, and I’m running into an issue where the connection works perfectly in my local environment, but fails in the Mendix ACCP (acceptance) environment.   In ACCP I get the following error: Unable to execute HTTP request: Connect to xxx(endpoint path) failed: connect timed out (SDK Attempt Count: 4) This is the error message in full: java.net.SocketTimeoutException com.mendix.systemwideinterfaces.MendixRuntimeException: software.amazon.awssdk.core.exception.SdkClientException: Unable to execute HTTP request: Connect to rossum-idp-s3bucket.s3.eu-central-1.amazonaws.com:443 [rossum-idp-s3bucket.s3.eu-central-1.amazonaws.com/3.5.134.102, rossum-idp-s3bucket.s3.eu-central-1.amazonaws.com/3.5.138.241, rossum-idp-s3bucket.s3.eu-central-1.amazonaws.com/3.5.138.218, rossum-idp-s3bucket.s3.eu-central-1.amazonaws.com/3.5.137.121, rossum-idp-s3bucket.s3.eu-central-1.amazonaws.com/52.219.169.226, rossum-idp-s3bucket.s3.eu-central-1.amazonaws.com/52.219.169.194, rossum-idp-s3bucket.s3.eu-central-1.amazonaws.com/3.5.138.68, rossum-idp-s3bucket.s3.eu-central-1.amazonaws.com/3.5.136.102] failed: connect timed out (SDK Attempt Count: 4) at com.mendix.basis.actionmanagement.ActionManager.executeSync(ActionManager.scala:109) Caused by: software.amazon.awssdk.core.exception.SdkClientException: Unable to execute HTTP request: Connect to rossum-idp-s3bucket.s3.eu-central-1.amazonaws.com:443 [rossum-idp-s3bucket.s3.eu-central-1.amazonaws.com/3.5.134.102, rossum-idp-s3bucket.s3.eu-central-1.amazonaws.com/3.5.138.241, rossum-idp-s3bucket.s3.eu-central-1.amazonaws.com/3.5.138.218, rossum-idp-s3bucket.s3.eu-central-1.amazonaws.com/3.5.137.121, rossum-idp-s3bucket.s3.eu-central-1.amazonaws.com/52.219.169.226, rossum-idp-s3bucket.s3.eu-central-1.amazonaws.com/52.219.169.194, rossum-idp-s3bucket.s3.eu-central-1.amazonaws.com/3.5.138.68, rossum-idp-s3bucket.s3.eu-central-1.amazonaws.com/3.5.136.102] failed: connect timed out (SDK Attempt Count: 4) at com.mendix.basis.actionmanagement.ActionManager.executeSync(ActionManager.scala:109) Caused by: Unable to execute HTTP request: Connect to rossum-idp-s3bucket.s3.eu-central-1.amazonaws.com:443 [rossum-idp-s3bucket.s3.eu-central-1.amazonaws.com/3.5.134.102, rossum-idp-s3bucket.s3.eu-central-1.amazonaws.com/3.5.138.241, rossum-idp-s3bucket.s3.eu-central-1.amazonaws.com/3.5.138.218, rossum-idp-s3bucket.s3.eu-central-1.amazonaws.com/3.5.137.121, rossum-idp-s3bucket.s3.eu-central-1.amazonaws.com/52.219.169.226, rossum-idp-s3bucket.s3.eu-central-1.amazonaws.com/52.219.169.194, rossum-idp-s3bucket.s3.eu-central-1.amazonaws.com/3.5.138.68, rossum-idp-s3bucket.s3.eu-central-1.amazonaws.com/3.5.136.102] failed: connect timed out (SDK Attempt Count: 4) at com.mendix.basis.actionmanagement.ActionManager.executeSync(ActionManager.scala:109) Caused by: Connect to rossum-idp-s3bucket.s3.eu-central-1.amazonaws.com:443 [rossum-idp-s3bucket.s3.eu-central-1.amazonaws.com/3.5.134.102, rossum-idp-s3bucket.s3.eu-central-1.amazonaws.com/3.5.138.241, rossum-idp-s3bucket.s3.eu-central-1.amazonaws.com/3.5.138.218, rossum-idp-s3bucket.s3.eu-central-1.amazonaws.com/3.5.137.121, rossum-idp-s3bucket.s3.eu-central-1.amazonaws.com/52.219.169.226, rossum-idp-s3bucket.s3.eu-central-1.amazonaws.com/52.219.169.194, rossum-idp-s3bucket.s3.eu-central-1.amazonaws.com/3.5.138.68, rossum-idp-s3bucket.s3.eu-central-1.amazonaws.com/3.5.136.102] failed: connect timed out at com.mendix.basis.actionmanagement.ActionManager.executeSync(ActionManager.scala:109) Caused by: connect timed out at com.mendix.basis.actionmanagement.ActionManager.executeSync(ActionManager.scala:109)     This is a TCP connection timeout, so the Mendix Cloud environment cannot even establish an HTTPS connection to the S3 endpoint. AWS never receives the request. What I already checked Bucket region is correct (eu-central-1) No issue with credentials (works locally) No CORS issue (not REST/JS) Not an AWS AccessDenied — it fails before TLS handshake I simply need my Mendix ACCP environment to reach this S3 endpoint on port 443. Any experience or guidance would be super appreciated. Thanks so much in advance!
asked
0 answers