GitHub user fstephany added a comment to the discussion: Accessing a table
stored in AWS S3Tables
Thanks for the pointer!
I've tried to add the endpoint when creating the catalog:
```
let catalog = S3TablesCatalogBuilder::default()
.with_client(s3_tables_client)
.load(
"s3tables_catalog",
HashMap::from([
(
S3TABLES_CATALOG_PROP_TABLE_BUCKET_ARN.to_string(),
"arn:aws:s3tables:eu-central-1:<account_id>:bucket/<bucket-name>".to_string(),
),
("region_name".to_string(), "eu-central-1".to_string()),
("profile_name".to_string(), "<aws-profile>".to_string()),
("s3tables.region".to_string(), "eu-central-1".to_string()),
("s3.region".to_string(), "eu-central-1".to_string()),
(
"s3.endpoint".to_string(),
"s3tables.eu-central-1.api.aws".to_string(),
),
]),
)
.await?;
```
The error is now the same as if I passed the the profile from an Environment
variable:
> Could not get table: Unexpected => Failure in doing io operation
>
> Source: Unexpected (persistent) at read, context: { called:
> reqsign::LoadCredential, service: s3, path:
> metadata/\<some-kind-of-id\>.metadata.json, range: 0- } => loading credential
> to sign http request, source: error sending request for url
> (http://169.254.169.254/latest/api/token): error sending request for url
> (http://169.254.169.254/latest/api/token): operation timed out
What I don't understand is the relation between the `aws_sdk_s3tables::Client`
used in the `S3TablesCatalogBuilder` and the S3 client that is used later. It
looks like it does not share the `aws_config::SdkConfig` and rebuilds an S3
client from scratch?
Is there a working example of iceberg-rust using the AWS S3Tables native
catalog? It's all very confusing for me at the moment :sweat_smile:
GitHub link:
https://github.com/apache/iceberg-rust/discussions/2182#discussioncomment-15945158
----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
