Problem connect S3 AWS

[alair.neto]

Friends.
I have a little problem for configure veeam to connect aws3, following the documentation, when configured the account and click in next, after the long time, the veeam show me the mensage.
"Failed to establish connection to Amazon S3 endpoint, See for logs for details."

[nielsengelen]

Did you configure the S3 endpoint as explained in our user guide?

Also, please don’t post log snippets as per our forum rules. If needed please open a support case and post it here for future reference.

[alair.neto]

Yes, i readed this tutorial, but my version is community, i think that this version dont support this feature. Although I have this option.
This is error:

"Failed to establish connection to Amazon S3 endpoint. See logs for deails."

[Mike Resseler]

Hi @alair.neto

Are you using Veeam Backup for AWS? Just asking as we call it free edition over there. It is only limited to 10 instances, but the S3 is in there. But I wonder, with that notification, what solution you are using. Veeam Backup for Office 365 or Veeam Backup & Replication?

[nielsengelen]

With community, you mean the Free edition (https://aws.amazon.com/marketplace/pp/B081VXF1Q9)? There is no difference between version except for maximum 10 instances in the Free edition. Did you set up something specific regarding VPC/subnets?

[alair.neto]

Hi @alair.neto

Are you using Veeam Backup for AWS? Just asking as we call it free edition over there. It is only limited to 10 instances, but the S3 is in there. But I wonder, with that notification, what solution you are using. Veeam Backup for Office 365 or Veeam Backup & Replication?

Hi
I using Veeam Backup & Replication 10

[Mike Resseler]

Ah, you are on the forum of Veeam Backup for AWS . No worries, I will move this post to the correct forum. But to answer your question, Veeam's cloud tier functionality is not supported in the community edition

Cheers
Mike

[veremin]

With the Community Edition you can only add object storage repository to import backups from, while you cannot use it as a Capacity Tier (part of Scale-Out Backup Repository).

The issue you have happens, while you're adding object storage repository (perfectly acceptable operation from licensing perspective), so, it must be caused by something else rather than licensing.

If you would like to investigate this problem further, kindly, reach our support team.

However, even if the technical issue is fixed, you will be able to only add object storage repository, you won't be able to move or copy backups there.

Thanks!