AWS Credential failure during S3 deploy

[corrylc]

Deploy is no longer possible when using AWS SSO profiles. This appears to be related to changes in AWS CLI and may have a fix in the upstream aws-sdk-go, see also aws/aws-sdk-go#4649 and hashicorp/terraform#32448

I encountered the same error in Terraform this morning, and was forced to update to resolve the issue. It appears that Hugo needs a similar update.

Some redactions done to protect environment names, but the output is the real error I get when running the command which worked a week ago.

% AWS_PROFILE=sso-profile-name hugo deploy --dryRun
Deploying to target "s3" (s3://bucket-name?region=us-east-1)
Error: blob (code=Unknown): NoCredentialProviders: no valid providers in chain. Deprecated.
	For verbose messaging see aws.Config.CredentialsChainVerboseErrors

What version of Hugo are you using (hugo version)?

$ hugo version
hugo v0.120.4-f11bca5fec2ebb3a02727fb2a5cfb08da96fd9df+extended darwin/arm64 BuildDate=2023-11-08T11:18:07Z VendorInfo=brew

Does this issue reproduce with the latest release?

Yes

[bep]

I merged an update in #11724 -- I don't have time to test this particular issue, so I'll leave this open until others can confirm. I will cut a release early next week.

[corrylc]

Thanks! I am not too familiar with go, but I did try the following, and the issue appears to be fixed!

CGO_ENABLED=1 go install -tags extended github.com/gohugoio/hugo@d528bbd6d0e63bb366ea8a3e95042f771c17817a
AWS_PROFILE=profile-name ~/go/bin/hugo deploy --dryRun

The SHA was HEAD at the time of my test, wasn't sure how to specify the head of the master branch.

Thanks for the quick fix!

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.