AWS_ENDPOINT is not working properly in v24.3.0

[def-]

Describe the problem

AWS_ENDPOINT is not working properly in v24.3.0, works fine in v24.2.

To Reproduce

We are running

CREATE EXTERNAL CONNECTION backup_bucket
AS 's3://persist/crdb-backup?AWS_ENDPOINT=http://minio:9000/&AWS_REGION=minio&AWS_ACCESS_KEY_ID=minioadmin&AWS_SECRET_ACCESS_KEY=minioadmin';
BACKUP INTO 'external://backup_bucket';
DROP EXTERNAL CONNECTION backup_bucket;

In old versions this connects to the host minio. In new CRDB version it connects to the host persist.minio, which does not exist.

Expected behavior Keep connecting to the right hostname, persist/crdb-backup is the bucket name. I could not find anything about this in the release notes: https://www.cockroachlabs.com/docs/releases/v24.3

Additional data / screenshots

ERROR: failed to construct External Connection details: failed to create s3 external connection: failed to write a sentinel ExternalStorage file: closing object: upload failed: operation error S3: PutObject, https response error StatusCode: 0, RequestID: , HostID: , request send failed, Put "http://persist.minio:9000/crdb-backup/crdb_external_storage_location?x-id=PutObject": dial tcp: lookup persist.minio on 127.0.0.11:53: no such host

Environment:

• CockroachDB version v24.3.0
• Server OS: Ubuntu 23.10
• Client app: cockroach sql

Additional context Failed tests in our CI

Jira issue: CRDB-45195

[blathers-crl[bot]]

Hi @def-, please add branch-* labels to identify which branch(es) this C-bug affects.

_{:owl: Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf.}

[blathers-crl[bot]]

Hello, I am Blathers. I am here to help you get the issue triaged.

Hoot - a bug! Though bugs are the bane of my existence, rest assured the wretched thing will get the best of care here.

I have CC'd a few people who may be able to assist you:

• @cockroachdb/disaster-recovery (found keywords: backup)

If we have not gotten back to your issue within a few business days, you can try the following:

• Join our community slack channel and ask on #cockroachdb.
• Try find someone from here if you know they worked closely on the area and CC them.

_{:owl: Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf.}

[blathers-crl[bot]]

cc @cockroachdb/disaster-recovery