Add S3-compatible storage support for Iceberg managed I/O

[dejii]

Summary

Adds AWS S3 and S3-compatible storage support (e.g., MinIO, Supabase Storage, etc.) to Beam’s Iceberg Managed I/O by including the iceberg-aws module in the expansion service.

Fixes: #37614

Background

Currently, the expansion service JAR bundles iceberg-gcp, which enables Google Cloud Storage (GCS) support out of the box. However, it does not include iceberg-aws, meaning S3-backed FileIO implementations (such as S3FileIO) are not available at runtime.

As a result, attempts to read from or write to S3 or S3-compatible storage fail with a ClassNotFoundException for org.apache.iceberg.aws.s3.S3FileIO.

What This Change Does:

• Adds the iceberg-aws dependency to the expansion service.
• Enables native AWS S3 support.
• Enables support for S3-compatible object storage (e.g., MinIO, Supabase Storage).
• Allows use of REST-based Iceberg catalogs backed by S3-compatible warehouses.

This enables read and write capabilities for Apache Iceberg using configurations such as:

ImmutableMap<String, String> catalogProperties = ImmutableMap.<String, String>builder()
    .put("type", "rest")
    .put("uri", options.getCatalogUri())
    .put("token", options.getCatalogToken())
    .put("warehouse", options.getWarehouse())
    .put("client.region", "us-east-1")
    .put("s3.endpoint", options.getS3Endpoint())
    .put("s3.access-key-id", options.getS3AccessKeyId())
    .put("s3.secret-access-key", options.getS3SecretAccessKey())
    .put("s3.path-style-access", "true")
    .put("s3.remote-signing-enabled", "false")
    .build();

I have verified this functionality by building a custom expansion service JAR that includes iceberg-aws and successfully running a Dataflow job that writes to an S3-compatible storage backend. With the dependency present, the pipeline executes without the previous ClassNotFoundException, and read/write operations function as expected

---

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

• Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
• Update CHANGES.md with noteworthy changes.
• If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

[gemini-code-assist]

Summary of Changes

Hello @dejii, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly enhances Apache Beam's Iceberg Managed I/O capabilities by integrating support for AWS S3 and other S3-compatible object storage solutions. By adding the necessary iceberg-aws dependency to the expansion service, it resolves previous runtime errors and allows users to seamlessly interact with Iceberg tables stored in S3-like environments, including those accessed via REST-based catalogs.

Highlights

• S3-compatible storage support: Enabled AWS S3 and S3-compatible storage (e.g., MinIO, Supabase Storage) for Beam's Iceberg Managed I/O.
• Dependency inclusion: Included the iceberg-aws module in the expansion service to resolve ClassNotFoundException for org.apache.iceberg.aws.s3.S3FileIO.
• Expanded capabilities: Allowed use of REST-based Iceberg catalogs backed by S3-compatible warehouses, enabling read and write operations.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog

• sdks/java/io/expansion-service/build.gradle
  • Added runtimeOnly project(":sdks:java:io:iceberg:aws") to the dependencies.
• sdks/java/io/iceberg/aws/build.gradle
  • Created a new Gradle build file.
  • Defined iceberg-aws and iceberg-aws-bundle as runtimeOnly dependencies.
  • Set publish: false as it's an intermediate JAR.
• settings.gradle.kts
  • Included the new sdks:java:io:iceberg:aws module.
  • Assigned the name "aws" to the new project.

Activity

• The pull request was created by dejii.
• No human activity (comments, reviews, approvals) has occurred yet.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[github-actions]

Assigning reviewers:

R: @Abacn for label java.

Note: If you would like to opt out of this review, comment assign to next reviewer.

Available commands:

• stop reviewer notifications - opt out of the automated review tooling
• remind me after tests pass - tag the comment author after tests pass
• waiting on author - shift the attention set back to the author (any comment or push by the author will return the attention set to the reviewers)

The PR bot will only process comments in the main thread (not review comments).

[Abacn]

R: @ahmedabu98

[github-actions]

Stopping reviewer notifications for this pull request: review requested by someone other than the bot, ceding control. If you'd like to restart, comment assign set of reviewers

[ahmedabu98]

Hey @dejii! Thanks for opening this PR. I actually covered this a few days ago in #37602.

Can you try your example again at HEAD and see if anything is missing?

[dejii]

@ahmedabu98 That’s awesome! I’ve had the change sitting in my fork for about two weeks and hadn’t checked the latest updates. I’ll give it another try with the current HEAD and share my feedback. Thanks!