Class: Aws::SageMaker::Types::CreateClusterRequest

Inherits:
Struct
  • Object
show all
Includes:
Aws::Structure
Defined in:
lib/aws-sdk-sagemaker/types.rb

Overview

See Also:

Constant Summary collapse

SENSITIVE = 
[]

Instance Attribute Summary collapse

Instance Attribute Details

#cluster_name ⇒ String

The name for the new SageMaker HyperPod cluster.

Returns:

  • (String) 


6263
6264
6265
6266
6267
6268
6269
6270
6271
6272
 
# File 'lib/aws-sdk-sagemaker/types.rb', line 6263

class CreateClusterRequest < Struct.new(
  :cluster_name,
  :instance_groups,
  :vpc_config,
  :tags,
  :orchestrator,
  :node_recovery)
  SENSITIVE = []
  include Aws::Structure
end

#instance_groups ⇒ Array<Types::ClusterInstanceGroupSpecification>

The instance groups to be created in the SageMaker HyperPod cluster.

Returns:



6263
6264
6265
6266
6267
6268
6269
6270
6271
6272
 
# File 'lib/aws-sdk-sagemaker/types.rb', line 6263

class CreateClusterRequest < Struct.new(
  :cluster_name,
  :instance_groups,
  :vpc_config,
  :tags,
  :orchestrator,
  :node_recovery)
  SENSITIVE = []
  include Aws::Structure
end

#node_recovery ⇒ String

The node recovery mode for the SageMaker HyperPod cluster. When set to ‘Automatic`, SageMaker HyperPod will automatically reboot or replace faulty nodes when issues are detected. When set to `None`, cluster administrators will need to manually manage any faulty cluster instances.

Returns:

  • (String) 


6263
6264
6265
6266
6267
6268
6269
6270
6271
6272
 
# File 'lib/aws-sdk-sagemaker/types.rb', line 6263

class CreateClusterRequest < Struct.new(
  :cluster_name,
  :instance_groups,
  :vpc_config,
  :tags,
  :orchestrator,
  :node_recovery)
  SENSITIVE = []
  include Aws::Structure
end

#orchestrator ⇒ Types::ClusterOrchestrator

The type of orchestrator to use for the SageMaker HyperPod cluster. Currently, the only supported value is ‘“eks”`, which is to use an Amazon Elastic Kubernetes Service (EKS) cluster as the orchestrator.

Returns:



6263
6264
6265
6266
6267
6268
6269
6270
6271
6272
 
# File 'lib/aws-sdk-sagemaker/types.rb', line 6263

class CreateClusterRequest < Struct.new(
  :cluster_name,
  :instance_groups,
  :vpc_config,
  :tags,
  :orchestrator,
  :node_recovery)
  SENSITIVE = []
  include Aws::Structure
end

#tags ⇒ Array<Types::Tag>

Custom tags for managing the SageMaker HyperPod cluster as an Amazon Web Services resource. You can add tags to your cluster in the same way you add them in other Amazon Web Services services that support tagging. To learn more about tagging Amazon Web Services resources in general, see [Tagging Amazon Web Services Resources User Guide].

[1]: docs.aws.amazon.com/tag-editor/latest/userguide/tagging.html

Returns:



6263
6264
6265
6266
6267
6268
6269
6270
6271
6272
 
# File 'lib/aws-sdk-sagemaker/types.rb', line 6263

class CreateClusterRequest < Struct.new(
  :cluster_name,
  :instance_groups,
  :vpc_config,
  :tags,
  :orchestrator,
  :node_recovery)
  SENSITIVE = []
  include Aws::Structure
end

#vpc_config ⇒ Types::VpcConfig

Specifies the Amazon Virtual Private Cloud (VPC) that is associated with the Amazon SageMaker HyperPod cluster. You can control access to and from your resources by configuring your VPC. For more information, see [Give SageMaker access to resources in your Amazon VPC].

<note markdown=“1”> When your Amazon VPC and subnets support IPv6, network communications differ based on the cluster orchestration platform:

* Slurm-orchestrated clusters automatically configure nodes with
 dual IPv6 and IPv4 addresses, allowing immediate IPv6 network
 communications.

  • In Amazon EKS-orchestrated clusters, nodes receive dual-stack addressing, but pods can only use IPv6 when the Amazon EKS cluster is explicitly IPv6-enabled. For information about deploying an IPv6 Amazon EKS cluster, see [Amazon EKS IPv6 Cluster Deployment].

Additional resources for IPv6 configuration:

* For information about adding IPv6 support to your VPC, see to
 [IPv6 Support for VPC][3].

  • For information about creating a new IPv6-compatible VPC, see [Amazon VPC Creation Guide].

  • To configure SageMaker HyperPod with a custom Amazon VPC, see [Custom Amazon VPC Setup for SageMaker HyperPod].

</note>

[1]: docs.aws.amazon.com/sagemaker/latest/dg/infrastructure-give-access.html [2]: docs.aws.amazon.com/eks/latest/userguide/deploy-ipv6-cluster.html#_deploy_an_ipv6_cluster_with_eksctl [3]: docs.aws.amazon.com/vpc/latest/userguide/vpc-migrate-ipv6.html [4]: docs.aws.amazon.com/vpc/latest/userguide/create-vpc.html [5]: docs.aws.amazon.com/sagemaker/latest/dg/sagemaker-hyperpod-prerequisites.html#sagemaker-hyperpod-prerequisites-optional-vpc

Returns:



6263
6264
6265
6266
6267
6268
6269
6270
6271
6272
 
# File 'lib/aws-sdk-sagemaker/types.rb', line 6263

class CreateClusterRequest < Struct.new(
  :cluster_name,
  :instance_groups,
  :vpc_config,
  :tags,
  :orchestrator,
  :node_recovery)
  SENSITIVE = []
  include Aws::Structure
end