wybuild.cmd.exe /upload to Amazon S3 fails intermittently with Error mentioning Amazon S3 will stop supporting TLS 1.0 and TLS 1.1

My wybuild.cmd.exe is v2.6.18.4

When I run wybuild.cmd.exe “C:\MyProject.wyp” /upload

I am intermittently seeing this response:
Uploading updates: Failed
[Error]: Failed to upload file '[Filename].wyu': Amazon S3 will stop supporting TLS 1.0 and TLS 1.1 connections. Please update your client to use TLS version 1.2 or above. To learn more and to update your client, see https://go.aws/3AUlVSb. For further assistance, contact AWS support.. Skipping the next 1 files.

But retry a few times and it will succeed without mentioning Amazon S3

I'm running this command as part of our CI pipeline and going back through build logs, I think it only started occurring 7th July.

Anyone understand the cause and why it is intermittent?

, edited

Amazon uses non-standards and we’re dropping support for them in the next release. We’ll only support SFTP and FTP.

Use Cyberduck to upload using proprietary protocols.

Thank you for your reply. I understand that you'll be dropping support for Amazon's non-standard protocols in the next release in favor of SFTP and FTP. However, I'm still trying to get to the bottom of the intermittent upload failures we've been experiencing.

I see you mentioned in older posts that wyUpdate supports TLS 1.2 when using the .NET 4.0 version of wyUpdate, which we are indeed using. My understanding, therefore, is that the changes Amazon is making to retire TLS 1.0 and 1.1 as outlined in https://go.aws/3AUlVSb, shouldn't affect us as our configuration should already be compatible with TLS 1.2.

Is this correct, or might there still be a risk for us? Specifically, could the intermittent upload error we're experiencing - the one indicating that TLS 1.0 and 1.1 are no longer supported - be a sign that we will eventually lose the ability to upload altogether once Amazon finishes retiring TLS 1.0 and 1.1 by December 31, 2023?

Or, is it more likely that we can continue to work around this error with retries, assuming it's caused by something other than the TLS version? I'm trying to understand the root cause and assess our future risk.

, edited

FYI for anyone reading this, in my case I resolved the upload issues by writing my own C# code to perform the S3 upload of files using the AWSSDK classes TransferUtility and TransferUtilityUploadRequest 

Reply
Discard post