nx powerpack s3 cache - custom aws environment variable name

[YoonjiJang]

i want to be able to use a different environment names, other than AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY and configure it in nx.json. e.g.

{
  "s3": {
    "region": "us-east-1",
    "bucket": "my-bucket",
    "accessKeyId": "$CUSTOM_AWS_ACCESS_KEY_ID",
    "secretAccessKey": "$CUSTOM_AWS_SECRET_ACCESS_KEY"
  }
}

i have multiple aws credentials for different parts of my ci/cd pipeline. plus, some providers such as netlify reserve the default environment variable names.

it doesn't look like this option is available as of powerpack-s3-cache v1.2.5. it'd be great if this can be added soon.

[Michsior14]

I have the same issue with the free version of the plugin (@nx/s3-cache). I would like to distribute the credentials via plugin (not for security or anything, just convenience) and using AWS_ACCESS_KEY_ID /AWS_SECRET_ACCESS_KEY pollutes the process environment variables when serving apps. FYI @vsavkin

[TheSpyder]

I'm part of a multi-region team and we chose to use region-specific buckets for our S3 cache. Developers in each region tend to work together so sharing caches is most important within a region to reduce latency. There's a separate bucket for CI that developers can't write to and is replicated to each region to pre-populate caches as much as possible.

We're using @pellegrims/nx-remotecache-s3 which makes this easy by allowing any option to be set through an environment variable instead of only in nx.json. We configure both region and bucket through our .env file.

I'm investigating whether we can switch to @nx/s3-cache after the recent announcement, but it won't work for us without this flexibility.

[buildiumben]

Same issue here, my company is planning to have a trusted bucket in our AWS prod environment that only our build process can read/write to and it would then be replicated into a bucket in our AWS dev environment that devs would be able to read from in their local builds. Our prod and dev environments are in different regions currently.

It seems like support for reading credentials through the AWS SDK was added but region is still required to be hard-coded.

Not having support for reading the region from pre-configured AWS environment variables that are standard, or just any environment variable, makes it seem like we will have to use a third-party plugin for caching.