ed3899 / kumo Goto Github PK

It looks like git is a common dependencie across the board. We might as well add it to the base

Clarify that the destroy script does not remove the AMI.
It is up to you to delete that from AWS.

Removing it from pulumi may introduce complex workflows and potential confusions when dealing with multiple AMIs.

Pulumi is only concerned with deploying an AMI.

May be add an additional env variable that allows you
to pick a specific one.

That way you could create multiple AMIs from packer but
only pick the one that best suits your needs

Ensure it runs to completion

Add the homebrew playbook

Password should be hashed on user.yml

Install aws cli with credentials from a vault

Ensure linux aliases playbook runs to completion

• User must have restricted non-root access
• It should automatically generate ssh key pair and place the private keys into the root dir of the local machine
• Environment variables should be used to get the username

https://code.visualstudio.com/docs/remote/tunnels#_using-the-code-cli

it basically allows a single user to remote tunnel into a machine without ssh keys

Requirements:

• An ssh config file should be generated once the up workflow is completed.
  Example:

    ```ssh_config
    Host cloud_dev
      HostName 52.10.25.215
      IdentityFile "D:\Documents\DevEnvironments\Cloud\Jammy64\ssh_key"
      User dev
      User 22
      UserKnownHostsFile /dev/null
      StrictHostKeyChecking no
      PasswordAuthentication no
      IdentitiesOnly yes
      LogLevel FATAL
    ```
  

• The file should be place at the root of the project.

• The file should be removed after the destroy workflow

• The file should have readonly permissions

Installed tags should be visible from the AMI

Go seems to be the go to language (no pun intended)
if we would want cross OS compatibility. Lots of cloud apps are written in Go so it makes sense if we want to attract contributors.

We could embed packer and pulumi binaries, use pulumi go sdk and compile all of that in a single binary specific for both Windows and MacOs archs.

Rust was considered but there is not pulumi sdk for that yet(it may also be overkill), Java is kind of outdated and unneccesarily verbose for our purposes, C# is verbose and adds the complexity of dealing with the
dotnet ecosystem lingo.

That way we can add to path, things are downloaded only in one place and the user is only concerned with a kumo.config.yml and an ssh config at his cwd

Find a way to generate an ssh key based on:

{cloud}-{ ami-name }-{timestamp}

Some of the validations are stacked. they should be split for easier debugging

Use ginkgo

Some variables don't need to be sensible

• Users should be able to list the ami's they have built based on the current kumo config
• They should be able to remotely delete them if desired
• Confirmation required
• If they are deleted delete their corresponding ssh key file. Maybe tags would be needed to associate and readonly for the ssh key to not be removed by the user. Optional?

We no longer need it, an ssh config is generated on the up workflow by terraform

Ensure there always at least two instances. In case one fails

The ec2 should go to sleep after a period of inactivity

Make sure to timeout after a predifined time

Automate the process via a script

Alternatives

In Japanese, the word for "cloud" is 雲 (くも, kumo).
In Japanese, the translation of "ethereal" is "幽玄" (yūgen).