nx-s3-plugin v1.0.7

nx-s3-plugin

This is an NX executor that can be used to make changes to remote S3 buckets.

Installation

Install the plugin in to your already configured NX workspace

npm i nx-s3-plugin

Executors

sync

The sync executor is similar to the aws s3 sync command. It will run a diff between local files and files contained in S3, and make S3 reflect the local directory. This can be very performant because only files which have changed will be uploaded. Bucket name can also be dynamically looked up from existing CloudFormation exports or SSM Parameters.

Uploaded Bucket Object content-type

This plugin uses mime-types to make a best guess at file mime types as they are uploaded to S3. This means your files should arrive in S3, ready to be served as a static assets without having to manually define the types.

AWS Credentials

The standard AWS credential chain of precedence is followed when making AWS calls. @aws-sdk/credential-provider-node is used to to load these values, so that documentation should be used when setting up AWS credentials. In most cases, simply having the proper environment variables or valid credentials in your ~/.aws/credentials file should be enough to get going. There is an optional profile argument that can be used if you wish to use a non-default set of credentials.

Properties

Usage

You do not need to add s3:// to bucketName, your CloudFormation export value, or your SSM parameter value. This plugin will add it for you.

Add the executor to the target section of project.json.

  "targets": {
    "upload-site": {
      "executor": "nx-s3-plugin:sync",
      "options": {
        "sourceFiles": "<source-directory>",
        "bucketName": "[cfe|ssm]:<target-bucket>",
      }
    }
  }

Static S3 Bucket Name

If you are directly targetting an S3 bucket, you can simply enter the name of the S3 bucket as the bucketName parameter in the NX task definition.

  "targets": {
    "upload-site": {
      "executor": "nx-s3-plugin:sync",
      "options": {
        "sourceFiles": "/my-compiled-website-files",
        "bucketName": "my-s3-bucket",
      }
    }
  }

Dynamic Cloudformation Export Lookup

If you prepend your bucketName with cfe:, this executor will attempt to locate a CloudFormation export with the same name. Omitting the cfe: prefix will simply use the bucketName value as is for the S3 url.

• If an export is found with a matching name, the value will be used for the S3 destination bucket.
• If an export is not found, an error will be thrown and no files will be uploaded.
• Matching is case-sensitive.
• This export must exist in the same account as the S3 bucket.
  • Cross-account lookup is not supported.

Example:

cfe:StaticWebSite will query CloudFormation for an export named StaticWebSite and use the value of that export as the bucketName.

  "targets": {
    "upload-site": {
      "executor": "nx-s3-plugin:sync",
      "options": {
        "sourceFiles": "/my-compiled-website-files",
        "bucketName": "cfe:StaticWebSite",
      }
    }
  }

Dynamic SSM Paramter Store Lookup

If you prepend your bucketName with ssm:, this executor will attempt to locate a SSM Paramter with the same name. Omitting the ssm: prefix will simply use the bucketName value as is for the S3 url.

• If an SSM Parameter is found with a matching name, the value will be used for the S3 destination bucket.
• If an SSM Parameter is not found, an error will be thrown and no files will be uploaded.
• Matching is case-sensitive.
• This SSM Parameter must exist in the same account as the S3 bucket.
  • Cross-account lookup is not supported.

Example:

ssm:/myapp/s3bucket will query for an SSM Parameter named /myapp/s3bucket and use the value of that export as the bucketName.

  "targets": {
    "upload-site": {
      "executor": "nx-s3-plugin:sync",
      "options": {
        "sourceFiles": "/my-compiled-website-files",
        "bucketName": "ssm:/myapp/s3bucket",
      }
    }
  }