Dell EMC ECS
Dell ECS is an enterprise platform where the storage administrator, not you, controls the credentials. Two details decide whether a connection works: the namespace your object user belongs to, and which of the two S3 ports the cluster exposes.
Connection settings
- Endpoint
- https://{host}:9021
- Default region
- default
- Addressing
- Path-style
- Temporary credentials
- Not applicable
A filled-in example
Every value below is fabricated — they are shaped like real Dell EMC ECS credentials so you can recognise yours, and they authenticate nothing.
- Endpoint
- https://ecs.example.internal:9021
- Region
- default
- Access key
- ecs-object-user
- Secret key
- EXAMPLEecsSecretKeyDoNotUse0123456789ab
- Addressing
- Path-style
The access key for ECS is the object user name itself, not a generated identifier. Your administrator creates it and issues the secret from the ECS portal.
Where each value comes from
Endpoint
Enter your ECS endpoint — e.g., https://ecs.example.com:9021 (S3 HTTPS port: 9022, HTTP: 9021).
Credentials
ECS credentials are managed by your storage administrator. Create an object user and generate S3 secret key via the ECS portal.
Notes
ECS uses namespaces — you may need to include the namespace in the URL or request headers. Ask your admin for the correct namespace.
What usually goes wrong
Batch deletes need a legacy checksum
ECS rejects the flexible checksum headers the current AWS SDK attaches to DeleteObjects, and answers with a checksum error that names none of this. S3 Explorer sends the legacy Content-MD5 header instead, which ECS accepts.
The namespace decides what you can see
ECS scopes buckets by namespace. An object user in the wrong namespace authenticates correctly and then lists nothing. If the connection succeeds but the bucket list is empty, the namespace is the first thing to check with your administrator.
The scheme has to match the port
ECS publishes S3 on a dedicated port rather than on 443, with one port for plain HTTP and another for HTTPS, and many installations then put both behind a load balancer. Get the exact pair from your administrator: an https URL aimed at the plain HTTP port fails during the TLS handshake, before any credential is read, which reads like a network outage rather than a configuration error.