oxidecomputer / oxidecomputer/buildomat
xtask-setup: configure use of SSH keys
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 72
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
Right now, xtask-setup configures the security group it creates to only allow SSH access from EC2 Instance Connect. The service works great on Linux (and allows us to have zero ports exposed to the public internet), but requires an agent that is not available on illumos.
We should consider how to enable SSH keys in xtask-setup for use within illumos:
- Should those be always configured, or should it be an option the user has to choose during setup? I kinda like that right now by default there are zero ports exposed for CI jobs.
- Other than enabling port 22 in the security group, should it configure the SSH key?
- If it configures the SSH key, should it do it through buildomat or through EC2's cloud-init?
- Which SSH key should it pick?
Contributor guide
No contributing guide indexed for this repository
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 at the xtask-setup entry point and inspect how it creates the security group and enables EC2 Instance Connect. Compare the SSH-key options raised here, including port 22, buildomat versus cloud-init, and key selection for illumos. Done requires a decided configuration policy and an agreed provisioning approach.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, rust
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100