Amazon S3#
To set up Amazon S3 as the data store for NeMo Data Store, provision an Amazon S3 bucket and pass its information into the NeMo Helm values.yaml
file.
You can set up an object store for the following NeMo microservices:
NeMo Data Store
Prerequisites#
Storage
Access to an object store such as Amazon S3.
Kubernetes
Secrets:
Object Store Configuration Values#
Set the
objectStorage.enabled
value totrue
.Provide the following information to the NeMo Data Store Helm chart at
objectStorage
:endpoint
: The endpoint of the object store.accessKey
: The access key for the object store.accessSecret
: The secret access key for the object store.bucketName
: The name of the object store bucket.region
: The region of the object store.ssl
: Whether to enable SSL for the object store.existingSecret
: The name of an existing secret resource containing the object store credentials. For example, Object store credentials.existingSecretAccessKey
: The name of an existing secret key containing the object store access key.
The following is an example values.yaml
file for setting up NeMo Data Store with an Amazon S3 object store.
objectStore:
enabled: true
endpoint: "<end point for s3 compatible service>"
# This is end point for s3 compatible service
# example (OCI): hostname.compat.objectstorage.us-chicago-1.oraclecloud.com
# example (AWS): s3.amazonaws.com
bucketName: "<bucket where files will be stored>"
# Name of s3 compatible bucket
region: "<region name for the object store>"
# example: (OCI) us-chicago-1
# example: (AWS) us-east-1
ssl: false
# if ssl transport for object store should be enabled
accessKey: "<access key id for the object store>"
accessSecret: "<secret access key for the object store>"
existingSecret: "<specify secret name for object store>"
existingSecretAccessKey: "<secret key name for accessKey>"
existingSecretAccessSecret: "<secret key name for accessSecret>"
# Access key ID and Secret access key credentials
# These can be provided in-line or specified in a secret