Is your feature request related to a problem? Please describe.
For whatever reason, when you use cdk to create an ssh_key_pair, it's impossible to give a descriptive name/description/whatever. We're lucky since we use only one, it could be the only one in the account if no other "user projects" has any. But it'd be nice to separate ours from the rest.
Describe the solution you'd like
Somehow keep ssh keys unique in the aws console.
Describe alternatives you've considered
I've asked for advice here with no luck yet.
I swear I've tried the params here too, but it's been a while. Maybe they only take place on creation, not replace? Also there's a key-pair listed in ec2 key-pair, but it's actually stored in ssm param manager. Maybe those flags only affect one, and I checked the wrong one? It's been a bit, and this isn't MVP, so I'm planning on coming back another time.
Is your feature request related to a problem? Please describe. For whatever reason, when you use cdk to create an ssh_key_pair, it's impossible to give a descriptive name/description/whatever. We're lucky since we use only one, it could be the only one in the account if no other "user projects" has any. But it'd be nice to separate ours from the rest.
Describe the solution you'd like Somehow keep ssh keys unique in the aws console.
Describe alternatives you've considered I've asked for advice here with no luck yet.
I swear I've tried the params here too, but it's been a while. Maybe they only take place on creation, not replace? Also there's a key-pair listed in
ec2 key-pair
, but it's actually stored in ssm param manager. Maybe those flags only affect one, and I checked the wrong one? It's been a bit, and this isn't MVP, so I'm planning on coming back another time.Additional context N/A