cortex CLI can be used to deploy models locally and/or to any number of clusters. Environments are used to select which cluster to use for a cortex command. An environment contains the information required to connect to a cluster (e.g. AWS credentials and Cortex operator URL).aws onlylocal onlylocal and aws--configure-env on cortex cluster upcortex CLI to connect to an existing clustercortex CLI on a new computer, you can configure it to access an existing Cortex cluster.cortex cluster commands specify the preferred AWS credentials using cli flags --aws-key AWS_ACCESS_KEY_ID --aws-secret AWS_SECRET_ACCESS_KEY. See IAM permissions for more details.local. This is the default environment for all Cortex commands (other than cortex cluster commands), which means that APIs will be deployed locally by default.cortex cluster up, an environment named aws is automatically created to point to your new cluster. You can name the environment something else via the --configure-env flag, e.g. cortex cluster up --configure-env prod. You can also use the --configure-env flag with cortex cluster info and cortex cluster configure to create/update the specified environment. You may interact with your cluster by appending --env aws to your cortex commands, e.g. cortex deploy --env aws.cortex env list, change the default environment with cortex env default, delete an environment with cortex env delete, and create/update an environment with cortex env configure.