I have been trying to do the same. After half a day of trying… I found this very interesting discussion -> https://github.com/gradle/gradle/issues/1464. And here the author mentions a property that you need to set “-Dorg.gradle.s3.endpoint=https://nyc3.digitaloceanspaces.com”.

publishing {
    repositories {
        maven {
            url "s3://if-mvn"
            credentials(AwsCredentials) {
                accessKey "access"
                secretKey "secret"
            }
        }
    }
}

Long story short: the url you set in publishing.repositories.maven is actually the bucket.

Are you able to change the S3 API signature? Try versions 2 and 4 and see if you have any success.

Were you ever able to solve this issue? There is the s3-wagon-private which works for Leiningen but ‘should’ work if you use the 's3p://’ urls.

If you’re looking for a managed solution that leverages S3 for storage, I founded CloudRepo which offers Private Maven Repositories and we store all the artifacts in S3.

If you need something above this type of support, please let me know - we’re always looking for new ways to improve and help people in the community.

As mentioned in here you have to set following property in your gradle.properties file:

systemProp.org.gradle.s3.endpoint

An example for the Frankfurt location would be

systemProp.org.gradle.s3.endpoint=https://fra1.digitaloceanspaces.com

Then yo can specify your repo as specified by the official Gradle documentation