S3-compatible Storage¶
In order to access datasets stored in S3-compatible storage, like MinIO, IBM Cloud Object Storage, Dell EMC ECS, etc, you have to configure the following parameters in values.yaml
file:
presto.hive.s3Endpoint
: The storage endpoint server. It can be found in the documentation of the S3-compatible storage.presto.hive.s3PathStyleAccess
: true. This determines whether the bucket name is provided in path-style (e.g., https://example.com/bucket-name/key-name) or virtual hosted-style (e.g., https://bucket-name.example.com/key-name).
Then, you have to provide credentials to the cluster.sh deploy
command:
cluster.sh deploy --s3-access-key xxx --s3-secret-access yyy --credstore-password zzz
--s3-access-key
: the Access Key Id--s3-secret-access
: the Secret Access Key. If this secret is not specified in the command line,cluster.sh deploy
will prompt for it, keeping secrets out of the bash history
Privileges for S3 Compatible Storage¶
The privileges required by the Denodo Embedded MPP when accessing the S3 compatible storage are:
Reading from S3 compatible storage:
s3:GetObject
s3:ListBucket
Writing to S3 compatible storage. Same as for reading and also:
s3:PutObject
s3:DeleteObject