EMC ECS: failed to establish connection

[Elgringo]

Hello,

I am trying to connecct Veeam to my S3 storage (EMC ECS) in order to create an S3 Object Storage type repository.
The S3 storage is located in my LAN.
Seems that veeam requires https access to the S3 endpoint.
The problem is that ECS uses a self-signed certificate... and veeam do not like self-signed certificate. Got the following message when trying to connect to ECS :"failed to establish connection to Amazon S3 endpoint".
Is there a way to make it works using such configuration (I mean self signed certificate on S3 endpoint) ?

Thanks !

[kqf_chris]

You could try importing the ECS cert into the Veeam server as a trusted root.

[tsightler]

Veeam should have no problem with self-signed certificates, I use one myself for a Ceph based S3 repo in the lab. When you add the repo it should prompt you to accept the certificate, it does this with all self-signed certificate. Is there any chance the certificate is expired or doesn't match the hostname or some other issue like that? Honestly, the error itself doesn't really look anything like an SSL/TLS level error though.

[perrylee]

Same situation here, I setup a S3 storage on our Freenas and when I try to add a repo I get the "Failed to establish connection to Amazon S3 endpoint" error.
Is there a solution to get this working with a self signed certificate.

[Gostev]

Nothing to add to Tom's response... it should work just fine as long as the certificate is valid, and most of our R&D labs use self-signed certificates.

[stevekarra]

There is a document which outlines how to set it up - https://www.dellemc.com/resources/en-us ... ide-wp.pdf

As Tom and Gostev mentioned, it should work fine as long as you accept the certs during the repo configuration. You will also need a load balancer for ECS - you can get one at https://www.loadbalancer.org/applicatio ... l-emc-ecs/

[graemep]

I ran into the same issue as originally posted, and what was making it slightly more confusing was the 'S3 Browser' app was connecting to the ECS storage (with it's SSL/TLS option selected) yet Veeam would report the failure to establish connection.

It turned out this was due to TLS support on the backup servers, which had the MS patch below installed, and just needed the DefaultSecureProtocols registry setting applied.

https://support.microsoft.com/en-gb/hel ... cols-in-wi

After these were applied (and a reboot), the connection was made first time.