
Advanced: Configuring a Custom Seldon Core SecretThe Seldon Core model deployer stack component allows configuring an additional secret attribute that can be used to specify custom credentials that Seldon Core should use to authenticate to the persistent storage service where models are located. This is useful if you want to connect Seldon Core to a persistent storage service that is not supported as a ZenML Artifact Store, or if you don't want to configure or use the same credentials configured for your Artifact Store. The secret attribute must be set to the name of a ZenML secret containing credentials configured in the format supported by Seldon Core.

This method is not recommended, because it limits the Seldon Core model deployer to a single persistent storage service, whereas using the Artifact Store credentials gives you more flexibility in combining the Seldon Core model deployer with any Artifact Store in the same ZenML stack.

Seldon Core model servers use rclone to connect to persistent storage services and the credentials that can be configured in the ZenML secret must also be in the configuration format supported by rclone. This section covers a few common use cases and provides examples of how to configure the ZenML secret to support them, but for more information on supported configuration options, you can always refer to the rclone documentation for various providers.

Example of configuring a Seldon Core secret for AWS S3:

zenml secret create s3-seldon-secret \

--rclone_config_s3_type="s3" \ # set to 's3' for S3 storage.

--rclone_config_s3_provider="aws" \ # the S3 provider (e.g. aws, Ceph, Minio).

--rclone_config_s3_env_auth=False \ # set to true to use implicit AWS authentication from EC2/ECS meta data

# (i.e. with IAM roles configuration). Only applies if access_key_id and secret_access_key are blank.

--rclone_config_s3_access_key_id="<AWS-ACCESS-KEY-ID>" \ # AWS Access Key ID.

--rclone_config_s3_secret_access_key="<AWS-SECRET-ACCESS-KEY>" \ # AWS Secret Access Key.