Proposed workflow on dealing with user permissions about quickstart-linux-bastion HOT 5 CLOSED

Got it. There's two components here. The obvious one is adding support for user-input of multiple usernames / SSH keys. That's the easy / straight forward part.

The more involved part is scaling the bastion quickstart to handle multiple users. Not impossible. I'll look into what it'd take to make this happen. We consider the Bastion quickstart to be 'foundational' because we include it as a submodule in a number of other quickstarts, so we're especially cautious to major changes. This just means more thorough vetting and perhaps a longer development lifecycle.

Of course - the repo is on github, so if you have the time / inclination to contibute, pull-requests are always welcome.

from quickstart-linux-bastion.

We're circling back on this. For the studio audience, the current thought is to leverage SSM Parameter Store and SecretStore to hold the user definitions / ssh keys / MFA (if we get that far).

from quickstart-linux-bastion.

@McKean. I'm less treating this as a General Guidance, and more of a Feature Request. In your use-case, would the keypairs be in EC2, or are you populating them via external sources? There are a few ways to accomplish this, but I'm trying to gather the specifics around your ideal configuration.

from quickstart-linux-bastion.

@agamzn thanks for your reply.
well ideally one could specify a text file with {username} {pubkey} per line, and this will generate usernames with key on the bastion. So yeah the keypairs would be in EC2 in the end. But could originate from an S3 bucket.

from quickstart-linux-bastion.

Tagged for v2.2

Roadmap/Progress can be tracked here

from quickstart-linux-bastion.