Cannot register legacy uppercase-named same-region S3 bucket

Ask the Community
,
1

Goal

I’m trying to add a same-region S3 bucket with READ ONLY access to my enrollment’s S3 bucket policies allow-list.

Background

In the connection settings of my Data Connection source, it states:

S3 buckets in the same AWS region where your Foundry instance is hosted must also be added to the S3 bucket policies allow-list on the network egress page in Control Panel.

Control Panel: Network egress → S3 bucket policies → AWS S3 Bucket Policies

I navigated there and attempted to add an AWS S3 Bucket Policy, with it correctly detecting the AWS bucket region: us-east-1.

But when I click save, nothing happens and no error message is visible on the frontend.

I believe this is because the bucket has a legacy uppercase name, made before March 2018; it accepts test1 but silently rejects TEST1 — both validated as us-east-1 before I clicked Save.

Questions

  1. Is there a supported way to register a same-region S3 bucket with a legacy uppercase name?
  2. Why is no error shown when the save fails?
2

Jacobs,

If you can, please create a support ticket with Palantir for work around. I assume there is no Cross-Account / Direct VPC Peering Routing to make this issue more complicated.