Skip to content

Document targeting Amazon ECS tasks through the operator-hosted sessions-manager - #402

Draft
itsamegraf wants to merge 3 commits into
mainfrom
ecs-operator-hosted-sessions-manager
Draft

itsamegraf wants to merge 3 commits into
mainfrom
ecs-operator-hosted-sessions-manager

Conversation

@itsamegraf

Copy link
Copy Markdown

Add an overview of mirrord for ECS (developer config, connection flow,
limitations) and a setup runbook for platform teams: the
operator.sessionsManager Helm value, the mirrord-operator-sessions-manager-agent
binding, the EKS access entry, the Transit Gateway and DNS path, and the
ECS task definition changes.

Describe how ECS workloads authenticate to the Operator in the security
docs, add the sessionassignments and sessiondataplanes resources to the
RBAC section, and point to the setup from the Operator install page.

Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com

itsamegraf and others added 3 commits October 2, 2026 17:05
…ons-manager

Add an overview of mirrord for ECS (developer config, connection flow,
limitations) and a setup runbook for platform teams: the
operator.sessionsManager Helm value, the mirrord-operator-sessions-manager-agent
binding, the EKS access entry, the Transit Gateway and DNS path, and the
ECS task definition changes.

Describe how ECS workloads authenticate to the Operator in the security
docs, add the sessionassignments and sessiondataplanes resources to the
RBAC section, and point to the setup from the Operator install page.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Introduce deployment modes for remote workloads: Operator-hosted, where
sessions-manager runs inside the customer's mirrord Operator, and
MetalBear Cloud (coming soon). Replace the combined ECS-on-EKS runbook
with separate pages for:

- setting up the Operator-hosted sessions-manager,
- adding the remote bootstrap to an Amazon ECS task, independent of the
  deployment mode,
- connecting ECS tasks to the Operator-hosted mode (IAM access entry,
  RBAC, network path, connection variables).

Point the security and Operator pages at the new structure.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Use "Serverless Workloads" for the section, matching the serverless/
target. State the writable /tmp requirement as a single ECS prerequisite.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant