"The connection with the server was terminated abnormally" when uploading to to S3 TransferUtility.UploadAsync on EC2 instance

Question

The error I'm getting is:

The thread 0xffc has exited with code 0 (0x0).
Exception thrown: 'System.IO.IOException' in System.Private.CoreLib.dll
Exception thrown: 'System.IO.IOException' in Anjuna1.dll
Exception thrown: 'System.IO.IOException' in System.Private.CoreLib.dll
Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware:Error: An unhandled exception has occurred: The write operation failed, see inner exception.

System.IO.IOException: The write operation failed, see inner exception. ---> 
System.Net.Http.WinHttpException: The connection with the server was 
terminated abnormally
   --- End of inner exception stack trace ---

Complete stack trace here: https://pastebin.com/BGny5ULG

The code (.net core 2) is as follows:

    private async Task S3UploadFileAsync(string fileName, Stream stream)
    {
        using (IAmazonS3 client = new AmazonS3Client(Amazon.RegionEndpoint.EUWest2))
        {
            var uploadRequest = new TransferUtilityUploadRequest
            {
                InputStream = stream,
                BucketName = "******-*****",
                CannedACL = S3CannedACL.AuthenticatedRead,
                Key = fileName
            };
            TransferUtility fileTransferUtility = new TransferUtility(client);
            try
            {

                await fileTransferUtility.UploadAsync(uploadRequest);
            }
            catch (System.Exception e)
            {
                throw e;
            }

        }
    }

The above code works fine when running on my local machine (Windows 10), just not on the EC2 instance (Windows Server 2016).

I've tried making the S3 bucket public, thinking it was a permission issue (still not working).

I thought it might be an issue with the windows firewall or the EC" instance security groups so I installed the AWS CLI and can upload to the S3 instance using that with no problems.

It doesn't matter what I upload, I've tried large, small and even empty files.

It takes around 30 seconds before the exception is caught, so it feels like something is timing out. Changing the code to a non-existent BucketName results in the same symptoms making me think it's got nothing to do with the bucket configuration (I've starred out the name).

Any help with suggestions for things to try would be appreciated - I've been working on this all day and I'm running out of ideas... Thanks!

Update: similar errors here suggest it's permissions related: https://matt40k.uk/2017/09/s3-errors/

The Update section saved my day: I got the wrong key/secret combination. Thanks, man! — Tamas, Oct 17 '18 at 12:52

score 2 · Answer 1 · answered May 17 '18 at 04:40

2

I expirienced the same issue while uploading file to S3 with ASP.NET Core 2.0 application and hope it might be helpful for someone. In my case the cause of exception was incorrect region parameter in constructor of AmazonS3Client.

var amazonS3Client = new AmazonS3Client(awsCredentials, Amazon.RegionEndpoint.USEast1);

So I share the thoughts of question's author that AWS .NET SDK doesn't provide well-formed detailed error messages.

answered May 17 '18 at 04:40

OL.

201
3
13

definitely bad error message. my problem was the wrong key / secret params, not the region... – Tamas Oct 17 '18 at 12:53
You are right, my Region was Ohio, therefore, I had to use Amazon.RegionEndpoint.USEast2 – mejiamanuel57 Nov 08 '18 at 21:10

Meurig · Accepted Answer · 2018-03-07T13:56:18.607

The issue appears to be related to permissions on the S3 bucket, if I comment out the following line the upload works:

CannedACL = S3CannedACL.AuthenticatedRead,

It's still not perfect, as without that line my app can't then download the file it's just uploaded - but at least I now know where to focus my efforts!

Ultimately this is looking like an issue with the AWS .NET SDK for not providing better error messages. I've opened an issue here: https://github.com/aws/aws-sdk-net/issues/890

Update: The underlying permission issue was eventually fixed by adding the AmazonS3FullAccess Policy to the aws-elasticbeanstalk-ec2-role as suggested in a comment here: Grant S3 access to Elastic Beanstalk instances

score 0 · Answer 3 · answered Nov 23 '18 at 05:23

I had the same problem when trying to upload images, i commented out the following line and the upload worked:

CannedACL = S3CannedACL.PublicRead

In my case the problem was the access permission for the bucket itself, it didn't allow public objects. I updated it to allow public objects and it worked. Hope it helps.

"The connection with the server was terminated abnormally" when uploading to to S3 TransferUtility.UploadAsync on EC2 instance

3 Answers3