Cloud API Reference
Customer-hosted cloud features
Some features are only available on customer-hosted clouds. Reach out to support@anyscale.com for info.
Cloud CLI
anyscale cloud setup
Usage
anyscale cloud setup [OPTIONS]
Set up a cloud provider.
Options
--provider
: The cloud provider type.--region
: Region to set up the credentials in.--name/-n
: Name of the cloud.--project-id
: Globally Unique project ID for GCP clouds (e.g., my-project-abc123)--functional-verify
: Verify the cloud is functional. This will check that the cloud can launch workspace/service.--anyscale-managed
: Let anyscale create all the resources.--enable-head-node-fault-tolerance
: Whether to enable head node fault tolerance for services.--yes/-y
: Skip asking for confirmation.--disable-auto-add-user
: All users in the organization will be added to clouds created withanyscale cloud setup
by default. Specify --disable-auto-add-user to disable this and instead manually grant users permissions to the cloud.--shared-storage
: The type of shared storage to use for the cloud. Use 'object-storage' for cloud bucket-based storage (e.g., S3, GCS), or 'nfs' for network file systems.
anyscale cloud register
Usage
anyscale cloud register [OPTIONS]
Register an anyscale cloud with your own resources.
Options
--provider
: The cloud provider type.--region
: Region to set up the credentials in.--compute-stack
: The compute stack type (VM or K8S).--name/-n
: Name of the cloud.--vpc-id
: The ID of the VPC.--subnet-ids
: Comma separated list of subnet ids.--file-storage-id
: File storage ID (e.g. EFS ID for AWS, Filestore instance ID for GCP)--efs-id
: The EFS ID.--anyscale-iam-role-id
: The Anyscale IAM Role ARN.--instance-iam-role-id
: The instance IAM role ARN.--security-group-ids
: IDs of the security groups.--s3-bucket-id
: S3 bucket ID.--external-id
: The trust policy external ID for the cross account IAM role.--memorydb-cluster-id
: Memorydb cluster ID--project-id
: Globally Unique project ID for GCP clouds (e.g., my-project-abc123)--vpc-name
: VPC name for GCP clouds--subnet-names
: Comma separated list of subnet names for GCP clouds--filestore-instance-id
: Filestore instance ID for GCP clouds.--filestore-location
: Filestore location for GCP clouds.--anyscale-service-account-email
: Anyscale service account email for GCP clouds.--instance-service-account-email
: Instance service account email for GCP clouds.--provider-name
: Workload Identity Federation provider name for Anyscale access.--firewall-policy-names
: Filewall policy names for GCP clouds--cloud-storage-bucket-name
: A fully qualified storage bucket name for cloud storage, e.g. s3://bucket-name, gs://bucket-name, or azure://bucket-name.--cloud-storage-bucket-endpoint
: An endpoint for cloud storage, e.g. used to override the default cloud storage scheme's endpoint (e.g. for S3, this would be passed to the AWS_ENDPOINT_URL environment variable).--cloud-storage-bucket-region
: The region of the cloud storage bucket. If not provided, the region of the cloud will be used to access the cloud storage bucket.--nfs-mount-target
: A comma-separated value representing a (zone, mount target) tuple, e.g. us-west-2a,1.2.3.4 (may be provided multiple times, one for each zone). If only one value is provided (e.g. 1.2.3.4), then that value will be used for all zones.--nfs-mount-path
: The path of the NFS server to mount from (e.g. nfs-target-address/nfs-path will be mounted).--memorystore-instance-name
: Memorystore instance name for GCP clouds--host-project-id
: Host project ID for shared VPC--kubernetes-zones
: On the Kubernetes compute stack, a comma-separated list of zones to launch pods in.--anyscale-operator-iam-identity
: On the Kubernetes compute stack, the cloud provider IAM identity federated with the Anyscale Operator's kubernetes service account, which will be used by Anyscale control plane for validation during Anyscale Operator bootstrap in the dataplane. IN AWS EKS, this is the ARN of the IAM role. For GCP GKE, this is the service account email.--private-network
: Use private network.--functional-verify
: Verify the cloud is functional. This will check that the cloud can launch workspace/service.--yes/-y
: Skip asking for confirmation.--skip-verifications
: Skip verifications. This will skip all verifications.--enable-auto-add-user
: If --enable-auto-add-user is specified for a cloud, all users in the organization will be added to the cloud by default. Otherwise users will need to be manually granted permissions to the cloud. Note: There may be up to 30 sec delay for all users to be granted permissions after the cloud is created.
anyscale cloud edit
Usage
anyscale cloud edit [OPTIONS] [CLOUD_NAME]
Edit registered cloud resource on Anyscale. Only applicable for anyscale registered clouds.
Options
--name/-n
: Edit cloud by name.--cloud-id/--id
: Edit cloud by id, alternative to cloud name.--aws-s3-id
: New S3 bucket ID.--aws-efs-id
: New EFS ID.--aws-efs-mount-target-ip
: New EFS mount target IP.--memorydb-cluster-id
: New AWS Memorydb cluster ID.--gcp-filestore-instance-id
: New GCP filestore instance id.--gcp-filestore-location
: New GCP filestore location.--gcp-cloud-storage-bucket-name
: New GCP Cloud storage bucket name.--memorystore-instance-name
: New Memorystore instance name for GCP clouds--functional-verify
: Verify the cloud is functional. This will check that the cloud can launch workspace/service.--enable-auto-add-user/--disable-auto-add-user
: If --enable-auto-add-user is specified for a cloud, all users in the organization will be added to the cloud by default. Note: There may be up to 30 sec delay for all users to be granted permissions after this feature is enabled.
Specifying --disable-auto-add-user will require that users are manually granted permissions to access the cloud. No existing cloud permissions are altered by specifying this flag.
anyscale cloud update
Usage
anyscale cloud update [OPTIONS] [CLOUD_NAME]
Update a managed cloud to the latest configuration. Only applicable for anyscale managed clouds.
Options
--cloud-id/--id
: Cloud id to update. Alternative to cloud name.--name/-n
: Update configuration of cloud by name.--yes/-y
: Skip asking for confirmation.--functional-verify
: Verify the cloud is functional. This will check that the cloud can launch workspace/service.--enable-head-node-fault-tolerance
: Whether to enable head node fault tolerance for services.--enable-auto-add-user/--disable-auto-add-user
: If --enable-auto-add-user is specified for a cloud, all users in the organization will be added to the cloud by default. Note: There may be up to 30 sec delay for all users to be granted permissions after this feature is enabled.
Specifying --disable-auto-add-user will require that users are manually granted permissions to access the cloud. No existing cloud permissions are altered by specifying this flag.
--file/-f
: YAML file containing the updated cloud spec.
anyscale cloud delete
Usage
anyscale cloud delete [OPTIONS] [CLOUD_NAME]
Delete a cloud.
Options
--name/-n
: Delete cloud by name.--cloud-id/--id
: Cloud id to delete. Alternative to cloud name.--yes/-y
: Don't ask for confirmation.
anyscale cloud verify
Usage
anyscale cloud verify [OPTIONS] [CLOUD_NAME]
Checks the healthiness of a cloud.
Options
--name/-n
: Verify cloud by name.--cloud-id/--id
: Verify cloud by cloud id, alternative to cloud name.--functional-verify
: Verify the cloud is functional. This will check that the cloud can launch workspace/service.--strict
: Strict Verify. Treat warnings as failures.