Skip to main content

Cloud API Reference (0.26.83)

View Markdown

Cloud API Reference (0.26.83)

note

This is archived documentation for version 0.26.83. For the current documentation, see current documentation.

Customer-hosted cloud features​

note

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.
  • --stack: The compute stack to use (vm or k8s).
  • --cluster-name: Kubernetes cluster name. (K8s)
  • --namespace: Kubernetes namespace for Anyscale operator. (K8s)
  • --project-id: Globally Unique project ID for GCP clouds (e.g., my-project-abc123)
  • --resource-group: Resource group for Azure clouds.
  • --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. (VM)
  • --enable-head-node-fault-tolerance: Whether to enable head node fault tolerance for services. (VM)
  • --yes/-y: Skip asking for confirmation.
  • --disable-auto-add-user: All users in the organization will be added to clouds created with anyscale 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. (VM)
  • --values-file: Path to save the generated Helm values file (for k8s stack, default: auto-generated with timestamp). (K8s)
  • --debug: Enable debug logging.
  • --operator-chart: Path to operator chart (skips helm repo add/update). (K8s)
  • --skip-resources: Create an empty cloud without provisioning resources. Use this to create a cloud record first and add resources later.

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 abfss://bucket-name@account.dfs.core.windows.net.
  • --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).
  • --persistent-volume-claim: For Kubernetes deployments only, the name of the persistent volume claim used to mount shared storage into pods. Mutually exclusive with NFS configurations.
  • --csi-ephemeral-volume-driver: For Kubernetes deployments only, the CSI ephemeral volume driver used to mount shared storage into pods. Mutually exclusive with NFS configurations.
  • --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.
  • --resource-file/-f: Path to a YAML file defining a cloud resource.
  • --azure-tenant-id: The Azure Tenant ID to use for the cloud.

anyscale cloud update​

Usage

anyscale cloud update [OPTIONS] [CLOUD_NAME]

Update a cloud.

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-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.
  • --resources-file/-f: Path to a YAML file defining a single cloud resource or a list of cloud resources. Only applicable for customer-managed resources.
  • --enable-head-node-fault-tolerance: Whether to enable head node fault tolerance for services. Only applicable for clouds with Anyscale-managed resources (clouds created via anyscale cloud setup).
  • --skip-verification: Skip cloud resource verification.

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.

anyscale cloud list​

Usage

anyscale cloud list [OPTIONS]

List information about clouds in your Anyscale organization.

Options

  • --name/-n: Name of cloud to get information about.
  • --cloud-id/--id: Id of cloud to get information about.
  • --max-items: Maximum number of clouds to return. If not specified, all results are returned.
  • --page-size: Items per page (max 50).
  • --interactive/--no-interactive: Use interactive paging.
  • -j/--json: Emit structured JSON to stdout.

anyscale cloud resource create Beta​

warning

This command undergoes rapid iteration. Users must be tolerant of change.

Usage

anyscale cloud resource create [OPTIONS]

Create a new cloud resource in an existing cloud.

Options

  • --cloud: The name of the cloud to add the new resource to.
  • --cloud-id: The ID of the cloud to add the new resource to.
  • --file/-f: Path to a YAML file defining the cloud resource.
  • --skip-verification: Skip cloud resource verification.
  • --yes/-y: Skip asking for confirmation.

Examples​

$ anyscale cloud resource create --cloud my-cloud -f new-cloud-resource.yaml
Successfully created cloud resource my-new-resource in cloud my-cloud.

$ cat new-cloud-resource.yaml
name: my-new-resource
provider: AWS
compute_stack: VM
region: us-west-2
networking_mode: PUBLIC
object_storage:
  bucket_name: s3://my-bucket
file_storage:
  file_storage_id: fs-123
aws_config:
  vpc_id: vpc-123
  subnet_ids:
  - subnet-123
  security_group_ids:
  - sg-123
  anyscale_iam_role_id: arn:aws:iam::123456789012:role/anyscale-role-123
  cluster_iam_role_id: arn:aws:iam::123456789012:role/cluster-role-123
  memorydb_cluster_name: my-memorydb-cluster

anyscale cloud resource delete Beta​

warning

This command undergoes rapid iteration. Users must be tolerant of change.

Usage

anyscale cloud resource delete [OPTIONS]

Remove a cloud resource from an existing cloud.

Options

  • --cloud: The name of the cloud to remove the resource from.
  • --resource: The name of the cloud resource to remove.
  • --yes/-y: Skip asking for confirmation.

Examples​

$ anyscale cloud resource delete --cloud my-cloud --resource my-resource
Output
Please confirm that you would like to remove resource my-resource from cloud my-cloud. [y/N]: y
(anyscale +3.5s) Successfully removed resource my-resource from cloud my-cloud!

anyscale cloud config get​

Usage

anyscale cloud config get [OPTIONS] [CLOUD_NAME]

Get the current configuration for a cloud.

Options

  • --name/-n: Update configuration of cloud by name.
  • --cloud-id/--id: Cloud id to get details about. Alternative to cloud name.
  • --resource: Name of the cloud resource to get details for. If not provided, defaults to the primary resource for the cloud.
  • --resource-id: Cloud resource ID to get details for. Alternative to cloud resource name.

anyscale cloud config update​

Usage

anyscale cloud config update [OPTIONS] [CLOUD_NAME]

Update the current configuration for a cloud.

Options

  • --name/-n: Update configuration of cloud by name.
  • --cloud-id/--id: Cloud id to update. Alternative to cloud name.
  • --enable-log-ingestion/--disable-log-ingestion: If --enable-log-ingestion is specified for a cloud, it will enable the log viewing and querying UI features for the clusters on this cloud. This will enable easier debugging. The logs produced by the clusters will be sent from the data plane to the control plane. Anyscale does not share this data with any third party or use it for any purpose other than serving the log UI for the customer. The log will be stored at most 30 days.Please note by disable this feature again, Anyscale doesn't delete the logs that have already been ingested. Your clusters may incur extra data transfer cost from the cloud provider by enabling this feature.
  • --enable-system-cluster/--disable-system-cluster: Enable or disable system cluster functionality.
  • --spec-file: Provide a path to a specification file.
  • --resource: Name of the cloud resource to get details for. If not provided, defaults to the primary resource for the cloud.
  • --resource-id: Cloud resource ID to get details for. Alternative to cloud resource name.

Examples​

$ anyscale cloud config update --cloud-id cloud_id --enable-log-ingestion --enable-system-cluster
--enable-log-ingestion is specified. [...] If you are sure you want to enable this feature, please type "consent": consent
Output
(anyscale +7.3s) Successfully updated log ingestion configuration for cloud, cloud_id to True
--enable-system-cluster is specified. [...] Are you sure you want to enable system cluster? [y/N]: y
Output
(anyscale +11.4s) Successfully enabled system cluster for cloud cloud_id

$ anyscale cloud config update --cloud-id cloud_id --spec-file iam.yaml
Output
(anyscale +2.1s) Successfully updated cloud configuration for cloud my-cloud (resource: cldrsrc_xyz123)

$ anyscale cloud config update --cloud-id cloud_id --resource shared-usw2 --spec-file iam.yaml
Output
(anyscale +2.1s) Successfully updated cloud configuration for cloud my-cloud (resource: cldrsrc_abc456)

$ anyscale cloud config update --cloud-id cloud_id --cloud-resource-id cldrsrc_xyz123 --spec-file iam.yaml
Output
(anyscale +2.1s) Successfully updated cloud configuration for cloud my-cloud (resource: cldrsrc_xyz123)

anyscale cloud set-default​

Usage

anyscale cloud set-default [OPTIONS] [CLOUD_NAME]

Sets default cloud for your organization. This operation can only be performed by organization admins, and the default cloud must have organization level permissions.

Options

  • --name/-n: Set cloud as default by name.
  • --cloud-id/--id: Cloud id to set as default. Alternative to cloud name.

anyscale cloud add-collaborators​

Usage

anyscale cloud add-collaborators [OPTIONS]

Add collaborators to the cloud.

Options

  • --cloud/-c: Name of the cloud to add collaborators to.
  • --users-file: Path to a YAML file containing a list of users to add to the cloud.

Examples​

$ anyscale cloud add-collaborators --cloud cloud_name --users-file collaborators.yaml
(anyscale +1.3s) Successfully added 2 collaborators to cloud cloud_name.
$ cat collaborators.yaml
collaborators:
  - email: "test1@anyscale.com"
    permission_level: "collaborator"
  - email: "test2@anyscale.com"
    permission_level: "readonly"

anyscale cloud get​

Usage

anyscale cloud get [OPTIONS]

Get information about a specific cloud.

Options

  • --name/-n: Name of the cloud to get information about.
  • --cloud-id/--id: ID of the cloud to get information about.
  • --output/-o: File to write the output YAML to.

Examples​

$ anyscale cloud get --name my-cloud
name: my-cloud
id: cld_123
resources:
- cloud_resource_id: cldrsrc_123
  name: vm-aws-us-west-2
  provider: AWS
  compute_stack: VM
  region: us-west-2
  networking_mode: PUBLIC
  object_storage:
    bucket_name: s3://my-bucket
  file_storage:
    file_storage_id: fs-123
  aws_config:
    vpc_id: vpc-123
    subnet_ids:
    - subnet-123
    security_group_ids:
    - sg-123
    anyscale_iam_role_id: arn:aws:iam::123456789012:role/anyscale-role-123
    cluster_iam_role_id: arn:aws:iam::123456789012:role/cluster-role-123
    memorydb_cluster_name: my-memorydb-cluster

anyscale cloud get-default​

Usage

anyscale cloud get-default [OPTIONS]

Get the default cloud for your organization.

Options

Examples​

$ anyscale cloud get-default
name: anyscale_v2_default_cloud
id: cld_abc
provider: AWS
region: us-west-2
created_at: 2022-10-18 05:12:13.335803+00:00
is_default: true
compute_stack: VM

anyscale cloud terminate-system-cluster​

Usage

anyscale cloud terminate-system-cluster [OPTIONS]

Terminate the system cluster for a specific given cloud.

Options

  • --cloud-id/--id: ID of the cloud to terminate the system cluster for.
  • -w/--wait: Block this CLI command and print logs until the job finishes.

Examples​

$ anyscale cloud terminate-system-cluster --cloud-id cloud_id --wait
(anyscale +1.3s) Waiting for system cluster termination............
(anyscale +1m22.9s) System cluster for cloud 'cloud_id' is Terminated.

Cloud SDK​

anyscale.cloud.add_collaborators​

Batch add collaborators to a cloud.

Arguments

  • cloud (str): The cloud to add users to.
  • collaborators (List[CreateCloudCollaborator]): The list of collaborators to add to the cloud.

Returns: str

Examples​

import anyscale
from anyscale.cloud.models import CloudPermissionLevel, CreateCloudCollaborator

anyscale.cloud.add_collaborators(
    cloud="cloud_name",
    collaborators=[
        CreateCloudCollaborator(
            email="test1@anyscale.com",
            permission_level=CloudPermissionLevel.WRITE,
        ),
        CreateCloudCollaborator(
            email="test2@anyscale.com",
            permission_level=CloudPermissionLevel.READONLY,
        ),
    ],
)

anyscale.cloud.list​

List clouds or fetch a single cloud by ID/name.

Arguments

  • cloud_id (str | None) = None: If provided, returns just the cloud with this ID wrapped in a one-page iterator.
  • name (str | None) = None: Substring or exact name to match against the cloud name.
  • max_items (int | None) = None: Maximum total number of items to yield (default: iterate all).
  • page_size (int | None) = None: Number of items to fetch per API request (default: API default).

Returns: ResultIterator[Cloud]

Examples​

import anyscale

# Example: Get the first 50 clouds
for cloud in anyscale.cloud.list(max_items=50):
    print(cloud.name)

anyscale.cloud.get​

Get the cloud model for the provided cloud ID or name.

If neither ID nor name is provided, returns None.

Arguments

  • id (str | None) = None: The ID of the cloud to retrieve.
  • name (str | None) = None: The name of the cloud to retrieve.

Returns: Cloud | None

Examples​

import anyscale

# Get a cloud by ID
cloud_by_id = anyscale.cloud.get(id="cloud_id")

# Get a cloud by name
cloud_by_name = anyscale.cloud.get(name="cloud_name")

anyscale.cloud.get_default​

Get the user's default cloud.

Arguments

Returns: Cloud | None

Examples​

import anyscale

# Get the user's default cloud
default_cloud = anyscale.cloud.get_default()

anyscale.cloud.terminate_system_cluster​

Terminate the system cluster for the specified cloud.

Arguments

  • cloud_id (str): The ID of the cloud whose system cluster should be terminated.
  • wait (bool | None) = False: If True, wait for the system cluster to be terminated before returning. Defaults to False.

Returns: str

Examples​

import anyscale

# Terminate the system cluster for the cloud with the specified ID
anyscale.cloud.terminate_system_cluster(cloud_id="cloud_id", wait=True)

Cloud Models​

Cloud​

Minimal Cloud resource model.

Fields​

  • name (str): Name of this Cloud.
  • id (str): Unique identifier for this Cloud.
  • provider (CloudProvider | str): Cloud provider (AWS, GCP, AZURE, GENERIC) or UNKNOWN if not recognized.
  • compute_stack (ComputeStack | str): The compute stack associated with this cloud's primary cloud resource, or UNKNOWN if not recognized.
  • region (str | None): Region for this Cloud.
  • created_at (datetime | None): When the Cloud was created.
  • is_default (bool | None): Whether this is the default cloud.
  • is_aggregated_logs_enabled (bool | None): Whether aggregated logs are enabled for this cloud.

Python Methods​

def to_dict(self) -> Dict[str, Any]
    """Return a dictionary representation of the model."""

Examples​

from datetime import datetime
from anyscale.cloud.models import Cloud, CloudProvider, ComputeStack

cloud = Cloud(
    name="my-cloud",
    id="cloud-123",
    provider="AWS",  # This will be validated as CloudProvider.AWS
    region="us-west-2",
    created_at=datetime.now(),
    is_default=True,
    compute_stack="VM"  # This will be validated as ComputeStack.VM
)

CloudPermissionLevel​

Permission levels for cloud collaborators.

Values​

  • WRITE: Write permission level for the cloud
  • READONLY: Readonly permission level for the cloud

CreateCloudCollaborator​

User to be added as a collaborator to a cloud.

Fields​

  • email (str): Email of the user to be added as a collaborator.
  • permission_level (CloudPermissionLevel): Permission level the added user should have for the cloud(one of: WRITE,READONLY

Python Methods​

def to_dict(self) -> Dict[str, Any]
    """Return a dictionary representation of the model."""

Examples​

import anyscale
from anyscale.cloud.models import CloudPermissionLevel, CreateCloudCollaborator

create_cloud_collaborator = CreateCloudCollaborator(
   # Email of the user to be added as a collaborator
    email="test@anyscale.com",
    # Permission level for the user to the cloud (CloudPermissionLevel.WRITE, CloudPermissionLevel.READONLY)
    permission_level=CloudPermissionLevel.READONLY,
)

CloudResource​

Cloud resource configuration.

Fields​

  • cloud_resource_id (str | None): Unique identifier for this cloud resource.
  • name (str | None): The name of this cloud resource.
  • provider (CloudProvider | str): The cloud provider type (e.g., AWS, GCP, AZURE, or GENERIC).
  • compute_stack (ComputeStack | str): The compute stack (VM or K8S).
  • region (str | None): The region (e.g., us-west-2).
  • networking_mode (NetworkingMode | None): Whether to use public or private networking.
  • object_storage (ObjectStorage | None): Object storage configuration.
  • file_storage (FileStorage | None): File storage configuration.
  • aws_config (AWSConfig | None): AWS provider-specific configurations.
  • gcp_config (GCPConfig | None): GCP provider-specific configurations.
  • kubernetes_config (KubernetesConfig | None): Kubernetes stack configurations.

Examples​

cloud_resource_id: cldrsrc_12345678901234567890123456
name: my-cloud-resource
provider: AWS
compute_stack: VM
region: us-west-2
networking_mode: PUBLIC
object_storage:
  bucket_name: s3://my-bucket
file_storage:
  file_storage_id: fs-12345678901234567
aws_config:
  vpc_id: vpc-12345678901234567
  subnet_ids:
  - subnet-11111111111111111
  - subnet-22222222222222222
  security_group_ids:
  - sg-12345678901234567
  anyscale_iam_role_id: arn:aws:iam::123456789012:role/anyscale-iam-role
  cluster_iam_role_id: arn:aws:iam::123456789012:role/cluster-node-role
  memorydb_cluster_name: my-memorydb-cluster

ComputeStack​

Type of compute stack for the cloud.

Values​

  • UNKNOWN: Unknown compute stack.
  • VM: Virtual machine-based compute stack.
  • K8S: Kubernetes-based compute stack.

CloudProvider​

Cloud infrastructure provider.

Values​

  • UNKNOWN: Unknown cloud provider.
  • AWS: Amazon Web Services.
  • GCP: Google Cloud Platform.
  • AZURE: Microsoft Azure.
  • GENERIC: Generic cloud provider.

NetworkingMode​

Networking mode for cloud resources.

Values​

  • PUBLIC: Direct networking.
  • PRIVATE: Customer-defined networking.

ObjectStorage​

Object storage configuration.

Fields​

  • bucket_name (str | None): The cloud storage bucket name, prefixed with the storage scheme (s3://bucket-name, gs://bucket-name, or abfss://bucket-name@account.dfs.core.windows.net).
  • region (str | None): The region for the cloud storage bucket. Defaults to the region of the cloud resource.
  • endpoint (str | None): The cloud storage endpoint, used to override the default cloud storage scheme's endpoint. For example, for S3, this will be passed to the AWS_ENDPOINT_URL environment variable.

Examples​

object_storage:
  bucket_name: s3://my-bucket

FileStorage​

File storage configuration.

Fields​

  • file_storage_id (str | None): For AWS, the EFS ID. For GCP, the Filestore instance name.
  • mount_targets (List[NFSMountTarget] | None): The mount target(s) to use.
  • mount_path (str | None): For GCP, the Filestore root directory. For NFS, the path of the server to mount from (e.g., <mount-target-address>/<mount-path> will be mounted).
  • persistent_volume_claim (str | None): For Kubernetes resources, the name of the persistent volume claim used to mount shared storage into pods.
  • csi_ephemeral_volume_driver (str | None): For Kubernetes resources, the CSI ephemeral volume driver used to mount shared storage into pods.

Examples​

file_storage:
  file_storage_id: fs-12345678901234567

NFSMountTarget​

NFS mount target configuration.

Fields​

  • address (str): The address of the NFS mount target.
  • zone (str | None): The zone of the NFS mount target. If not set, this mount target may be used in any zone.

Examples​

nfs_mount_target:
  address: 123.456.789.012

AWSConfig​

AWS provider-specific configurations.

Fields​

  • vpc_id (str | None): The VPC ID.
  • subnet_ids (List[str] | None): List of subnet IDs.
  • zones (List[str] | None): The availability zone corresponding to each subnet ID.
  • security_group_ids (List[str] | None): List of security group IDs.
  • anyscale_iam_role_id (str | None): The Anyscale IAM role ARN.
  • external_id (str | None): The trust policy external ID for the cross-account IAM role
  • cluster_iam_role_id (str | None): The IAM role ARN used by Ray clusters.
  • memorydb_cluster_name (str | None): The MemoryDB cluster name.
  • memorydb_cluster_arn (str | None): The MemoryDB cluster ARN.
  • memorydb_cluster_endpoint (str | None): The MemoryDB cluster endpoint.
  • cloudformation_id (str | None): The CloudFormation stack ID, for Anyscale-managed resources.

Examples​

aws_config:
  vpc_id: vpc-12345678901234567
  subnet_ids:
    - subnet-11111111111111111
    - subnet-22222222222222222
  security_group_ids:
    - sg-12345678901234567
  anyscale_iam_role_id: arn:aws:iam::123456789012:role/anyscale-iam-role
  cluster_iam_role_id: arn:aws:iam::123456789012:role/cluster-node-role
  memorydb_cluster_name: my-memorydb-cluster

GCPConfig​

GCP provider-specific configurations.

Fields​

  • project_id (str | None): The GCP project ID.
  • host_project_id (str | None): The host project ID for shared VPCs.
  • provider_name (str | None): Workload Identity Federation provider name for Anyscale access.
  • vpc_name (str | None): VPC name.
  • subnet_names (List[str] | None): List of GCP subnet names.
  • firewall_policy_names (List[str] | None): List of GCP firewall policy names.
  • anyscale_service_account_email (str | None): The Anyscale service account email.
  • cluster_service_account_email (str | None): The service account email attached to Ray clusters.
  • memorystore_instance_name (str | None): The Memorystore instance name.
  • memorystore_endpoint (str | None): The Memorystore instance endpoint.
  • deployment_manager_id (str | None): The deployment manager deployment ID, for Anyscale-managed resources.

Examples​

gcp_config:
  project_id: my-project
  provider_name: projects/123456789012/locations/global/workloadIdentityPools/my-cloud/providers/my-provider
  vpc_name: my-vpc
  subnet_names:
    - my-subnet
  firewall_policy_names:
    - my-firewall-policy
  anyscale_service_account_email: my-anyscale-service-account@my-project.iam.gserviceaccount.com
  cluster_service_account_email: my-cluster-service-account@my-project.iam.gserviceaccount.com
  memorystore_instance_name: my-memorystore-instance

KubernetesConfig​

Kubernetes stack configurations.

Fields​

  • anyscale_operator_iam_id (str | None): 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.
  • zones (List[str] | None): List of zones to launch pods in.

Examples​

kubernetes_config:
  anyscale_operator_iam_id: arn:aws:iam::123456789012:role/anyscale-operator-role
  zones:
    - us-west-2a
    - us-west-2b
    - us-west-2c