the full set of permissions of the IAM user or AWSaccount root user associated with the credentials. For production, it is

recommended to use the AWS IAM Role, AWS Session Token or AWS Federation Token

authentication method instead.

An AWS region is required and the connector may only be used to access AWS

resources in the specified region.

If you already have the local AWS CLI set up with these credentials, they will

be automatically picked up when auto-configuration is used.

Attributes:

aws_access_key_id {string, secret, required}: AWS Access Key ID

aws_secret_access_key {string, secret, required}: AWS Secret Access Key

region {string, required}: AWS Region

endpoint_url {string, optional}: AWS Endpoint URL

────────────────────────────────────────────────────────────────────────────────

Resource Types are a way of organizing resources into logical, well-known classes based on the standard and/or protocol used to access them, or simply based on their vendor. This creates a unified language that can be used to declare the types of resources that are provided by Service Connectors on one hand and the types of resources that are required by Stack Components on the other hand.

For example, we use the generic kubernetes-cluster resource type to refer to any and all Kubernetes clusters, since they are all generally accessible using the same standard libraries, clients and API regardless of whether they are Amazon EKS, Google GKE, Azure AKS or another flavor of managed or self-hosted deployment. Similarly, there is a generic docker-registry resource type that covers any and all container registries that implement the Docker/OCI interface, be it DockerHub, Amazon ECR, Google GCR, Azure ACR, K3D or something similar. Stack Components that need to connect to a Kubernetes cluster (e.g. the Kubernetes Orchestrator or the Seldon Model Deployer) can use the kubernetes-cluster resource type identifier to describe their resource requirements and remain agnostic of their vendor.