aws-cloudformation / aws-cloudformation/cloudformation-coverage-roadmap

Allow the parameter store which contains the private portion of a dynamically generated AWS::EC2::KeyPair to be KMS encrypted with a specific key

Open
#1,163 0 comments 1 reaction 0 assignees View on GitHub
enhancement
Dominant language
No language data
Stars
1.1k
Forks
62
PR merge metrics
No merged PRs in 30d

Description

### Name of the resource

Other

### Resource name

AWS::EC2::KeyPair

### Description

We are very happy we're able to have CloudFormation autogenerate and maintain an SSH key public/private pair. When the private half gets shipped off as a securestring to the parameter store, it is encrypted with the account-wide alias/aws/ssm KMS key.

It would be great if we could define the KMS that is used for encrypting the value in the parameter store so we can scope the access to the key to only resources associated with a user or application that relate to the EC2 key itself.

### Other Details

_No response_

Contributor guide

Open the contributing guide

Research direction

The issue concerns AWS::EC2::KeyPair, Systems Manager Parameter Store, and KMS, but names no repository files, tests, or implementation entry points. Start by reviewing the CloudFormation resource behavior and related AWS service documentation; done would mean supporting a user-specified KMS key for encrypting the generated private key in Parameter Store.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
cloud, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.