serverless / serverless/serverless
Support aliases at "provider.kmsKeyArn" and "functions[].kmsKeyArn"
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 46.9k
- Forks
- 5.7k
- Avg merge
- 10h 7m
- Merged PRs (30d)
- 57
Description
This is a Bug Report
Description
I would like to use a key alias for awsKmsKeyArn:
service:
name: foo
awsKmsKeyArn: arn:aws:kms:eu-west-1:<account>:alias/<label>
What happens is: CloudFormation hangs :-( After about 30 minutes it terminates with UPDATE_FAILED: "Lambda was unable to configure access to your environment variables due to an internal service error" and rolls back.
This might be a bug in CloudFormation itself, but would be good if could be worked around.
Moved from: #3672
Additional Data
- Serverless Framework Version you're using: 1.21.0 (with serverless-wsgi 1.3.0)
- Operating System: Ubuntu 16.04
- Stack Trace: n/a
- Provider Error messages: as above
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how provider.kmsKeyArn and functions[].kmsKeyArn are processed, then reproduce the reported configuration with an AWS KMS alias. Done means both configuration paths accept aliases and deploy without the CloudFormation environment-variable failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100