Skip to content

Conversation

@kbatuigas
Copy link
Contributor

@kbatuigas kbatuigas commented Aug 1, 2025

Description

Related PR to add Glue doc to Cloud: redpanda-data/cloud-docs#363

This pull request introduces updates to the Antora playbook and documentation for integrating Redpanda topics with AWS Glue Data Catalog. The changes include branch updates in the playbook, dynamic versioning for prerequisites, and detailed instructions for configuring credentials and cluster properties for AWS Glue integration. Below is a summary of the most important changes:

Playbook Updates

  • Updated the branch reference for the cloud-docs repository in the local-antora-playbook.yml file to DOC-1377-cloud-aws-glue for more targeted documentation updates.

Documentation Enhancements for AWS Glue Integration

  • Dynamic Versioning and Prerequisite Updates:

    • Introduced dynamic variables (rp_version and rpk_install_doc) to specify Redpanda version and rpk installation instructions based on the environment (env-cloud or non-cloud). This ensures accurate and up-to-date prerequisites for users.
  • Credential Configuration:

    • Added separate instructions for configuring AWS Glue credentials in cloud and non-cloud environments. Non-cloud users can override S3 credentials, while cloud users must use specific properties for AWS Glue.
  • Cluster Property Placeholders:

    • Included detailed explanations for placeholders such as <aws-region>, <bucket-name>, <warehouse-path>, <glue-access-key>, and <glue-secret-key-name> to guide users in setting up their configurations securely and correctly. [1] [2]

These changes aim to improve clarity, flexibility, and precision in the documentation, making it easier for users to integrate Redpanda with AWS Glue.

Resolves https://redpandadata.atlassian.net/browse/
Review deadline: 4 Aug

Page previews

Cloud: Query Iceberg Topics Using AWS Glue

Self-managed version: Query Iceberg Topics Using AWS Glue

Checks

  • New feature
  • Content gap
  • Support Follow-up
  • Small fix (typos, links, copyedits, etc)

@kbatuigas kbatuigas requested a review from a team as a code owner August 1, 2025 22:14
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Aug 1, 2025

Important

Review skipped

Auto incremental reviews are disabled on this repository.

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.

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

📝 Walkthrough

Walkthrough

This pull request updates the Antora playbook configuration to reference the DOC-1377-cloud-aws-glue branch of the cloud-docs repository instead of main. It also refactors the Iceberg documentation for AWS Glue integration, clarifying and unifying environment-specific instructions for both cloud and non-cloud deployments. The documentation now more explicitly details the configuration of credentials, especially for cloud environments, and introduces variables for versioning and installation documentation. No changes to exported or public code entities are present; all modifications are documentation and configuration updates.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Docs
    participant Redpanda Cluster

    User->>Docs: Access Iceberg AWS Glue documentation
    Docs-->>User: Show prerequisites (version, install doc link)
    alt Non-cloud environment
        User->>Docs: View non-cloud configuration
        Docs-->>User: Show S3/shared credentials or override options
        User->>Redpanda Cluster: Configure cluster with S3 or Glue credentials
    else Cloud environment
        User->>Docs: View cloud configuration
        Docs-->>User: Show AWS-specific cluster property requirements
        User->>Redpanda Cluster: Configure cluster with required AWS Glue properties (access_key, secret_key, region)
    end
Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~7 minutes

Assessment against linked issues

Objective Addressed Explanation
Document feature: AWS Glue Support for Iceberg (DOC-1377)
AWS Glue in Cloud must use AWS-specific cluster properties to pass credentials (DOC-1548)

Assessment against linked issues: Out-of-scope changes

No out-of-scope changes found.

Possibly related PRs

  • DOC-1449 revert playbook #1164: Both PRs modify the local-antora-playbook.yml file by changing the branch specification for the redpanda-data/cloud-docs content source URL, directly relating their changes at the configuration level.
  • Update Iceberg catalog doc for Cloud (single source) #1113: Both PRs modify the Antora playbook branch reference for the cloud-docs repository and update Iceberg-related documentation to better handle cloud environment configurations, focusing on AWS Glue and secret management, indicating a related scope of documentation improvements for cloud Iceberg integration.

Suggested reviewers

  • micheleRP
  • simon0191
  • Feediver1
✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch DOC-1548-aws-glue-in-cloud-must-use-aws-specific-cluster-pr

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai generate unit tests to generate unit tests for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@netlify
Copy link

netlify bot commented Aug 1, 2025

Deploy Preview for redpanda-docs-preview ready!

Name Link
🔨 Latest commit a99ecc9
🔍 Latest deploy log https://app.netlify.com/projects/redpanda-docs-preview/deploys/68928df0de16dd000846c085
😎 Deploy Preview https://deploy-preview-1275--redpanda-docs-preview.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.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (4)
modules/manage/pages/iceberg/iceberg-topics-aws-glue.adoc (4)

118-124: Commented credentials block – consider showing both credential flavours

Right now the example shows the override properties only as commented lines. Users may miss that they still need cloud_storage_* if they stick with shared credentials. A brief comment above the snippet such as “Either keep these commented lines or delete them to reuse S3 credentials” would reduce ambiguity.


128-132: Placeholder list: missing full stop causes Antora warning

AsciiDoc treats the -- delimited block as a dlist description. Term lines must end with :: or a period. Add a trailing period or convert to an unordered list to avoid “dangling description” warnings.

- - `<bucket-name>` and `<warehouse-path>`: AWS Glue requires ...
+ - `<bucket-name>` and `<warehouse-path>`:: AWS Glue requires ...

149-151: Secret macro render-ability

${secrets.<glue-secret-key-name>} renders literally in the docs site because Antora does not evaluate shell-style expansions.
Wrap it in backticks or change to secrets.<glue-secret-key-name> so the text is shown as-is.

-  iceberg_rest_catalog_aws_secret_key=${secrets.<glue-secret-key-name>}
+  iceberg_rest_catalog_aws_secret_key=`secrets.<glue-secret-key-name>`

157-162: Consistent placeholder ordering

Swap <glue-region> and <glue-access-key> to keep region-specific placeholders grouped together (<aws-region>, <glue-region>).

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1ee0227 and fe550b0.

📒 Files selected for processing (2)
  • local-antora-playbook.yml (1 hunks)
  • modules/manage/pages/iceberg/iceberg-topics-aws-glue.adoc (4 hunks)
🧰 Additional context used
🧠 Learnings (2)
📚 Learning: in the redpanda documentation, topic property cross-references like <> and <<...
Learnt from: Feediver1
PR: redpanda-data/docs#1153
File: modules/reference/pages/properties/topic-properties.adoc:45-50
Timestamp: 2025-07-16T19:33:20.420Z
Learning: In the Redpanda documentation, topic property cross-references like <<max.compaction.lag.ms>> and <<min.compaction.lag.ms>> require corresponding property definition sections with anchors like [[maxcompactionlagms]] and [[mincompactionlagms]] to prevent broken links.

Applied to files:

  • modules/manage/pages/iceberg/iceberg-topics-aws-glue.adoc
📚 Learning: in asciidoc documentation for redpanda, the syntax `+` and `--` around content blocks within a `[tab...
Learnt from: kbatuigas
PR: redpanda-data/docs#1113
File: modules/manage/partials/iceberg/use-iceberg-catalogs.adoc:100-107
Timestamp: 2025-05-07T01:06:00.937Z
Learning: In AsciiDoc documentation for Redpanda, the syntax `+` and `--` around content blocks within a `[tabs]` section are valid AsciiDoc formatting elements for tabbed content. The `+` after a tab name (like `rpk::`) indicates that the following block belongs to that tab, and the `--` markers enclose the content for that tab. These are not diff artifacts and should not be removed.

Applied to files:

  • modules/manage/pages/iceberg/iceberg-topics-aws-glue.adoc
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)
  • GitHub Check: Redirect rules - redpanda-docs-preview
  • GitHub Check: Header rules - redpanda-docs-preview
  • GitHub Check: Pages changed - redpanda-docs-preview
🔇 Additional comments (5)
local-antora-playbook.yml (1)

20-20: Branch pin may break once the feature branch is deleted

Pointing the content source to a short-lived feature branch (DOC-1377-cloud-aws-glue) means the docs build will 404 once that branch is deleted after merge.
Consider either:

-  - url: https://github.com/redpanda-data/cloud-docs
-    branches: 'DOC-1377-cloud-aws-glue'
+  - url: https://github.com/redpanda-data/cloud-docs
+    branches: ['main', 'DOC-1377-cloud-aws-glue']   # fall back to main

or reverting this change as soon as the feature branch is merged into main.

modules/manage/pages/iceberg/iceberg-topics-aws-glue.adoc (4)

26-27: Attribute reuse looks good

Using {rp_version} and {rpk_install_doc} removes hard-coding and will auto-update when the attributes are bumped.


83-92: Cross-reference anchors could be missing

The four new iceberg_rest_catalog_aws_* properties are referenced via config_ref. Ensure they are defined in
modules/reference/pages/properties/cluster-properties.adoc (each needs [[iceberg_rest_catalog_aws_access_key]] etc.).
A missing anchor silently renders as plain text and breaks the link checker.


94-100: Secret reference wording is clear

Calling out that iceberg_rest_catalog_aws_secret_key must be a secret and pointing to the next section is helpful.


12-20: Version split is intentional for Cloud (beta) vs self-hosted (GA)
The AWS Glue integration is marked Beta on Redpanda Cloud—hence the :rp_version: 25.2 in the Cloud block—while self-hosted users need only the minimum GA release (25.1.7) as noted in the release notes (“The AWS Glue catalog integration is available in Redpanda version 25.1.7 and later”). No change needed.

Likely an incorrect or invalid review comment.

@kbatuigas
Copy link
Contributor Author

@simon0191 @mattschumpert not currently part of the diff - How should the guidance in the Authorize access to AWS Glue section change for Cloud?

For example, I don't know if this is relevant to Cloud:

You can use the same access credentials that you configured for S3 (IAM role, access keys, and KMS key), as long as you have also added read and write access to AWS Glue Data Catalog.

For example, you could create a separate IAM policy that manages access to AWS Glue, and attach it to the IAM role that Redpanda also uses to access S3.

Do customers create a new IAM user in AWS and attach a policy with Glue permissions like in the example provided?

The instructions for using iceberg_rest_catalog_aws_* properties are in the subsequent sections.

@mattschumpert
Copy link

@kbatuigas
For Cloud specifically, I think we should recommend they create a new policy/Role since most BYOC customers aren't creating the Tiered Storage IAM policy / role on their own, Redpanda is. Maybe BYOVPC but not sure even. And so here, I guess using access keys (with the secret setup as an RP Cloud secret) is the best way to setup the connection from Redpanda to Glue.

For self-hosted its different. They must be creating the IAM role/policy or using access keys for Tiered Storage on their own.

@kbatuigas kbatuigas requested a review from wdberkeley August 4, 2025 22:13
Copy link

@andrwng andrwng left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, just one question to clarify

endif::[]

ifdef::env-cloud[]
You must configure credentials for the AWS Glue Data Catalog integration using the following properties:
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just double checking, are these always needed? Do the cloud_storage_* credentials not work in cloud?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's right -- cloud_storage_* properties are not exposed in Cloud because we manage the cloud storage bucket.

Copy link
Collaborator

@paulohtb6 paulohtb6 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@kbatuigas kbatuigas merged commit 337c57f into main Aug 5, 2025
7 checks passed
@kbatuigas kbatuigas deleted the DOC-1548-aws-glue-in-cloud-must-use-aws-specific-cluster-pr branch August 5, 2025 23:09
@coderabbitai coderabbitai bot mentioned this pull request Aug 25, 2025
4 tasks
@coderabbitai coderabbitai bot mentioned this pull request Oct 5, 2025
4 tasks
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.

6 participants