Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

make moduleKeyName configurable in kmsCryto.js

Open
#217 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
50/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Stale
Tech stack
aws, javascript
Domain
cloud, security

Research direction

Open kmsCrypto.js and locate the moduleKeyName declaration. Check how the KMS key name is used, then verify that S3_REDSHIFT_LOADER_KMS_KEY_NAME can override the default alias while the existing alias remains the fallback. Done means the configurable name is used without changing the default behavior.

Written by the indexing model from the issue text.

Description

Could anyone helping me making a quick change?
In kmsCrypto.js file,
change
var moduleKeyName = "alias/LambdaRedshiftLoaderKey";
to
var moduleKeyName = process.env.S3_REDSHIFT_LOADER_KMS_KEY_NAME || "alias/LambdaRedshiftLoaderKey";

I have a requirement to use the different name for the key...thanks...
This is urgent, it would be nice if someone could help ASAP. thanks.....

Dominant language
JavaScript
Stars
595
Forks
161
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from awslabs/aws-lambda-redshift-loader

All issues in awslabs/aws-lambda-redshift-loader

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.