TrustFailure Error Thrown When Using AWS Powershell - powershell

Question

I am trying to use AWS powershell to update metadata for items in my S3 bucket. I am using the script:
Set-AWSCredentials -ProfileName S3Test ;
write-S3Object -BucketName myS3bucket `
-Key Folder/Subfolder/Myfile.txt `
-Content "Myfile.txt `
-Metadata #{"x-amz-meta-custommetadata" = "TESTMEtadata"} `
-Headers #{"Content-Type" = "binary/octet-stream"} ;
I am able to run this script successfully from my own account on my computer but when I try to automate this script using a service account I am getting the error message:
write-S3Object : A WebException with status TrustFailure was thrown.
At line:1 char:1
+ write-S3Object -BucketName myS3Bucket `
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation:
(Amazon.PowerShe...eS3ObjectCmdlet:WriteS3ObjectCmdlet) [Write-S3Obje
t], InvalidOperationException
+ FullyQualifiedErrorId :
Amazon.Runtime.AmazonServiceException,Amazon.PowerShell.Cmdlets.S3.WriteS3ObjectCmdlet
From what I have found on similar issues I tried to add this line to my script:
[System.Net.ServicePointManager]::ServerCertificateValidationCallback = {$true} ;
However this results in a different error message:
write-S3Object : A WebException with status RecieveFailure was thrown.
At line:1 char:1
+ write-S3Object -BucketName myS3Bucket `
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation:
(Amazon.PowerShe...eS3ObjectCmdlet:WriteS3ObjectCmdlet) [Write-S3Obje
t], InvalidOperationException
+ FullyQualifiedErrorId :
Amazon.Runtime.AmazonServiceException,Amazon.PowerShell.Cmdlets.S3.WriteS3ObjectCmdlet
Does anyone have any idea what may be causing these problems and how I would be able to resolve them?

Answer 1

It seems liken a callback is run using what is defined in:
[System.Net.ServicePointManager]::ServerCertificateValidationCallback = {$true}
I'm not exactly sure what triggers it based off of what I read but the callback seems to be set on service accounts.
Try setting it to:
[System.Net.ServicePointManager]::ServerCertificateValidationCallback = $null
Reference:
https://forrestbrazeal.com/2015/06/15/adventures-in-aws-the-worlds-scariest-stack-trace/

Answer 2

Check your date on the server.
I had the same error accessing AWS endpoints, but the solution was a touch simpler... I was testing a process where I set the date on the server back a couple of months, which caused the AWS connection process to throw the request out.