wip

[morga471]

No description provided.

[morga471]

Recapping some of the conversation between Myself and Bryan Sylvis. Jason S. is following up on a request by Jamie C. for a get-well plan for iebcloud. Bryan Sylvis reached out to me on this topic. I have started a document and jotted down a few ideas as included in this PR.

Bryan wants to not use RHEL (licensing costs) but wants to know how we would manage whatever solution we intend.
He was more concerned about security and control, then usability (IMO). He conceptually prefers a single desktop environment to reason about as opposed to allowing developers to manage a development environment for themselves.

We have a lot of leeway in suggestions here, this is an opportunity to define what we want to manage and how access patterns for cloud resources should happen.

I'm not against the EKS cluster path.

We could consider something like an ECS Service with a Task Container per user per session.

We could do AWS Workspaces with Amazon Linux 2023. ----> I think this is the best path based on constraints, but I'm probably overlooking something.

We should additionally consider how the "Jump Host" pattern will be used as teams migrate to the cloud, standardize its use patterns, formally answer the application container development location, etc.