PowerPlatformConnectors icon indicating copy to clipboard operation
PowerPlatformConnectors copied to clipboard

[BUG] Amazon S3 Bucket connector not working

Open karzuo opened this issue 7 months ago • 18 comments

Type of Connector

Independent Publisher Connector

Name of Connector

Amazon S3 Bucket (Independent Publisher)

Describe the bug

It always throw an internal server error whichever method I tried:

Image

{
    "statusCode": 500,
    "headers": {
        "Access-Control-Allow-Methods": "GET, PUT, PATCH, DELETE, POST",
        "Access-Control-Allow-Origin": "*",
        "Access-Control-Max-Age": "3600",
        "Access-Control-Expose-Headers": "*",
        "x-ms-environment-id": "default-2414a4c8-fba7-469b-acad-5dfec2865467",
        "x-ms-tenant-id": "2414a4c8-fba7-469b-acad-5dfec2865467",
        "x-ms-dlp-re": "-|-",
        "x-ms-dlp-gu": "-|-",
        "x-ms-dlp-ef": "-|-/-|-|-",
        "Date": "Wed, 26 Mar 2025 01:34:31 GMT",
        "Content-Length": "419",
        "Content-Type": "application/json"
    },
    "body": {
        "error": {
            "code": 500,
            "message": "Sequence contains no elements\r\n   at System.Linq.Enumerable.First[TSource](IEnumerable`1 source)",
            "source": "default-2414a4c8-fba7-469b-acad-5dfec2865467.03.common.asia.azure-apihub.net",
            "path": "choose[4]\\when[1]\\choose[1]\\otherwise",
            "policyId": "",
            "clientRequestId": "92735caa-7d10-4520-be4f-4ee59dd76ea3",
            "dreeSet": "true"
        }
    }
}

Is this a security bug?

No, this is not a security bug

What is the severity of this bug?

Severity 1 - Connector is broken or there's a very serious issue

To Reproduce

Set up a simple manual trigger pipeline with Delete Object.

Region: ap-southeast-1

Expected behavior

It should return status 200, success regardless whether the file is present (I tried it by using http request, manually signing the api and it worked)

Environment summary

Set up via Cloud Flow UI:

Image

Additional context

Not sure if it is a connection issue, because the error is the same when I try giving wrong credentials as well. There is no issue with my credentials as it has full access to S3 and tested to work fine using other methods.

karzuo avatar Mar 26 '25 01:03 karzuo