Skip to content

docs(sagemaker): add IAM Identity Center access guide and template - #49

Open
man-running wants to merge 1 commit into
mainfrom
docs/sagemaker-identity-center
Open

man-running wants to merge 1 commit into
mainfrom
docs/sagemaker-identity-center

Conversation

@man-running

Copy link
Copy Markdown
Contributor

Adds a federated path to sagemaker:InvokeEndpoint for orgs whose users come from Entra ID, Okta or another IdP, as an alternative to the long-lived access key that scripts/create-sagemaker-invoke-user.ts creates. No IAM users, no static keys.

What's here

  • docs/self-hosted-sagemaker-identity-center.md — platform-team setup (MiruInvoke permission set, group assignment, provisioning check) by console or CloudFormation; per-developer aws configure sso; what SSO session expiry looks like from Miru and its MCP server; OIDC roles for CI; a sagemaker.runtime interface endpoint for keeping client traffic off the public internet.
  • examples/sagemaker-marketplace/cloudformation/miru-identity-center.yml — permission set, inline policy and group assignment in one stack.

Docs and a template only — no source changes.

Two things worth a reviewer's attention

This page is not yet linked from the main guide. The companion edits to docs/self-hosted-sagemaker.md (splitting step 2 into Identity Center vs IAM user, plus deploy-wizard notes) are deliberately held back, because @kevalkapdee's feature/prd-435-update-sagemaker-setup-docs restructures that same file around the CloudFormation/CDK templates. Landing both would conflict on step numbering. Those edits are ready and will be folded into PRD-435 rather than merged here, which is when the inbound link appears.

The template deploys to a different account than its neighbour. It sits beside sagemaker-marketplace-endpoint.yml, but that one goes to the workload account holding the endpoint, while this goes to the Identity Center management or delegated-admin account, in the Identity Center region. Called out in the doc, but the co-location does invite the assumption they're one stack run — happy to move it to examples/identity-center/ if that reads better.

Checks

  • Template parses; its declared parameters match the --parameter-overrides in the doc (PermissionSetName and SessionDuration omitted, both have defaults).
  • Relative links resolve.
  • Script names and CLI flags referenced in the doc verified against package.json and parseSetupCliArgs.

🤖 Generated with Claude Code

https://claude.ai/code/session_01QMuenzrkUj9uZ3kwVjLiwT

Document the federated path to sagemaker:InvokeEndpoint for orgs whose
users come from Entra ID, Okta or another IdP, as an alternative to the
long-lived access key created by the invoke-user runbook.

Covers the platform-team setup (MiruInvoke permission set, group
assignment, provisioning check) by console or CloudFormation, the
per-developer `aws configure sso`, what SSO session expiry looks like
from Miru and its MCP server, OIDC roles for CI, and a sagemaker.runtime
interface endpoint for keeping client traffic off the public internet.

The template sits alongside the endpoint template in
examples/sagemaker-marketplace/cloudformation, though it deploys to a
different account — Identity Center management or delegated admin, in
the Identity Center region, not the endpoint account.

The companion updates to docs/self-hosted-sagemaker.md are held back to
land with the CloudFormation/CDK restructure in PRD-435, so this page is
not yet linked from the main guide.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QMuenzrkUj9uZ3kwVjLiwT
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