Skip to content

DOC-2297: Cross-account IAM delegation for BYOC on AWS (draft)#633

Draft
micheleRP wants to merge 6 commits into
mainfrom
DOC-2297-cross-account-iam
Draft

DOC-2297: Cross-account IAM delegation for BYOC on AWS (draft)#633
micheleRP wants to merge 6 commits into
mainfrom
DOC-2297-cross-account-iam

Conversation

@micheleRP

@micheleRP micheleRP commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

Summary

Draft documentation for cross-account IAM delegation for BYOC on AWS (ENG-1139, targeted 26.2 / 2026-07-14). AWS-only, new clusters only; existing clusters and Azure/GCP keep the agent-based rpk cloud byoc apply model.

Jira: https://redpandadata.atlassian.net/browse/DOC-2297

Changes

  • Reference: reworked the AWS section of security:partial$iam-policies.adoc from cloudv2 apps/redpanda-agent/infra/aws/redpanda/agent/instance_profile.tf (30 statements) into friendly, anchored sections with Permission | Access | Why it is needed tables and collapsible Terraform. The published partial had drifted ~90 actions behind source; this restores full parity. GCP and Azure sections reformatted to match (same structure), and refreshed from source to close drift.
  • Concept: new "Provisioning models on AWS" section in byoc-arch.adoc (cross-account vs. agent-based comparison).
  • How-to: new cross-account-iam-aws.adoc (added to nav) + a cross-link TIP on the AWS create page.
  • What's New: draft July 2026 entry.

Status: DRAFT — not for merge

Open items are marked inline as TODO(team) / TODO(eng), pending SME confirmation (team post + Denis's permission-justification sheet):

  1. Exact Cloud UI / deploy wizard steps (ENG-1129)
  2. Customer role Terraform delivery mechanism
  3. External ID surfacing + step ordering (CIAINFRA-3970)
  4. Exact role name + trust policy content
  5. Confirm the cross-account role grants the same permission set as the agent policy; feature-gating (Redpanda SQL / AI Gateway / RDS); the ~90 "why it is needed" cells

Preview pages

Deploy preview is still building; links go live once the Netlify deploy-preview check passes.

🤖 Generated with Claude Code

Rework the AWS IAM policies reference from cloudv2 source, add a
cross-account deploy how-to and concept, plus a draft What's New entry.
AWS-only, new clusters only (ENG-1139, targeted 26.2). Existing clusters
keep the agent-based rpk cloud byoc apply model.

- security: rebuild AWS section of iam-policies.adoc partial from
  instance_profile.tf (30 statements) into friendly, anchored sections
  with why-tables and collapsible Terraform; reframe for cross-account.
  GCP/Azure sections unchanged.
- get-started: new cross-account-iam-aws.adoc how-to + nav entry
- get-started: byoc-arch.adoc provisioning-models section + create-page
  cross-link TIP
- get-started: draft What's New entry (do not publish before GA)

Contains TODO(team)/TODO(eng) placeholders pending SME confirmation.
Draft, not for merge.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@netlify

netlify Bot commented Jul 9, 2026

Copy link
Copy Markdown

Deploy Preview for rp-cloud ready!

Name Link
🔨 Latest commit 2bb02aa
🔍 Latest deploy log https://app.netlify.com/projects/rp-cloud/deploys/6a5063d7259f64000897fc6b
😎 Deploy Preview https://deploy-preview-633--rp-cloud.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@coderabbitai

coderabbitai Bot commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 2158dc00-acd4-423f-8d1c-8353b5daf35c

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch DOC-2297-cross-account-iam

Comment @coderabbitai help to get the list of available commands.

micheleRP and others added 5 commits July 9, 2026 17:35
Rebuild the GCP and Azure sections of the iam-policies.adoc partial from
cloudv2 source (role_redpanda_agent.tf, azure/agent/iam.tf) into the same
friendly, anchored sections with Permission | Access | Why it is needed
tables, plus a collapsible full role definition. Both keep the agent-based
framing (no cross-account delegation this release).

Refresh from source also closes drift: GCP adds secretmanager.* and
serviceusage.* and a Redpanda SQL storage role; Azure adds the private
endpoint / private DNS / Log Analytics actions the published page lacked.

Reuses Denis's "why" text where the permission still exists; newer actions
are marked TODO(eng). Reformatted at PM (Denis) request for consistency.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Rewrite create-byoc-cluster-aws.adoc so cross-account IAM delegation is the
primary path for new AWS clusters: grant IAM permissions (create the
cross-account role) as a prerequisite, then create the cluster. Retire the
separate cross-account-iam-aws.adoc how-to and fold it in; its IDs are kept
as page-aliases so links redirect to the create page.

- nav: drop the standalone cross-account how-to entry
- byoc-arch.adoc, whats-new-cloud.adoc: repoint links to the create page
- cluster-types/byoc/index.adoc: note cross-account delegation for AWS

The "Grant IAM permissions" section is self-contained so it can be split
into a dedicated prerequisite page later if the real Terraform makes it long.
Still draft: TODO(team) placeholders remain pending SME answers.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Add a note in the BYOC setup section so readers know the agent-based
rpk cloud byoc apply flow is not the default for new AWS clusters, linking
to the Provisioning models on AWS section.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Rewrite the What's New entry to lead with the benefit (simpler, more
transparent deployment) rather than the feature name. Keep 'cross-account
IAM delegation' in a parenthetical for searchability.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Drop the first sentence that echoed the heading; open with the concrete
change instead.

Co-Authored-By: Claude Opus 4.8 (1M context) <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