         │ s3://zenml-generative-chat            ┃┗━━━━━━━━━━━━━━━┷━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛

zenml service-connector verify aws-s3-multi-instance --resource-id s3://zenml-demos

Example Command Output

Service connector 'aws-s3-multi-instance' is correctly configured with valid credentials and has access to the following resources:

┏━━━━━━━━━━━━━━━┯━━━━━━━━━━━━━━━━━━┓

┃ RESOURCE TYPE │ RESOURCE NAMES   ┃

┠───────────────┼──────────────────┨

┃ 📦 s3-bucket  │ s3://zenml-demos ┃

┗━━━━━━━━━━━━━━━┷━━━━━━━━━━━━━━━━━━┛

Finally, verifying the single-instance Service Connector is straight-forward and requires no further explanation:

zenml service-connector verify aws-s3-zenfiles

Example Command Output

Service connector 'aws-s3-zenfiles' is correctly configured with valid credentials and has access to the following resources:

┏━━━━━━━━━━━━━━━┯━━━━━━━━━━━━━━━━┓

┃ RESOURCE TYPE │ RESOURCE NAMES ┃

┠───────────────┼────────────────┨

┃ 📦 s3-bucket  │ s3://zenfiles  ┃

┗━━━━━━━━━━━━━━━┷━━━━━━━━━━━━━━━━┛

Configure local clients

Yet another neat feature built into some Service Container Types that is the opposite of Service Connector auto-configuration is the ability to configure local CLI and SDK utilities installed on your host, like the Docker or Kubernetes CLI (kubectl) with credentials issued by a compatible Service Connector.

You may need to exercise this feature to get direct CLI access to a remote service in order to manually manage some configurations or resources, to debug some workloads or to simply verify that the Service Connector credentials are actually working.