Deploying Maven Artifacts to AWS S3 but getting issue of Signature Version 4 Authentication

[ibankang]

Hi everyone,

I am trying to deploy Maven project JARs and artifacts to an AWS S3 bucket using the following extension in my pom.xml:

org.springframework.build aws-maven 5.0.0.RELEASE

//Deploy Path


s3-releases
s3://your-bucket-name/maven-releases


I have also configured my AWS credentials in settings.xml under as follows:

aws-s3-deploy ${env.AWS_ACCESS_KEY_ID} ${env.AWS_SECRET_ACCESS_KEY} However, when I run the mvn clean deploy command, I get the following error:

Status Code: 400, AWS Service: Amazon S3, AWS Request ID: ,
AWS Error Code: InvalidRequest,
AWS Error Message: The authorization mechanism you have provided is not supported.
Please use AWS4-HMAC-SHA256.
From my research, this issue occurs because AWS S3 now requires Signature Version 4 (AWS4-HMAC-SHA256) for authentication, and the aws-maven plugin does not support it.

Questions:

1. What is the current best approach to deploy Maven artifacts to an AWS S3 bucket?
2. Are there any updated Maven plugins that support AWS Signature Version 4 for S3 deployment?
3. Has anyone successfully deployed Maven artifacts to AWS S3 using modern authentication methods?
   Any guidance or alternative solutions would be greatly appreciated!

I Tried:
I explored multiple approaches for deploying Maven artifacts to AWS S3, aiming to find a modern, working solution since older plugins (like aws-maven and s3-wagon) do not support AWS Signature Version 4.

What I Tried:

1. aws-maven (Spring Plugin) → Failed

Added:


org.springframework.build
aws-maven
5.0.0.RELEASE


Error: AWS4-HMAC-SHA256 required → This plugin does not support AWS Signature V4.

2. s3-maven-plugin → Not Found

Tried using:

com.github.platform-team
s3-maven-plugin
2.0.0

Error: Could not find artifact in Maven Central → This plugin is either outdated or unavailable.

3. s3-wagon → Not Found

Tried:

org.carlspring.maven
s3-wagon
1.3.1

Error: Artifact not found in Maven Central.

4. AWS CodeArtifact (Works, but Different)

CodeArtifact is not an S3 bucket, but a managed repository service.
Artifacts are stored internally in S3, but you cannot access them directly as S3 objects.
Requires authentication with AWS CLI.

What I Expected:
A working Maven plugin to directly deploy artifacts to an S3 bucket like a Maven repository.
A solution that supports AWS Signature Version 4 (AWS4-HMAC-SHA256).
A modern alternative to outdated/unmaintained plugins.

Let me know which approach you prefer!