AWS S3 bucket as storage - Invalid connection

GroupDocs.Total Cloud Product Family
1

I’m trying to configure a AWS S3 bucket as storage.
I’ve created the bucket and iam user, and after adding the bucket and credentials on groupdocs cloud, the “verify connection” gives me “Invalid connection”

The policy used to connect the iam user with the bucket is the following

{
    "Statement": [
        {
            "Action": [
                "s3:*"
            ],
            "Effect": "Allow",
            "Resource": [
                "arn:aws:s3:::tf-xxxx-groupdocs",
                "arn:aws:s3:::tf-xxxx-groupdocs/*"
            ]
        }
    ],
    "Version": "2012-10-17"
}

groupdocs-s3.png (28.5 KB)

I manually tested the access using key+secret and could do upload/download/delete/list

Do the bucket need to be in any specific region? this is created in eu-west-1

2

@dhjimmie

No, there is no specific region requirement to configure AWS S3 storage with the GroupDocs Cloud API.

Please note that when you configure external Amazon S3 storage, the GroupDocs Cloud APIs need access to the following APIs on the bucket. Please double check the access.

Required APIs access:

  • GetObjectMetadada API
  • ListObjects API

Optional APIs:

  • CopyObject API
  • PutObject API
  • GetPreSignedURL API
  • PutBucket API
  • PutBucketVersioning API
  • DeleteObject API
  • ListVersions API
  • GetObject API
  • DeleteBucket API
3

thanks for your help,

I did change the action to these now (even though I believe the wildcard earlier was providing access to all actions)

Action = [
          "s3:GetObjectMetadata",
          "s3:ListBucket",
          "s3:CopyObject",
          "s3:PutObject",
          "s3:GetObject",
          "s3:PutBucket",
          "s3:PutBucketVersioning",
          "s3:DeleteObject",
          "s3:ListBucketVersions",
          "s3:DeleteBucket"
        ]

Same result. It still says “Invalid connection”.
I double checked the credentials by using “FileZilla Pro”

4

@dhjimmie

We are looking into the issue and will update you shortly.

5

I proceeded by testing the API even if I get the error on “Verify connection”.
It appears that it actually works, so the error is inaccurate.

6

@

Thanks for the update. Definitely, it will help us investigate the issue.