feat(vpc): add Interface VPC endpoint for S3 Tables#190
Merged
Conversation
Keeps s3tables.<region>.amazonaws.com traffic on the AWS private network. Defaults to enabled; set enable_s3tables_endpoint=false in regions where S3 Tables is not yet available.
github-actions
Bot
added
no-need-doc
maxsxu
approved these changes
May 12, 2026
maxsxu
pushed a commit
that referenced
this pull request
May 14, 2026
🤖 I have created a release *beep* *boop* --- ## [4.9.0](v4.8.0...v4.9.0) (2026-05-14) ### Features * allow overriding S3 bucket names in dns-bucket module ([#185](#185)) ([bcd1546](bcd1546)) * **iam:** manage AWS Load Balancer Controller policy inline ([#188](#188)) ([682e686](682e686)) * **vpc:** add Interface VPC endpoint for S3 Tables ([#190](#190)) ([a1436d8](a1436d8)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
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
2 participants
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.
Motivation
S3 Tables traffic (
s3tables.<region>.amazonaws.com) is not routed through the S3 gateway endpoint, so today every BYOC deployment's S3 Tables traffic leaves the VPC over the public internet. Customers running S3 Tables catalogs against StreamNative clusters have no way to keep that traffic on the AWS private network.Modifications
modules/vpc:enable_s3tables_endpoint(bool, defaulttrue).aws_security_group.s3tables_endpointallowing HTTPS from the VPC CIDR.aws_vpc_endpoint.s3tables_endpointas an Interface endpoint (AWS publishescom.amazonaws.<region>.s3tablesas Interface-only), attached toaws_subnet.private[*], withprivate_dns_enabled = true.Verifying this change
This change is verified via end-to-end deployment.