Values.ClusterSourceA regional grouping of one or more container instances where you can run task requests. Each account receives a default cluster the first time you use the Amazon ECS service, but you may also create other clusters. Clusters may contain more than one instance type simultaneously.
type nonrec t = {clusterArn : String_.t option;The Amazon Resource Name (ARN) that identifies the cluster. For more information about the ARN format, see Amazon Resource Name (ARN) in the Amazon ECS Developer Guide.
*)clusterName : String_.t option;A user-generated string that you use to identify your cluster.
*)configuration : ClusterConfiguration.t option;The execute command and managed storage configuration for the cluster.
*)status : String_.t option;The status of the cluster. The following are the possible states that are returned. ACTIVE The cluster is ready to accept tasks and if applicable you can register container instances with the cluster. PROVISIONING The cluster has capacity providers that are associated with it and the resources needed for the capacity provider are being created. DEPROVISIONING The cluster has capacity providers that are associated with it and the resources needed for the capacity provider are being deleted. FAILED The cluster has capacity providers that are associated with it and the resources needed for the capacity provider have failed to create. INACTIVE The cluster has been deleted. Clusters with an INACTIVE status may remain discoverable in your account for a period of time. However, this behavior is subject to change in the future. We don't recommend that you rely on INACTIVE clusters persisting.
*)registeredContainerInstancesCount : Integer.t option;The number of container instances registered into the cluster. This includes container instances in both ACTIVE and DRAINING status.
*)runningTasksCount : Integer.t option;The number of tasks in the cluster that are in the RUNNING state.
*)pendingTasksCount : Integer.t option;The number of tasks in the cluster that are in the PENDING state.
*)activeServicesCount : Integer.t option;The number of services that are running on the cluster in an ACTIVE state. You can view these services with ListServices.
*)statistics : Statistics.t option;Additional information about your clusters that are separated by launch type. They include the following: runningEC2TasksCount RunningFargateTasksCount pendingEC2TasksCount pendingFargateTasksCount activeEC2ServiceCount activeFargateServiceCount drainingEC2ServiceCount drainingFargateServiceCount
*)settings : ClusterSettings.t option;The settings for the cluster. This parameter indicates whether CloudWatch Container Insights is on or off for a cluster.
*)capacityProviders : StringList.t option;The capacity providers associated with the cluster.
*)defaultCapacityProviderStrategy : CapacityProviderStrategy.t option;The default capacity provider strategy for the cluster. When services or tasks are run in the cluster with no launch type or capacity provider strategy specified, the default capacity provider strategy is used.
*)attachments : Attachments.t option;The resources attached to a cluster. When using a capacity provider with a cluster, the capacity provider and associated resources are returned as cluster attachments.
*)attachmentsStatus : String_.t option;The status of the capacity providers associated with the cluster. The following are the states that are returned. UPDATE_IN_PROGRESS The available capacity providers for the cluster are updating. UPDATE_COMPLETE The capacity providers have successfully updated. UPDATE_FAILED The capacity provider updates failed.
*)serviceConnectDefaults : ClusterServiceConnectDefaults.t option;Use this parameter to set a default Service Connect namespace. After you set a default Service Connect namespace, any new services with Service Connect turned on that are created in the cluster are added as client services in the namespace. This setting only applies to new services that set the enabled parameter to true in the ServiceConnectConfiguration. You can set the namespace of each service individually in the ServiceConnectConfiguration to override this default parameter. Tasks that run in a namespace can use short names to connect to services in the namespace. Tasks can connect to services across all of the clusters in the namespace. Tasks connect through a managed proxy container that collects logs and metrics for increased visibility. Only the tasks that Amazon ECS services create are supported with Service Connect. For more information, see Service Connect in the Amazon Elastic Container Service Developer Guide.
*)}val make :
?clusterArn:??? ->
?clusterName:??? ->
?configuration:??? ->
?status:??? ->
?registeredContainerInstancesCount:??? ->
?runningTasksCount:??? ->
?pendingTasksCount:??? ->
?activeServicesCount:??? ->
?statistics:??? ->
?tags:??? ->
?settings:??? ->
?capacityProviders:??? ->
?defaultCapacityProviderStrategy:??? ->
?attachments:??? ->
?attachmentsStatus:??? ->
?serviceConnectDefaults:??? ->
unit ->
tval to_value :
t ->
[> `Structure of
(string
* [> `Integer of Integer.t
| `List of
[> `String of String_.t
| `Structure of
(string
* [> `Enum of string
| `Integer of CapacityProviderStrategyItemWeight.t
| `List of
[> `Structure of (string * [> `String of String_.t ]) list ]
list
| `String of String_.t ])
list ]
list
| `String of String_.t
| `Structure of
(string
* [> `String of String_.t
| `Structure of
(string
* [> `Enum of string
| `String of String_.t
| `Structure of
(string
* [> `Boolean of Boolean.t | `String of String_.t ])
list ])
list ])
list ])
list ]