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 AWS access and secret key ID to the kubectl create secret
command:
ENV Variable |
Description |
---|---|
AWS_ACCESS_KEY_ID |
AWS access key ID |
AWS_SECRET_ACCESS_KEY |
AWS secret key |
kubectl create secret generic mpp-credentials
--from-literal=METASTORE_DB_PASSWORD=hive
--from-literal=AWS_ACCESS_KEY_ID=awsaccesskeyid
--from-literal=AWS_SECRET_ACCESS_KEY=awssecretaccesskey
It’s also necessary to set true the objectStorage.aws.securityCredentials.enabled
property in values.yaml
Run helm install
sentence
helm install prestocluster prestocluster/
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