Skip to content

DELL ECS compatibility #40

Description

@klaci71

Dear dev-team,

Can we use this fdw with on-prem s3 compatible DELL ECS?
Even though we set the endpoint to our own address, fdw tries to connect to Amazon AWS.

CREATE SERVER parquet_s3_srv
FOREIGN DATA WRAPPER parquet_s3_fdw
OPTIONS (region 'us-east-1', endpoint 'https://own_endpoint');

CREATE USER MAPPING FOR public SERVER parquet_s3_srv OPTIONS (user 'xxxxx', password 'yyyyy');

CREATE FOREIGN TABLE schema.table (
id int,
feature_0 decimal,
feature_1 decimal
)
SERVER parquet_s3_srv
OPTIONS (
filename 's3://bucket/dir/name.parquet'
);

After configuring these, based on the tcpdump output, it tries to communicate only with s3-1.amazonaws.com.

select * from schema.table;

ERROR: parquet_s3_fdw: failed to extract row groups from Parquet file: failed to open Parquet file HeadObject failed ('s3://bucket/dir/name.parquet')

09:21:20.097504 IP (tos 0x0, ttl 64, id 28251, offset 0, flags [DF], proto TCP (6), length 60)
own_node.49258 > s3-1.amazonaws.com.https: Flags [S], cksum 0xfc5f (incorrect -> 0xc37b), seq 1406358599, win 64240, options [mss 1460,sackOK,TS val 3223413504 ecr 0,nop,wscale 7], length 0
09:21:20.098617 IP (tos 0x0, ttl 125, id 10025, offset 0, flags [DF], proto TCP (6), length 40)
s3-1.amazonaws.com.https > own_node.49258: Flags [R.], cksum 0x81f4 (correct), seq 1945260919, ack 1406358600, win 0, length 0

We tried to adjust this environment variable, but didn't help:

export AWS_EC2_METADATA_DISABLED=true

Thank you for your help.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions