Re: [PATCH v4 1/8] aws: prevent SSH key conflicts across multiple kdevops directories

On 9/16/25 5:34 PM, Luis Chamberlain wrote:
> Benefits:
> - Prevents accidental key overwrites in AWS backend
> - No more lockouts from existing instances when using multiple directories
> - Backward compatible - users can still use shared keys if needed
> - Consistent with Lambda Labs implementation pattern
> - Each directory's instances are isolated with their own SSH keys
> 
> Example:
> Directory: /home/user/projects/kdevops
> AWS Key Name: kdevops-aws-projects-kdevops-a8999659
> Local Keys: ~/.ssh/kdevops-aws-projects-kdevops-a8999659[.pub]
> 
> This ensures that running kdevops from different directories will never
> conflict, as each gets its own unique key name in both AWS and locally.
> 
> Generated-by: Claude AI
> Signed-off-by: Luis Chamberlain <[email protected]>

I did something like this by hand, using the pathname configured
in the existing terraform ssh config menu. It's definitely a
problem.

But seems like this might be an issue for all the cloud providers, so
maybe this idea could be applied in the generic terraform ssh config
menu instead of making it specific to AWS and Lambda? But I might be
missing something.

-- 
Chuck Lever