Added S3 gateway endpoint, STS and Kinesis interface endpoints

[gergelj]

Pull Request

Description

Brief description of what this PR does and why.

Category

• core-platform
• data-engineering
• data-governance
• data-warehousing
• genai-ml
• launch-accelerator
• workspace-setup

Type of Change

• New project
• Bug fix
• Enhancement
• Documentation

Project Details

Project Name: AWS BYOVPC
Purpose: Terraform code for workspace deployment
Technologies Used: Terraform

Testing

• Code runs without errors
• Documentation is complete
• Used only synthetic data

Security Compliance ✅

• No customer data, PII, or proprietary information
• No credentials or access tokens
• Only synthetic data used
• Third-party licenses acknowledged

---

By submitting this PR, I confirm I have followed the CONTRIBUTING.md guidelines and security requirements.

[gergelj]

This setup requires a separate subnet that holds the STS and Kinesis interface endpoints. This subnet is called 'intra' subnet.

[gergelj]

Tests done:

• cluster startup is successful
• S3 storage is accessible (read/write)
• route table is updated, so that the EC2s can access the S3 gateway endpoint

• prefix list ID (which resolves to com.amazonaws.<region>.s3) routes to the S3 gateway endpoint, which is more specific than the 0.0.0.0/0 that routes to the NAT gateway

[jpgianfaldoni]

LGTM