Repository navigation
Docs: Add Amazon S3 Tables catalog section - #4166
Open
athenawemmert wants to merge 2 commits into
Open
athenawemmert wants to merge 2 commits into
athenawemmert wants to merge 2 commits into
Conversation
Add the S3 Tables Iceberg REST endpoint to Common Integrations, next to AWS Glue, in the same shape as the other REST integrations: a link to the AWS docs and the catalog YAML. The warehouse is the table bucket ARN and the signing name is s3tables, not the execute-api default.
ebyhr
approved these changes
Oct 28, 2026
Comment on lines
582
to
583
| ##### AWS Glue | ||
|
|
Member
There was a problem hiding this comment.
nit: We could add https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-tables-integrating-glue-endpoint.html here.
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rationale for this change
The configuration docs reach Amazon S3 Tables only through the AWS Glue example (
s3tablescatalogwarehouse). Connecting PyIceberg straight to the S3 Tables Iceberg REST endpoint needs two non-default keys that are easy to miss: the warehouse is the table bucket ARN, andrest.signing-namemust bes3tables(PyIceberg defaults toexecute-api).This adds an
Amazon S3 Tablesentry under "Common Integrations & Examples", next to AWS Glue, in the same shape as the other REST integrations: a link to the AWS docs and the catalog YAML.Are these changes tested?
Docs only. I used this configuration against a real S3 Tables table bucket in us-west-2 with PyIceberg 0.12.0 (
pyiceberg[pyarrow,rest-sigv4]): create namespace, create table, append, and scan all succeeded, with requests signed fors3tables. markdownlint and codespell pass, andmkdocs build --strictsucceeds.I used an AI assistant to draft the section and the test harness, then reviewed the text and checked each key against the AWS docs, the PyIceberg source, and the live run. I only tested us-west-2.
Are there any user-facing changes?
Documentation only.