Copyright | (c) 2013-2023 Brendan Hay |
---|---|
License | Mozilla Public License, v. 2.0. |
Maintainer | Brendan Hay |
Stability | auto-generated |
Portability | non-portable (GHC extensions) |
Safe Haskell | Safe-Inferred |
Language | Haskell2010 |
Creates a new Amazon ECS cluster. By default, your account receives a
default
cluster when you launch your first container instance.
However, you can create your own cluster with a unique name with the
CreateCluster
action.
When you call the CreateCluster API operation, Amazon ECS attempts to create the Amazon ECS service-linked role for your account. This is so that it can manage required resources in other Amazon Web Services services on your behalf. However, if the IAM user that makes the call doesn't have permissions to create the service-linked role, it isn't created. For more information, see Using service-linked roles for Amazon ECS in the Amazon Elastic Container Service Developer Guide.
Synopsis
- data CreateCluster = CreateCluster' {}
- newCreateCluster :: CreateCluster
- createCluster_capacityProviders :: Lens' CreateCluster (Maybe [Text])
- createCluster_clusterName :: Lens' CreateCluster (Maybe Text)
- createCluster_configuration :: Lens' CreateCluster (Maybe ClusterConfiguration)
- createCluster_defaultCapacityProviderStrategy :: Lens' CreateCluster (Maybe [CapacityProviderStrategyItem])
- createCluster_serviceConnectDefaults :: Lens' CreateCluster (Maybe ClusterServiceConnectDefaultsRequest)
- createCluster_settings :: Lens' CreateCluster (Maybe [ClusterSetting])
- createCluster_tags :: Lens' CreateCluster (Maybe [Tag])
- data CreateClusterResponse = CreateClusterResponse' {
- cluster :: Maybe Cluster
- httpStatus :: Int
- newCreateClusterResponse :: Int -> CreateClusterResponse
- createClusterResponse_cluster :: Lens' CreateClusterResponse (Maybe Cluster)
- createClusterResponse_httpStatus :: Lens' CreateClusterResponse Int
Creating a Request
data CreateCluster Source #
See: newCreateCluster
smart constructor.
CreateCluster' | |
|
Instances
newCreateCluster :: CreateCluster Source #
Create a value of CreateCluster
with all optional fields omitted.
Use generic-lens or optics to modify other optional fields.
The following record fields are available, with the corresponding lenses provided for backwards compatibility:
CreateCluster
, createCluster_capacityProviders
- The short name of one or more capacity providers to associate with the
cluster. A capacity provider must be associated with a cluster before it
can be included as part of the default capacity provider strategy of the
cluster or used in a capacity provider strategy when calling the
CreateService or RunTask actions.
If specifying a capacity provider that uses an Auto Scaling group, the capacity provider must be created but not associated with another cluster. New Auto Scaling group capacity providers can be created with the CreateCapacityProvider API operation.
To use a Fargate capacity provider, specify either the FARGATE
or
FARGATE_SPOT
capacity providers. The Fargate capacity providers are
available to all accounts and only need to be associated with a cluster
to be used.
The PutClusterCapacityProviders API operation is used to update the list of available capacity providers for a cluster after the cluster is created.
CreateCluster
, createCluster_clusterName
- The name of your cluster. If you don't specify a name for your cluster,
you create a cluster that's named default
. Up to 255 letters
(uppercase and lowercase), numbers, underscores, and hyphens are
allowed.
CreateCluster
, createCluster_configuration
- The execute
command configuration for the cluster.
CreateCluster
, createCluster_defaultCapacityProviderStrategy
- The capacity provider strategy to set as the default for the cluster.
After a default capacity provider strategy is set for a cluster, when
you call the RunTask or CreateService APIs with no capacity provider
strategy or launch type specified, the default capacity provider
strategy for the cluster is used.
If a default capacity provider strategy isn't defined for a cluster when it was created, it can be defined later with the PutClusterCapacityProviders API operation.
CreateCluster
, createCluster_serviceConnectDefaults
- 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.
CreateCluster
, createCluster_settings
- The setting to use when creating a cluster. This parameter is used to
turn on CloudWatch Container Insights for a cluster. If this value is
specified, it overrides the containerInsights
value set with
PutAccountSetting or PutAccountSettingDefault.
CreateCluster
, createCluster_tags
- The metadata that you apply to the cluster to help you categorize and
organize them. Each tag consists of a key and an optional value. You
define both.
The following basic restrictions apply to tags:
- Maximum number of tags per resource - 50
- For each resource, each tag key must be unique, and each tag key can have only one value.
- Maximum key length - 128 Unicode characters in UTF-8
- Maximum value length - 256 Unicode characters in UTF-8
- If your tagging schema is used across multiple services and resources, remember that other services may have restrictions on allowed characters. Generally allowed characters are: letters, numbers, and spaces representable in UTF-8, and the following characters: + - = . _ : / @.
- Tag keys and values are case-sensitive.
- Do not use
aws:
,AWS:
, or any upper or lowercase combination of such as a prefix for either keys or values as it is reserved for Amazon Web Services use. You cannot edit or delete tag keys or values with this prefix. Tags with this prefix do not count against your tags per resource limit.
Request Lenses
createCluster_capacityProviders :: Lens' CreateCluster (Maybe [Text]) Source #
The short name of one or more capacity providers to associate with the cluster. A capacity provider must be associated with a cluster before it can be included as part of the default capacity provider strategy of the cluster or used in a capacity provider strategy when calling the CreateService or RunTask actions.
If specifying a capacity provider that uses an Auto Scaling group, the capacity provider must be created but not associated with another cluster. New Auto Scaling group capacity providers can be created with the CreateCapacityProvider API operation.
To use a Fargate capacity provider, specify either the FARGATE
or
FARGATE_SPOT
capacity providers. The Fargate capacity providers are
available to all accounts and only need to be associated with a cluster
to be used.
The PutClusterCapacityProviders API operation is used to update the list of available capacity providers for a cluster after the cluster is created.
createCluster_clusterName :: Lens' CreateCluster (Maybe Text) Source #
The name of your cluster. If you don't specify a name for your cluster,
you create a cluster that's named default
. Up to 255 letters
(uppercase and lowercase), numbers, underscores, and hyphens are
allowed.
createCluster_configuration :: Lens' CreateCluster (Maybe ClusterConfiguration) Source #
The execute
command configuration for the cluster.
createCluster_defaultCapacityProviderStrategy :: Lens' CreateCluster (Maybe [CapacityProviderStrategyItem]) Source #
The capacity provider strategy to set as the default for the cluster. After a default capacity provider strategy is set for a cluster, when you call the RunTask or CreateService APIs with no capacity provider strategy or launch type specified, the default capacity provider strategy for the cluster is used.
If a default capacity provider strategy isn't defined for a cluster when it was created, it can be defined later with the PutClusterCapacityProviders API operation.
createCluster_serviceConnectDefaults :: Lens' CreateCluster (Maybe ClusterServiceConnectDefaultsRequest) Source #
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.
createCluster_settings :: Lens' CreateCluster (Maybe [ClusterSetting]) Source #
The setting to use when creating a cluster. This parameter is used to
turn on CloudWatch Container Insights for a cluster. If this value is
specified, it overrides the containerInsights
value set with
PutAccountSetting or PutAccountSettingDefault.
createCluster_tags :: Lens' CreateCluster (Maybe [Tag]) Source #
The metadata that you apply to the cluster to help you categorize and organize them. Each tag consists of a key and an optional value. You define both.
The following basic restrictions apply to tags:
- Maximum number of tags per resource - 50
- For each resource, each tag key must be unique, and each tag key can have only one value.
- Maximum key length - 128 Unicode characters in UTF-8
- Maximum value length - 256 Unicode characters in UTF-8
- If your tagging schema is used across multiple services and resources, remember that other services may have restrictions on allowed characters. Generally allowed characters are: letters, numbers, and spaces representable in UTF-8, and the following characters: + - = . _ : / @.
- Tag keys and values are case-sensitive.
- Do not use
aws:
,AWS:
, or any upper or lowercase combination of such as a prefix for either keys or values as it is reserved for Amazon Web Services use. You cannot edit or delete tag keys or values with this prefix. Tags with this prefix do not count against your tags per resource limit.
Destructuring the Response
data CreateClusterResponse Source #
See: newCreateClusterResponse
smart constructor.
CreateClusterResponse' | |
|
Instances
newCreateClusterResponse Source #
Create a value of CreateClusterResponse
with all optional fields omitted.
Use generic-lens or optics to modify other optional fields.
The following record fields are available, with the corresponding lenses provided for backwards compatibility:
$sel:cluster:CreateClusterResponse'
, createClusterResponse_cluster
- The full description of your new cluster.
$sel:httpStatus:CreateClusterResponse'
, createClusterResponse_httpStatus
- The response's http status code.
Response Lenses
createClusterResponse_cluster :: Lens' CreateClusterResponse (Maybe Cluster) Source #
The full description of your new cluster.
createClusterResponse_httpStatus :: Lens' CreateClusterResponse Int Source #
The response's http status code.