AWS Maven Wagon

Description

This project is a fork of a Maven Wagon which is also a fork of the original AWS Maven for Amazon S3.

Why this fork?

• to support Server Side Encryption and more
• don't understand why s3 "directories" have to be PUBLIC_READ.
• hopefully for a pull request into platform-team's aws-maven.

Usage

To publish Maven artifacts to S3 a build extension must be defined in a project's pom.xml. The latest version of the wagon can be found on the aws-maven page in Maven Central.

<project>
  ...
  <build>
    ...
    <extensions>
      ...
      <extension>
        <groupId>com.github.lpezet</groupId>
        <artifactId>aws-maven</artifactId>
        <version>6.0.0</version>
      </extension>
      ...
    </extensions>
    ...
  </build>
  ...
</project>

Once the build extension is configured distribution management repositories can be defined in the pom.xml with an s3:// scheme.

<project>
  ...
  <distributionManagement>
    <repository>
      <id>aws-release</id>
      <name>AWS Release Repository</name>
      <url>s3://<BUCKET>/release</url>
    </repository>
    <snapshotRepository>
      <id>aws-snapshot</id>
      <name>AWS Snapshot Repository</name>
      <url>s3://<BUCKET>/snapshot</url>
    </snapshotRepository>
  </distributionManagement>
  ...
</project>

AWS Credentials

Credentials to use for AWS S3 Client can be specifie in different ways:

• in ~/.m2/settings.xml when defining servers for snapshot and release repositories. The access key should be used to populate the username element, and the secret access key should be used to populate the password element.
• aws.accessKeyId and aws.secretKey system properties
• AWS_ACCESS_KEY_ID (or AWS_ACCESS_KEY) and AWS_SECRET_KEY (or AWS_SECRET_ACCESS_KEY) environment variables
• The Amazon EC2 Instance Metadata Service

Finally the ~/.m2/settings.xml must be updated to include access and secret keys for the account. The access key should be used to populate the username element, and the secret access key should be used to populate the password element.

AWS STS (MFA)

If using MFA, it's possible to have AWS S3 Client pick up the profile from your local ~/.aws/credentials file. In this use case, don't specify username and password in your ~/.m2/settings.xml. Best is to store AWS STS info into a profile and specify the profile as environment variable. For example:

$ aws-mfa myprofile 123456
$ env AWS_PROFILE=myprofile-mfa AWS_REGION=us-east-1 mvn clean deploy

where aws-mfa is a script that would use AK and SK from profile myprofile to request a session token and store the results in ~/.aws/credentials under profile myprofile-mfa.

settings.xml

<settings>
  ...
  <servers>
    ...
    <server>
      <id>aws-release</id>
      <username>0123456789ABCDEFGHIJ</username>
      <password>0123456789abcdefghijklmnopqrstuvwxyzABCD</password>
      <configuration>
        <sse>true</sse> <!-- (optional) whether or not to use server-side encryption (sse) -->
		<sseAlgorithm>AES256</sseAlgorithm> <!-- (optional) algorithm to use for sse. Either AES256 or aws:kms -->
		<sseBase64Key>ABCDEF1234567890</sseBase64Key> <!-- (optional) base64 encoded key to use for sse when not using sseAlgorithm -->
      </configuration>
    </server>
    <server>
      <id>aws-snapshot</id>
      <!-- see above -->
      ...
    </server>
    ...
  </servers>
  ...
</settings>

Connecting through a Proxy

For being able to connect behind an HTTP proxy you need to add the following configuration to ~/.m2/settings.xml:

<settings>
  ...
  <proxies>
     ...
     <proxy>
         <active>true</active>
         <protocol>s3</protocol>
         <host>myproxy.host.com</host>
         <port>8080</port>
         <username>proxyuser</username>
         <password>somepassword</password>
         <nonProxyHosts>www.google.com|*.somewhere.com</nonProxyHosts>
     </proxy>
     ...
    </proxies>
  ...
</settings>

Making Artifacts Public

This wagon doesn't set an explict ACL for each artifact that is uploaded. Instead you should create an AWS Bucket Policy to set permissions on objects. A bucket policy can be set in the AWS Console and can be generated using the AWS Policy Generator.

In order to make the contents of a bucket public you need to add statements with the following details to your policy:

Effect	Principal	Action	Amazon Resource Name (ARN)
Allow	*	ListBucket	arn:aws:s3:::<BUCKET>
Allow	*	GetObject	arn:aws:s3:::<BUCKET>/*

If your policy is setup properly it should look something like:

{
  "Id": "Policy1397027253868",
  "Statement": [
    {
      "Sid": "Stmt1397027243665",
      "Action": [
        "s3:ListBucket"
      ],
      "Effect": "Allow",
      "Resource": "arn:aws:s3:::<BUCKET>",
      "Principal": {
        "AWS": [
          "*"
        ]
      }
    },
    {
      "Sid": "Stmt1397027177153",
      "Action": [
        "s3:GetObject"
      ],
      "Effect": "Allow",
      "Resource": "arn:aws:s3:::<BUCKET>/*",
      "Principal": {
        "AWS": [
          "*"
        ]
      }
    }
  ]
}

If you prefer to use the command line, you can use the following script to make the contents of a bucket public:

BUCKET=<BUCKET>
TIMESTAMP=$(date +%Y%m%d%H%M)
POLICY=$(cat<<EOF
{
  "Id": "public-read-policy-$TIMESTAMP",
  "Statement": [
    {
      "Sid": "list-bucket-$TIMESTAMP",
      "Action": [
        "s3:ListBucket"
      ],
      "Effect": "Allow",
      "Resource": "arn:aws:s3:::$BUCKET",
      "Principal": {
        "AWS": [
          "*"
        ]
      }
    },
    {
      "Sid": "get-object-$TIMESTAMP",
      "Action": [
        "s3:GetObject"
      ],
      "Effect": "Allow",
      "Resource": "arn:aws:s3:::$BUCKET/*",
      "Principal": {
        "AWS": [
          "*"
        ]
      }
    }
  ]
}
EOF
)

aws s3api put-bucket-policy --bucket $BUCKET --policy "$POLICY"

Release process

Create release and upload artifacts (jar, javadoc and source code) to OSS Sonatype (Nexus):

mvn clean release:prepare
mvn release:perform

Go to OSS Sonatype and check Staging Repository and make sure everything is there (i.e. source code, artifact, and javadoc). Click Close to close repository and go through verification process. If failed, Drop repository and address issues (might want to delete git tags, revert versions, etc.). If succeeded, Release repo.

Release Notes

• 6.0.0
  • Updated to the latest versions of aws-sdk and maven-wagon.
  • Changed order of aws credential resolution strategy.
  • Added support of all regions defined in aws-sdk.

License

Copyright 2018-Present LPezet.

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.