Docs Home
This is the latest version of Azure Native. Use the Azure Native v2 docs if using the v2 version of this package.
Azure Native v3.2.0 published on Monday, Apr 14, 2025 by Pulumi
azure-native.awsconnector.EcsService
Explore with Pulumi AI
This is the latest version of Azure Native. Use the Azure Native v2 docs if using the v2 version of this package.
Azure Native v3.2.0 published on Monday, Apr 14, 2025 by Pulumi
A Microsoft.AwsConnector resource
Uses Azure REST API version 2024-12-01. In version 2.x of the Azure Native provider, it used API version 2024-12-01.
Create EcsService Resource
Resources are created with functions called constructors. To learn more about declaring and configuring resources, see Resources.
Constructor syntax
new EcsService(name: string, args: EcsServiceArgs, opts?: CustomResourceOptions);@overload
def EcsService(resource_name: str,
args: EcsServiceArgs,
opts: Optional[ResourceOptions] = None)
@overload
def EcsService(resource_name: str,
opts: Optional[ResourceOptions] = None,
resource_group_name: Optional[str] = None,
location: Optional[str] = None,
name: Optional[str] = None,
properties: Optional[EcsServicePropertiesArgs] = None,
tags: Optional[Mapping[str, str]] = None)func NewEcsService(ctx *Context, name string, args EcsServiceArgs, opts ...ResourceOption) (*EcsService, error)public EcsService(string name, EcsServiceArgs args, CustomResourceOptions? opts = null)public EcsService(String name, EcsServiceArgs args)
public EcsService(String name, EcsServiceArgs args, CustomResourceOptions options)
type: azure-native:awsconnector:EcsService
properties: # The arguments to resource properties.
options: # Bag of options to control resource's behavior.
Parameters
- name
This property is required. string - The unique name of the resource.
- args
This property is required. EcsServiceArgs - The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- resource_name
This property is required. str - The unique name of the resource.
- args
This property is required. EcsServiceArgs - The arguments to resource properties.
- opts ResourceOptions
- Bag of options to control resource's behavior.
- ctx Context
- Context object for the current deployment.
- name
This property is required. string - The unique name of the resource.
- args
This property is required. EcsServiceArgs - The arguments to resource properties.
- opts ResourceOption
- Bag of options to control resource's behavior.
- name
This property is required. string - The unique name of the resource.
- args
This property is required. EcsServiceArgs - The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- name
This property is required. String - The unique name of the resource.
- args
This property is required. EcsServiceArgs - The arguments to resource properties.
- options CustomResourceOptions
- Bag of options to control resource's behavior.
Constructor example
The following reference example uses placeholder values for all input properties.
var ecsServiceResource = new AzureNative.AwsConnector.EcsService("ecsServiceResource", new()
{
ResourceGroupName = "string",
Location = "string",
Name = "string",
Properties = new AzureNative.AwsConnector.Inputs.EcsServicePropertiesArgs
{
Arn = "string",
AwsAccountId = "string",
AwsProperties = new AzureNative.AwsConnector.Inputs.AwsEcsServicePropertiesArgs
{
CapacityProviderStrategy = new[]
{
new AzureNative.AwsConnector.Inputs.CapacityProviderStrategyItemArgs
{
Base = 0,
CapacityProvider = "string",
Weight = 0,
},
},
Cluster = "string",
DeploymentConfiguration = new AzureNative.AwsConnector.Inputs.DeploymentConfigurationArgs
{
Alarms = new AzureNative.AwsConnector.Inputs.DeploymentAlarmsArgs
{
AlarmNames = new[]
{
"string",
},
Enable = false,
Rollback = false,
},
DeploymentCircuitBreaker = new AzureNative.AwsConnector.Inputs.DeploymentCircuitBreakerArgs
{
Enable = false,
Rollback = false,
},
MaximumPercent = 0,
MinimumHealthyPercent = 0,
},
DeploymentController = new AzureNative.AwsConnector.Inputs.DeploymentControllerArgs
{
Type = "string",
},
DesiredCount = 0,
EnableECSManagedTags = false,
EnableExecuteCommand = false,
HealthCheckGracePeriodSeconds = 0,
LaunchType = "string",
LoadBalancers = new[]
{
new AzureNative.AwsConnector.Inputs.LoadBalancerArgs
{
ContainerName = "string",
ContainerPort = 0,
LoadBalancerName = "string",
TargetGroupArn = "string",
},
},
Name = "string",
NetworkConfiguration = new AzureNative.AwsConnector.Inputs.NetworkConfigurationArgs
{
AwsvpcConfiguration = new AzureNative.AwsConnector.Inputs.AwsVpcConfigurationArgs
{
AssignPublicIp = "string",
SecurityGroups = new[]
{
"string",
},
Subnets = new[]
{
"string",
},
},
},
PlacementConstraints = new[]
{
new AzureNative.AwsConnector.Inputs.PlacementConstraintArgs
{
Expression = "string",
Type = "string",
},
},
PlacementStrategies = new[]
{
new AzureNative.AwsConnector.Inputs.PlacementStrategyArgs
{
Field = "string",
Type = "string",
},
},
PlatformVersion = "string",
PropagateTags = "string",
Role = "string",
SchedulingStrategy = "string",
ServiceArn = "string",
ServiceConnectConfiguration = new AzureNative.AwsConnector.Inputs.ServiceConnectConfigurationArgs
{
Enabled = false,
LogConfiguration = new AzureNative.AwsConnector.Inputs.LogConfigurationArgs
{
LogDriver = "string",
Options = "any",
SecretOptions = new[]
{
new AzureNative.AwsConnector.Inputs.SecretArgs
{
Name = "string",
ValueFrom = "string",
},
},
},
Namespace = "string",
Services = new[]
{
new AzureNative.AwsConnector.Inputs.ServiceConnectServiceArgs
{
ClientAliases = new[]
{
new AzureNative.AwsConnector.Inputs.ServiceConnectClientAliasArgs
{
DnsName = "string",
Port = 0,
},
},
DiscoveryName = "string",
IngressPortOverride = 0,
PortName = "string",
Timeout = new AzureNative.AwsConnector.Inputs.TimeoutConfigurationArgs
{
IdleTimeoutSeconds = 0,
PerRequestTimeoutSeconds = 0,
},
Tls = new AzureNative.AwsConnector.Inputs.ServiceConnectTlsConfigurationArgs
{
IssuerCertificateAuthority = new AzureNative.AwsConnector.Inputs.ServiceConnectTlsCertificateAuthorityArgs
{
AwsPcaAuthorityArn = "string",
},
KmsKey = "string",
RoleArn = "string",
},
},
},
},
ServiceName = "string",
ServiceRegistries = new[]
{
new AzureNative.AwsConnector.Inputs.ServiceRegistryArgs
{
ContainerName = "string",
ContainerPort = 0,
Port = 0,
RegistryArn = "string",
},
},
Tags = new[]
{
new AzureNative.AwsConnector.Inputs.TagArgs
{
Key = "string",
Value = "string",
},
},
TaskDefinition = "string",
VolumeConfigurations = new[]
{
new AzureNative.AwsConnector.Inputs.ServiceVolumeConfigurationArgs
{
ManagedEBSVolume = new AzureNative.AwsConnector.Inputs.ServiceManagedEBSVolumeConfigurationArgs
{
Encrypted = false,
FilesystemType = "string",
Iops = 0,
KmsKeyId = "string",
RoleArn = "string",
SizeInGiB = 0,
SnapshotId = "string",
TagSpecifications = new[]
{
new AzureNative.AwsConnector.Inputs.EBSTagSpecificationArgs
{
PropagateTags = "string",
ResourceType = "string",
Tags = new[]
{
new AzureNative.AwsConnector.Inputs.TagArgs
{
Key = "string",
Value = "string",
},
},
},
},
Throughput = 0,
VolumeType = "string",
},
Name = "string",
},
},
},
AwsRegion = "string",
AwsSourceSchema = "string",
AwsTags =
{
{ "string", "string" },
},
PublicCloudConnectorsResourceId = "string",
PublicCloudResourceName = "string",
},
Tags =
{
{ "string", "string" },
},
});
example, err := awsconnector.NewEcsService(ctx, "ecsServiceResource", &awsconnector.EcsServiceArgs{
ResourceGroupName: pulumi.String("string"),
Location: pulumi.String("string"),
Name: pulumi.String("string"),
Properties: &awsconnector.EcsServicePropertiesArgs{
Arn: pulumi.String("string"),
AwsAccountId: pulumi.String("string"),
AwsProperties: &awsconnector.AwsEcsServicePropertiesArgs{
CapacityProviderStrategy: awsconnector.CapacityProviderStrategyItemArray{
&awsconnector.CapacityProviderStrategyItemArgs{
Base: pulumi.Int(0),
CapacityProvider: pulumi.String("string"),
Weight: pulumi.Int(0),
},
},
Cluster: pulumi.String("string"),
DeploymentConfiguration: &awsconnector.DeploymentConfigurationArgs{
Alarms: &awsconnector.DeploymentAlarmsArgs{
AlarmNames: pulumi.StringArray{
pulumi.String("string"),
},
Enable: pulumi.Bool(false),
Rollback: pulumi.Bool(false),
},
DeploymentCircuitBreaker: &awsconnector.DeploymentCircuitBreakerArgs{
Enable: pulumi.Bool(false),
Rollback: pulumi.Bool(false),
},
MaximumPercent: pulumi.Int(0),
MinimumHealthyPercent: pulumi.Int(0),
},
DeploymentController: &awsconnector.DeploymentControllerArgs{
Type: pulumi.String("string"),
},
DesiredCount: pulumi.Int(0),
EnableECSManagedTags: pulumi.Bool(false),
EnableExecuteCommand: pulumi.Bool(false),
HealthCheckGracePeriodSeconds: pulumi.Int(0),
LaunchType: pulumi.String("string"),
LoadBalancers: awsconnector.LoadBalancerArray{
&awsconnector.LoadBalancerArgs{
ContainerName: pulumi.String("string"),
ContainerPort: pulumi.Int(0),
LoadBalancerName: pulumi.String("string"),
TargetGroupArn: pulumi.String("string"),
},
},
Name: pulumi.String("string"),
NetworkConfiguration: &awsconnector.NetworkConfigurationArgs{
AwsvpcConfiguration: &awsconnector.AwsVpcConfigurationArgs{
AssignPublicIp: pulumi.String("string"),
SecurityGroups: pulumi.StringArray{
pulumi.String("string"),
},
Subnets: pulumi.StringArray{
pulumi.String("string"),
},
},
},
PlacementConstraints: awsconnector.PlacementConstraintArray{
&awsconnector.PlacementConstraintArgs{
Expression: pulumi.String("string"),
Type: pulumi.String("string"),
},
},
PlacementStrategies: awsconnector.PlacementStrategyArray{
&awsconnector.PlacementStrategyArgs{
Field: pulumi.String("string"),
Type: pulumi.String("string"),
},
},
PlatformVersion: pulumi.String("string"),
PropagateTags: pulumi.String("string"),
Role: pulumi.String("string"),
SchedulingStrategy: pulumi.String("string"),
ServiceArn: pulumi.String("string"),
ServiceConnectConfiguration: &awsconnector.ServiceConnectConfigurationArgs{
Enabled: pulumi.Bool(false),
LogConfiguration: &awsconnector.LogConfigurationArgs{
LogDriver: pulumi.String("string"),
Options: pulumi.Any("any"),
SecretOptions: awsconnector.SecretArray{
&awsconnector.SecretArgs{
Name: pulumi.String("string"),
ValueFrom: pulumi.String("string"),
},
},
},
Namespace: pulumi.String("string"),
Services: awsconnector.ServiceConnectServiceArray{
&awsconnector.ServiceConnectServiceArgs{
ClientAliases: awsconnector.ServiceConnectClientAliasArray{
&awsconnector.ServiceConnectClientAliasArgs{
DnsName: pulumi.String("string"),
Port: pulumi.Int(0),
},
},
DiscoveryName: pulumi.String("string"),
IngressPortOverride: pulumi.Int(0),
PortName: pulumi.String("string"),
Timeout: &awsconnector.TimeoutConfigurationArgs{
IdleTimeoutSeconds: pulumi.Int(0),
PerRequestTimeoutSeconds: pulumi.Int(0),
},
Tls: &awsconnector.ServiceConnectTlsConfigurationArgs{
IssuerCertificateAuthority: &awsconnector.ServiceConnectTlsCertificateAuthorityArgs{
AwsPcaAuthorityArn: pulumi.String("string"),
},
KmsKey: pulumi.String("string"),
RoleArn: pulumi.String("string"),
},
},
},
},
ServiceName: pulumi.String("string"),
ServiceRegistries: awsconnector.ServiceRegistryArray{
&awsconnector.ServiceRegistryArgs{
ContainerName: pulumi.String("string"),
ContainerPort: pulumi.Int(0),
Port: pulumi.Int(0),
RegistryArn: pulumi.String("string"),
},
},
Tags: awsconnector.TagArray{
&awsconnector.TagArgs{
Key: pulumi.String("string"),
Value: pulumi.String("string"),
},
},
TaskDefinition: pulumi.String("string"),
VolumeConfigurations: awsconnector.ServiceVolumeConfigurationArray{
&awsconnector.ServiceVolumeConfigurationArgs{
ManagedEBSVolume: &awsconnector.ServiceManagedEBSVolumeConfigurationArgs{
Encrypted: pulumi.Bool(false),
FilesystemType: pulumi.String("string"),
Iops: pulumi.Int(0),
KmsKeyId: pulumi.String("string"),
RoleArn: pulumi.String("string"),
SizeInGiB: pulumi.Int(0),
SnapshotId: pulumi.String("string"),
TagSpecifications: awsconnector.EBSTagSpecificationArray{
&awsconnector.EBSTagSpecificationArgs{
PropagateTags: pulumi.String("string"),
ResourceType: pulumi.String("string"),
Tags: awsconnector.TagArray{
&awsconnector.TagArgs{
Key: pulumi.String("string"),
Value: pulumi.String("string"),
},
},
},
},
Throughput: pulumi.Int(0),
VolumeType: pulumi.String("string"),
},
Name: pulumi.String("string"),
},
},
},
AwsRegion: pulumi.String("string"),
AwsSourceSchema: pulumi.String("string"),
AwsTags: pulumi.StringMap{
"string": pulumi.String("string"),
},
PublicCloudConnectorsResourceId: pulumi.String("string"),
PublicCloudResourceName: pulumi.String("string"),
},
Tags: pulumi.StringMap{
"string": pulumi.String("string"),
},
})
var ecsServiceResource = new EcsService("ecsServiceResource", EcsServiceArgs.builder()
.resourceGroupName("string")
.location("string")
.name("string")
.properties(EcsServicePropertiesArgs.builder()
.arn("string")
.awsAccountId("string")
.awsProperties(AwsEcsServicePropertiesArgs.builder()
.capacityProviderStrategy(CapacityProviderStrategyItemArgs.builder()
.base(0)
.capacityProvider("string")
.weight(0)
.build())
.cluster("string")
.deploymentConfiguration(DeploymentConfigurationArgs.builder()
.alarms(DeploymentAlarmsArgs.builder()
.alarmNames("string")
.enable(false)
.rollback(false)
.build())
.deploymentCircuitBreaker(DeploymentCircuitBreakerArgs.builder()
.enable(false)
.rollback(false)
.build())
.maximumPercent(0)
.minimumHealthyPercent(0)
.build())
.deploymentController(DeploymentControllerArgs.builder()
.type("string")
.build())
.desiredCount(0)
.enableECSManagedTags(false)
.enableExecuteCommand(false)
.healthCheckGracePeriodSeconds(0)
.launchType("string")
.loadBalancers(LoadBalancerArgs.builder()
.containerName("string")
.containerPort(0)
.loadBalancerName("string")
.targetGroupArn("string")
.build())
.name("string")
.networkConfiguration(NetworkConfigurationArgs.builder()
.awsvpcConfiguration(AwsVpcConfigurationArgs.builder()
.assignPublicIp("string")
.securityGroups("string")
.subnets("string")
.build())
.build())
.placementConstraints(PlacementConstraintArgs.builder()
.expression("string")
.type("string")
.build())
.placementStrategies(PlacementStrategyArgs.builder()
.field("string")
.type("string")
.build())
.platformVersion("string")
.propagateTags("string")
.role("string")
.schedulingStrategy("string")
.serviceArn("string")
.serviceConnectConfiguration(ServiceConnectConfigurationArgs.builder()
.enabled(false)
.logConfiguration(LogConfigurationArgs.builder()
.logDriver("string")
.options("any")
.secretOptions(SecretArgs.builder()
.name("string")
.valueFrom("string")
.build())
.build())
.namespace("string")
.services(ServiceConnectServiceArgs.builder()
.clientAliases(ServiceConnectClientAliasArgs.builder()
.dnsName("string")
.port(0)
.build())
.discoveryName("string")
.ingressPortOverride(0)
.portName("string")
.timeout(TimeoutConfigurationArgs.builder()
.idleTimeoutSeconds(0)
.perRequestTimeoutSeconds(0)
.build())
.tls(ServiceConnectTlsConfigurationArgs.builder()
.issuerCertificateAuthority(ServiceConnectTlsCertificateAuthorityArgs.builder()
.awsPcaAuthorityArn("string")
.build())
.kmsKey("string")
.roleArn("string")
.build())
.build())
.build())
.serviceName("string")
.serviceRegistries(ServiceRegistryArgs.builder()
.containerName("string")
.containerPort(0)
.port(0)
.registryArn("string")
.build())
.tags(TagArgs.builder()
.key("string")
.value("string")
.build())
.taskDefinition("string")
.volumeConfigurations(ServiceVolumeConfigurationArgs.builder()
.managedEBSVolume(ServiceManagedEBSVolumeConfigurationArgs.builder()
.encrypted(false)
.filesystemType("string")
.iops(0)
.kmsKeyId("string")
.roleArn("string")
.sizeInGiB(0)
.snapshotId("string")
.tagSpecifications(EBSTagSpecificationArgs.builder()
.propagateTags("string")
.resourceType("string")
.tags(TagArgs.builder()
.key("string")
.value("string")
.build())
.build())
.throughput(0)
.volumeType("string")
.build())
.name("string")
.build())
.build())
.awsRegion("string")
.awsSourceSchema("string")
.awsTags(Map.of("string", "string"))
.publicCloudConnectorsResourceId("string")
.publicCloudResourceName("string")
.build())
.tags(Map.of("string", "string"))
.build());
ecs_service_resource = azure_native.awsconnector.EcsService("ecsServiceResource",
resource_group_name="string",
location="string",
name="string",
properties={
"arn": "string",
"aws_account_id": "string",
"aws_properties": {
"capacity_provider_strategy": [{
"base": 0,
"capacity_provider": "string",
"weight": 0,
}],
"cluster": "string",
"deployment_configuration": {
"alarms": {
"alarm_names": ["string"],
"enable": False,
"rollback": False,
},
"deployment_circuit_breaker": {
"enable": False,
"rollback": False,
},
"maximum_percent": 0,
"minimum_healthy_percent": 0,
},
"deployment_controller": {
"type": "string",
},
"desired_count": 0,
"enable_ecs_managed_tags": False,
"enable_execute_command": False,
"health_check_grace_period_seconds": 0,
"launch_type": "string",
"load_balancers": [{
"container_name": "string",
"container_port": 0,
"load_balancer_name": "string",
"target_group_arn": "string",
}],
"name": "string",
"network_configuration": {
"awsvpc_configuration": {
"assign_public_ip": "string",
"security_groups": ["string"],
"subnets": ["string"],
},
},
"placement_constraints": [{
"expression": "string",
"type": "string",
}],
"placement_strategies": [{
"field": "string",
"type": "string",
}],
"platform_version": "string",
"propagate_tags": "string",
"role": "string",
"scheduling_strategy": "string",
"service_arn": "string",
"service_connect_configuration": {
"enabled": False,
"log_configuration": {
"log_driver": "string",
"options": "any",
"secret_options": [{
"name": "string",
"value_from": "string",
}],
},
"namespace": "string",
"services": [{
"client_aliases": [{
"dns_name": "string",
"port": 0,
}],
"discovery_name": "string",
"ingress_port_override": 0,
"port_name": "string",
"timeout": {
"idle_timeout_seconds": 0,
"per_request_timeout_seconds": 0,
},
"tls": {
"issuer_certificate_authority": {
"aws_pca_authority_arn": "string",
},
"kms_key": "string",
"role_arn": "string",
},
}],
},
"service_name": "string",
"service_registries": [{
"container_name": "string",
"container_port": 0,
"port": 0,
"registry_arn": "string",
}],
"tags": [{
"key": "string",
"value": "string",
}],
"task_definition": "string",
"volume_configurations": [{
"managed_ebs_volume": {
"encrypted": False,
"filesystem_type": "string",
"iops": 0,
"kms_key_id": "string",
"role_arn": "string",
"size_in_gi_b": 0,
"snapshot_id": "string",
"tag_specifications": [{
"propagate_tags": "string",
"resource_type": "string",
"tags": [{
"key": "string",
"value": "string",
}],
}],
"throughput": 0,
"volume_type": "string",
},
"name": "string",
}],
},
"aws_region": "string",
"aws_source_schema": "string",
"aws_tags": {
"string": "string",
},
"public_cloud_connectors_resource_id": "string",
"public_cloud_resource_name": "string",
},
tags={
"string": "string",
})
const ecsServiceResource = new azure_native.awsconnector.EcsService("ecsServiceResource", {
resourceGroupName: "string",
location: "string",
name: "string",
properties: {
arn: "string",
awsAccountId: "string",
awsProperties: {
capacityProviderStrategy: [{
base: 0,
capacityProvider: "string",
weight: 0,
}],
cluster: "string",
deploymentConfiguration: {
alarms: {
alarmNames: ["string"],
enable: false,
rollback: false,
},
deploymentCircuitBreaker: {
enable: false,
rollback: false,
},
maximumPercent: 0,
minimumHealthyPercent: 0,
},
deploymentController: {
type: "string",
},
desiredCount: 0,
enableECSManagedTags: false,
enableExecuteCommand: false,
healthCheckGracePeriodSeconds: 0,
launchType: "string",
loadBalancers: [{
containerName: "string",
containerPort: 0,
loadBalancerName: "string",
targetGroupArn: "string",
}],
name: "string",
networkConfiguration: {
awsvpcConfiguration: {
assignPublicIp: "string",
securityGroups: ["string"],
subnets: ["string"],
},
},
placementConstraints: [{
expression: "string",
type: "string",
}],
placementStrategies: [{
field: "string",
type: "string",
}],
platformVersion: "string",
propagateTags: "string",
role: "string",
schedulingStrategy: "string",
serviceArn: "string",
serviceConnectConfiguration: {
enabled: false,
logConfiguration: {
logDriver: "string",
options: "any",
secretOptions: [{
name: "string",
valueFrom: "string",
}],
},
namespace: "string",
services: [{
clientAliases: [{
dnsName: "string",
port: 0,
}],
discoveryName: "string",
ingressPortOverride: 0,
portName: "string",
timeout: {
idleTimeoutSeconds: 0,
perRequestTimeoutSeconds: 0,
},
tls: {
issuerCertificateAuthority: {
awsPcaAuthorityArn: "string",
},
kmsKey: "string",
roleArn: "string",
},
}],
},
serviceName: "string",
serviceRegistries: [{
containerName: "string",
containerPort: 0,
port: 0,
registryArn: "string",
}],
tags: [{
key: "string",
value: "string",
}],
taskDefinition: "string",
volumeConfigurations: [{
managedEBSVolume: {
encrypted: false,
filesystemType: "string",
iops: 0,
kmsKeyId: "string",
roleArn: "string",
sizeInGiB: 0,
snapshotId: "string",
tagSpecifications: [{
propagateTags: "string",
resourceType: "string",
tags: [{
key: "string",
value: "string",
}],
}],
throughput: 0,
volumeType: "string",
},
name: "string",
}],
},
awsRegion: "string",
awsSourceSchema: "string",
awsTags: {
string: "string",
},
publicCloudConnectorsResourceId: "string",
publicCloudResourceName: "string",
},
tags: {
string: "string",
},
});
type: azure-native:awsconnector:EcsService
properties:
location: string
name: string
properties:
arn: string
awsAccountId: string
awsProperties:
capacityProviderStrategy:
- base: 0
capacityProvider: string
weight: 0
cluster: string
deploymentConfiguration:
alarms:
alarmNames:
- string
enable: false
rollback: false
deploymentCircuitBreaker:
enable: false
rollback: false
maximumPercent: 0
minimumHealthyPercent: 0
deploymentController:
type: string
desiredCount: 0
enableECSManagedTags: false
enableExecuteCommand: false
healthCheckGracePeriodSeconds: 0
launchType: string
loadBalancers:
- containerName: string
containerPort: 0
loadBalancerName: string
targetGroupArn: string
name: string
networkConfiguration:
awsvpcConfiguration:
assignPublicIp: string
securityGroups:
- string
subnets:
- string
placementConstraints:
- expression: string
type: string
placementStrategies:
- field: string
type: string
platformVersion: string
propagateTags: string
role: string
schedulingStrategy: string
serviceArn: string
serviceConnectConfiguration:
enabled: false
logConfiguration:
logDriver: string
options: any
secretOptions:
- name: string
valueFrom: string
namespace: string
services:
- clientAliases:
- dnsName: string
port: 0
discoveryName: string
ingressPortOverride: 0
portName: string
timeout:
idleTimeoutSeconds: 0
perRequestTimeoutSeconds: 0
tls:
issuerCertificateAuthority:
awsPcaAuthorityArn: string
kmsKey: string
roleArn: string
serviceName: string
serviceRegistries:
- containerName: string
containerPort: 0
port: 0
registryArn: string
tags:
- key: string
value: string
taskDefinition: string
volumeConfigurations:
- managedEBSVolume:
encrypted: false
filesystemType: string
iops: 0
kmsKeyId: string
roleArn: string
sizeInGiB: 0
snapshotId: string
tagSpecifications:
- propagateTags: string
resourceType: string
tags:
- key: string
value: string
throughput: 0
volumeType: string
name: string
awsRegion: string
awsSourceSchema: string
awsTags:
string: string
publicCloudConnectorsResourceId: string
publicCloudResourceName: string
resourceGroupName: string
tags:
string: string
EcsService Resource Properties
To learn more about resource properties and how to use them, see Inputs and Outputs in the Architecture and Concepts docs.
Inputs
In Python, inputs that are objects can be passed either as argument classes or as dictionary literals.
The EcsService resource accepts the following input properties:
- Resource
Group Name stringThis property is required. 
Changes to this property will trigger replacement. - The name of the resource group. The name is case insensitive.
- Location
- The geo-location where the resource lives
- Name
- Name of EcsService
- Properties
Pulumi.
Azure Native. Aws Connector. Inputs. Ecs Service Properties - The resource-specific properties for this resource.
- Dictionary<string, string>
- Resource tags.
- Resource
Group Name stringThis property is required. Changes to this property will trigger replacement. - The name of the resource group. The name is case insensitive.
- Location
- The geo-location where the resource lives
- Name
- Name of EcsService
- Properties
Ecs
Service Properties Args - The resource-specific properties for this resource.
- map[string]string
- Resource tags.
- resource
Group Name StringThis property is required. Changes to this property will trigger replacement. - The name of the resource group. The name is case insensitive.
- location
- The geo-location where the resource lives
- name
- Name of EcsService
- properties
Ecs
Service Properties - The resource-specific properties for this resource.
- Map<String,String>
- Resource tags.
- resource
Group Name stringThis property is required. Changes to this property will trigger replacement. - The name of the resource group. The name is case insensitive.
- location
- The geo-location where the resource lives
- name
- Name of EcsService
- properties
Ecs
Service Properties - The resource-specific properties for this resource.
- {[key: string]: string}
- Resource tags.
- resource_
group_ name strThis property is required. Changes to this property will trigger replacement. - The name of the resource group. The name is case insensitive.
- location
- The geo-location where the resource lives
- name
- Name of EcsService
- properties
Ecs
Service Properties Args - The resource-specific properties for this resource.
- Mapping[str, str]
- Resource tags.
- resource
Group Name StringThis property is required. Changes to this property will trigger replacement. - The name of the resource group. The name is case insensitive.
- location
- The geo-location where the resource lives
- name
- Name of EcsService
- properties Property Map
- The resource-specific properties for this resource.
- Map<String>
- Resource tags.
Outputs
All input properties are implicitly available as output properties. Additionally, the EcsService resource produces the following output properties:
- Azure
Api stringVersion - The Azure API version of the resource.
- Id string
- The provider-assigned unique ID for this managed resource.
- System
Data Pulumi.Azure Native. Aws Connector. Outputs. System Data Response - Azure Resource Manager metadata containing createdBy and modifiedBy information.
- Type string
- The type of the resource. E.g. "Microsoft.Compute/virtualMachines" or "Microsoft.Storage/storageAccounts"
- Azure
Api stringVersion - The Azure API version of the resource.
- Id string
- The provider-assigned unique ID for this managed resource.
- System
Data SystemData Response - Azure Resource Manager metadata containing createdBy and modifiedBy information.
- Type string
- The type of the resource. E.g. "Microsoft.Compute/virtualMachines" or "Microsoft.Storage/storageAccounts"
- azure
Api StringVersion - The Azure API version of the resource.
- id String
- The provider-assigned unique ID for this managed resource.
- system
Data SystemData Response - Azure Resource Manager metadata containing createdBy and modifiedBy information.
- type String
- The type of the resource. E.g. "Microsoft.Compute/virtualMachines" or "Microsoft.Storage/storageAccounts"
- azure
Api stringVersion - The Azure API version of the resource.
- id string
- The provider-assigned unique ID for this managed resource.
- system
Data SystemData Response - Azure Resource Manager metadata containing createdBy and modifiedBy information.
- type string
- The type of the resource. E.g. "Microsoft.Compute/virtualMachines" or "Microsoft.Storage/storageAccounts"
- azure_
api_ strversion - The Azure API version of the resource.
- id str
- The provider-assigned unique ID for this managed resource.
- system_
data SystemData Response - Azure Resource Manager metadata containing createdBy and modifiedBy information.
- type str
- The type of the resource. E.g. "Microsoft.Compute/virtualMachines" or "Microsoft.Storage/storageAccounts"
- azure
Api StringVersion - The Azure API version of the resource.
- id String
- The provider-assigned unique ID for this managed resource.
- system
Data Property Map - Azure Resource Manager metadata containing createdBy and modifiedBy information.
- type String
- The type of the resource. E.g. "Microsoft.Compute/virtualMachines" or "Microsoft.Storage/storageAccounts"
Supporting Types
AwsEcsServiceProperties, AwsEcsServicePropertiesArgs
, AwsEcsServicePropertiesArgs
- Capacity
Provider List<Pulumi.Strategy Azure Native. Aws Connector. Inputs. Capacity Provider Strategy Item> - The capacity provider strategy to use for the service. If a
capacityProviderStrategyis specified, thelaunchTypeparameter must be omitted. If nocapacityProviderStrategyorlaunchTypeis specified, thedefaultCapacityProviderStrategyfor the cluster is used. A capacity provider strategy may contain a maximum of 6 capacity providers. - Cluster string
- The short name or full Amazon Resource Name (ARN) of the cluster that you run your service on. If you do not specify a cluster, the default cluster is assumed.
- Deployment
Configuration Pulumi.Azure Native. Aws Connector. Inputs. Deployment Configuration - Optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks. The
DeploymentConfigurationproperty specifies optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks. - Deployment
Controller Pulumi.Azure Native. Aws Connector. Inputs. Deployment Controller - The deployment controller to use for the service. If no deployment controller is specified, the default value of
ECSis used. The deployment controller to use for the service. For more information, see Amazon ECS deployment types in the Amazon Elastic Container Service Developer Guide. - Desired
Count int - The number of instantiations of the specified task definition to place and keep running in your service. For new services, if a desired count is not specified, a default value of
1is used. When using theDAEMONscheduling strategy, the desired count is not required. For existing services, if a desired count is not specified, it is omitted from the operation. - bool
- Specifies whether to turn on Amazon ECS managed tags for the tasks within the service. For more information, see Tagging your Amazon ECS resources in the Amazon Elastic Container Service Developer Guide. When you use Amazon ECS managed tags, you need to set the
propagateTagsrequest parameter. - Enable
Execute boolCommand - Determines whether the execute command functionality is turned on for the service. If
true, the execute command functionality is turned on for all containers in tasks as part of the service. - Health
Check intGrace Period Seconds - The period of time, in seconds, that the Amazon ECS service scheduler ignores unhealthy Elastic Load Balancing target health checks after a task has first started. This is only used when your service is configured to use a load balancer. If your service has a load balancer defined and you don't specify a health check grace period value, the default value of
0is used. If you do not use an Elastic Load Balancing, we recommend that you use thestartPeriodin the task definition health check parameters. For more information, see Health check. If your service's tasks take a while to start and respond to Elastic Load Balancing health checks, you can specify a health check grace period of up to 2,147,483,647 seconds (about 69 years). During that time, the Amazon ECS service scheduler ignores health check status. This grace period can prevent the service scheduler from marking tasks as unhealthy and stopping them before they have time to come up. - Launch
Type string | Pulumi.Azure Native. Aws Connector. Launch Type - The launch type on which to run your service. For more information, see Amazon ECS Launch Types in the Amazon Elastic Container Service Developer Guide.
- Load
Balancers List<Pulumi.Azure Native. Aws Connector. Inputs. Load Balancer> - A list of load balancer objects to associate with the service. If you specify the
Roleproperty,LoadBalancersmust be specified as well. For information about the number of load balancers that you can specify per service, see Service Load Balancing in the Amazon Elastic Container Service Developer Guide. - Name string
- Property name
- Network
Configuration Pulumi.Azure Native. Aws Connector. Inputs. Network Configuration - The network configuration for the service. This parameter is required for task definitions that use the
awsvpcnetwork mode to receive their own elastic network interface, and it is not supported for other network modes. For more information, see Task Networking in the Amazon Elastic Container Service Developer Guide. TheNetworkConfigurationproperty specifies an object representing the network configuration for a task or service. - Placement
Constraints List<Pulumi.Azure Native. Aws Connector. Inputs. Placement Constraint> - An array of placement constraint objects to use for tasks in your service. You can specify a maximum of 10 constraints for each task. This limit includes constraints in the task definition and those specified at runtime.
- Placement
Strategies List<Pulumi.Azure Native. Aws Connector. Inputs. Placement Strategy> - The placement strategy objects to use for tasks in your service. You can specify a maximum of 5 strategy rules for each service.
- Platform
Version string - The platform version that your tasks in the service are running on. A platform version is specified only for tasks using the Fargate launch type. If one isn't specified, the
LATESTplatform version is used. For more information, see platform versions in the Amazon Elastic Container Service Developer Guide. -
string | Pulumi.
Azure Native. Aws Connector. Propagate Tags - Specifies whether to propagate the tags from the task definition to the task. If no value is specified, the tags aren't propagated. Tags can only be propagated to the task during task creation. To add tags to a task after task creation, use the TagResource API action. The default is
NONE. - Role string
- The name or full Amazon Resource Name (ARN) of the IAM role that allows Amazon ECS to make calls to your load balancer on your behalf. This parameter is only permitted if you are using a load balancer with your service and your task definition doesn't use the
awsvpcnetwork mode. If you specify theroleparameter, you must also specify a load balancer object with theloadBalancersparameter. If your account has already created the Amazon ECS service-linked role, that role is used for your service unless you specify a role here. The service-linked role is required if your task definition uses theawsvpcnetwork mode or if the service is configured to use service discovery, an external deployment controller, multiple target groups, or Elastic Inference accelerators in which case you don't specify a role here. For more information, see Using service-linked roles for Amazon ECS in the Amazon Elastic Container Service Developer Guide. If your specified role has a path other than/, then you must either specify the full role ARN (this is recommended) or prefix the role name with the path. For example, if a role with the namebarhas a path of/foo/then you would specify/foo/baras the role name. For more information, see Friendly names and paths in the IAM User Guide. - Scheduling
Strategy string | Pulumi.Azure Native. Aws Connector. Scheduling Strategy - The scheduling strategy to use for the service. For more information, see Services. There are two service scheduler strategies available: +
REPLICA-The replica scheduling strategy places and maintains the desired number of tasks across your cluster. By default, the service scheduler spreads tasks across Availability Zones. You can use task placement strategies and constraints to customize task placement decisions. This scheduler strategy is required if the service uses theCODE_DEPLOYorEXTERNALdeployment controller types. +DAEMON-The daemon scheduling strategy deploys exactly one task on each active container instance that meets all of the task placement constraints that you specify in your cluster. The service scheduler also evaluates the task placement constraints for running tasks and will stop tasks that don't meet the placement constraints. When you're using this strategy, you don't need to specify a desired number of tasks, a task placement strategy, or use Service Auto Scaling policies. Tasks using the Fargate launch type or theCODE_DEPLOYorEXTERNALdeployment controller types don't support theDAEMONscheduling strategy. - Service
Arn string - Property serviceArn
- Service
Connect Pulumi.Configuration Azure Native. Aws Connector. Inputs. Service Connect Configuration - The configuration for this service to discover and connect to services, and be discovered by, and connected from, other services within a namespace. 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. The Service Connect configuration of your Amazon ECS service. The configuration for this service to discover and connect to services, and be discovered by, and connected from, other services within a namespace. 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.
- Service
Name string - The name of your service. Up to 255 letters (uppercase and lowercase), numbers, underscores, and hyphens are allowed. Service names must be unique within a cluster, but you can have similarly named services in multiple clusters within a Region or across multiple Regions. The stack update fails if you change any properties that require replacement and the
ServiceNameis configured. This is because AWS CloudFormation creates the replacement service first, but eachServiceNamemust be unique in the cluster. - Service
Registries List<Pulumi.Azure Native. Aws Connector. Inputs. Service Registry> - The details of the service discovery registry to associate with this service. For more information, see Service discovery. Each service may be associated with one service registry. Multiple service registries for each service isn't supported.
-
List<Pulumi.
Azure Native. Aws Connector. Inputs. Tag> - The metadata that you apply to the service to help you categorize and organize them. Each tag consists of a key and an optional value, both of which you define. When a service is deleted, the tags are deleted as well. 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 AWS 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. - Task
Definition string - The
familyandrevision(family:revision) or full ARN of the task definition to run in your service. If arevisionisn't specified, the latestACTIVErevision is used. A task definition must be specified if the service uses either theECSorCODE_DEPLOYdeployment controllers. For more information about deployment types, see Amazon ECS deployment types. - Volume
Configurations List<Pulumi.Azure Native. Aws Connector. Inputs. Service Volume Configuration> - The configuration for a volume specified in the task definition as a volume that is configured at launch time. Currently, the only supported volume type is an Amazon EBS volume.
- Capacity
Provider []CapacityStrategy Provider Strategy Item - The capacity provider strategy to use for the service. If a
capacityProviderStrategyis specified, thelaunchTypeparameter must be omitted. If nocapacityProviderStrategyorlaunchTypeis specified, thedefaultCapacityProviderStrategyfor the cluster is used. A capacity provider strategy may contain a maximum of 6 capacity providers. - Cluster string
- The short name or full Amazon Resource Name (ARN) of the cluster that you run your service on. If you do not specify a cluster, the default cluster is assumed.
- Deployment
Configuration DeploymentConfiguration - Optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks. The
DeploymentConfigurationproperty specifies optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks. - Deployment
Controller DeploymentController - The deployment controller to use for the service. If no deployment controller is specified, the default value of
ECSis used. The deployment controller to use for the service. For more information, see Amazon ECS deployment types in the Amazon Elastic Container Service Developer Guide. - Desired
Count int - The number of instantiations of the specified task definition to place and keep running in your service. For new services, if a desired count is not specified, a default value of
1is used. When using theDAEMONscheduling strategy, the desired count is not required. For existing services, if a desired count is not specified, it is omitted from the operation. - bool
- Specifies whether to turn on Amazon ECS managed tags for the tasks within the service. For more information, see Tagging your Amazon ECS resources in the Amazon Elastic Container Service Developer Guide. When you use Amazon ECS managed tags, you need to set the
propagateTagsrequest parameter. - Enable
Execute boolCommand - Determines whether the execute command functionality is turned on for the service. If
true, the execute command functionality is turned on for all containers in tasks as part of the service. - Health
Check intGrace Period Seconds - The period of time, in seconds, that the Amazon ECS service scheduler ignores unhealthy Elastic Load Balancing target health checks after a task has first started. This is only used when your service is configured to use a load balancer. If your service has a load balancer defined and you don't specify a health check grace period value, the default value of
0is used. If you do not use an Elastic Load Balancing, we recommend that you use thestartPeriodin the task definition health check parameters. For more information, see Health check. If your service's tasks take a while to start and respond to Elastic Load Balancing health checks, you can specify a health check grace period of up to 2,147,483,647 seconds (about 69 years). During that time, the Amazon ECS service scheduler ignores health check status. This grace period can prevent the service scheduler from marking tasks as unhealthy and stopping them before they have time to come up. - Launch
Type string | LaunchType - The launch type on which to run your service. For more information, see Amazon ECS Launch Types in the Amazon Elastic Container Service Developer Guide.
- Load
Balancers []LoadBalancer - A list of load balancer objects to associate with the service. If you specify the
Roleproperty,LoadBalancersmust be specified as well. For information about the number of load balancers that you can specify per service, see Service Load Balancing in the Amazon Elastic Container Service Developer Guide. - Name string
- Property name
- Network
Configuration NetworkConfiguration - The network configuration for the service. This parameter is required for task definitions that use the
awsvpcnetwork mode to receive their own elastic network interface, and it is not supported for other network modes. For more information, see Task Networking in the Amazon Elastic Container Service Developer Guide. TheNetworkConfigurationproperty specifies an object representing the network configuration for a task or service. - Placement
Constraints []PlacementConstraint - An array of placement constraint objects to use for tasks in your service. You can specify a maximum of 10 constraints for each task. This limit includes constraints in the task definition and those specified at runtime.
- Placement
Strategies []PlacementStrategy - The placement strategy objects to use for tasks in your service. You can specify a maximum of 5 strategy rules for each service.
- Platform
Version string - The platform version that your tasks in the service are running on. A platform version is specified only for tasks using the Fargate launch type. If one isn't specified, the
LATESTplatform version is used. For more information, see platform versions in the Amazon Elastic Container Service Developer Guide. -
string | Propagate
Tags - Specifies whether to propagate the tags from the task definition to the task. If no value is specified, the tags aren't propagated. Tags can only be propagated to the task during task creation. To add tags to a task after task creation, use the TagResource API action. The default is
NONE. - Role string
- The name or full Amazon Resource Name (ARN) of the IAM role that allows Amazon ECS to make calls to your load balancer on your behalf. This parameter is only permitted if you are using a load balancer with your service and your task definition doesn't use the
awsvpcnetwork mode. If you specify theroleparameter, you must also specify a load balancer object with theloadBalancersparameter. If your account has already created the Amazon ECS service-linked role, that role is used for your service unless you specify a role here. The service-linked role is required if your task definition uses theawsvpcnetwork mode or if the service is configured to use service discovery, an external deployment controller, multiple target groups, or Elastic Inference accelerators in which case you don't specify a role here. For more information, see Using service-linked roles for Amazon ECS in the Amazon Elastic Container Service Developer Guide. If your specified role has a path other than/, then you must either specify the full role ARN (this is recommended) or prefix the role name with the path. For example, if a role with the namebarhas a path of/foo/then you would specify/foo/baras the role name. For more information, see Friendly names and paths in the IAM User Guide. - Scheduling
Strategy string | SchedulingStrategy - The scheduling strategy to use for the service. For more information, see Services. There are two service scheduler strategies available: +
REPLICA-The replica scheduling strategy places and maintains the desired number of tasks across your cluster. By default, the service scheduler spreads tasks across Availability Zones. You can use task placement strategies and constraints to customize task placement decisions. This scheduler strategy is required if the service uses theCODE_DEPLOYorEXTERNALdeployment controller types. +DAEMON-The daemon scheduling strategy deploys exactly one task on each active container instance that meets all of the task placement constraints that you specify in your cluster. The service scheduler also evaluates the task placement constraints for running tasks and will stop tasks that don't meet the placement constraints. When you're using this strategy, you don't need to specify a desired number of tasks, a task placement strategy, or use Service Auto Scaling policies. Tasks using the Fargate launch type or theCODE_DEPLOYorEXTERNALdeployment controller types don't support theDAEMONscheduling strategy. - Service
Arn string - Property serviceArn
- Service
Connect ServiceConfiguration Connect Configuration - The configuration for this service to discover and connect to services, and be discovered by, and connected from, other services within a namespace. 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. The Service Connect configuration of your Amazon ECS service. The configuration for this service to discover and connect to services, and be discovered by, and connected from, other services within a namespace. 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.
- Service
Name string - The name of your service. Up to 255 letters (uppercase and lowercase), numbers, underscores, and hyphens are allowed. Service names must be unique within a cluster, but you can have similarly named services in multiple clusters within a Region or across multiple Regions. The stack update fails if you change any properties that require replacement and the
ServiceNameis configured. This is because AWS CloudFormation creates the replacement service first, but eachServiceNamemust be unique in the cluster. - Service
Registries []ServiceRegistry - The details of the service discovery registry to associate with this service. For more information, see Service discovery. Each service may be associated with one service registry. Multiple service registries for each service isn't supported.
- []Tag
- The metadata that you apply to the service to help you categorize and organize them. Each tag consists of a key and an optional value, both of which you define. When a service is deleted, the tags are deleted as well. 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 AWS 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. - Task
Definition string - The
familyandrevision(family:revision) or full ARN of the task definition to run in your service. If arevisionisn't specified, the latestACTIVErevision is used. A task definition must be specified if the service uses either theECSorCODE_DEPLOYdeployment controllers. For more information about deployment types, see Amazon ECS deployment types. - Volume
Configurations []ServiceVolume Configuration - The configuration for a volume specified in the task definition as a volume that is configured at launch time. Currently, the only supported volume type is an Amazon EBS volume.
- capacity
Provider List<CapacityStrategy Provider Strategy Item> - The capacity provider strategy to use for the service. If a
capacityProviderStrategyis specified, thelaunchTypeparameter must be omitted. If nocapacityProviderStrategyorlaunchTypeis specified, thedefaultCapacityProviderStrategyfor the cluster is used. A capacity provider strategy may contain a maximum of 6 capacity providers. - cluster String
- The short name or full Amazon Resource Name (ARN) of the cluster that you run your service on. If you do not specify a cluster, the default cluster is assumed.
- deployment
Configuration DeploymentConfiguration - Optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks. The
DeploymentConfigurationproperty specifies optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks. - deployment
Controller DeploymentController - The deployment controller to use for the service. If no deployment controller is specified, the default value of
ECSis used. The deployment controller to use for the service. For more information, see Amazon ECS deployment types in the Amazon Elastic Container Service Developer Guide. - desired
Count Integer - The number of instantiations of the specified task definition to place and keep running in your service. For new services, if a desired count is not specified, a default value of
1is used. When using theDAEMONscheduling strategy, the desired count is not required. For existing services, if a desired count is not specified, it is omitted from the operation. - Boolean
- Specifies whether to turn on Amazon ECS managed tags for the tasks within the service. For more information, see Tagging your Amazon ECS resources in the Amazon Elastic Container Service Developer Guide. When you use Amazon ECS managed tags, you need to set the
propagateTagsrequest parameter. - enable
Execute BooleanCommand - Determines whether the execute command functionality is turned on for the service. If
true, the execute command functionality is turned on for all containers in tasks as part of the service. - health
Check IntegerGrace Period Seconds - The period of time, in seconds, that the Amazon ECS service scheduler ignores unhealthy Elastic Load Balancing target health checks after a task has first started. This is only used when your service is configured to use a load balancer. If your service has a load balancer defined and you don't specify a health check grace period value, the default value of
0is used. If you do not use an Elastic Load Balancing, we recommend that you use thestartPeriodin the task definition health check parameters. For more information, see Health check. If your service's tasks take a while to start and respond to Elastic Load Balancing health checks, you can specify a health check grace period of up to 2,147,483,647 seconds (about 69 years). During that time, the Amazon ECS service scheduler ignores health check status. This grace period can prevent the service scheduler from marking tasks as unhealthy and stopping them before they have time to come up. - launch
Type String | LaunchType - The launch type on which to run your service. For more information, see Amazon ECS Launch Types in the Amazon Elastic Container Service Developer Guide.
- load
Balancers List<LoadBalancer> - A list of load balancer objects to associate with the service. If you specify the
Roleproperty,LoadBalancersmust be specified as well. For information about the number of load balancers that you can specify per service, see Service Load Balancing in the Amazon Elastic Container Service Developer Guide. - name String
- Property name
- network
Configuration NetworkConfiguration - The network configuration for the service. This parameter is required for task definitions that use the
awsvpcnetwork mode to receive their own elastic network interface, and it is not supported for other network modes. For more information, see Task Networking in the Amazon Elastic Container Service Developer Guide. TheNetworkConfigurationproperty specifies an object representing the network configuration for a task or service. - placement
Constraints List<PlacementConstraint> - An array of placement constraint objects to use for tasks in your service. You can specify a maximum of 10 constraints for each task. This limit includes constraints in the task definition and those specified at runtime.
- placement
Strategies List<PlacementStrategy> - The placement strategy objects to use for tasks in your service. You can specify a maximum of 5 strategy rules for each service.
- platform
Version String - The platform version that your tasks in the service are running on. A platform version is specified only for tasks using the Fargate launch type. If one isn't specified, the
LATESTplatform version is used. For more information, see platform versions in the Amazon Elastic Container Service Developer Guide. -
String | Propagate
Tags - Specifies whether to propagate the tags from the task definition to the task. If no value is specified, the tags aren't propagated. Tags can only be propagated to the task during task creation. To add tags to a task after task creation, use the TagResource API action. The default is
NONE. - role String
- The name or full Amazon Resource Name (ARN) of the IAM role that allows Amazon ECS to make calls to your load balancer on your behalf. This parameter is only permitted if you are using a load balancer with your service and your task definition doesn't use the
awsvpcnetwork mode. If you specify theroleparameter, you must also specify a load balancer object with theloadBalancersparameter. If your account has already created the Amazon ECS service-linked role, that role is used for your service unless you specify a role here. The service-linked role is required if your task definition uses theawsvpcnetwork mode or if the service is configured to use service discovery, an external deployment controller, multiple target groups, or Elastic Inference accelerators in which case you don't specify a role here. For more information, see Using service-linked roles for Amazon ECS in the Amazon Elastic Container Service Developer Guide. If your specified role has a path other than/, then you must either specify the full role ARN (this is recommended) or prefix the role name with the path. For example, if a role with the namebarhas a path of/foo/then you would specify/foo/baras the role name. For more information, see Friendly names and paths in the IAM User Guide. - scheduling
Strategy String | SchedulingStrategy - The scheduling strategy to use for the service. For more information, see Services. There are two service scheduler strategies available: +
REPLICA-The replica scheduling strategy places and maintains the desired number of tasks across your cluster. By default, the service scheduler spreads tasks across Availability Zones. You can use task placement strategies and constraints to customize task placement decisions. This scheduler strategy is required if the service uses theCODE_DEPLOYorEXTERNALdeployment controller types. +DAEMON-The daemon scheduling strategy deploys exactly one task on each active container instance that meets all of the task placement constraints that you specify in your cluster. The service scheduler also evaluates the task placement constraints for running tasks and will stop tasks that don't meet the placement constraints. When you're using this strategy, you don't need to specify a desired number of tasks, a task placement strategy, or use Service Auto Scaling policies. Tasks using the Fargate launch type or theCODE_DEPLOYorEXTERNALdeployment controller types don't support theDAEMONscheduling strategy. - service
Arn String - Property serviceArn
- service
Connect ServiceConfiguration Connect Configuration - The configuration for this service to discover and connect to services, and be discovered by, and connected from, other services within a namespace. 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. The Service Connect configuration of your Amazon ECS service. The configuration for this service to discover and connect to services, and be discovered by, and connected from, other services within a namespace. 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.
- service
Name String - The name of your service. Up to 255 letters (uppercase and lowercase), numbers, underscores, and hyphens are allowed. Service names must be unique within a cluster, but you can have similarly named services in multiple clusters within a Region or across multiple Regions. The stack update fails if you change any properties that require replacement and the
ServiceNameis configured. This is because AWS CloudFormation creates the replacement service first, but eachServiceNamemust be unique in the cluster. - service
Registries List<ServiceRegistry> - The details of the service discovery registry to associate with this service. For more information, see Service discovery. Each service may be associated with one service registry. Multiple service registries for each service isn't supported.
- List<Tag>
- The metadata that you apply to the service to help you categorize and organize them. Each tag consists of a key and an optional value, both of which you define. When a service is deleted, the tags are deleted as well. 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 AWS 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. - task
Definition String - The
familyandrevision(family:revision) or full ARN of the task definition to run in your service. If arevisionisn't specified, the latestACTIVErevision is used. A task definition must be specified if the service uses either theECSorCODE_DEPLOYdeployment controllers. For more information about deployment types, see Amazon ECS deployment types. - volume
Configurations List<ServiceVolume Configuration> - The configuration for a volume specified in the task definition as a volume that is configured at launch time. Currently, the only supported volume type is an Amazon EBS volume.
- capacity
Provider CapacityStrategy Provider Strategy Item[] - The capacity provider strategy to use for the service. If a
capacityProviderStrategyis specified, thelaunchTypeparameter must be omitted. If nocapacityProviderStrategyorlaunchTypeis specified, thedefaultCapacityProviderStrategyfor the cluster is used. A capacity provider strategy may contain a maximum of 6 capacity providers. - cluster string
- The short name or full Amazon Resource Name (ARN) of the cluster that you run your service on. If you do not specify a cluster, the default cluster is assumed.
- deployment
Configuration DeploymentConfiguration - Optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks. The
DeploymentConfigurationproperty specifies optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks. - deployment
Controller DeploymentController - The deployment controller to use for the service. If no deployment controller is specified, the default value of
ECSis used. The deployment controller to use for the service. For more information, see Amazon ECS deployment types in the Amazon Elastic Container Service Developer Guide. - desired
Count number - The number of instantiations of the specified task definition to place and keep running in your service. For new services, if a desired count is not specified, a default value of
1is used. When using theDAEMONscheduling strategy, the desired count is not required. For existing services, if a desired count is not specified, it is omitted from the operation. - boolean
- Specifies whether to turn on Amazon ECS managed tags for the tasks within the service. For more information, see Tagging your Amazon ECS resources in the Amazon Elastic Container Service Developer Guide. When you use Amazon ECS managed tags, you need to set the
propagateTagsrequest parameter. - enable
Execute booleanCommand - Determines whether the execute command functionality is turned on for the service. If
true, the execute command functionality is turned on for all containers in tasks as part of the service. - health
Check numberGrace Period Seconds - The period of time, in seconds, that the Amazon ECS service scheduler ignores unhealthy Elastic Load Balancing target health checks after a task has first started. This is only used when your service is configured to use a load balancer. If your service has a load balancer defined and you don't specify a health check grace period value, the default value of
0is used. If you do not use an Elastic Load Balancing, we recommend that you use thestartPeriodin the task definition health check parameters. For more information, see Health check. If your service's tasks take a while to start and respond to Elastic Load Balancing health checks, you can specify a health check grace period of up to 2,147,483,647 seconds (about 69 years). During that time, the Amazon ECS service scheduler ignores health check status. This grace period can prevent the service scheduler from marking tasks as unhealthy and stopping them before they have time to come up. - launch
Type string | LaunchType - The launch type on which to run your service. For more information, see Amazon ECS Launch Types in the Amazon Elastic Container Service Developer Guide.
- load
Balancers LoadBalancer[] - A list of load balancer objects to associate with the service. If you specify the
Roleproperty,LoadBalancersmust be specified as well. For information about the number of load balancers that you can specify per service, see Service Load Balancing in the Amazon Elastic Container Service Developer Guide. - name string
- Property name
- network
Configuration NetworkConfiguration - The network configuration for the service. This parameter is required for task definitions that use the
awsvpcnetwork mode to receive their own elastic network interface, and it is not supported for other network modes. For more information, see Task Networking in the Amazon Elastic Container Service Developer Guide. TheNetworkConfigurationproperty specifies an object representing the network configuration for a task or service. - placement
Constraints PlacementConstraint[] - An array of placement constraint objects to use for tasks in your service. You can specify a maximum of 10 constraints for each task. This limit includes constraints in the task definition and those specified at runtime.
- placement
Strategies PlacementStrategy[] - The placement strategy objects to use for tasks in your service. You can specify a maximum of 5 strategy rules for each service.
- platform
Version string - The platform version that your tasks in the service are running on. A platform version is specified only for tasks using the Fargate launch type. If one isn't specified, the
LATESTplatform version is used. For more information, see platform versions in the Amazon Elastic Container Service Developer Guide. -
string | Propagate
Tags - Specifies whether to propagate the tags from the task definition to the task. If no value is specified, the tags aren't propagated. Tags can only be propagated to the task during task creation. To add tags to a task after task creation, use the TagResource API action. The default is
NONE. - role string
- The name or full Amazon Resource Name (ARN) of the IAM role that allows Amazon ECS to make calls to your load balancer on your behalf. This parameter is only permitted if you are using a load balancer with your service and your task definition doesn't use the
awsvpcnetwork mode. If you specify theroleparameter, you must also specify a load balancer object with theloadBalancersparameter. If your account has already created the Amazon ECS service-linked role, that role is used for your service unless you specify a role here. The service-linked role is required if your task definition uses theawsvpcnetwork mode or if the service is configured to use service discovery, an external deployment controller, multiple target groups, or Elastic Inference accelerators in which case you don't specify a role here. For more information, see Using service-linked roles for Amazon ECS in the Amazon Elastic Container Service Developer Guide. If your specified role has a path other than/, then you must either specify the full role ARN (this is recommended) or prefix the role name with the path. For example, if a role with the namebarhas a path of/foo/then you would specify/foo/baras the role name. For more information, see Friendly names and paths in the IAM User Guide. - scheduling
Strategy string | SchedulingStrategy - The scheduling strategy to use for the service. For more information, see Services. There are two service scheduler strategies available: +
REPLICA-The replica scheduling strategy places and maintains the desired number of tasks across your cluster. By default, the service scheduler spreads tasks across Availability Zones. You can use task placement strategies and constraints to customize task placement decisions. This scheduler strategy is required if the service uses theCODE_DEPLOYorEXTERNALdeployment controller types. +DAEMON-The daemon scheduling strategy deploys exactly one task on each active container instance that meets all of the task placement constraints that you specify in your cluster. The service scheduler also evaluates the task placement constraints for running tasks and will stop tasks that don't meet the placement constraints. When you're using this strategy, you don't need to specify a desired number of tasks, a task placement strategy, or use Service Auto Scaling policies. Tasks using the Fargate launch type or theCODE_DEPLOYorEXTERNALdeployment controller types don't support theDAEMONscheduling strategy. - service
Arn string - Property serviceArn
- service
Connect ServiceConfiguration Connect Configuration - The configuration for this service to discover and connect to services, and be discovered by, and connected from, other services within a namespace. 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. The Service Connect configuration of your Amazon ECS service. The configuration for this service to discover and connect to services, and be discovered by, and connected from, other services within a namespace. 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.
- service
Name string - The name of your service. Up to 255 letters (uppercase and lowercase), numbers, underscores, and hyphens are allowed. Service names must be unique within a cluster, but you can have similarly named services in multiple clusters within a Region or across multiple Regions. The stack update fails if you change any properties that require replacement and the
ServiceNameis configured. This is because AWS CloudFormation creates the replacement service first, but eachServiceNamemust be unique in the cluster. - service
Registries ServiceRegistry[] - The details of the service discovery registry to associate with this service. For more information, see Service discovery. Each service may be associated with one service registry. Multiple service registries for each service isn't supported.
- Tag[]
- The metadata that you apply to the service to help you categorize and organize them. Each tag consists of a key and an optional value, both of which you define. When a service is deleted, the tags are deleted as well. 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 AWS 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. - task
Definition string - The
familyandrevision(family:revision) or full ARN of the task definition to run in your service. If arevisionisn't specified, the latestACTIVErevision is used. A task definition must be specified if the service uses either theECSorCODE_DEPLOYdeployment controllers. For more information about deployment types, see Amazon ECS deployment types. - volume
Configurations ServiceVolume Configuration[] - The configuration for a volume specified in the task definition as a volume that is configured at launch time. Currently, the only supported volume type is an Amazon EBS volume.
- capacity_
provider_ Sequence[Capacitystrategy Provider Strategy Item] - The capacity provider strategy to use for the service. If a
capacityProviderStrategyis specified, thelaunchTypeparameter must be omitted. If nocapacityProviderStrategyorlaunchTypeis specified, thedefaultCapacityProviderStrategyfor the cluster is used. A capacity provider strategy may contain a maximum of 6 capacity providers. - cluster str
- The short name or full Amazon Resource Name (ARN) of the cluster that you run your service on. If you do not specify a cluster, the default cluster is assumed.
- deployment_
configuration DeploymentConfiguration - Optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks. The
DeploymentConfigurationproperty specifies optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks. - deployment_
controller DeploymentController - The deployment controller to use for the service. If no deployment controller is specified, the default value of
ECSis used. The deployment controller to use for the service. For more information, see Amazon ECS deployment types in the Amazon Elastic Container Service Developer Guide. - desired_
count int - The number of instantiations of the specified task definition to place and keep running in your service. For new services, if a desired count is not specified, a default value of
1is used. When using theDAEMONscheduling strategy, the desired count is not required. For existing services, if a desired count is not specified, it is omitted from the operation. - bool
- Specifies whether to turn on Amazon ECS managed tags for the tasks within the service. For more information, see Tagging your Amazon ECS resources in the Amazon Elastic Container Service Developer Guide. When you use Amazon ECS managed tags, you need to set the
propagateTagsrequest parameter. - enable_
execute_ boolcommand - Determines whether the execute command functionality is turned on for the service. If
true, the execute command functionality is turned on for all containers in tasks as part of the service. - health_
check_ intgrace_ period_ seconds - The period of time, in seconds, that the Amazon ECS service scheduler ignores unhealthy Elastic Load Balancing target health checks after a task has first started. This is only used when your service is configured to use a load balancer. If your service has a load balancer defined and you don't specify a health check grace period value, the default value of
0is used. If you do not use an Elastic Load Balancing, we recommend that you use thestartPeriodin the task definition health check parameters. For more information, see Health check. If your service's tasks take a while to start and respond to Elastic Load Balancing health checks, you can specify a health check grace period of up to 2,147,483,647 seconds (about 69 years). During that time, the Amazon ECS service scheduler ignores health check status. This grace period can prevent the service scheduler from marking tasks as unhealthy and stopping them before they have time to come up. - launch_
type str | LaunchType - The launch type on which to run your service. For more information, see Amazon ECS Launch Types in the Amazon Elastic Container Service Developer Guide.
- load_
balancers Sequence[LoadBalancer] - A list of load balancer objects to associate with the service. If you specify the
Roleproperty,LoadBalancersmust be specified as well. For information about the number of load balancers that you can specify per service, see Service Load Balancing in the Amazon Elastic Container Service Developer Guide. - name str
- Property name
- network_
configuration NetworkConfiguration - The network configuration for the service. This parameter is required for task definitions that use the
awsvpcnetwork mode to receive their own elastic network interface, and it is not supported for other network modes. For more information, see Task Networking in the Amazon Elastic Container Service Developer Guide. TheNetworkConfigurationproperty specifies an object representing the network configuration for a task or service. - placement_
constraints Sequence[PlacementConstraint] - An array of placement constraint objects to use for tasks in your service. You can specify a maximum of 10 constraints for each task. This limit includes constraints in the task definition and those specified at runtime.
- placement_
strategies Sequence[PlacementStrategy] - The placement strategy objects to use for tasks in your service. You can specify a maximum of 5 strategy rules for each service.
- platform_
version str - The platform version that your tasks in the service are running on. A platform version is specified only for tasks using the Fargate launch type. If one isn't specified, the
LATESTplatform version is used. For more information, see platform versions in the Amazon Elastic Container Service Developer Guide. -
str | Propagate
Tags - Specifies whether to propagate the tags from the task definition to the task. If no value is specified, the tags aren't propagated. Tags can only be propagated to the task during task creation. To add tags to a task after task creation, use the TagResource API action. The default is
NONE. - role str
- The name or full Amazon Resource Name (ARN) of the IAM role that allows Amazon ECS to make calls to your load balancer on your behalf. This parameter is only permitted if you are using a load balancer with your service and your task definition doesn't use the
awsvpcnetwork mode. If you specify theroleparameter, you must also specify a load balancer object with theloadBalancersparameter. If your account has already created the Amazon ECS service-linked role, that role is used for your service unless you specify a role here. The service-linked role is required if your task definition uses theawsvpcnetwork mode or if the service is configured to use service discovery, an external deployment controller, multiple target groups, or Elastic Inference accelerators in which case you don't specify a role here. For more information, see Using service-linked roles for Amazon ECS in the Amazon Elastic Container Service Developer Guide. If your specified role has a path other than/, then you must either specify the full role ARN (this is recommended) or prefix the role name with the path. For example, if a role with the namebarhas a path of/foo/then you would specify/foo/baras the role name. For more information, see Friendly names and paths in the IAM User Guide. - scheduling_
strategy str | SchedulingStrategy - The scheduling strategy to use for the service. For more information, see Services. There are two service scheduler strategies available: +
REPLICA-The replica scheduling strategy places and maintains the desired number of tasks across your cluster. By default, the service scheduler spreads tasks across Availability Zones. You can use task placement strategies and constraints to customize task placement decisions. This scheduler strategy is required if the service uses theCODE_DEPLOYorEXTERNALdeployment controller types. +DAEMON-The daemon scheduling strategy deploys exactly one task on each active container instance that meets all of the task placement constraints that you specify in your cluster. The service scheduler also evaluates the task placement constraints for running tasks and will stop tasks that don't meet the placement constraints. When you're using this strategy, you don't need to specify a desired number of tasks, a task placement strategy, or use Service Auto Scaling policies. Tasks using the Fargate launch type or theCODE_DEPLOYorEXTERNALdeployment controller types don't support theDAEMONscheduling strategy. - service_
arn str - Property serviceArn
- service_
connect_ Serviceconfiguration Connect Configuration - The configuration for this service to discover and connect to services, and be discovered by, and connected from, other services within a namespace. 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. The Service Connect configuration of your Amazon ECS service. The configuration for this service to discover and connect to services, and be discovered by, and connected from, other services within a namespace. 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.
- service_
name str - The name of your service. Up to 255 letters (uppercase and lowercase), numbers, underscores, and hyphens are allowed. Service names must be unique within a cluster, but you can have similarly named services in multiple clusters within a Region or across multiple Regions. The stack update fails if you change any properties that require replacement and the
ServiceNameis configured. This is because AWS CloudFormation creates the replacement service first, but eachServiceNamemust be unique in the cluster. - service_
registries Sequence[ServiceRegistry] - The details of the service discovery registry to associate with this service. For more information, see Service discovery. Each service may be associated with one service registry. Multiple service registries for each service isn't supported.
- Sequence[Tag]
- The metadata that you apply to the service to help you categorize and organize them. Each tag consists of a key and an optional value, both of which you define. When a service is deleted, the tags are deleted as well. 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 AWS 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. - task_
definition str - The
familyandrevision(family:revision) or full ARN of the task definition to run in your service. If arevisionisn't specified, the latestACTIVErevision is used. A task definition must be specified if the service uses either theECSorCODE_DEPLOYdeployment controllers. For more information about deployment types, see Amazon ECS deployment types. - volume_
configurations Sequence[ServiceVolume Configuration] - The configuration for a volume specified in the task definition as a volume that is configured at launch time. Currently, the only supported volume type is an Amazon EBS volume.
- capacity
Provider List<Property Map>Strategy - The capacity provider strategy to use for the service. If a
capacityProviderStrategyis specified, thelaunchTypeparameter must be omitted. If nocapacityProviderStrategyorlaunchTypeis specified, thedefaultCapacityProviderStrategyfor the cluster is used. A capacity provider strategy may contain a maximum of 6 capacity providers. - cluster String
- The short name or full Amazon Resource Name (ARN) of the cluster that you run your service on. If you do not specify a cluster, the default cluster is assumed.
- deployment
Configuration Property Map - Optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks. The
DeploymentConfigurationproperty specifies optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks. - deployment
Controller Property Map - The deployment controller to use for the service. If no deployment controller is specified, the default value of
ECSis used. The deployment controller to use for the service. For more information, see Amazon ECS deployment types in the Amazon Elastic Container Service Developer Guide. - desired
Count Number - The number of instantiations of the specified task definition to place and keep running in your service. For new services, if a desired count is not specified, a default value of
1is used. When using theDAEMONscheduling strategy, the desired count is not required. For existing services, if a desired count is not specified, it is omitted from the operation. - Boolean
- Specifies whether to turn on Amazon ECS managed tags for the tasks within the service. For more information, see Tagging your Amazon ECS resources in the Amazon Elastic Container Service Developer Guide. When you use Amazon ECS managed tags, you need to set the
propagateTagsrequest parameter. - enable
Execute BooleanCommand - Determines whether the execute command functionality is turned on for the service. If
true, the execute command functionality is turned on for all containers in tasks as part of the service. - health
Check NumberGrace Period Seconds - The period of time, in seconds, that the Amazon ECS service scheduler ignores unhealthy Elastic Load Balancing target health checks after a task has first started. This is only used when your service is configured to use a load balancer. If your service has a load balancer defined and you don't specify a health check grace period value, the default value of
0is used. If you do not use an Elastic Load Balancing, we recommend that you use thestartPeriodin the task definition health check parameters. For more information, see Health check. If your service's tasks take a while to start and respond to Elastic Load Balancing health checks, you can specify a health check grace period of up to 2,147,483,647 seconds (about 69 years). During that time, the Amazon ECS service scheduler ignores health check status. This grace period can prevent the service scheduler from marking tasks as unhealthy and stopping them before they have time to come up. - launch
Type String | "EC2" | "EXTERNAL" | "FARGATE" - The launch type on which to run your service. For more information, see Amazon ECS Launch Types in the Amazon Elastic Container Service Developer Guide.
- load
Balancers List<Property Map> - A list of load balancer objects to associate with the service. If you specify the
Roleproperty,LoadBalancersmust be specified as well. For information about the number of load balancers that you can specify per service, see Service Load Balancing in the Amazon Elastic Container Service Developer Guide. - name String
- Property name
- network
Configuration Property Map - The network configuration for the service. This parameter is required for task definitions that use the
awsvpcnetwork mode to receive their own elastic network interface, and it is not supported for other network modes. For more information, see Task Networking in the Amazon Elastic Container Service Developer Guide. TheNetworkConfigurationproperty specifies an object representing the network configuration for a task or service. - placement
Constraints List<Property Map> - An array of placement constraint objects to use for tasks in your service. You can specify a maximum of 10 constraints for each task. This limit includes constraints in the task definition and those specified at runtime.
- placement
Strategies List<Property Map> - The placement strategy objects to use for tasks in your service. You can specify a maximum of 5 strategy rules for each service.
- platform
Version String - The platform version that your tasks in the service are running on. A platform version is specified only for tasks using the Fargate launch type. If one isn't specified, the
LATESTplatform version is used. For more information, see platform versions in the Amazon Elastic Container Service Developer Guide. - String | "SERVICE" | "TASK_DEFINITION"
- Specifies whether to propagate the tags from the task definition to the task. If no value is specified, the tags aren't propagated. Tags can only be propagated to the task during task creation. To add tags to a task after task creation, use the TagResource API action. The default is
NONE. - role String
- The name or full Amazon Resource Name (ARN) of the IAM role that allows Amazon ECS to make calls to your load balancer on your behalf. This parameter is only permitted if you are using a load balancer with your service and your task definition doesn't use the
awsvpcnetwork mode. If you specify theroleparameter, you must also specify a load balancer object with theloadBalancersparameter. If your account has already created the Amazon ECS service-linked role, that role is used for your service unless you specify a role here. The service-linked role is required if your task definition uses theawsvpcnetwork mode or if the service is configured to use service discovery, an external deployment controller, multiple target groups, or Elastic Inference accelerators in which case you don't specify a role here. For more information, see Using service-linked roles for Amazon ECS in the Amazon Elastic Container Service Developer Guide. If your specified role has a path other than/, then you must either specify the full role ARN (this is recommended) or prefix the role name with the path. For example, if a role with the namebarhas a path of/foo/then you would specify/foo/baras the role name. For more information, see Friendly names and paths in the IAM User Guide. - scheduling
Strategy String | "DAEMON" | "REPLICA" - The scheduling strategy to use for the service. For more information, see Services. There are two service scheduler strategies available: +
REPLICA-The replica scheduling strategy places and maintains the desired number of tasks across your cluster. By default, the service scheduler spreads tasks across Availability Zones. You can use task placement strategies and constraints to customize task placement decisions. This scheduler strategy is required if the service uses theCODE_DEPLOYorEXTERNALdeployment controller types. +DAEMON-The daemon scheduling strategy deploys exactly one task on each active container instance that meets all of the task placement constraints that you specify in your cluster. The service scheduler also evaluates the task placement constraints for running tasks and will stop tasks that don't meet the placement constraints. When you're using this strategy, you don't need to specify a desired number of tasks, a task placement strategy, or use Service Auto Scaling policies. Tasks using the Fargate launch type or theCODE_DEPLOYorEXTERNALdeployment controller types don't support theDAEMONscheduling strategy. - service
Arn String - Property serviceArn
- service
Connect Property MapConfiguration - The configuration for this service to discover and connect to services, and be discovered by, and connected from, other services within a namespace. 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. The Service Connect configuration of your Amazon ECS service. The configuration for this service to discover and connect to services, and be discovered by, and connected from, other services within a namespace. 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.
- service
Name String - The name of your service. Up to 255 letters (uppercase and lowercase), numbers, underscores, and hyphens are allowed. Service names must be unique within a cluster, but you can have similarly named services in multiple clusters within a Region or across multiple Regions. The stack update fails if you change any properties that require replacement and the
ServiceNameis configured. This is because AWS CloudFormation creates the replacement service first, but eachServiceNamemust be unique in the cluster. - service
Registries List<Property Map> - The details of the service discovery registry to associate with this service. For more information, see Service discovery. Each service may be associated with one service registry. Multiple service registries for each service isn't supported.
- List<Property Map>
- The metadata that you apply to the service to help you categorize and organize them. Each tag consists of a key and an optional value, both of which you define. When a service is deleted, the tags are deleted as well. 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 AWS 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. - task
Definition String - The
familyandrevision(family:revision) or full ARN of the task definition to run in your service. If arevisionisn't specified, the latestACTIVErevision is used. A task definition must be specified if the service uses either theECSorCODE_DEPLOYdeployment controllers. For more information about deployment types, see Amazon ECS deployment types. - volume
Configurations List<Property Map> - The configuration for a volume specified in the task definition as a volume that is configured at launch time. Currently, the only supported volume type is an Amazon EBS volume.
AwsEcsServicePropertiesResponse, AwsEcsServicePropertiesResponseArgs
, AwsEcsServicePropertiesResponseArgs
- Capacity
Provider List<Pulumi.Strategy Azure Native. Aws Connector. Inputs. Capacity Provider Strategy Item Response> - The capacity provider strategy to use for the service. If a
capacityProviderStrategyis specified, thelaunchTypeparameter must be omitted. If nocapacityProviderStrategyorlaunchTypeis specified, thedefaultCapacityProviderStrategyfor the cluster is used. A capacity provider strategy may contain a maximum of 6 capacity providers. - Cluster string
- The short name or full Amazon Resource Name (ARN) of the cluster that you run your service on. If you do not specify a cluster, the default cluster is assumed.
- Deployment
Configuration Pulumi.Azure Native. Aws Connector. Inputs. Deployment Configuration Response - Optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks. The
DeploymentConfigurationproperty specifies optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks. - Deployment
Controller Pulumi.Azure Native. Aws Connector. Inputs. Deployment Controller Response - The deployment controller to use for the service. If no deployment controller is specified, the default value of
ECSis used. The deployment controller to use for the service. For more information, see Amazon ECS deployment types in the Amazon Elastic Container Service Developer Guide. - Desired
Count int - The number of instantiations of the specified task definition to place and keep running in your service. For new services, if a desired count is not specified, a default value of
1is used. When using theDAEMONscheduling strategy, the desired count is not required. For existing services, if a desired count is not specified, it is omitted from the operation. - bool
- Specifies whether to turn on Amazon ECS managed tags for the tasks within the service. For more information, see Tagging your Amazon ECS resources in the Amazon Elastic Container Service Developer Guide. When you use Amazon ECS managed tags, you need to set the
propagateTagsrequest parameter. - Enable
Execute boolCommand - Determines whether the execute command functionality is turned on for the service. If
true, the execute command functionality is turned on for all containers in tasks as part of the service. - Health
Check intGrace Period Seconds - The period of time, in seconds, that the Amazon ECS service scheduler ignores unhealthy Elastic Load Balancing target health checks after a task has first started. This is only used when your service is configured to use a load balancer. If your service has a load balancer defined and you don't specify a health check grace period value, the default value of
0is used. If you do not use an Elastic Load Balancing, we recommend that you use thestartPeriodin the task definition health check parameters. For more information, see Health check. If your service's tasks take a while to start and respond to Elastic Load Balancing health checks, you can specify a health check grace period of up to 2,147,483,647 seconds (about 69 years). During that time, the Amazon ECS service scheduler ignores health check status. This grace period can prevent the service scheduler from marking tasks as unhealthy and stopping them before they have time to come up. - Launch
Type string - The launch type on which to run your service. For more information, see Amazon ECS Launch Types in the Amazon Elastic Container Service Developer Guide.
- Load
Balancers List<Pulumi.Azure Native. Aws Connector. Inputs. Load Balancer Response> - A list of load balancer objects to associate with the service. If you specify the
Roleproperty,LoadBalancersmust be specified as well. For information about the number of load balancers that you can specify per service, see Service Load Balancing in the Amazon Elastic Container Service Developer Guide. - Name string
- Property name
- Network
Configuration Pulumi.Azure Native. Aws Connector. Inputs. Network Configuration Response - The network configuration for the service. This parameter is required for task definitions that use the
awsvpcnetwork mode to receive their own elastic network interface, and it is not supported for other network modes. For more information, see Task Networking in the Amazon Elastic Container Service Developer Guide. TheNetworkConfigurationproperty specifies an object representing the network configuration for a task or service. - Placement
Constraints List<Pulumi.Azure Native. Aws Connector. Inputs. Placement Constraint Response> - An array of placement constraint objects to use for tasks in your service. You can specify a maximum of 10 constraints for each task. This limit includes constraints in the task definition and those specified at runtime.
- Placement
Strategies List<Pulumi.Azure Native. Aws Connector. Inputs. Placement Strategy Response> - The placement strategy objects to use for tasks in your service. You can specify a maximum of 5 strategy rules for each service.
- Platform
Version string - The platform version that your tasks in the service are running on. A platform version is specified only for tasks using the Fargate launch type. If one isn't specified, the
LATESTplatform version is used. For more information, see platform versions in the Amazon Elastic Container Service Developer Guide. - string
- Specifies whether to propagate the tags from the task definition to the task. If no value is specified, the tags aren't propagated. Tags can only be propagated to the task during task creation. To add tags to a task after task creation, use the TagResource API action. The default is
NONE. - Role string
- The name or full Amazon Resource Name (ARN) of the IAM role that allows Amazon ECS to make calls to your load balancer on your behalf. This parameter is only permitted if you are using a load balancer with your service and your task definition doesn't use the
awsvpcnetwork mode. If you specify theroleparameter, you must also specify a load balancer object with theloadBalancersparameter. If your account has already created the Amazon ECS service-linked role, that role is used for your service unless you specify a role here. The service-linked role is required if your task definition uses theawsvpcnetwork mode or if the service is configured to use service discovery, an external deployment controller, multiple target groups, or Elastic Inference accelerators in which case you don't specify a role here. For more information, see Using service-linked roles for Amazon ECS in the Amazon Elastic Container Service Developer Guide. If your specified role has a path other than/, then you must either specify the full role ARN (this is recommended) or prefix the role name with the path. For example, if a role with the namebarhas a path of/foo/then you would specify/foo/baras the role name. For more information, see Friendly names and paths in the IAM User Guide. - Scheduling
Strategy string - The scheduling strategy to use for the service. For more information, see Services. There are two service scheduler strategies available: +
REPLICA-The replica scheduling strategy places and maintains the desired number of tasks across your cluster. By default, the service scheduler spreads tasks across Availability Zones. You can use task placement strategies and constraints to customize task placement decisions. This scheduler strategy is required if the service uses theCODE_DEPLOYorEXTERNALdeployment controller types. +DAEMON-The daemon scheduling strategy deploys exactly one task on each active container instance that meets all of the task placement constraints that you specify in your cluster. The service scheduler also evaluates the task placement constraints for running tasks and will stop tasks that don't meet the placement constraints. When you're using this strategy, you don't need to specify a desired number of tasks, a task placement strategy, or use Service Auto Scaling policies. Tasks using the Fargate launch type or theCODE_DEPLOYorEXTERNALdeployment controller types don't support theDAEMONscheduling strategy. - Service
Arn string - Property serviceArn
- Service
Connect Pulumi.Configuration Azure Native. Aws Connector. Inputs. Service Connect Configuration Response - The configuration for this service to discover and connect to services, and be discovered by, and connected from, other services within a namespace. 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. The Service Connect configuration of your Amazon ECS service. The configuration for this service to discover and connect to services, and be discovered by, and connected from, other services within a namespace. 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.
- Service
Name string - The name of your service. Up to 255 letters (uppercase and lowercase), numbers, underscores, and hyphens are allowed. Service names must be unique within a cluster, but you can have similarly named services in multiple clusters within a Region or across multiple Regions. The stack update fails if you change any properties that require replacement and the
ServiceNameis configured. This is because AWS CloudFormation creates the replacement service first, but eachServiceNamemust be unique in the cluster. - Service
Registries List<Pulumi.Azure Native. Aws Connector. Inputs. Service Registry Response> - The details of the service discovery registry to associate with this service. For more information, see Service discovery. Each service may be associated with one service registry. Multiple service registries for each service isn't supported.
-
List<Pulumi.
Azure Native. Aws Connector. Inputs. Tag Response> - The metadata that you apply to the service to help you categorize and organize them. Each tag consists of a key and an optional value, both of which you define. When a service is deleted, the tags are deleted as well. 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 AWS 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. - Task
Definition string - The
familyandrevision(family:revision) or full ARN of the task definition to run in your service. If arevisionisn't specified, the latestACTIVErevision is used. A task definition must be specified if the service uses either theECSorCODE_DEPLOYdeployment controllers. For more information about deployment types, see Amazon ECS deployment types. - Volume
Configurations List<Pulumi.Azure Native. Aws Connector. Inputs. Service Volume Configuration Response> - The configuration for a volume specified in the task definition as a volume that is configured at launch time. Currently, the only supported volume type is an Amazon EBS volume.
- Capacity
Provider []CapacityStrategy Provider Strategy Item Response - The capacity provider strategy to use for the service. If a
capacityProviderStrategyis specified, thelaunchTypeparameter must be omitted. If nocapacityProviderStrategyorlaunchTypeis specified, thedefaultCapacityProviderStrategyfor the cluster is used. A capacity provider strategy may contain a maximum of 6 capacity providers. - Cluster string
- The short name or full Amazon Resource Name (ARN) of the cluster that you run your service on. If you do not specify a cluster, the default cluster is assumed.
- Deployment
Configuration DeploymentConfiguration Response - Optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks. The
DeploymentConfigurationproperty specifies optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks. - Deployment
Controller DeploymentController Response - The deployment controller to use for the service. If no deployment controller is specified, the default value of
ECSis used. The deployment controller to use for the service. For more information, see Amazon ECS deployment types in the Amazon Elastic Container Service Developer Guide. - Desired
Count int - The number of instantiations of the specified task definition to place and keep running in your service. For new services, if a desired count is not specified, a default value of
1is used. When using theDAEMONscheduling strategy, the desired count is not required. For existing services, if a desired count is not specified, it is omitted from the operation. - bool
- Specifies whether to turn on Amazon ECS managed tags for the tasks within the service. For more information, see Tagging your Amazon ECS resources in the Amazon Elastic Container Service Developer Guide. When you use Amazon ECS managed tags, you need to set the
propagateTagsrequest parameter. - Enable
Execute boolCommand - Determines whether the execute command functionality is turned on for the service. If
true, the execute command functionality is turned on for all containers in tasks as part of the service. - Health
Check intGrace Period Seconds - The period of time, in seconds, that the Amazon ECS service scheduler ignores unhealthy Elastic Load Balancing target health checks after a task has first started. This is only used when your service is configured to use a load balancer. If your service has a load balancer defined and you don't specify a health check grace period value, the default value of
0is used. If you do not use an Elastic Load Balancing, we recommend that you use thestartPeriodin the task definition health check parameters. For more information, see Health check. If your service's tasks take a while to start and respond to Elastic Load Balancing health checks, you can specify a health check grace period of up to 2,147,483,647 seconds (about 69 years). During that time, the Amazon ECS service scheduler ignores health check status. This grace period can prevent the service scheduler from marking tasks as unhealthy and stopping them before they have time to come up. - Launch
Type string - The launch type on which to run your service. For more information, see Amazon ECS Launch Types in the Amazon Elastic Container Service Developer Guide.
- Load
Balancers []LoadBalancer Response - A list of load balancer objects to associate with the service. If you specify the
Roleproperty,LoadBalancersmust be specified as well. For information about the number of load balancers that you can specify per service, see Service Load Balancing in the Amazon Elastic Container Service Developer Guide. - Name string
- Property name
- Network
Configuration NetworkConfiguration Response - The network configuration for the service. This parameter is required for task definitions that use the
awsvpcnetwork mode to receive their own elastic network interface, and it is not supported for other network modes. For more information, see Task Networking in the Amazon Elastic Container Service Developer Guide. TheNetworkConfigurationproperty specifies an object representing the network configuration for a task or service. - Placement
Constraints []PlacementConstraint Response - An array of placement constraint objects to use for tasks in your service. You can specify a maximum of 10 constraints for each task. This limit includes constraints in the task definition and those specified at runtime.
- Placement
Strategies []PlacementStrategy Response - The placement strategy objects to use for tasks in your service. You can specify a maximum of 5 strategy rules for each service.
- Platform
Version string - The platform version that your tasks in the service are running on. A platform version is specified only for tasks using the Fargate launch type. If one isn't specified, the
LATESTplatform version is used. For more information, see platform versions in the Amazon Elastic Container Service Developer Guide. - string
- Specifies whether to propagate the tags from the task definition to the task. If no value is specified, the tags aren't propagated. Tags can only be propagated to the task during task creation. To add tags to a task after task creation, use the TagResource API action. The default is
NONE. - Role string
- The name or full Amazon Resource Name (ARN) of the IAM role that allows Amazon ECS to make calls to your load balancer on your behalf. This parameter is only permitted if you are using a load balancer with your service and your task definition doesn't use the
awsvpcnetwork mode. If you specify theroleparameter, you must also specify a load balancer object with theloadBalancersparameter. If your account has already created the Amazon ECS service-linked role, that role is used for your service unless you specify a role here. The service-linked role is required if your task definition uses theawsvpcnetwork mode or if the service is configured to use service discovery, an external deployment controller, multiple target groups, or Elastic Inference accelerators in which case you don't specify a role here. For more information, see Using service-linked roles for Amazon ECS in the Amazon Elastic Container Service Developer Guide. If your specified role has a path other than/, then you must either specify the full role ARN (this is recommended) or prefix the role name with the path. For example, if a role with the namebarhas a path of/foo/then you would specify/foo/baras the role name. For more information, see Friendly names and paths in the IAM User Guide. - Scheduling
Strategy string - The scheduling strategy to use for the service. For more information, see Services. There are two service scheduler strategies available: +
REPLICA-The replica scheduling strategy places and maintains the desired number of tasks across your cluster. By default, the service scheduler spreads tasks across Availability Zones. You can use task placement strategies and constraints to customize task placement decisions. This scheduler strategy is required if the service uses theCODE_DEPLOYorEXTERNALdeployment controller types. +DAEMON-The daemon scheduling strategy deploys exactly one task on each active container instance that meets all of the task placement constraints that you specify in your cluster. The service scheduler also evaluates the task placement constraints for running tasks and will stop tasks that don't meet the placement constraints. When you're using this strategy, you don't need to specify a desired number of tasks, a task placement strategy, or use Service Auto Scaling policies. Tasks using the Fargate launch type or theCODE_DEPLOYorEXTERNALdeployment controller types don't support theDAEMONscheduling strategy. - Service
Arn string - Property serviceArn
- Service
Connect ServiceConfiguration Connect Configuration Response - The configuration for this service to discover and connect to services, and be discovered by, and connected from, other services within a namespace. 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. The Service Connect configuration of your Amazon ECS service. The configuration for this service to discover and connect to services, and be discovered by, and connected from, other services within a namespace. 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.
- Service
Name string - The name of your service. Up to 255 letters (uppercase and lowercase), numbers, underscores, and hyphens are allowed. Service names must be unique within a cluster, but you can have similarly named services in multiple clusters within a Region or across multiple Regions. The stack update fails if you change any properties that require replacement and the
ServiceNameis configured. This is because AWS CloudFormation creates the replacement service first, but eachServiceNamemust be unique in the cluster. - Service
Registries []ServiceRegistry Response - The details of the service discovery registry to associate with this service. For more information, see Service discovery. Each service may be associated with one service registry. Multiple service registries for each service isn't supported.
-
[]Tag
Response - The metadata that you apply to the service to help you categorize and organize them. Each tag consists of a key and an optional value, both of which you define. When a service is deleted, the tags are deleted as well. 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 AWS 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. - Task
Definition string - The
familyandrevision(family:revision) or full ARN of the task definition to run in your service. If arevisionisn't specified, the latestACTIVErevision is used. A task definition must be specified if the service uses either theECSorCODE_DEPLOYdeployment controllers. For more information about deployment types, see Amazon ECS deployment types. - Volume
Configurations []ServiceVolume Configuration Response - The configuration for a volume specified in the task definition as a volume that is configured at launch time. Currently, the only supported volume type is an Amazon EBS volume.
- capacity
Provider List<CapacityStrategy Provider Strategy Item Response> - The capacity provider strategy to use for the service. If a
capacityProviderStrategyis specified, thelaunchTypeparameter must be omitted. If nocapacityProviderStrategyorlaunchTypeis specified, thedefaultCapacityProviderStrategyfor the cluster is used. A capacity provider strategy may contain a maximum of 6 capacity providers. - cluster String
- The short name or full Amazon Resource Name (ARN) of the cluster that you run your service on. If you do not specify a cluster, the default cluster is assumed.
- deployment
Configuration DeploymentConfiguration Response - Optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks. The
DeploymentConfigurationproperty specifies optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks. - deployment
Controller DeploymentController Response - The deployment controller to use for the service. If no deployment controller is specified, the default value of
ECSis used. The deployment controller to use for the service. For more information, see Amazon ECS deployment types in the Amazon Elastic Container Service Developer Guide. - desired
Count Integer - The number of instantiations of the specified task definition to place and keep running in your service. For new services, if a desired count is not specified, a default value of
1is used. When using theDAEMONscheduling strategy, the desired count is not required. For existing services, if a desired count is not specified, it is omitted from the operation. - Boolean
- Specifies whether to turn on Amazon ECS managed tags for the tasks within the service. For more information, see Tagging your Amazon ECS resources in the Amazon Elastic Container Service Developer Guide. When you use Amazon ECS managed tags, you need to set the
propagateTagsrequest parameter. - enable
Execute BooleanCommand - Determines whether the execute command functionality is turned on for the service. If
true, the execute command functionality is turned on for all containers in tasks as part of the service. - health
Check IntegerGrace Period Seconds - The period of time, in seconds, that the Amazon ECS service scheduler ignores unhealthy Elastic Load Balancing target health checks after a task has first started. This is only used when your service is configured to use a load balancer. If your service has a load balancer defined and you don't specify a health check grace period value, the default value of
0is used. If you do not use an Elastic Load Balancing, we recommend that you use thestartPeriodin the task definition health check parameters. For more information, see Health check. If your service's tasks take a while to start and respond to Elastic Load Balancing health checks, you can specify a health check grace period of up to 2,147,483,647 seconds (about 69 years). During that time, the Amazon ECS service scheduler ignores health check status. This grace period can prevent the service scheduler from marking tasks as unhealthy and stopping them before they have time to come up. - launch
Type String - The launch type on which to run your service. For more information, see Amazon ECS Launch Types in the Amazon Elastic Container Service Developer Guide.
- load
Balancers List<LoadBalancer Response> - A list of load balancer objects to associate with the service. If you specify the
Roleproperty,LoadBalancersmust be specified as well. For information about the number of load balancers that you can specify per service, see Service Load Balancing in the Amazon Elastic Container Service Developer Guide. - name String
- Property name
- network
Configuration NetworkConfiguration Response - The network configuration for the service. This parameter is required for task definitions that use the
awsvpcnetwork mode to receive their own elastic network interface, and it is not supported for other network modes. For more information, see Task Networking in the Amazon Elastic Container Service Developer Guide. TheNetworkConfigurationproperty specifies an object representing the network configuration for a task or service. - placement
Constraints List<PlacementConstraint Response> - An array of placement constraint objects to use for tasks in your service. You can specify a maximum of 10 constraints for each task. This limit includes constraints in the task definition and those specified at runtime.
- placement
Strategies List<PlacementStrategy Response> - The placement strategy objects to use for tasks in your service. You can specify a maximum of 5 strategy rules for each service.
- platform
Version String - The platform version that your tasks in the service are running on. A platform version is specified only for tasks using the Fargate launch type. If one isn't specified, the
LATESTplatform version is used. For more information, see platform versions in the Amazon Elastic Container Service Developer Guide. - String
- Specifies whether to propagate the tags from the task definition to the task. If no value is specified, the tags aren't propagated. Tags can only be propagated to the task during task creation. To add tags to a task after task creation, use the TagResource API action. The default is
NONE. - role String
- The name or full Amazon Resource Name (ARN) of the IAM role that allows Amazon ECS to make calls to your load balancer on your behalf. This parameter is only permitted if you are using a load balancer with your service and your task definition doesn't use the
awsvpcnetwork mode. If you specify theroleparameter, you must also specify a load balancer object with theloadBalancersparameter. If your account has already created the Amazon ECS service-linked role, that role is used for your service unless you specify a role here. The service-linked role is required if your task definition uses theawsvpcnetwork mode or if the service is configured to use service discovery, an external deployment controller, multiple target groups, or Elastic Inference accelerators in which case you don't specify a role here. For more information, see Using service-linked roles for Amazon ECS in the Amazon Elastic Container Service Developer Guide. If your specified role has a path other than/, then you must either specify the full role ARN (this is recommended) or prefix the role name with the path. For example, if a role with the namebarhas a path of/foo/then you would specify/foo/baras the role name. For more information, see Friendly names and paths in the IAM User Guide. - scheduling
Strategy String - The scheduling strategy to use for the service. For more information, see Services. There are two service scheduler strategies available: +
REPLICA-The replica scheduling strategy places and maintains the desired number of tasks across your cluster. By default, the service scheduler spreads tasks across Availability Zones. You can use task placement strategies and constraints to customize task placement decisions. This scheduler strategy is required if the service uses theCODE_DEPLOYorEXTERNALdeployment controller types. +DAEMON-The daemon scheduling strategy deploys exactly one task on each active container instance that meets all of the task placement constraints that you specify in your cluster. The service scheduler also evaluates the task placement constraints for running tasks and will stop tasks that don't meet the placement constraints. When you're using this strategy, you don't need to specify a desired number of tasks, a task placement strategy, or use Service Auto Scaling policies. Tasks using the Fargate launch type or theCODE_DEPLOYorEXTERNALdeployment controller types don't support theDAEMONscheduling strategy. - service
Arn String - Property serviceArn
- service
Connect ServiceConfiguration Connect Configuration Response - The configuration for this service to discover and connect to services, and be discovered by, and connected from, other services within a namespace. 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. The Service Connect configuration of your Amazon ECS service. The configuration for this service to discover and connect to services, and be discovered by, and connected from, other services within a namespace. 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.
- service
Name String - The name of your service. Up to 255 letters (uppercase and lowercase), numbers, underscores, and hyphens are allowed. Service names must be unique within a cluster, but you can have similarly named services in multiple clusters within a Region or across multiple Regions. The stack update fails if you change any properties that require replacement and the
ServiceNameis configured. This is because AWS CloudFormation creates the replacement service first, but eachServiceNamemust be unique in the cluster. - service
Registries List<ServiceRegistry Response> - The details of the service discovery registry to associate with this service. For more information, see Service discovery. Each service may be associated with one service registry. Multiple service registries for each service isn't supported.
-
List<Tag
Response> - The metadata that you apply to the service to help you categorize and organize them. Each tag consists of a key and an optional value, both of which you define. When a service is deleted, the tags are deleted as well. 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 AWS 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. - task
Definition String - The
familyandrevision(family:revision) or full ARN of the task definition to run in your service. If arevisionisn't specified, the latestACTIVErevision is used. A task definition must be specified if the service uses either theECSorCODE_DEPLOYdeployment controllers. For more information about deployment types, see Amazon ECS deployment types. - volume
Configurations List<ServiceVolume Configuration Response> - The configuration for a volume specified in the task definition as a volume that is configured at launch time. Currently, the only supported volume type is an Amazon EBS volume.
- capacity
Provider CapacityStrategy Provider Strategy Item Response[] - The capacity provider strategy to use for the service. If a
capacityProviderStrategyis specified, thelaunchTypeparameter must be omitted. If nocapacityProviderStrategyorlaunchTypeis specified, thedefaultCapacityProviderStrategyfor the cluster is used. A capacity provider strategy may contain a maximum of 6 capacity providers. - cluster string
- The short name or full Amazon Resource Name (ARN) of the cluster that you run your service on. If you do not specify a cluster, the default cluster is assumed.
- deployment
Configuration DeploymentConfiguration Response - Optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks. The
DeploymentConfigurationproperty specifies optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks. - deployment
Controller DeploymentController Response - The deployment controller to use for the service. If no deployment controller is specified, the default value of
ECSis used. The deployment controller to use for the service. For more information, see Amazon ECS deployment types in the Amazon Elastic Container Service Developer Guide. - desired
Count number - The number of instantiations of the specified task definition to place and keep running in your service. For new services, if a desired count is not specified, a default value of
1is used. When using theDAEMONscheduling strategy, the desired count is not required. For existing services, if a desired count is not specified, it is omitted from the operation. - boolean
- Specifies whether to turn on Amazon ECS managed tags for the tasks within the service. For more information, see Tagging your Amazon ECS resources in the Amazon Elastic Container Service Developer Guide. When you use Amazon ECS managed tags, you need to set the
propagateTagsrequest parameter. - enable
Execute booleanCommand - Determines whether the execute command functionality is turned on for the service. If
true, the execute command functionality is turned on for all containers in tasks as part of the service. - health
Check numberGrace Period Seconds - The period of time, in seconds, that the Amazon ECS service scheduler ignores unhealthy Elastic Load Balancing target health checks after a task has first started. This is only used when your service is configured to use a load balancer. If your service has a load balancer defined and you don't specify a health check grace period value, the default value of
0is used. If you do not use an Elastic Load Balancing, we recommend that you use thestartPeriodin the task definition health check parameters. For more information, see Health check. If your service's tasks take a while to start and respond to Elastic Load Balancing health checks, you can specify a health check grace period of up to 2,147,483,647 seconds (about 69 years). During that time, the Amazon ECS service scheduler ignores health check status. This grace period can prevent the service scheduler from marking tasks as unhealthy and stopping them before they have time to come up. - launch
Type string - The launch type on which to run your service. For more information, see Amazon ECS Launch Types in the Amazon Elastic Container Service Developer Guide.
- load
Balancers LoadBalancer Response[] - A list of load balancer objects to associate with the service. If you specify the
Roleproperty,LoadBalancersmust be specified as well. For information about the number of load balancers that you can specify per service, see Service Load Balancing in the Amazon Elastic Container Service Developer Guide. - name string
- Property name
- network
Configuration NetworkConfiguration Response - The network configuration for the service. This parameter is required for task definitions that use the
awsvpcnetwork mode to receive their own elastic network interface, and it is not supported for other network modes. For more information, see Task Networking in the Amazon Elastic Container Service Developer Guide. TheNetworkConfigurationproperty specifies an object representing the network configuration for a task or service. - placement
Constraints PlacementConstraint Response[] - An array of placement constraint objects to use for tasks in your service. You can specify a maximum of 10 constraints for each task. This limit includes constraints in the task definition and those specified at runtime.
- placement
Strategies PlacementStrategy Response[] - The placement strategy objects to use for tasks in your service. You can specify a maximum of 5 strategy rules for each service.
- platform
Version string - The platform version that your tasks in the service are running on. A platform version is specified only for tasks using the Fargate launch type. If one isn't specified, the
LATESTplatform version is used. For more information, see platform versions in the Amazon Elastic Container Service Developer Guide. - string
- Specifies whether to propagate the tags from the task definition to the task. If no value is specified, the tags aren't propagated. Tags can only be propagated to the task during task creation. To add tags to a task after task creation, use the TagResource API action. The default is
NONE. - role string
- The name or full Amazon Resource Name (ARN) of the IAM role that allows Amazon ECS to make calls to your load balancer on your behalf. This parameter is only permitted if you are using a load balancer with your service and your task definition doesn't use the
awsvpcnetwork mode. If you specify theroleparameter, you must also specify a load balancer object with theloadBalancersparameter. If your account has already created the Amazon ECS service-linked role, that role is used for your service unless you specify a role here. The service-linked role is required if your task definition uses theawsvpcnetwork mode or if the service is configured to use service discovery, an external deployment controller, multiple target groups, or Elastic Inference accelerators in which case you don't specify a role here. For more information, see Using service-linked roles for Amazon ECS in the Amazon Elastic Container Service Developer Guide. If your specified role has a path other than/, then you must either specify the full role ARN (this is recommended) or prefix the role name with the path. For example, if a role with the namebarhas a path of/foo/then you would specify/foo/baras the role name. For more information, see Friendly names and paths in the IAM User Guide. - scheduling
Strategy string - The scheduling strategy to use for the service. For more information, see Services. There are two service scheduler strategies available: +
REPLICA-The replica scheduling strategy places and maintains the desired number of tasks across your cluster. By default, the service scheduler spreads tasks across Availability Zones. You can use task placement strategies and constraints to customize task placement decisions. This scheduler strategy is required if the service uses theCODE_DEPLOYorEXTERNALdeployment controller types. +DAEMON-The daemon scheduling strategy deploys exactly one task on each active container instance that meets all of the task placement constraints that you specify in your cluster. The service scheduler also evaluates the task placement constraints for running tasks and will stop tasks that don't meet the placement constraints. When you're using this strategy, you don't need to specify a desired number of tasks, a task placement strategy, or use Service Auto Scaling policies. Tasks using the Fargate launch type or theCODE_DEPLOYorEXTERNALdeployment controller types don't support theDAEMONscheduling strategy. - service
Arn string - Property serviceArn
- service
Connect ServiceConfiguration Connect Configuration Response - The configuration for this service to discover and connect to services, and be discovered by, and connected from, other services within a namespace. 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. The Service Connect configuration of your Amazon ECS service. The configuration for this service to discover and connect to services, and be discovered by, and connected from, other services within a namespace. 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.
- service
Name string - The name of your service. Up to 255 letters (uppercase and lowercase), numbers, underscores, and hyphens are allowed. Service names must be unique within a cluster, but you can have similarly named services in multiple clusters within a Region or across multiple Regions. The stack update fails if you change any properties that require replacement and the
ServiceNameis configured. This is because AWS CloudFormation creates the replacement service first, but eachServiceNamemust be unique in the cluster. - service
Registries ServiceRegistry Response[] - The details of the service discovery registry to associate with this service. For more information, see Service discovery. Each service may be associated with one service registry. Multiple service registries for each service isn't supported.
-
Tag
Response[] - The metadata that you apply to the service to help you categorize and organize them. Each tag consists of a key and an optional value, both of which you define. When a service is deleted, the tags are deleted as well. 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 AWS 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. - task
Definition string - The
familyandrevision(family:revision) or full ARN of the task definition to run in your service. If arevisionisn't specified, the latestACTIVErevision is used. A task definition must be specified if the service uses either theECSorCODE_DEPLOYdeployment controllers. For more information about deployment types, see Amazon ECS deployment types. - volume
Configurations ServiceVolume Configuration Response[] - The configuration for a volume specified in the task definition as a volume that is configured at launch time. Currently, the only supported volume type is an Amazon EBS volume.
- capacity_
provider_ Sequence[Capacitystrategy Provider Strategy Item Response] - The capacity provider strategy to use for the service. If a
capacityProviderStrategyis specified, thelaunchTypeparameter must be omitted. If nocapacityProviderStrategyorlaunchTypeis specified, thedefaultCapacityProviderStrategyfor the cluster is used. A capacity provider strategy may contain a maximum of 6 capacity providers. - cluster str
- The short name or full Amazon Resource Name (ARN) of the cluster that you run your service on. If you do not specify a cluster, the default cluster is assumed.
- deployment_
configuration DeploymentConfiguration Response - Optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks. The
DeploymentConfigurationproperty specifies optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks. - deployment_
controller DeploymentController Response - The deployment controller to use for the service. If no deployment controller is specified, the default value of
ECSis used. The deployment controller to use for the service. For more information, see Amazon ECS deployment types in the Amazon Elastic Container Service Developer Guide. - desired_
count int - The number of instantiations of the specified task definition to place and keep running in your service. For new services, if a desired count is not specified, a default value of
1is used. When using theDAEMONscheduling strategy, the desired count is not required. For existing services, if a desired count is not specified, it is omitted from the operation. - bool
- Specifies whether to turn on Amazon ECS managed tags for the tasks within the service. For more information, see Tagging your Amazon ECS resources in the Amazon Elastic Container Service Developer Guide. When you use Amazon ECS managed tags, you need to set the
propagateTagsrequest parameter. - enable_
execute_ boolcommand - Determines whether the execute command functionality is turned on for the service. If
true, the execute command functionality is turned on for all containers in tasks as part of the service. - health_
check_ intgrace_ period_ seconds - The period of time, in seconds, that the Amazon ECS service scheduler ignores unhealthy Elastic Load Balancing target health checks after a task has first started. This is only used when your service is configured to use a load balancer. If your service has a load balancer defined and you don't specify a health check grace period value, the default value of
0is used. If you do not use an Elastic Load Balancing, we recommend that you use thestartPeriodin the task definition health check parameters. For more information, see Health check. If your service's tasks take a while to start and respond to Elastic Load Balancing health checks, you can specify a health check grace period of up to 2,147,483,647 seconds (about 69 years). During that time, the Amazon ECS service scheduler ignores health check status. This grace period can prevent the service scheduler from marking tasks as unhealthy and stopping them before they have time to come up. - launch_
type str - The launch type on which to run your service. For more information, see Amazon ECS Launch Types in the Amazon Elastic Container Service Developer Guide.
- load_
balancers Sequence[LoadBalancer Response] - A list of load balancer objects to associate with the service. If you specify the
Roleproperty,LoadBalancersmust be specified as well. For information about the number of load balancers that you can specify per service, see Service Load Balancing in the Amazon Elastic Container Service Developer Guide. - name str
- Property name
- network_
configuration NetworkConfiguration Response - The network configuration for the service. This parameter is required for task definitions that use the
awsvpcnetwork mode to receive their own elastic network interface, and it is not supported for other network modes. For more information, see Task Networking in the Amazon Elastic Container Service Developer Guide. TheNetworkConfigurationproperty specifies an object representing the network configuration for a task or service. - placement_
constraints Sequence[PlacementConstraint Response] - An array of placement constraint objects to use for tasks in your service. You can specify a maximum of 10 constraints for each task. This limit includes constraints in the task definition and those specified at runtime.
- placement_
strategies Sequence[PlacementStrategy Response] - The placement strategy objects to use for tasks in your service. You can specify a maximum of 5 strategy rules for each service.
- platform_
version str - The platform version that your tasks in the service are running on. A platform version is specified only for tasks using the Fargate launch type. If one isn't specified, the
LATESTplatform version is used. For more information, see platform versions in the Amazon Elastic Container Service Developer Guide. - str
- Specifies whether to propagate the tags from the task definition to the task. If no value is specified, the tags aren't propagated. Tags can only be propagated to the task during task creation. To add tags to a task after task creation, use the TagResource API action. The default is
NONE. - role str
- The name or full Amazon Resource Name (ARN) of the IAM role that allows Amazon ECS to make calls to your load balancer on your behalf. This parameter is only permitted if you are using a load balancer with your service and your task definition doesn't use the
awsvpcnetwork mode. If you specify theroleparameter, you must also specify a load balancer object with theloadBalancersparameter. If your account has already created the Amazon ECS service-linked role, that role is used for your service unless you specify a role here. The service-linked role is required if your task definition uses theawsvpcnetwork mode or if the service is configured to use service discovery, an external deployment controller, multiple target groups, or Elastic Inference accelerators in which case you don't specify a role here. For more information, see Using service-linked roles for Amazon ECS in the Amazon Elastic Container Service Developer Guide. If your specified role has a path other than/, then you must either specify the full role ARN (this is recommended) or prefix the role name with the path. For example, if a role with the namebarhas a path of/foo/then you would specify/foo/baras the role name. For more information, see Friendly names and paths in the IAM User Guide. - scheduling_
strategy str - The scheduling strategy to use for the service. For more information, see Services. There are two service scheduler strategies available: +
REPLICA-The replica scheduling strategy places and maintains the desired number of tasks across your cluster. By default, the service scheduler spreads tasks across Availability Zones. You can use task placement strategies and constraints to customize task placement decisions. This scheduler strategy is required if the service uses theCODE_DEPLOYorEXTERNALdeployment controller types. +DAEMON-The daemon scheduling strategy deploys exactly one task on each active container instance that meets all of the task placement constraints that you specify in your cluster. The service scheduler also evaluates the task placement constraints for running tasks and will stop tasks that don't meet the placement constraints. When you're using this strategy, you don't need to specify a desired number of tasks, a task placement strategy, or use Service Auto Scaling policies. Tasks using the Fargate launch type or theCODE_DEPLOYorEXTERNALdeployment controller types don't support theDAEMONscheduling strategy. - service_
arn str - Property serviceArn
- service_
connect_ Serviceconfiguration Connect Configuration Response - The configuration for this service to discover and connect to services, and be discovered by, and connected from, other services within a namespace. 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. The Service Connect configuration of your Amazon ECS service. The configuration for this service to discover and connect to services, and be discovered by, and connected from, other services within a namespace. 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.
- service_
name str - The name of your service. Up to 255 letters (uppercase and lowercase), numbers, underscores, and hyphens are allowed. Service names must be unique within a cluster, but you can have similarly named services in multiple clusters within a Region or across multiple Regions. The stack update fails if you change any properties that require replacement and the
ServiceNameis configured. This is because AWS CloudFormation creates the replacement service first, but eachServiceNamemust be unique in the cluster. - service_
registries Sequence[ServiceRegistry Response] - The details of the service discovery registry to associate with this service. For more information, see Service discovery. Each service may be associated with one service registry. Multiple service registries for each service isn't supported.
-
Sequence[Tag
Response] - The metadata that you apply to the service to help you categorize and organize them. Each tag consists of a key and an optional value, both of which you define. When a service is deleted, the tags are deleted as well. 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 AWS 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. - task_
definition str - The
familyandrevision(family:revision) or full ARN of the task definition to run in your service. If arevisionisn't specified, the latestACTIVErevision is used. A task definition must be specified if the service uses either theECSorCODE_DEPLOYdeployment controllers. For more information about deployment types, see Amazon ECS deployment types. - volume_
configurations Sequence[ServiceVolume Configuration Response] - The configuration for a volume specified in the task definition as a volume that is configured at launch time. Currently, the only supported volume type is an Amazon EBS volume.
- capacity
Provider List<Property Map>Strategy - The capacity provider strategy to use for the service. If a
capacityProviderStrategyis specified, thelaunchTypeparameter must be omitted. If nocapacityProviderStrategyorlaunchTypeis specified, thedefaultCapacityProviderStrategyfor the cluster is used. A capacity provider strategy may contain a maximum of 6 capacity providers. - cluster String
- The short name or full Amazon Resource Name (ARN) of the cluster that you run your service on. If you do not specify a cluster, the default cluster is assumed.
- deployment
Configuration Property Map - Optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks. The
DeploymentConfigurationproperty specifies optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks. - deployment
Controller Property Map - The deployment controller to use for the service. If no deployment controller is specified, the default value of
ECSis used. The deployment controller to use for the service. For more information, see Amazon ECS deployment types in the Amazon Elastic Container Service Developer Guide. - desired
Count Number - The number of instantiations of the specified task definition to place and keep running in your service. For new services, if a desired count is not specified, a default value of
1is used. When using theDAEMONscheduling strategy, the desired count is not required. For existing services, if a desired count is not specified, it is omitted from the operation. - Boolean
- Specifies whether to turn on Amazon ECS managed tags for the tasks within the service. For more information, see Tagging your Amazon ECS resources in the Amazon Elastic Container Service Developer Guide. When you use Amazon ECS managed tags, you need to set the
propagateTagsrequest parameter. - enable
Execute BooleanCommand - Determines whether the execute command functionality is turned on for the service. If
true, the execute command functionality is turned on for all containers in tasks as part of the service. - health
Check NumberGrace Period Seconds - The period of time, in seconds, that the Amazon ECS service scheduler ignores unhealthy Elastic Load Balancing target health checks after a task has first started. This is only used when your service is configured to use a load balancer. If your service has a load balancer defined and you don't specify a health check grace period value, the default value of
0is used. If you do not use an Elastic Load Balancing, we recommend that you use thestartPeriodin the task definition health check parameters. For more information, see Health check. If your service's tasks take a while to start and respond to Elastic Load Balancing health checks, you can specify a health check grace period of up to 2,147,483,647 seconds (about 69 years). During that time, the Amazon ECS service scheduler ignores health check status. This grace period can prevent the service scheduler from marking tasks as unhealthy and stopping them before they have time to come up. - launch
Type String - The launch type on which to run your service. For more information, see Amazon ECS Launch Types in the Amazon Elastic Container Service Developer Guide.
- load
Balancers List<Property Map> - A list of load balancer objects to associate with the service. If you specify the
Roleproperty,LoadBalancersmust be specified as well. For information about the number of load balancers that you can specify per service, see Service Load Balancing in the Amazon Elastic Container Service Developer Guide. - name String
- Property name
- network
Configuration Property Map - The network configuration for the service. This parameter is required for task definitions that use the
awsvpcnetwork mode to receive their own elastic network interface, and it is not supported for other network modes. For more information, see Task Networking in the Amazon Elastic Container Service Developer Guide. TheNetworkConfigurationproperty specifies an object representing the network configuration for a task or service. - placement
Constraints List<Property Map> - An array of placement constraint objects to use for tasks in your service. You can specify a maximum of 10 constraints for each task. This limit includes constraints in the task definition and those specified at runtime.
- placement
Strategies List<Property Map> - The placement strategy objects to use for tasks in your service. You can specify a maximum of 5 strategy rules for each service.
- platform
Version String - The platform version that your tasks in the service are running on. A platform version is specified only for tasks using the Fargate launch type. If one isn't specified, the
LATESTplatform version is used. For more information, see platform versions in the Amazon Elastic Container Service Developer Guide. - String
- Specifies whether to propagate the tags from the task definition to the task. If no value is specified, the tags aren't propagated. Tags can only be propagated to the task during task creation. To add tags to a task after task creation, use the TagResource API action. The default is
NONE. - role String
- The name or full Amazon Resource Name (ARN) of the IAM role that allows Amazon ECS to make calls to your load balancer on your behalf. This parameter is only permitted if you are using a load balancer with your service and your task definition doesn't use the
awsvpcnetwork mode. If you specify theroleparameter, you must also specify a load balancer object with theloadBalancersparameter. If your account has already created the Amazon ECS service-linked role, that role is used for your service unless you specify a role here. The service-linked role is required if your task definition uses theawsvpcnetwork mode or if the service is configured to use service discovery, an external deployment controller, multiple target groups, or Elastic Inference accelerators in which case you don't specify a role here. For more information, see Using service-linked roles for Amazon ECS in the Amazon Elastic Container Service Developer Guide. If your specified role has a path other than/, then you must either specify the full role ARN (this is recommended) or prefix the role name with the path. For example, if a role with the namebarhas a path of/foo/then you would specify/foo/baras the role name. For more information, see Friendly names and paths in the IAM User Guide. - scheduling
Strategy String - The scheduling strategy to use for the service. For more information, see Services. There are two service scheduler strategies available: +
REPLICA-The replica scheduling strategy places and maintains the desired number of tasks across your cluster. By default, the service scheduler spreads tasks across Availability Zones. You can use task placement strategies and constraints to customize task placement decisions. This scheduler strategy is required if the service uses theCODE_DEPLOYorEXTERNALdeployment controller types. +DAEMON-The daemon scheduling strategy deploys exactly one task on each active container instance that meets all of the task placement constraints that you specify in your cluster. The service scheduler also evaluates the task placement constraints for running tasks and will stop tasks that don't meet the placement constraints. When you're using this strategy, you don't need to specify a desired number of tasks, a task placement strategy, or use Service Auto Scaling policies. Tasks using the Fargate launch type or theCODE_DEPLOYorEXTERNALdeployment controller types don't support theDAEMONscheduling strategy. - service
Arn String - Property serviceArn
- service
Connect Property MapConfiguration - The configuration for this service to discover and connect to services, and be discovered by, and connected from, other services within a namespace. 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. The Service Connect configuration of your Amazon ECS service. The configuration for this service to discover and connect to services, and be discovered by, and connected from, other services within a namespace. 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.
- service
Name String - The name of your service. Up to 255 letters (uppercase and lowercase), numbers, underscores, and hyphens are allowed. Service names must be unique within a cluster, but you can have similarly named services in multiple clusters within a Region or across multiple Regions. The stack update fails if you change any properties that require replacement and the
ServiceNameis configured. This is because AWS CloudFormation creates the replacement service first, but eachServiceNamemust be unique in the cluster. - service
Registries List<Property Map> - The details of the service discovery registry to associate with this service. For more information, see Service discovery. Each service may be associated with one service registry. Multiple service registries for each service isn't supported.
- List<Property Map>
- The metadata that you apply to the service to help you categorize and organize them. Each tag consists of a key and an optional value, both of which you define. When a service is deleted, the tags are deleted as well. 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 AWS 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. - task
Definition String - The
familyandrevision(family:revision) or full ARN of the task definition to run in your service. If arevisionisn't specified, the latestACTIVErevision is used. A task definition must be specified if the service uses either theECSorCODE_DEPLOYdeployment controllers. For more information about deployment types, see Amazon ECS deployment types. - volume
Configurations List<Property Map> - The configuration for a volume specified in the task definition as a volume that is configured at launch time. Currently, the only supported volume type is an Amazon EBS volume.
AwsVpcConfiguration, AwsVpcConfigurationArgs
, AwsVpcConfigurationArgs
- Assign
Public string | Pulumi.Ip Azure Native. Aws Connector. Aws Vpc Configuration Assign Public Ip - Whether the task's elastic network interface receives a public IP address. The default value is
DISABLED. - Security
Groups List<string> - The IDs of the security groups associated with the task or service. If you don't specify a security group, the default security group for the VPC is used. There's a limit of 5 security groups that can be specified per
AwsVpcConfiguration. All specified security groups must be from the same VPC. - Subnets List<string>
- The IDs of the subnets associated with the task or service. There's a limit of 16 subnets that can be specified per
AwsVpcConfiguration. All specified subnets must be from the same VPC.
- Assign
Public string | AwsIp Vpc Configuration Assign Public Ip - Whether the task's elastic network interface receives a public IP address. The default value is
DISABLED. - Security
Groups []string - The IDs of the security groups associated with the task or service. If you don't specify a security group, the default security group for the VPC is used. There's a limit of 5 security groups that can be specified per
AwsVpcConfiguration. All specified security groups must be from the same VPC. - Subnets []string
- The IDs of the subnets associated with the task or service. There's a limit of 16 subnets that can be specified per
AwsVpcConfiguration. All specified subnets must be from the same VPC.
- assign
Public String | AwsIp Vpc Configuration Assign Public Ip - Whether the task's elastic network interface receives a public IP address. The default value is
DISABLED. - security
Groups List<String> - The IDs of the security groups associated with the task or service. If you don't specify a security group, the default security group for the VPC is used. There's a limit of 5 security groups that can be specified per
AwsVpcConfiguration. All specified security groups must be from the same VPC. - subnets List<String>
- The IDs of the subnets associated with the task or service. There's a limit of 16 subnets that can be specified per
AwsVpcConfiguration. All specified subnets must be from the same VPC.
- assign
Public string | AwsIp Vpc Configuration Assign Public Ip - Whether the task's elastic network interface receives a public IP address. The default value is
DISABLED. - security
Groups string[] - The IDs of the security groups associated with the task or service. If you don't specify a security group, the default security group for the VPC is used. There's a limit of 5 security groups that can be specified per
AwsVpcConfiguration. All specified security groups must be from the same VPC. - subnets string[]
- The IDs of the subnets associated with the task or service. There's a limit of 16 subnets that can be specified per
AwsVpcConfiguration. All specified subnets must be from the same VPC.
- assign_
public_ str | Awsip Vpc Configuration Assign Public Ip - Whether the task's elastic network interface receives a public IP address. The default value is
DISABLED. - security_
groups Sequence[str] - The IDs of the security groups associated with the task or service. If you don't specify a security group, the default security group for the VPC is used. There's a limit of 5 security groups that can be specified per
AwsVpcConfiguration. All specified security groups must be from the same VPC. - subnets Sequence[str]
- The IDs of the subnets associated with the task or service. There's a limit of 16 subnets that can be specified per
AwsVpcConfiguration. All specified subnets must be from the same VPC.
- assign
Public String | "DISABLED" | "ENABLED"Ip - Whether the task's elastic network interface receives a public IP address. The default value is
DISABLED. - security
Groups List<String> - The IDs of the security groups associated with the task or service. If you don't specify a security group, the default security group for the VPC is used. There's a limit of 5 security groups that can be specified per
AwsVpcConfiguration. All specified security groups must be from the same VPC. - subnets List<String>
- The IDs of the subnets associated with the task or service. There's a limit of 16 subnets that can be specified per
AwsVpcConfiguration. All specified subnets must be from the same VPC.
AwsVpcConfigurationAssignPublicIp, AwsVpcConfigurationAssignPublicIpArgs
, AwsVpcConfigurationAssignPublicIpArgs
- DISABLED
- DISABLEDAwsVpcConfigurationAssignPublicIp enum DISABLED
- ENABLED
- ENABLEDAwsVpcConfigurationAssignPublicIp enum ENABLED
- Aws
Vpc Configuration Assign Public Ip DISABLED - DISABLEDAwsVpcConfigurationAssignPublicIp enum DISABLED
- Aws
Vpc Configuration Assign Public Ip ENABLED - ENABLEDAwsVpcConfigurationAssignPublicIp enum ENABLED
- DISABLED
- DISABLEDAwsVpcConfigurationAssignPublicIp enum DISABLED
- ENABLED
- ENABLEDAwsVpcConfigurationAssignPublicIp enum ENABLED
- DISABLED
- DISABLEDAwsVpcConfigurationAssignPublicIp enum DISABLED
- ENABLED
- ENABLEDAwsVpcConfigurationAssignPublicIp enum ENABLED
- DISABLED
- DISABLEDAwsVpcConfigurationAssignPublicIp enum DISABLED
- ENABLED
- ENABLEDAwsVpcConfigurationAssignPublicIp enum ENABLED
- "DISABLED"
- DISABLEDAwsVpcConfigurationAssignPublicIp enum DISABLED
- "ENABLED"
- ENABLEDAwsVpcConfigurationAssignPublicIp enum ENABLED
AwsVpcConfigurationResponse, AwsVpcConfigurationResponseArgs
, AwsVpcConfigurationResponseArgs
- Assign
Public stringIp - Whether the task's elastic network interface receives a public IP address. The default value is
DISABLED. - Security
Groups List<string> - The IDs of the security groups associated with the task or service. If you don't specify a security group, the default security group for the VPC is used. There's a limit of 5 security groups that can be specified per
AwsVpcConfiguration. All specified security groups must be from the same VPC. - Subnets List<string>
- The IDs of the subnets associated with the task or service. There's a limit of 16 subnets that can be specified per
AwsVpcConfiguration. All specified subnets must be from the same VPC.
- Assign
Public stringIp - Whether the task's elastic network interface receives a public IP address. The default value is
DISABLED. - Security
Groups []string - The IDs of the security groups associated with the task or service. If you don't specify a security group, the default security group for the VPC is used. There's a limit of 5 security groups that can be specified per
AwsVpcConfiguration. All specified security groups must be from the same VPC. - Subnets []string
- The IDs of the subnets associated with the task or service. There's a limit of 16 subnets that can be specified per
AwsVpcConfiguration. All specified subnets must be from the same VPC.
- assign
Public StringIp - Whether the task's elastic network interface receives a public IP address. The default value is
DISABLED. - security
Groups List<String> - The IDs of the security groups associated with the task or service. If you don't specify a security group, the default security group for the VPC is used. There's a limit of 5 security groups that can be specified per
AwsVpcConfiguration. All specified security groups must be from the same VPC. - subnets List<String>
- The IDs of the subnets associated with the task or service. There's a limit of 16 subnets that can be specified per
AwsVpcConfiguration. All specified subnets must be from the same VPC.
- assign
Public stringIp - Whether the task's elastic network interface receives a public IP address. The default value is
DISABLED. - security
Groups string[] - The IDs of the security groups associated with the task or service. If you don't specify a security group, the default security group for the VPC is used. There's a limit of 5 security groups that can be specified per
AwsVpcConfiguration. All specified security groups must be from the same VPC. - subnets string[]
- The IDs of the subnets associated with the task or service. There's a limit of 16 subnets that can be specified per
AwsVpcConfiguration. All specified subnets must be from the same VPC.
- assign_
public_ strip - Whether the task's elastic network interface receives a public IP address. The default value is
DISABLED. - security_
groups Sequence[str] - The IDs of the security groups associated with the task or service. If you don't specify a security group, the default security group for the VPC is used. There's a limit of 5 security groups that can be specified per
AwsVpcConfiguration. All specified security groups must be from the same VPC. - subnets Sequence[str]
- The IDs of the subnets associated with the task or service. There's a limit of 16 subnets that can be specified per
AwsVpcConfiguration. All specified subnets must be from the same VPC.
- assign
Public StringIp - Whether the task's elastic network interface receives a public IP address. The default value is
DISABLED. - security
Groups List<String> - The IDs of the security groups associated with the task or service. If you don't specify a security group, the default security group for the VPC is used. There's a limit of 5 security groups that can be specified per
AwsVpcConfiguration. All specified security groups must be from the same VPC. - subnets List<String>
- The IDs of the subnets associated with the task or service. There's a limit of 16 subnets that can be specified per
AwsVpcConfiguration. All specified subnets must be from the same VPC.
CapacityProviderStrategyItem, CapacityProviderStrategyItemArgs
, CapacityProviderStrategyItemArgs
- Base int
- The base value designates how many tasks, at a minimum, to run on the specified capacity provider. Only one capacity provider in a capacity provider strategy can have a base defined. If no value is specified, the default value of
0is used. - Capacity
Provider string - The short name of the capacity provider.
- Weight int
- The weight value designates the relative percentage of the total number of tasks launched that should use the specified capacity provider. The
weightvalue is taken into consideration after thebasevalue, if defined, is satisfied. If noweightvalue is specified, the default value of0is used. When multiple capacity providers are specified within a capacity provider strategy, at least one of the capacity providers must have a weight value greater than zero and any capacity providers with a weight of0can't be used to place tasks. If you specify multiple capacity providers in a strategy that all have a weight of0, anyRunTaskorCreateServiceactions using the capacity provider strategy will fail. An example scenario for using weights is defining a strategy that contains two capacity providers and both have a weight of1, then when thebaseis satisfied, the tasks will be split evenly across the two capacity providers. Using that same logic, if you specify a weight of1for capacityProviderA and a weight of4for capacityProviderB, then for every one task that's run using capacityProviderA, four tasks would use capacityProviderB.
- Base int
- The base value designates how many tasks, at a minimum, to run on the specified capacity provider. Only one capacity provider in a capacity provider strategy can have a base defined. If no value is specified, the default value of
0is used. - Capacity
Provider string - The short name of the capacity provider.
- Weight int
- The weight value designates the relative percentage of the total number of tasks launched that should use the specified capacity provider. The
weightvalue is taken into consideration after thebasevalue, if defined, is satisfied. If noweightvalue is specified, the default value of0is used. When multiple capacity providers are specified within a capacity provider strategy, at least one of the capacity providers must have a weight value greater than zero and any capacity providers with a weight of0can't be used to place tasks. If you specify multiple capacity providers in a strategy that all have a weight of0, anyRunTaskorCreateServiceactions using the capacity provider strategy will fail. An example scenario for using weights is defining a strategy that contains two capacity providers and both have a weight of1, then when thebaseis satisfied, the tasks will be split evenly across the two capacity providers. Using that same logic, if you specify a weight of1for capacityProviderA and a weight of4for capacityProviderB, then for every one task that's run using capacityProviderA, four tasks would use capacityProviderB.
- base Integer
- The base value designates how many tasks, at a minimum, to run on the specified capacity provider. Only one capacity provider in a capacity provider strategy can have a base defined. If no value is specified, the default value of
0is used. - capacity
Provider String - The short name of the capacity provider.
- weight Integer
- The weight value designates the relative percentage of the total number of tasks launched that should use the specified capacity provider. The
weightvalue is taken into consideration after thebasevalue, if defined, is satisfied. If noweightvalue is specified, the default value of0is used. When multiple capacity providers are specified within a capacity provider strategy, at least one of the capacity providers must have a weight value greater than zero and any capacity providers with a weight of0can't be used to place tasks. If you specify multiple capacity providers in a strategy that all have a weight of0, anyRunTaskorCreateServiceactions using the capacity provider strategy will fail. An example scenario for using weights is defining a strategy that contains two capacity providers and both have a weight of1, then when thebaseis satisfied, the tasks will be split evenly across the two capacity providers. Using that same logic, if you specify a weight of1for capacityProviderA and a weight of4for capacityProviderB, then for every one task that's run using capacityProviderA, four tasks would use capacityProviderB.
- base number
- The base value designates how many tasks, at a minimum, to run on the specified capacity provider. Only one capacity provider in a capacity provider strategy can have a base defined. If no value is specified, the default value of
0is used. - capacity
Provider string - The short name of the capacity provider.
- weight number
- The weight value designates the relative percentage of the total number of tasks launched that should use the specified capacity provider. The
weightvalue is taken into consideration after thebasevalue, if defined, is satisfied. If noweightvalue is specified, the default value of0is used. When multiple capacity providers are specified within a capacity provider strategy, at least one of the capacity providers must have a weight value greater than zero and any capacity providers with a weight of0can't be used to place tasks. If you specify multiple capacity providers in a strategy that all have a weight of0, anyRunTaskorCreateServiceactions using the capacity provider strategy will fail. An example scenario for using weights is defining a strategy that contains two capacity providers and both have a weight of1, then when thebaseis satisfied, the tasks will be split evenly across the two capacity providers. Using that same logic, if you specify a weight of1for capacityProviderA and a weight of4for capacityProviderB, then for every one task that's run using capacityProviderA, four tasks would use capacityProviderB.
- base int
- The base value designates how many tasks, at a minimum, to run on the specified capacity provider. Only one capacity provider in a capacity provider strategy can have a base defined. If no value is specified, the default value of
0is used. - capacity_
provider str - The short name of the capacity provider.
- weight int
- The weight value designates the relative percentage of the total number of tasks launched that should use the specified capacity provider. The
weightvalue is taken into consideration after thebasevalue, if defined, is satisfied. If noweightvalue is specified, the default value of0is used. When multiple capacity providers are specified within a capacity provider strategy, at least one of the capacity providers must have a weight value greater than zero and any capacity providers with a weight of0can't be used to place tasks. If you specify multiple capacity providers in a strategy that all have a weight of0, anyRunTaskorCreateServiceactions using the capacity provider strategy will fail. An example scenario for using weights is defining a strategy that contains two capacity providers and both have a weight of1, then when thebaseis satisfied, the tasks will be split evenly across the two capacity providers. Using that same logic, if you specify a weight of1for capacityProviderA and a weight of4for capacityProviderB, then for every one task that's run using capacityProviderA, four tasks would use capacityProviderB.
- base Number
- The base value designates how many tasks, at a minimum, to run on the specified capacity provider. Only one capacity provider in a capacity provider strategy can have a base defined. If no value is specified, the default value of
0is used. - capacity
Provider String - The short name of the capacity provider.
- weight Number
- The weight value designates the relative percentage of the total number of tasks launched that should use the specified capacity provider. The
weightvalue is taken into consideration after thebasevalue, if defined, is satisfied. If noweightvalue is specified, the default value of0is used. When multiple capacity providers are specified within a capacity provider strategy, at least one of the capacity providers must have a weight value greater than zero and any capacity providers with a weight of0can't be used to place tasks. If you specify multiple capacity providers in a strategy that all have a weight of0, anyRunTaskorCreateServiceactions using the capacity provider strategy will fail. An example scenario for using weights is defining a strategy that contains two capacity providers and both have a weight of1, then when thebaseis satisfied, the tasks will be split evenly across the two capacity providers. Using that same logic, if you specify a weight of1for capacityProviderA and a weight of4for capacityProviderB, then for every one task that's run using capacityProviderA, four tasks would use capacityProviderB.
CapacityProviderStrategyItemResponse, CapacityProviderStrategyItemResponseArgs
, CapacityProviderStrategyItemResponseArgs
- Base int
- The base value designates how many tasks, at a minimum, to run on the specified capacity provider. Only one capacity provider in a capacity provider strategy can have a base defined. If no value is specified, the default value of
0is used. - Capacity
Provider string - The short name of the capacity provider.
- Weight int
- The weight value designates the relative percentage of the total number of tasks launched that should use the specified capacity provider. The
weightvalue is taken into consideration after thebasevalue, if defined, is satisfied. If noweightvalue is specified, the default value of0is used. When multiple capacity providers are specified within a capacity provider strategy, at least one of the capacity providers must have a weight value greater than zero and any capacity providers with a weight of0can't be used to place tasks. If you specify multiple capacity providers in a strategy that all have a weight of0, anyRunTaskorCreateServiceactions using the capacity provider strategy will fail. An example scenario for using weights is defining a strategy that contains two capacity providers and both have a weight of1, then when thebaseis satisfied, the tasks will be split evenly across the two capacity providers. Using that same logic, if you specify a weight of1for capacityProviderA and a weight of4for capacityProviderB, then for every one task that's run using capacityProviderA, four tasks would use capacityProviderB.
- Base int
- The base value designates how many tasks, at a minimum, to run on the specified capacity provider. Only one capacity provider in a capacity provider strategy can have a base defined. If no value is specified, the default value of
0is used. - Capacity
Provider string - The short name of the capacity provider.
- Weight int
- The weight value designates the relative percentage of the total number of tasks launched that should use the specified capacity provider. The
weightvalue is taken into consideration after thebasevalue, if defined, is satisfied. If noweightvalue is specified, the default value of0is used. When multiple capacity providers are specified within a capacity provider strategy, at least one of the capacity providers must have a weight value greater than zero and any capacity providers with a weight of0can't be used to place tasks. If you specify multiple capacity providers in a strategy that all have a weight of0, anyRunTaskorCreateServiceactions using the capacity provider strategy will fail. An example scenario for using weights is defining a strategy that contains two capacity providers and both have a weight of1, then when thebaseis satisfied, the tasks will be split evenly across the two capacity providers. Using that same logic, if you specify a weight of1for capacityProviderA and a weight of4for capacityProviderB, then for every one task that's run using capacityProviderA, four tasks would use capacityProviderB.
- base Integer
- The base value designates how many tasks, at a minimum, to run on the specified capacity provider. Only one capacity provider in a capacity provider strategy can have a base defined. If no value is specified, the default value of
0is used. - capacity
Provider String - The short name of the capacity provider.
- weight Integer
- The weight value designates the relative percentage of the total number of tasks launched that should use the specified capacity provider. The
weightvalue is taken into consideration after thebasevalue, if defined, is satisfied. If noweightvalue is specified, the default value of0is used. When multiple capacity providers are specified within a capacity provider strategy, at least one of the capacity providers must have a weight value greater than zero and any capacity providers with a weight of0can't be used to place tasks. If you specify multiple capacity providers in a strategy that all have a weight of0, anyRunTaskorCreateServiceactions using the capacity provider strategy will fail. An example scenario for using weights is defining a strategy that contains two capacity providers and both have a weight of1, then when thebaseis satisfied, the tasks will be split evenly across the two capacity providers. Using that same logic, if you specify a weight of1for capacityProviderA and a weight of4for capacityProviderB, then for every one task that's run using capacityProviderA, four tasks would use capacityProviderB.
- base number
- The base value designates how many tasks, at a minimum, to run on the specified capacity provider. Only one capacity provider in a capacity provider strategy can have a base defined. If no value is specified, the default value of
0is used. - capacity
Provider string - The short name of the capacity provider.
- weight number
- The weight value designates the relative percentage of the total number of tasks launched that should use the specified capacity provider. The
weightvalue is taken into consideration after thebasevalue, if defined, is satisfied. If noweightvalue is specified, the default value of0is used. When multiple capacity providers are specified within a capacity provider strategy, at least one of the capacity providers must have a weight value greater than zero and any capacity providers with a weight of0can't be used to place tasks. If you specify multiple capacity providers in a strategy that all have a weight of0, anyRunTaskorCreateServiceactions using the capacity provider strategy will fail. An example scenario for using weights is defining a strategy that contains two capacity providers and both have a weight of1, then when thebaseis satisfied, the tasks will be split evenly across the two capacity providers. Using that same logic, if you specify a weight of1for capacityProviderA and a weight of4for capacityProviderB, then for every one task that's run using capacityProviderA, four tasks would use capacityProviderB.
- base int
- The base value designates how many tasks, at a minimum, to run on the specified capacity provider. Only one capacity provider in a capacity provider strategy can have a base defined. If no value is specified, the default value of
0is used. - capacity_
provider str - The short name of the capacity provider.
- weight int
- The weight value designates the relative percentage of the total number of tasks launched that should use the specified capacity provider. The
weightvalue is taken into consideration after thebasevalue, if defined, is satisfied. If noweightvalue is specified, the default value of0is used. When multiple capacity providers are specified within a capacity provider strategy, at least one of the capacity providers must have a weight value greater than zero and any capacity providers with a weight of0can't be used to place tasks. If you specify multiple capacity providers in a strategy that all have a weight of0, anyRunTaskorCreateServiceactions using the capacity provider strategy will fail. An example scenario for using weights is defining a strategy that contains two capacity providers and both have a weight of1, then when thebaseis satisfied, the tasks will be split evenly across the two capacity providers. Using that same logic, if you specify a weight of1for capacityProviderA and a weight of4for capacityProviderB, then for every one task that's run using capacityProviderA, four tasks would use capacityProviderB.
- base Number
- The base value designates how many tasks, at a minimum, to run on the specified capacity provider. Only one capacity provider in a capacity provider strategy can have a base defined. If no value is specified, the default value of
0is used. - capacity
Provider String - The short name of the capacity provider.
- weight Number
- The weight value designates the relative percentage of the total number of tasks launched that should use the specified capacity provider. The
weightvalue is taken into consideration after thebasevalue, if defined, is satisfied. If noweightvalue is specified, the default value of0is used. When multiple capacity providers are specified within a capacity provider strategy, at least one of the capacity providers must have a weight value greater than zero and any capacity providers with a weight of0can't be used to place tasks. If you specify multiple capacity providers in a strategy that all have a weight of0, anyRunTaskorCreateServiceactions using the capacity provider strategy will fail. An example scenario for using weights is defining a strategy that contains two capacity providers and both have a weight of1, then when thebaseis satisfied, the tasks will be split evenly across the two capacity providers. Using that same logic, if you specify a weight of1for capacityProviderA and a weight of4for capacityProviderB, then for every one task that's run using capacityProviderA, four tasks would use capacityProviderB.
DeploymentAlarms, DeploymentAlarmsArgs
, DeploymentAlarmsArgs
- Alarm
Names List<string> - One or more CloudWatch alarm names. Use a ',' to separate the alarms.
- Enable bool
- Determines whether to use the CloudWatch alarm option in the service deployment process.
- Rollback bool
- Determines whether to configure Amazon ECS to roll back the service if a service deployment fails. If rollback is used, when a service deployment fails, the service is rolled back to the last deployment that completed successfully.
- Alarm
Names []string - One or more CloudWatch alarm names. Use a ',' to separate the alarms.
- Enable bool
- Determines whether to use the CloudWatch alarm option in the service deployment process.
- Rollback bool
- Determines whether to configure Amazon ECS to roll back the service if a service deployment fails. If rollback is used, when a service deployment fails, the service is rolled back to the last deployment that completed successfully.
- alarm
Names List<String> - One or more CloudWatch alarm names. Use a ',' to separate the alarms.
- enable Boolean
- Determines whether to use the CloudWatch alarm option in the service deployment process.
- rollback Boolean
- Determines whether to configure Amazon ECS to roll back the service if a service deployment fails. If rollback is used, when a service deployment fails, the service is rolled back to the last deployment that completed successfully.
- alarm
Names string[] - One or more CloudWatch alarm names. Use a ',' to separate the alarms.
- enable boolean
- Determines whether to use the CloudWatch alarm option in the service deployment process.
- rollback boolean
- Determines whether to configure Amazon ECS to roll back the service if a service deployment fails. If rollback is used, when a service deployment fails, the service is rolled back to the last deployment that completed successfully.
- alarm_
names Sequence[str] - One or more CloudWatch alarm names. Use a ',' to separate the alarms.
- enable bool
- Determines whether to use the CloudWatch alarm option in the service deployment process.
- rollback bool
- Determines whether to configure Amazon ECS to roll back the service if a service deployment fails. If rollback is used, when a service deployment fails, the service is rolled back to the last deployment that completed successfully.
- alarm
Names List<String> - One or more CloudWatch alarm names. Use a ',' to separate the alarms.
- enable Boolean
- Determines whether to use the CloudWatch alarm option in the service deployment process.
- rollback Boolean
- Determines whether to configure Amazon ECS to roll back the service if a service deployment fails. If rollback is used, when a service deployment fails, the service is rolled back to the last deployment that completed successfully.
DeploymentAlarmsResponse, DeploymentAlarmsResponseArgs
, DeploymentAlarmsResponseArgs
- Alarm
Names List<string> - One or more CloudWatch alarm names. Use a ',' to separate the alarms.
- Enable bool
- Determines whether to use the CloudWatch alarm option in the service deployment process.
- Rollback bool
- Determines whether to configure Amazon ECS to roll back the service if a service deployment fails. If rollback is used, when a service deployment fails, the service is rolled back to the last deployment that completed successfully.
- Alarm
Names []string - One or more CloudWatch alarm names. Use a ',' to separate the alarms.
- Enable bool
- Determines whether to use the CloudWatch alarm option in the service deployment process.
- Rollback bool
- Determines whether to configure Amazon ECS to roll back the service if a service deployment fails. If rollback is used, when a service deployment fails, the service is rolled back to the last deployment that completed successfully.
- alarm
Names List<String> - One or more CloudWatch alarm names. Use a ',' to separate the alarms.
- enable Boolean
- Determines whether to use the CloudWatch alarm option in the service deployment process.
- rollback Boolean
- Determines whether to configure Amazon ECS to roll back the service if a service deployment fails. If rollback is used, when a service deployment fails, the service is rolled back to the last deployment that completed successfully.
- alarm
Names string[] - One or more CloudWatch alarm names. Use a ',' to separate the alarms.
- enable boolean
- Determines whether to use the CloudWatch alarm option in the service deployment process.
- rollback boolean
- Determines whether to configure Amazon ECS to roll back the service if a service deployment fails. If rollback is used, when a service deployment fails, the service is rolled back to the last deployment that completed successfully.
- alarm_
names Sequence[str] - One or more CloudWatch alarm names. Use a ',' to separate the alarms.
- enable bool
- Determines whether to use the CloudWatch alarm option in the service deployment process.
- rollback bool
- Determines whether to configure Amazon ECS to roll back the service if a service deployment fails. If rollback is used, when a service deployment fails, the service is rolled back to the last deployment that completed successfully.
- alarm
Names List<String> - One or more CloudWatch alarm names. Use a ',' to separate the alarms.
- enable Boolean
- Determines whether to use the CloudWatch alarm option in the service deployment process.
- rollback Boolean
- Determines whether to configure Amazon ECS to roll back the service if a service deployment fails. If rollback is used, when a service deployment fails, the service is rolled back to the last deployment that completed successfully.
DeploymentCircuitBreaker, DeploymentCircuitBreakerArgs
, DeploymentCircuitBreakerArgs
- Enable bool
- Determines whether to use the deployment circuit breaker logic for the service.
- Rollback bool
- Determines whether to configure Amazon ECS to roll back the service if a service deployment fails. If rollback is on, when a service deployment fails, the service is rolled back to the last deployment that completed successfully.
- Enable bool
- Determines whether to use the deployment circuit breaker logic for the service.
- Rollback bool
- Determines whether to configure Amazon ECS to roll back the service if a service deployment fails. If rollback is on, when a service deployment fails, the service is rolled back to the last deployment that completed successfully.
- enable Boolean
- Determines whether to use the deployment circuit breaker logic for the service.
- rollback Boolean
- Determines whether to configure Amazon ECS to roll back the service if a service deployment fails. If rollback is on, when a service deployment fails, the service is rolled back to the last deployment that completed successfully.
- enable boolean
- Determines whether to use the deployment circuit breaker logic for the service.
- rollback boolean
- Determines whether to configure Amazon ECS to roll back the service if a service deployment fails. If rollback is on, when a service deployment fails, the service is rolled back to the last deployment that completed successfully.
- enable bool
- Determines whether to use the deployment circuit breaker logic for the service.
- rollback bool
- Determines whether to configure Amazon ECS to roll back the service if a service deployment fails. If rollback is on, when a service deployment fails, the service is rolled back to the last deployment that completed successfully.
- enable Boolean
- Determines whether to use the deployment circuit breaker logic for the service.
- rollback Boolean
- Determines whether to configure Amazon ECS to roll back the service if a service deployment fails. If rollback is on, when a service deployment fails, the service is rolled back to the last deployment that completed successfully.
DeploymentCircuitBreakerResponse, DeploymentCircuitBreakerResponseArgs
, DeploymentCircuitBreakerResponseArgs
- Enable bool
- Determines whether to use the deployment circuit breaker logic for the service.
- Rollback bool
- Determines whether to configure Amazon ECS to roll back the service if a service deployment fails. If rollback is on, when a service deployment fails, the service is rolled back to the last deployment that completed successfully.
- Enable bool
- Determines whether to use the deployment circuit breaker logic for the service.
- Rollback bool
- Determines whether to configure Amazon ECS to roll back the service if a service deployment fails. If rollback is on, when a service deployment fails, the service is rolled back to the last deployment that completed successfully.
- enable Boolean
- Determines whether to use the deployment circuit breaker logic for the service.
- rollback Boolean
- Determines whether to configure Amazon ECS to roll back the service if a service deployment fails. If rollback is on, when a service deployment fails, the service is rolled back to the last deployment that completed successfully.
- enable boolean
- Determines whether to use the deployment circuit breaker logic for the service.
- rollback boolean
- Determines whether to configure Amazon ECS to roll back the service if a service deployment fails. If rollback is on, when a service deployment fails, the service is rolled back to the last deployment that completed successfully.
- enable bool
- Determines whether to use the deployment circuit breaker logic for the service.
- rollback bool
- Determines whether to configure Amazon ECS to roll back the service if a service deployment fails. If rollback is on, when a service deployment fails, the service is rolled back to the last deployment that completed successfully.
- enable Boolean
- Determines whether to use the deployment circuit breaker logic for the service.
- rollback Boolean
- Determines whether to configure Amazon ECS to roll back the service if a service deployment fails. If rollback is on, when a service deployment fails, the service is rolled back to the last deployment that completed successfully.
DeploymentConfiguration, DeploymentConfigurationArgs
, DeploymentConfigurationArgs
- Alarms
Pulumi.
Azure Native. Aws Connector. Inputs. Deployment Alarms - Information about the CloudWatch alarms. One of the methods which provide a way for you to quickly identify when a deployment has failed, and then to optionally roll back the failure to the last working deployment. When the alarms are generated, Amazon ECS sets the service deployment to failed. Set the rollback parameter to have Amazon ECS to roll back your service to the last completed deployment after a failure. You can only use the
DeploymentAlarmsmethod to detect failures when theDeploymentControlleris set toECS(rolling update). For more information, see Rolling update in the Amazon Elastic Container Service Developer Guide. - Deployment
Circuit Pulumi.Breaker Azure Native. Aws Connector. Inputs. Deployment Circuit Breaker - The deployment circuit breaker can only be used for services using the rolling update (
ECS) deployment type. The deployment circuit breaker determines whether a service deployment will fail if the service can't reach a steady state. If you use the deployment circuit breaker, a service deployment will transition to a failed state and stop launching new tasks. If you use the rollback option, when a service deployment fails, the service is rolled back to the last deployment that completed successfully. For more information, see Rolling update in the Amazon Elastic Container Service Developer Guide The deployment circuit breaker can only be used for services using the rolling update (ECS) deployment type. The deployment circuit breaker determines whether a service deployment will fail if the service can't reach a steady state. If it is turned on, a service deployment will transition to a failed state and stop launching new tasks. You can also configure Amazon ECS to roll back your service to the last completed deployment after a failure. For more information, see Rolling update in the Amazon Elastic Container Service Developer Guide. For more information about API failure reasons, see API failure reasons in the Amazon Elastic Container Service Developer Guide. - Maximum
Percent int - If a service is using the rolling update (
ECS) deployment type, themaximumPercentparameter represents an upper limit on the number of your service's tasks that are allowed in theRUNNINGorPENDINGstate during a deployment, as a percentage of thedesiredCount(rounded down to the nearest integer). This parameter enables you to define the deployment batch size. For example, if your service is using theREPLICAservice scheduler and has adesiredCountof four tasks and amaximumPercentvalue of 200%, the scheduler may start four new tasks before stopping the four older tasks (provided that the cluster resources required to do this are available). The defaultmaximumPercentvalue for a service using theREPLICAservice scheduler is 200%. If a service is using either the blue/green (CODE_DEPLOY) orEXTERNALdeployment types and tasks that use the EC2 launch type, the maximum percent value is set to the default value and is used to define the upper limit on the number of the tasks in the service that remain in theRUNNINGstate while the container instances are in theDRAININGstate. If the tasks in the service use the Fargate launch type, the maximum percent value is not used, although it is returned when describing your service. - Minimum
Healthy intPercent - If a service is using the rolling update (
ECS) deployment type, theminimumHealthyPercentrepresents a lower limit on the number of your service's tasks that must remain in theRUNNINGstate during a deployment, as a percentage of thedesiredCount(rounded up to the nearest integer). This parameter enables you to deploy without using additional cluster capacity. For example, if your service has adesiredCountof four tasks and aminimumHealthyPercentof 50%, the service scheduler may stop two existing tasks to free up cluster capacity before starting two new tasks. For services that do not use a load balancer, the following should be noted: + A service is considered healthy if all essential containers within the tasks in the service pass their health checks. + If a task has no essential containers with a health check defined, the service scheduler will wait for 40 seconds after a task reaches aRUNNINGstate before the task is counted towards the minimum healthy percent total. + If a task has one or more essential containers with a health check defined, the service scheduler will wait for the task to reach a healthy status before counting it towards the minimum healthy percent total. A task is considered healthy when all essential containers within the task have passed their health checks. The amount of time the service scheduler can wait for is determined by the container health check settings. For services that do use a load balancer, the following should be noted: + If a task has no essential containers with a health check defined, the service scheduler will wait for the load balancer target group health check to return a healthy status before counting the task towards the minimum healthy percent total. + If a task has an essential container with a health check defined, the service scheduler will wait for both the task to reach a healthy status and the load balancer target group health check to return a healthy status before counting the task towards the minimum healthy percent total. If a service is using either the blue/green (CODE_DEPLOY) orEXTERNALdeployment types and is running tasks that use the EC2 launch type, the minimum healthy percent value is set to the default value and is used to define the lower limit on the number of the tasks in the service that remain in theRUNNINGstate while the container instances are in theDRAININGstate. If a service is using either the blue/green (CODE_DEPLOY) orEXTERNALdeployment types and is running tasks that use the Fargate launch type, the minimum healthy percent value is not used, although it is returned when describing your service.
- Alarms
Deployment
Alarms - Information about the CloudWatch alarms. One of the methods which provide a way for you to quickly identify when a deployment has failed, and then to optionally roll back the failure to the last working deployment. When the alarms are generated, Amazon ECS sets the service deployment to failed. Set the rollback parameter to have Amazon ECS to roll back your service to the last completed deployment after a failure. You can only use the
DeploymentAlarmsmethod to detect failures when theDeploymentControlleris set toECS(rolling update). For more information, see Rolling update in the Amazon Elastic Container Service Developer Guide. - Deployment
Circuit DeploymentBreaker Circuit Breaker - The deployment circuit breaker can only be used for services using the rolling update (
ECS) deployment type. The deployment circuit breaker determines whether a service deployment will fail if the service can't reach a steady state. If you use the deployment circuit breaker, a service deployment will transition to a failed state and stop launching new tasks. If you use the rollback option, when a service deployment fails, the service is rolled back to the last deployment that completed successfully. For more information, see Rolling update in the Amazon Elastic Container Service Developer Guide The deployment circuit breaker can only be used for services using the rolling update (ECS) deployment type. The deployment circuit breaker determines whether a service deployment will fail if the service can't reach a steady state. If it is turned on, a service deployment will transition to a failed state and stop launching new tasks. You can also configure Amazon ECS to roll back your service to the last completed deployment after a failure. For more information, see Rolling update in the Amazon Elastic Container Service Developer Guide. For more information about API failure reasons, see API failure reasons in the Amazon Elastic Container Service Developer Guide. - Maximum
Percent int - If a service is using the rolling update (
ECS) deployment type, themaximumPercentparameter represents an upper limit on the number of your service's tasks that are allowed in theRUNNINGorPENDINGstate during a deployment, as a percentage of thedesiredCount(rounded down to the nearest integer). This parameter enables you to define the deployment batch size. For example, if your service is using theREPLICAservice scheduler and has adesiredCountof four tasks and amaximumPercentvalue of 200%, the scheduler may start four new tasks before stopping the four older tasks (provided that the cluster resources required to do this are available). The defaultmaximumPercentvalue for a service using theREPLICAservice scheduler is 200%. If a service is using either the blue/green (CODE_DEPLOY) orEXTERNALdeployment types and tasks that use the EC2 launch type, the maximum percent value is set to the default value and is used to define the upper limit on the number of the tasks in the service that remain in theRUNNINGstate while the container instances are in theDRAININGstate. If the tasks in the service use the Fargate launch type, the maximum percent value is not used, although it is returned when describing your service. - Minimum
Healthy intPercent - If a service is using the rolling update (
ECS) deployment type, theminimumHealthyPercentrepresents a lower limit on the number of your service's tasks that must remain in theRUNNINGstate during a deployment, as a percentage of thedesiredCount(rounded up to the nearest integer). This parameter enables you to deploy without using additional cluster capacity. For example, if your service has adesiredCountof four tasks and aminimumHealthyPercentof 50%, the service scheduler may stop two existing tasks to free up cluster capacity before starting two new tasks. For services that do not use a load balancer, the following should be noted: + A service is considered healthy if all essential containers within the tasks in the service pass their health checks. + If a task has no essential containers with a health check defined, the service scheduler will wait for 40 seconds after a task reaches aRUNNINGstate before the task is counted towards the minimum healthy percent total. + If a task has one or more essential containers with a health check defined, the service scheduler will wait for the task to reach a healthy status before counting it towards the minimum healthy percent total. A task is considered healthy when all essential containers within the task have passed their health checks. The amount of time the service scheduler can wait for is determined by the container health check settings. For services that do use a load balancer, the following should be noted: + If a task has no essential containers with a health check defined, the service scheduler will wait for the load balancer target group health check to return a healthy status before counting the task towards the minimum healthy percent total. + If a task has an essential container with a health check defined, the service scheduler will wait for both the task to reach a healthy status and the load balancer target group health check to return a healthy status before counting the task towards the minimum healthy percent total. If a service is using either the blue/green (CODE_DEPLOY) orEXTERNALdeployment types and is running tasks that use the EC2 launch type, the minimum healthy percent value is set to the default value and is used to define the lower limit on the number of the tasks in the service that remain in theRUNNINGstate while the container instances are in theDRAININGstate. If a service is using either the blue/green (CODE_DEPLOY) orEXTERNALdeployment types and is running tasks that use the Fargate launch type, the minimum healthy percent value is not used, although it is returned when describing your service.
- alarms
Deployment
Alarms - Information about the CloudWatch alarms. One of the methods which provide a way for you to quickly identify when a deployment has failed, and then to optionally roll back the failure to the last working deployment. When the alarms are generated, Amazon ECS sets the service deployment to failed. Set the rollback parameter to have Amazon ECS to roll back your service to the last completed deployment after a failure. You can only use the
DeploymentAlarmsmethod to detect failures when theDeploymentControlleris set toECS(rolling update). For more information, see Rolling update in the Amazon Elastic Container Service Developer Guide. - deployment
Circuit DeploymentBreaker Circuit Breaker - The deployment circuit breaker can only be used for services using the rolling update (
ECS) deployment type. The deployment circuit breaker determines whether a service deployment will fail if the service can't reach a steady state. If you use the deployment circuit breaker, a service deployment will transition to a failed state and stop launching new tasks. If you use the rollback option, when a service deployment fails, the service is rolled back to the last deployment that completed successfully. For more information, see Rolling update in the Amazon Elastic Container Service Developer Guide The deployment circuit breaker can only be used for services using the rolling update (ECS) deployment type. The deployment circuit breaker determines whether a service deployment will fail if the service can't reach a steady state. If it is turned on, a service deployment will transition to a failed state and stop launching new tasks. You can also configure Amazon ECS to roll back your service to the last completed deployment after a failure. For more information, see Rolling update in the Amazon Elastic Container Service Developer Guide. For more information about API failure reasons, see API failure reasons in the Amazon Elastic Container Service Developer Guide. - maximum
Percent Integer - If a service is using the rolling update (
ECS) deployment type, themaximumPercentparameter represents an upper limit on the number of your service's tasks that are allowed in theRUNNINGorPENDINGstate during a deployment, as a percentage of thedesiredCount(rounded down to the nearest integer). This parameter enables you to define the deployment batch size. For example, if your service is using theREPLICAservice scheduler and has adesiredCountof four tasks and amaximumPercentvalue of 200%, the scheduler may start four new tasks before stopping the four older tasks (provided that the cluster resources required to do this are available). The defaultmaximumPercentvalue for a service using theREPLICAservice scheduler is 200%. If a service is using either the blue/green (CODE_DEPLOY) orEXTERNALdeployment types and tasks that use the EC2 launch type, the maximum percent value is set to the default value and is used to define the upper limit on the number of the tasks in the service that remain in theRUNNINGstate while the container instances are in theDRAININGstate. If the tasks in the service use the Fargate launch type, the maximum percent value is not used, although it is returned when describing your service. - minimum
Healthy IntegerPercent - If a service is using the rolling update (
ECS) deployment type, theminimumHealthyPercentrepresents a lower limit on the number of your service's tasks that must remain in theRUNNINGstate during a deployment, as a percentage of thedesiredCount(rounded up to the nearest integer). This parameter enables you to deploy without using additional cluster capacity. For example, if your service has adesiredCountof four tasks and aminimumHealthyPercentof 50%, the service scheduler may stop two existing tasks to free up cluster capacity before starting two new tasks. For services that do not use a load balancer, the following should be noted: + A service is considered healthy if all essential containers within the tasks in the service pass their health checks. + If a task has no essential containers with a health check defined, the service scheduler will wait for 40 seconds after a task reaches aRUNNINGstate before the task is counted towards the minimum healthy percent total. + If a task has one or more essential containers with a health check defined, the service scheduler will wait for the task to reach a healthy status before counting it towards the minimum healthy percent total. A task is considered healthy when all essential containers within the task have passed their health checks. The amount of time the service scheduler can wait for is determined by the container health check settings. For services that do use a load balancer, the following should be noted: + If a task has no essential containers with a health check defined, the service scheduler will wait for the load balancer target group health check to return a healthy status before counting the task towards the minimum healthy percent total. + If a task has an essential container with a health check defined, the service scheduler will wait for both the task to reach a healthy status and the load balancer target group health check to return a healthy status before counting the task towards the minimum healthy percent total. If a service is using either the blue/green (CODE_DEPLOY) orEXTERNALdeployment types and is running tasks that use the EC2 launch type, the minimum healthy percent value is set to the default value and is used to define the lower limit on the number of the tasks in the service that remain in theRUNNINGstate while the container instances are in theDRAININGstate. If a service is using either the blue/green (CODE_DEPLOY) orEXTERNALdeployment types and is running tasks that use the Fargate launch type, the minimum healthy percent value is not used, although it is returned when describing your service.
- alarms
Deployment
Alarms - Information about the CloudWatch alarms. One of the methods which provide a way for you to quickly identify when a deployment has failed, and then to optionally roll back the failure to the last working deployment. When the alarms are generated, Amazon ECS sets the service deployment to failed. Set the rollback parameter to have Amazon ECS to roll back your service to the last completed deployment after a failure. You can only use the
DeploymentAlarmsmethod to detect failures when theDeploymentControlleris set toECS(rolling update). For more information, see Rolling update in the Amazon Elastic Container Service Developer Guide. - deployment
Circuit DeploymentBreaker Circuit Breaker - The deployment circuit breaker can only be used for services using the rolling update (
ECS) deployment type. The deployment circuit breaker determines whether a service deployment will fail if the service can't reach a steady state. If you use the deployment circuit breaker, a service deployment will transition to a failed state and stop launching new tasks. If you use the rollback option, when a service deployment fails, the service is rolled back to the last deployment that completed successfully. For more information, see Rolling update in the Amazon Elastic Container Service Developer Guide The deployment circuit breaker can only be used for services using the rolling update (ECS) deployment type. The deployment circuit breaker determines whether a service deployment will fail if the service can't reach a steady state. If it is turned on, a service deployment will transition to a failed state and stop launching new tasks. You can also configure Amazon ECS to roll back your service to the last completed deployment after a failure. For more information, see Rolling update in the Amazon Elastic Container Service Developer Guide. For more information about API failure reasons, see API failure reasons in the Amazon Elastic Container Service Developer Guide. - maximum
Percent number - If a service is using the rolling update (
ECS) deployment type, themaximumPercentparameter represents an upper limit on the number of your service's tasks that are allowed in theRUNNINGorPENDINGstate during a deployment, as a percentage of thedesiredCount(rounded down to the nearest integer). This parameter enables you to define the deployment batch size. For example, if your service is using theREPLICAservice scheduler and has adesiredCountof four tasks and amaximumPercentvalue of 200%, the scheduler may start four new tasks before stopping the four older tasks (provided that the cluster resources required to do this are available). The defaultmaximumPercentvalue for a service using theREPLICAservice scheduler is 200%. If a service is using either the blue/green (CODE_DEPLOY) orEXTERNALdeployment types and tasks that use the EC2 launch type, the maximum percent value is set to the default value and is used to define the upper limit on the number of the tasks in the service that remain in theRUNNINGstate while the container instances are in theDRAININGstate. If the tasks in the service use the Fargate launch type, the maximum percent value is not used, although it is returned when describing your service. - minimum
Healthy numberPercent - If a service is using the rolling update (
ECS) deployment type, theminimumHealthyPercentrepresents a lower limit on the number of your service's tasks that must remain in theRUNNINGstate during a deployment, as a percentage of thedesiredCount(rounded up to the nearest integer). This parameter enables you to deploy without using additional cluster capacity. For example, if your service has adesiredCountof four tasks and aminimumHealthyPercentof 50%, the service scheduler may stop two existing tasks to free up cluster capacity before starting two new tasks. For services that do not use a load balancer, the following should be noted: + A service is considered healthy if all essential containers within the tasks in the service pass their health checks. + If a task has no essential containers with a health check defined, the service scheduler will wait for 40 seconds after a task reaches aRUNNINGstate before the task is counted towards the minimum healthy percent total. + If a task has one or more essential containers with a health check defined, the service scheduler will wait for the task to reach a healthy status before counting it towards the minimum healthy percent total. A task is considered healthy when all essential containers within the task have passed their health checks. The amount of time the service scheduler can wait for is determined by the container health check settings. For services that do use a load balancer, the following should be noted: + If a task has no essential containers with a health check defined, the service scheduler will wait for the load balancer target group health check to return a healthy status before counting the task towards the minimum healthy percent total. + If a task has an essential container with a health check defined, the service scheduler will wait for both the task to reach a healthy status and the load balancer target group health check to return a healthy status before counting the task towards the minimum healthy percent total. If a service is using either the blue/green (CODE_DEPLOY) orEXTERNALdeployment types and is running tasks that use the EC2 launch type, the minimum healthy percent value is set to the default value and is used to define the lower limit on the number of the tasks in the service that remain in theRUNNINGstate while the container instances are in theDRAININGstate. If a service is using either the blue/green (CODE_DEPLOY) orEXTERNALdeployment types and is running tasks that use the Fargate launch type, the minimum healthy percent value is not used, although it is returned when describing your service.
- alarms
Deployment
Alarms - Information about the CloudWatch alarms. One of the methods which provide a way for you to quickly identify when a deployment has failed, and then to optionally roll back the failure to the last working deployment. When the alarms are generated, Amazon ECS sets the service deployment to failed. Set the rollback parameter to have Amazon ECS to roll back your service to the last completed deployment after a failure. You can only use the
DeploymentAlarmsmethod to detect failures when theDeploymentControlleris set toECS(rolling update). For more information, see Rolling update in the Amazon Elastic Container Service Developer Guide. - deployment_
circuit_ Deploymentbreaker Circuit Breaker - The deployment circuit breaker can only be used for services using the rolling update (
ECS) deployment type. The deployment circuit breaker determines whether a service deployment will fail if the service can't reach a steady state. If you use the deployment circuit breaker, a service deployment will transition to a failed state and stop launching new tasks. If you use the rollback option, when a service deployment fails, the service is rolled back to the last deployment that completed successfully. For more information, see Rolling update in the Amazon Elastic Container Service Developer Guide The deployment circuit breaker can only be used for services using the rolling update (ECS) deployment type. The deployment circuit breaker determines whether a service deployment will fail if the service can't reach a steady state. If it is turned on, a service deployment will transition to a failed state and stop launching new tasks. You can also configure Amazon ECS to roll back your service to the last completed deployment after a failure. For more information, see Rolling update in the Amazon Elastic Container Service Developer Guide. For more information about API failure reasons, see API failure reasons in the Amazon Elastic Container Service Developer Guide. - maximum_
percent int - If a service is using the rolling update (
ECS) deployment type, themaximumPercentparameter represents an upper limit on the number of your service's tasks that are allowed in theRUNNINGorPENDINGstate during a deployment, as a percentage of thedesiredCount(rounded down to the nearest integer). This parameter enables you to define the deployment batch size. For example, if your service is using theREPLICAservice scheduler and has adesiredCountof four tasks and amaximumPercentvalue of 200%, the scheduler may start four new tasks before stopping the four older tasks (provided that the cluster resources required to do this are available). The defaultmaximumPercentvalue for a service using theREPLICAservice scheduler is 200%. If a service is using either the blue/green (CODE_DEPLOY) orEXTERNALdeployment types and tasks that use the EC2 launch type, the maximum percent value is set to the default value and is used to define the upper limit on the number of the tasks in the service that remain in theRUNNINGstate while the container instances are in theDRAININGstate. If the tasks in the service use the Fargate launch type, the maximum percent value is not used, although it is returned when describing your service. - minimum_
healthy_ intpercent - If a service is using the rolling update (
ECS) deployment type, theminimumHealthyPercentrepresents a lower limit on the number of your service's tasks that must remain in theRUNNINGstate during a deployment, as a percentage of thedesiredCount(rounded up to the nearest integer). This parameter enables you to deploy without using additional cluster capacity. For example, if your service has adesiredCountof four tasks and aminimumHealthyPercentof 50%, the service scheduler may stop two existing tasks to free up cluster capacity before starting two new tasks. For services that do not use a load balancer, the following should be noted: + A service is considered healthy if all essential containers within the tasks in the service pass their health checks. + If a task has no essential containers with a health check defined, the service scheduler will wait for 40 seconds after a task reaches aRUNNINGstate before the task is counted towards the minimum healthy percent total. + If a task has one or more essential containers with a health check defined, the service scheduler will wait for the task to reach a healthy status before counting it towards the minimum healthy percent total. A task is considered healthy when all essential containers within the task have passed their health checks. The amount of time the service scheduler can wait for is determined by the container health check settings. For services that do use a load balancer, the following should be noted: + If a task has no essential containers with a health check defined, the service scheduler will wait for the load balancer target group health check to return a healthy status before counting the task towards the minimum healthy percent total. + If a task has an essential container with a health check defined, the service scheduler will wait for both the task to reach a healthy status and the load balancer target group health check to return a healthy status before counting the task towards the minimum healthy percent total. If a service is using either the blue/green (CODE_DEPLOY) orEXTERNALdeployment types and is running tasks that use the EC2 launch type, the minimum healthy percent value is set to the default value and is used to define the lower limit on the number of the tasks in the service that remain in theRUNNINGstate while the container instances are in theDRAININGstate. If a service is using either the blue/green (CODE_DEPLOY) orEXTERNALdeployment types and is running tasks that use the Fargate launch type, the minimum healthy percent value is not used, although it is returned when describing your service.
- alarms Property Map
- Information about the CloudWatch alarms. One of the methods which provide a way for you to quickly identify when a deployment has failed, and then to optionally roll back the failure to the last working deployment. When the alarms are generated, Amazon ECS sets the service deployment to failed. Set the rollback parameter to have Amazon ECS to roll back your service to the last completed deployment after a failure. You can only use the
DeploymentAlarmsmethod to detect failures when theDeploymentControlleris set toECS(rolling update). For more information, see Rolling update in the Amazon Elastic Container Service Developer Guide. - deployment
Circuit Property MapBreaker - The deployment circuit breaker can only be used for services using the rolling update (
ECS) deployment type. The deployment circuit breaker determines whether a service deployment will fail if the service can't reach a steady state. If you use the deployment circuit breaker, a service deployment will transition to a failed state and stop launching new tasks. If you use the rollback option, when a service deployment fails, the service is rolled back to the last deployment that completed successfully. For more information, see Rolling update in the Amazon Elastic Container Service Developer Guide The deployment circuit breaker can only be used for services using the rolling update (ECS) deployment type. The deployment circuit breaker determines whether a service deployment will fail if the service can't reach a steady state. If it is turned on, a service deployment will transition to a failed state and stop launching new tasks. You can also configure Amazon ECS to roll back your service to the last completed deployment after a failure. For more information, see Rolling update in the Amazon Elastic Container Service Developer Guide. For more information about API failure reasons, see API failure reasons in the Amazon Elastic Container Service Developer Guide. - maximum
Percent Number - If a service is using the rolling update (
ECS) deployment type, themaximumPercentparameter represents an upper limit on the number of your service's tasks that are allowed in theRUNNINGorPENDINGstate during a deployment, as a percentage of thedesiredCount(rounded down to the nearest integer). This parameter enables you to define the deployment batch size. For example, if your service is using theREPLICAservice scheduler and has adesiredCountof four tasks and amaximumPercentvalue of 200%, the scheduler may start four new tasks before stopping the four older tasks (provided that the cluster resources required to do this are available). The defaultmaximumPercentvalue for a service using theREPLICAservice scheduler is 200%. If a service is using either the blue/green (CODE_DEPLOY) orEXTERNALdeployment types and tasks that use the EC2 launch type, the maximum percent value is set to the default value and is used to define the upper limit on the number of the tasks in the service that remain in theRUNNINGstate while the container instances are in theDRAININGstate. If the tasks in the service use the Fargate launch type, the maximum percent value is not used, although it is returned when describing your service. - minimum
Healthy NumberPercent - If a service is using the rolling update (
ECS) deployment type, theminimumHealthyPercentrepresents a lower limit on the number of your service's tasks that must remain in theRUNNINGstate during a deployment, as a percentage of thedesiredCount(rounded up to the nearest integer). This parameter enables you to deploy without using additional cluster capacity. For example, if your service has adesiredCountof four tasks and aminimumHealthyPercentof 50%, the service scheduler may stop two existing tasks to free up cluster capacity before starting two new tasks. For services that do not use a load balancer, the following should be noted: + A service is considered healthy if all essential containers within the tasks in the service pass their health checks. + If a task has no essential containers with a health check defined, the service scheduler will wait for 40 seconds after a task reaches aRUNNINGstate before the task is counted towards the minimum healthy percent total. + If a task has one or more essential containers with a health check defined, the service scheduler will wait for the task to reach a healthy status before counting it towards the minimum healthy percent total. A task is considered healthy when all essential containers within the task have passed their health checks. The amount of time the service scheduler can wait for is determined by the container health check settings. For services that do use a load balancer, the following should be noted: + If a task has no essential containers with a health check defined, the service scheduler will wait for the load balancer target group health check to return a healthy status before counting the task towards the minimum healthy percent total. + If a task has an essential container with a health check defined, the service scheduler will wait for both the task to reach a healthy status and the load balancer target group health check to return a healthy status before counting the task towards the minimum healthy percent total. If a service is using either the blue/green (CODE_DEPLOY) orEXTERNALdeployment types and is running tasks that use the EC2 launch type, the minimum healthy percent value is set to the default value and is used to define the lower limit on the number of the tasks in the service that remain in theRUNNINGstate while the container instances are in theDRAININGstate. If a service is using either the blue/green (CODE_DEPLOY) orEXTERNALdeployment types and is running tasks that use the Fargate launch type, the minimum healthy percent value is not used, although it is returned when describing your service.
DeploymentConfigurationResponse, DeploymentConfigurationResponseArgs
, DeploymentConfigurationResponseArgs
- Alarms
Pulumi.
Azure Native. Aws Connector. Inputs. Deployment Alarms Response - Information about the CloudWatch alarms. One of the methods which provide a way for you to quickly identify when a deployment has failed, and then to optionally roll back the failure to the last working deployment. When the alarms are generated, Amazon ECS sets the service deployment to failed. Set the rollback parameter to have Amazon ECS to roll back your service to the last completed deployment after a failure. You can only use the
DeploymentAlarmsmethod to detect failures when theDeploymentControlleris set toECS(rolling update). For more information, see Rolling update in the Amazon Elastic Container Service Developer Guide. - Deployment
Circuit Pulumi.Breaker Azure Native. Aws Connector. Inputs. Deployment Circuit Breaker Response - The deployment circuit breaker can only be used for services using the rolling update (
ECS) deployment type. The deployment circuit breaker determines whether a service deployment will fail if the service can't reach a steady state. If you use the deployment circuit breaker, a service deployment will transition to a failed state and stop launching new tasks. If you use the rollback option, when a service deployment fails, the service is rolled back to the last deployment that completed successfully. For more information, see Rolling update in the Amazon Elastic Container Service Developer Guide The deployment circuit breaker can only be used for services using the rolling update (ECS) deployment type. The deployment circuit breaker determines whether a service deployment will fail if the service can't reach a steady state. If it is turned on, a service deployment will transition to a failed state and stop launching new tasks. You can also configure Amazon ECS to roll back your service to the last completed deployment after a failure. For more information, see Rolling update in the Amazon Elastic Container Service Developer Guide. For more information about API failure reasons, see API failure reasons in the Amazon Elastic Container Service Developer Guide. - Maximum
Percent int - If a service is using the rolling update (
ECS) deployment type, themaximumPercentparameter represents an upper limit on the number of your service's tasks that are allowed in theRUNNINGorPENDINGstate during a deployment, as a percentage of thedesiredCount(rounded down to the nearest integer). This parameter enables you to define the deployment batch size. For example, if your service is using theREPLICAservice scheduler and has adesiredCountof four tasks and amaximumPercentvalue of 200%, the scheduler may start four new tasks before stopping the four older tasks (provided that the cluster resources required to do this are available). The defaultmaximumPercentvalue for a service using theREPLICAservice scheduler is 200%. If a service is using either the blue/green (CODE_DEPLOY) orEXTERNALdeployment types and tasks that use the EC2 launch type, the maximum percent value is set to the default value and is used to define the upper limit on the number of the tasks in the service that remain in theRUNNINGstate while the container instances are in theDRAININGstate. If the tasks in the service use the Fargate launch type, the maximum percent value is not used, although it is returned when describing your service. - Minimum
Healthy intPercent - If a service is using the rolling update (
ECS) deployment type, theminimumHealthyPercentrepresents a lower limit on the number of your service's tasks that must remain in theRUNNINGstate during a deployment, as a percentage of thedesiredCount(rounded up to the nearest integer). This parameter enables you to deploy without using additional cluster capacity. For example, if your service has adesiredCountof four tasks and aminimumHealthyPercentof 50%, the service scheduler may stop two existing tasks to free up cluster capacity before starting two new tasks. For services that do not use a load balancer, the following should be noted: + A service is considered healthy if all essential containers within the tasks in the service pass their health checks. + If a task has no essential containers with a health check defined, the service scheduler will wait for 40 seconds after a task reaches aRUNNINGstate before the task is counted towards the minimum healthy percent total. + If a task has one or more essential containers with a health check defined, the service scheduler will wait for the task to reach a healthy status before counting it towards the minimum healthy percent total. A task is considered healthy when all essential containers within the task have passed their health checks. The amount of time the service scheduler can wait for is determined by the container health check settings. For services that do use a load balancer, the following should be noted: + If a task has no essential containers with a health check defined, the service scheduler will wait for the load balancer target group health check to return a healthy status before counting the task towards the minimum healthy percent total. + If a task has an essential container with a health check defined, the service scheduler will wait for both the task to reach a healthy status and the load balancer target group health check to return a healthy status before counting the task towards the minimum healthy percent total. If a service is using either the blue/green (CODE_DEPLOY) orEXTERNALdeployment types and is running tasks that use the EC2 launch type, the minimum healthy percent value is set to the default value and is used to define the lower limit on the number of the tasks in the service that remain in theRUNNINGstate while the container instances are in theDRAININGstate. If a service is using either the blue/green (CODE_DEPLOY) orEXTERNALdeployment types and is running tasks that use the Fargate launch type, the minimum healthy percent value is not used, although it is returned when describing your service.
- Alarms
Deployment
Alarms Response - Information about the CloudWatch alarms. One of the methods which provide a way for you to quickly identify when a deployment has failed, and then to optionally roll back the failure to the last working deployment. When the alarms are generated, Amazon ECS sets the service deployment to failed. Set the rollback parameter to have Amazon ECS to roll back your service to the last completed deployment after a failure. You can only use the
DeploymentAlarmsmethod to detect failures when theDeploymentControlleris set toECS(rolling update). For more information, see Rolling update in the Amazon Elastic Container Service Developer Guide. - Deployment
Circuit DeploymentBreaker Circuit Breaker Response - The deployment circuit breaker can only be used for services using the rolling update (
ECS) deployment type. The deployment circuit breaker determines whether a service deployment will fail if the service can't reach a steady state. If you use the deployment circuit breaker, a service deployment will transition to a failed state and stop launching new tasks. If you use the rollback option, when a service deployment fails, the service is rolled back to the last deployment that completed successfully. For more information, see Rolling update in the Amazon Elastic Container Service Developer Guide The deployment circuit breaker can only be used for services using the rolling update (ECS) deployment type. The deployment circuit breaker determines whether a service deployment will fail if the service can't reach a steady state. If it is turned on, a service deployment will transition to a failed state and stop launching new tasks. You can also configure Amazon ECS to roll back your service to the last completed deployment after a failure. For more information, see Rolling update in the Amazon Elastic Container Service Developer Guide. For more information about API failure reasons, see API failure reasons in the Amazon Elastic Container Service Developer Guide. - Maximum
Percent int - If a service is using the rolling update (
ECS) deployment type, themaximumPercentparameter represents an upper limit on the number of your service's tasks that are allowed in theRUNNINGorPENDINGstate during a deployment, as a percentage of thedesiredCount(rounded down to the nearest integer). This parameter enables you to define the deployment batch size. For example, if your service is using theREPLICAservice scheduler and has adesiredCountof four tasks and amaximumPercentvalue of 200%, the scheduler may start four new tasks before stopping the four older tasks (provided that the cluster resources required to do this are available). The defaultmaximumPercentvalue for a service using theREPLICAservice scheduler is 200%. If a service is using either the blue/green (CODE_DEPLOY) orEXTERNALdeployment types and tasks that use the EC2 launch type, the maximum percent value is set to the default value and is used to define the upper limit on the number of the tasks in the service that remain in theRUNNINGstate while the container instances are in theDRAININGstate. If the tasks in the service use the Fargate launch type, the maximum percent value is not used, although it is returned when describing your service. - Minimum
Healthy intPercent - If a service is using the rolling update (
ECS) deployment type, theminimumHealthyPercentrepresents a lower limit on the number of your service's tasks that must remain in theRUNNINGstate during a deployment, as a percentage of thedesiredCount(rounded up to the nearest integer). This parameter enables you to deploy without using additional cluster capacity. For example, if your service has adesiredCountof four tasks and aminimumHealthyPercentof 50%, the service scheduler may stop two existing tasks to free up cluster capacity before starting two new tasks. For services that do not use a load balancer, the following should be noted: + A service is considered healthy if all essential containers within the tasks in the service pass their health checks. + If a task has no essential containers with a health check defined, the service scheduler will wait for 40 seconds after a task reaches aRUNNINGstate before the task is counted towards the minimum healthy percent total. + If a task has one or more essential containers with a health check defined, the service scheduler will wait for the task to reach a healthy status before counting it towards the minimum healthy percent total. A task is considered healthy when all essential containers within the task have passed their health checks. The amount of time the service scheduler can wait for is determined by the container health check settings. For services that do use a load balancer, the following should be noted: + If a task has no essential containers with a health check defined, the service scheduler will wait for the load balancer target group health check to return a healthy status before counting the task towards the minimum healthy percent total. + If a task has an essential container with a health check defined, the service scheduler will wait for both the task to reach a healthy status and the load balancer target group health check to return a healthy status before counting the task towards the minimum healthy percent total. If a service is using either the blue/green (CODE_DEPLOY) orEXTERNALdeployment types and is running tasks that use the EC2 launch type, the minimum healthy percent value is set to the default value and is used to define the lower limit on the number of the tasks in the service that remain in theRUNNINGstate while the container instances are in theDRAININGstate. If a service is using either the blue/green (CODE_DEPLOY) orEXTERNALdeployment types and is running tasks that use the Fargate launch type, the minimum healthy percent value is not used, although it is returned when describing your service.
- alarms
Deployment
Alarms Response - Information about the CloudWatch alarms. One of the methods which provide a way for you to quickly identify when a deployment has failed, and then to optionally roll back the failure to the last working deployment. When the alarms are generated, Amazon ECS sets the service deployment to failed. Set the rollback parameter to have Amazon ECS to roll back your service to the last completed deployment after a failure. You can only use the
DeploymentAlarmsmethod to detect failures when theDeploymentControlleris set toECS(rolling update). For more information, see Rolling update in the Amazon Elastic Container Service Developer Guide. - deployment
Circuit DeploymentBreaker Circuit Breaker Response - The deployment circuit breaker can only be used for services using the rolling update (
ECS) deployment type. The deployment circuit breaker determines whether a service deployment will fail if the service can't reach a steady state. If you use the deployment circuit breaker, a service deployment will transition to a failed state and stop launching new tasks. If you use the rollback option, when a service deployment fails, the service is rolled back to the last deployment that completed successfully. For more information, see Rolling update in the Amazon Elastic Container Service Developer Guide The deployment circuit breaker can only be used for services using the rolling update (ECS) deployment type. The deployment circuit breaker determines whether a service deployment will fail if the service can't reach a steady state. If it is turned on, a service deployment will transition to a failed state and stop launching new tasks. You can also configure Amazon ECS to roll back your service to the last completed deployment after a failure. For more information, see Rolling update in the Amazon Elastic Container Service Developer Guide. For more information about API failure reasons, see API failure reasons in the Amazon Elastic Container Service Developer Guide. - maximum
Percent Integer - If a service is using the rolling update (
ECS) deployment type, themaximumPercentparameter represents an upper limit on the number of your service's tasks that are allowed in theRUNNINGorPENDINGstate during a deployment, as a percentage of thedesiredCount(rounded down to the nearest integer). This parameter enables you to define the deployment batch size. For example, if your service is using theREPLICAservice scheduler and has adesiredCountof four tasks and amaximumPercentvalue of 200%, the scheduler may start four new tasks before stopping the four older tasks (provided that the cluster resources required to do this are available). The defaultmaximumPercentvalue for a service using theREPLICAservice scheduler is 200%. If a service is using either the blue/green (CODE_DEPLOY) orEXTERNALdeployment types and tasks that use the EC2 launch type, the maximum percent value is set to the default value and is used to define the upper limit on the number of the tasks in the service that remain in theRUNNINGstate while the container instances are in theDRAININGstate. If the tasks in the service use the Fargate launch type, the maximum percent value is not used, although it is returned when describing your service. - minimum
Healthy IntegerPercent - If a service is using the rolling update (
ECS) deployment type, theminimumHealthyPercentrepresents a lower limit on the number of your service's tasks that must remain in theRUNNINGstate during a deployment, as a percentage of thedesiredCount(rounded up to the nearest integer). This parameter enables you to deploy without using additional cluster capacity. For example, if your service has adesiredCountof four tasks and aminimumHealthyPercentof 50%, the service scheduler may stop two existing tasks to free up cluster capacity before starting two new tasks. For services that do not use a load balancer, the following should be noted: + A service is considered healthy if all essential containers within the tasks in the service pass their health checks. + If a task has no essential containers with a health check defined, the service scheduler will wait for 40 seconds after a task reaches aRUNNINGstate before the task is counted towards the minimum healthy percent total. + If a task has one or more essential containers with a health check defined, the service scheduler will wait for the task to reach a healthy status before counting it towards the minimum healthy percent total. A task is considered healthy when all essential containers within the task have passed their health checks. The amount of time the service scheduler can wait for is determined by the container health check settings. For services that do use a load balancer, the following should be noted: + If a task has no essential containers with a health check defined, the service scheduler will wait for the load balancer target group health check to return a healthy status before counting the task towards the minimum healthy percent total. + If a task has an essential container with a health check defined, the service scheduler will wait for both the task to reach a healthy status and the load balancer target group health check to return a healthy status before counting the task towards the minimum healthy percent total. If a service is using either the blue/green (CODE_DEPLOY) orEXTERNALdeployment types and is running tasks that use the EC2 launch type, the minimum healthy percent value is set to the default value and is used to define the lower limit on the number of the tasks in the service that remain in theRUNNINGstate while the container instances are in theDRAININGstate. If a service is using either the blue/green (CODE_DEPLOY) orEXTERNALdeployment types and is running tasks that use the Fargate launch type, the minimum healthy percent value is not used, although it is returned when describing your service.
- alarms
Deployment
Alarms Response - Information about the CloudWatch alarms. One of the methods which provide a way for you to quickly identify when a deployment has failed, and then to optionally roll back the failure to the last working deployment. When the alarms are generated, Amazon ECS sets the service deployment to failed. Set the rollback parameter to have Amazon ECS to roll back your service to the last completed deployment after a failure. You can only use the
DeploymentAlarmsmethod to detect failures when theDeploymentControlleris set toECS(rolling update). For more information, see Rolling update in the Amazon Elastic Container Service Developer Guide. - deployment
Circuit DeploymentBreaker Circuit Breaker Response - The deployment circuit breaker can only be used for services using the rolling update (
ECS) deployment type. The deployment circuit breaker determines whether a service deployment will fail if the service can't reach a steady state. If you use the deployment circuit breaker, a service deployment will transition to a failed state and stop launching new tasks. If you use the rollback option, when a service deployment fails, the service is rolled back to the last deployment that completed successfully. For more information, see Rolling update in the Amazon Elastic Container Service Developer Guide The deployment circuit breaker can only be used for services using the rolling update (ECS) deployment type. The deployment circuit breaker determines whether a service deployment will fail if the service can't reach a steady state. If it is turned on, a service deployment will transition to a failed state and stop launching new tasks. You can also configure Amazon ECS to roll back your service to the last completed deployment after a failure. For more information, see Rolling update in the Amazon Elastic Container Service Developer Guide. For more information about API failure reasons, see API failure reasons in the Amazon Elastic Container Service Developer Guide. - maximum
Percent number - If a service is using the rolling update (
ECS) deployment type, themaximumPercentparameter represents an upper limit on the number of your service's tasks that are allowed in theRUNNINGorPENDINGstate during a deployment, as a percentage of thedesiredCount(rounded down to the nearest integer). This parameter enables you to define the deployment batch size. For example, if your service is using theREPLICAservice scheduler and has adesiredCountof four tasks and amaximumPercentvalue of 200%, the scheduler may start four new tasks before stopping the four older tasks (provided that the cluster resources required to do this are available). The defaultmaximumPercentvalue for a service using theREPLICAservice scheduler is 200%. If a service is using either the blue/green (CODE_DEPLOY) orEXTERNALdeployment types and tasks that use the EC2 launch type, the maximum percent value is set to the default value and is used to define the upper limit on the number of the tasks in the service that remain in theRUNNINGstate while the container instances are in theDRAININGstate. If the tasks in the service use the Fargate launch type, the maximum percent value is not used, although it is returned when describing your service. - minimum
Healthy numberPercent - If a service is using the rolling update (
ECS) deployment type, theminimumHealthyPercentrepresents a lower limit on the number of your service's tasks that must remain in theRUNNINGstate during a deployment, as a percentage of thedesiredCount(rounded up to the nearest integer). This parameter enables you to deploy without using additional cluster capacity. For example, if your service has adesiredCountof four tasks and aminimumHealthyPercentof 50%, the service scheduler may stop two existing tasks to free up cluster capacity before starting two new tasks. For services that do not use a load balancer, the following should be noted: + A service is considered healthy if all essential containers within the tasks in the service pass their health checks. + If a task has no essential containers with a health check defined, the service scheduler will wait for 40 seconds after a task reaches aRUNNINGstate before the task is counted towards the minimum healthy percent total. + If a task has one or more essential containers with a health check defined, the service scheduler will wait for the task to reach a healthy status before counting it towards the minimum healthy percent total. A task is considered healthy when all essential containers within the task have passed their health checks. The amount of time the service scheduler can wait for is determined by the container health check settings. For services that do use a load balancer, the following should be noted: + If a task has no essential containers with a health check defined, the service scheduler will wait for the load balancer target group health check to return a healthy status before counting the task towards the minimum healthy percent total. + If a task has an essential container with a health check defined, the service scheduler will wait for both the task to reach a healthy status and the load balancer target group health check to return a healthy status before counting the task towards the minimum healthy percent total. If a service is using either the blue/green (CODE_DEPLOY) orEXTERNALdeployment types and is running tasks that use the EC2 launch type, the minimum healthy percent value is set to the default value and is used to define the lower limit on the number of the tasks in the service that remain in theRUNNINGstate while the container instances are in theDRAININGstate. If a service is using either the blue/green (CODE_DEPLOY) orEXTERNALdeployment types and is running tasks that use the Fargate launch type, the minimum healthy percent value is not used, although it is returned when describing your service.
- alarms
Deployment
Alarms Response - Information about the CloudWatch alarms. One of the methods which provide a way for you to quickly identify when a deployment has failed, and then to optionally roll back the failure to the last working deployment. When the alarms are generated, Amazon ECS sets the service deployment to failed. Set the rollback parameter to have Amazon ECS to roll back your service to the last completed deployment after a failure. You can only use the
DeploymentAlarmsmethod to detect failures when theDeploymentControlleris set toECS(rolling update). For more information, see Rolling update in the Amazon Elastic Container Service Developer Guide. - deployment_
circuit_ Deploymentbreaker Circuit Breaker Response - The deployment circuit breaker can only be used for services using the rolling update (
ECS) deployment type. The deployment circuit breaker determines whether a service deployment will fail if the service can't reach a steady state. If you use the deployment circuit breaker, a service deployment will transition to a failed state and stop launching new tasks. If you use the rollback option, when a service deployment fails, the service is rolled back to the last deployment that completed successfully. For more information, see Rolling update in the Amazon Elastic Container Service Developer Guide The deployment circuit breaker can only be used for services using the rolling update (ECS) deployment type. The deployment circuit breaker determines whether a service deployment will fail if the service can't reach a steady state. If it is turned on, a service deployment will transition to a failed state and stop launching new tasks. You can also configure Amazon ECS to roll back your service to the last completed deployment after a failure. For more information, see Rolling update in the Amazon Elastic Container Service Developer Guide. For more information about API failure reasons, see API failure reasons in the Amazon Elastic Container Service Developer Guide. - maximum_
percent int - If a service is using the rolling update (
ECS) deployment type, themaximumPercentparameter represents an upper limit on the number of your service's tasks that are allowed in theRUNNINGorPENDINGstate during a deployment, as a percentage of thedesiredCount(rounded down to the nearest integer). This parameter enables you to define the deployment batch size. For example, if your service is using theREPLICAservice scheduler and has adesiredCountof four tasks and amaximumPercentvalue of 200%, the scheduler may start four new tasks before stopping the four older tasks (provided that the cluster resources required to do this are available). The defaultmaximumPercentvalue for a service using theREPLICAservice scheduler is 200%. If a service is using either the blue/green (CODE_DEPLOY) orEXTERNALdeployment types and tasks that use the EC2 launch type, the maximum percent value is set to the default value and is used to define the upper limit on the number of the tasks in the service that remain in theRUNNINGstate while the container instances are in theDRAININGstate. If the tasks in the service use the Fargate launch type, the maximum percent value is not used, although it is returned when describing your service. - minimum_
healthy_ intpercent - If a service is using the rolling update (
ECS) deployment type, theminimumHealthyPercentrepresents a lower limit on the number of your service's tasks that must remain in theRUNNINGstate during a deployment, as a percentage of thedesiredCount(rounded up to the nearest integer). This parameter enables you to deploy without using additional cluster capacity. For example, if your service has adesiredCountof four tasks and aminimumHealthyPercentof 50%, the service scheduler may stop two existing tasks to free up cluster capacity before starting two new tasks. For services that do not use a load balancer, the following should be noted: + A service is considered healthy if all essential containers within the tasks in the service pass their health checks. + If a task has no essential containers with a health check defined, the service scheduler will wait for 40 seconds after a task reaches aRUNNINGstate before the task is counted towards the minimum healthy percent total. + If a task has one or more essential containers with a health check defined, the service scheduler will wait for the task to reach a healthy status before counting it towards the minimum healthy percent total. A task is considered healthy when all essential containers within the task have passed their health checks. The amount of time the service scheduler can wait for is determined by the container health check settings. For services that do use a load balancer, the following should be noted: + If a task has no essential containers with a health check defined, the service scheduler will wait for the load balancer target group health check to return a healthy status before counting the task towards the minimum healthy percent total. + If a task has an essential container with a health check defined, the service scheduler will wait for both the task to reach a healthy status and the load balancer target group health check to return a healthy status before counting the task towards the minimum healthy percent total. If a service is using either the blue/green (CODE_DEPLOY) orEXTERNALdeployment types and is running tasks that use the EC2 launch type, the minimum healthy percent value is set to the default value and is used to define the lower limit on the number of the tasks in the service that remain in theRUNNINGstate while the container instances are in theDRAININGstate. If a service is using either the blue/green (CODE_DEPLOY) orEXTERNALdeployment types and is running tasks that use the Fargate launch type, the minimum healthy percent value is not used, although it is returned when describing your service.
- alarms Property Map
- Information about the CloudWatch alarms. One of the methods which provide a way for you to quickly identify when a deployment has failed, and then to optionally roll back the failure to the last working deployment. When the alarms are generated, Amazon ECS sets the service deployment to failed. Set the rollback parameter to have Amazon ECS to roll back your service to the last completed deployment after a failure. You can only use the
DeploymentAlarmsmethod to detect failures when theDeploymentControlleris set toECS(rolling update). For more information, see Rolling update in the Amazon Elastic Container Service Developer Guide. - deployment
Circuit Property MapBreaker - The deployment circuit breaker can only be used for services using the rolling update (
ECS) deployment type. The deployment circuit breaker determines whether a service deployment will fail if the service can't reach a steady state. If you use the deployment circuit breaker, a service deployment will transition to a failed state and stop launching new tasks. If you use the rollback option, when a service deployment fails, the service is rolled back to the last deployment that completed successfully. For more information, see Rolling update in the Amazon Elastic Container Service Developer Guide The deployment circuit breaker can only be used for services using the rolling update (ECS) deployment type. The deployment circuit breaker determines whether a service deployment will fail if the service can't reach a steady state. If it is turned on, a service deployment will transition to a failed state and stop launching new tasks. You can also configure Amazon ECS to roll back your service to the last completed deployment after a failure. For more information, see Rolling update in the Amazon Elastic Container Service Developer Guide. For more information about API failure reasons, see API failure reasons in the Amazon Elastic Container Service Developer Guide. - maximum
Percent Number - If a service is using the rolling update (
ECS) deployment type, themaximumPercentparameter represents an upper limit on the number of your service's tasks that are allowed in theRUNNINGorPENDINGstate during a deployment, as a percentage of thedesiredCount(rounded down to the nearest integer). This parameter enables you to define the deployment batch size. For example, if your service is using theREPLICAservice scheduler and has adesiredCountof four tasks and amaximumPercentvalue of 200%, the scheduler may start four new tasks before stopping the four older tasks (provided that the cluster resources required to do this are available). The defaultmaximumPercentvalue for a service using theREPLICAservice scheduler is 200%. If a service is using either the blue/green (CODE_DEPLOY) orEXTERNALdeployment types and tasks that use the EC2 launch type, the maximum percent value is set to the default value and is used to define the upper limit on the number of the tasks in the service that remain in theRUNNINGstate while the container instances are in theDRAININGstate. If the tasks in the service use the Fargate launch type, the maximum percent value is not used, although it is returned when describing your service. - minimum
Healthy NumberPercent - If a service is using the rolling update (
ECS) deployment type, theminimumHealthyPercentrepresents a lower limit on the number of your service's tasks that must remain in theRUNNINGstate during a deployment, as a percentage of thedesiredCount(rounded up to the nearest integer). This parameter enables you to deploy without using additional cluster capacity. For example, if your service has adesiredCountof four tasks and aminimumHealthyPercentof 50%, the service scheduler may stop two existing tasks to free up cluster capacity before starting two new tasks. For services that do not use a load balancer, the following should be noted: + A service is considered healthy if all essential containers within the tasks in the service pass their health checks. + If a task has no essential containers with a health check defined, the service scheduler will wait for 40 seconds after a task reaches aRUNNINGstate before the task is counted towards the minimum healthy percent total. + If a task has one or more essential containers with a health check defined, the service scheduler will wait for the task to reach a healthy status before counting it towards the minimum healthy percent total. A task is considered healthy when all essential containers within the task have passed their health checks. The amount of time the service scheduler can wait for is determined by the container health check settings. For services that do use a load balancer, the following should be noted: + If a task has no essential containers with a health check defined, the service scheduler will wait for the load balancer target group health check to return a healthy status before counting the task towards the minimum healthy percent total. + If a task has an essential container with a health check defined, the service scheduler will wait for both the task to reach a healthy status and the load balancer target group health check to return a healthy status before counting the task towards the minimum healthy percent total. If a service is using either the blue/green (CODE_DEPLOY) orEXTERNALdeployment types and is running tasks that use the EC2 launch type, the minimum healthy percent value is set to the default value and is used to define the lower limit on the number of the tasks in the service that remain in theRUNNINGstate while the container instances are in theDRAININGstate. If a service is using either the blue/green (CODE_DEPLOY) orEXTERNALdeployment types and is running tasks that use the Fargate launch type, the minimum healthy percent value is not used, although it is returned when describing your service.
DeploymentController, DeploymentControllerArgs
, DeploymentControllerArgs
- Type
string | Pulumi.
Azure Native. Aws Connector. Deployment Controller Type - The deployment controller type to use. There are three deployment controller types available: + ECS The rolling update (ECS) deployment type involves replacing the current running version of the container with the latest version. The number of containers Amazon ECS adds or removes from the service during a rolling update is controlled by adjusting the minimum and maximum number of healthy tasks allowed during a service deployment, as specified in the DeploymentConfiguration. + CODE_DEPLOY The blue/green (CODE_DEPLOY) deployment type uses the blue/green deployment model powered by , which allows you to verify a new deployment of a service before sending production traffic to it. + EXTERNAL The external (EXTERNAL) deployment type enables you to use any third-party deployment controller for full control over the deployment process for an Amazon ECS service.
- Type
string | Deployment
Controller Type - The deployment controller type to use. There are three deployment controller types available: + ECS The rolling update (ECS) deployment type involves replacing the current running version of the container with the latest version. The number of containers Amazon ECS adds or removes from the service during a rolling update is controlled by adjusting the minimum and maximum number of healthy tasks allowed during a service deployment, as specified in the DeploymentConfiguration. + CODE_DEPLOY The blue/green (CODE_DEPLOY) deployment type uses the blue/green deployment model powered by , which allows you to verify a new deployment of a service before sending production traffic to it. + EXTERNAL The external (EXTERNAL) deployment type enables you to use any third-party deployment controller for full control over the deployment process for an Amazon ECS service.
- type
String | Deployment
Controller Type - The deployment controller type to use. There are three deployment controller types available: + ECS The rolling update (ECS) deployment type involves replacing the current running version of the container with the latest version. The number of containers Amazon ECS adds or removes from the service during a rolling update is controlled by adjusting the minimum and maximum number of healthy tasks allowed during a service deployment, as specified in the DeploymentConfiguration. + CODE_DEPLOY The blue/green (CODE_DEPLOY) deployment type uses the blue/green deployment model powered by , which allows you to verify a new deployment of a service before sending production traffic to it. + EXTERNAL The external (EXTERNAL) deployment type enables you to use any third-party deployment controller for full control over the deployment process for an Amazon ECS service.
- type
string | Deployment
Controller Type - The deployment controller type to use. There are three deployment controller types available: + ECS The rolling update (ECS) deployment type involves replacing the current running version of the container with the latest version. The number of containers Amazon ECS adds or removes from the service during a rolling update is controlled by adjusting the minimum and maximum number of healthy tasks allowed during a service deployment, as specified in the DeploymentConfiguration. + CODE_DEPLOY The blue/green (CODE_DEPLOY) deployment type uses the blue/green deployment model powered by , which allows you to verify a new deployment of a service before sending production traffic to it. + EXTERNAL The external (EXTERNAL) deployment type enables you to use any third-party deployment controller for full control over the deployment process for an Amazon ECS service.
- type
str | Deployment
Controller Type - The deployment controller type to use. There are three deployment controller types available: + ECS The rolling update (ECS) deployment type involves replacing the current running version of the container with the latest version. The number of containers Amazon ECS adds or removes from the service during a rolling update is controlled by adjusting the minimum and maximum number of healthy tasks allowed during a service deployment, as specified in the DeploymentConfiguration. + CODE_DEPLOY The blue/green (CODE_DEPLOY) deployment type uses the blue/green deployment model powered by , which allows you to verify a new deployment of a service before sending production traffic to it. + EXTERNAL The external (EXTERNAL) deployment type enables you to use any third-party deployment controller for full control over the deployment process for an Amazon ECS service.
- type String | "CODE_DEPLOY" | "ECS" | "EXTERNAL"
- The deployment controller type to use. There are three deployment controller types available: + ECS The rolling update (ECS) deployment type involves replacing the current running version of the container with the latest version. The number of containers Amazon ECS adds or removes from the service during a rolling update is controlled by adjusting the minimum and maximum number of healthy tasks allowed during a service deployment, as specified in the DeploymentConfiguration. + CODE_DEPLOY The blue/green (CODE_DEPLOY) deployment type uses the blue/green deployment model powered by , which allows you to verify a new deployment of a service before sending production traffic to it. + EXTERNAL The external (EXTERNAL) deployment type enables you to use any third-party deployment controller for full control over the deployment process for an Amazon ECS service.
DeploymentControllerResponse, DeploymentControllerResponseArgs
, DeploymentControllerResponseArgs
- Type string
- The deployment controller type to use. There are three deployment controller types available: + ECS The rolling update (ECS) deployment type involves replacing the current running version of the container with the latest version. The number of containers Amazon ECS adds or removes from the service during a rolling update is controlled by adjusting the minimum and maximum number of healthy tasks allowed during a service deployment, as specified in the DeploymentConfiguration. + CODE_DEPLOY The blue/green (CODE_DEPLOY) deployment type uses the blue/green deployment model powered by , which allows you to verify a new deployment of a service before sending production traffic to it. + EXTERNAL The external (EXTERNAL) deployment type enables you to use any third-party deployment controller for full control over the deployment process for an Amazon ECS service.
- Type string
- The deployment controller type to use. There are three deployment controller types available: + ECS The rolling update (ECS) deployment type involves replacing the current running version of the container with the latest version. The number of containers Amazon ECS adds or removes from the service during a rolling update is controlled by adjusting the minimum and maximum number of healthy tasks allowed during a service deployment, as specified in the DeploymentConfiguration. + CODE_DEPLOY The blue/green (CODE_DEPLOY) deployment type uses the blue/green deployment model powered by , which allows you to verify a new deployment of a service before sending production traffic to it. + EXTERNAL The external (EXTERNAL) deployment type enables you to use any third-party deployment controller for full control over the deployment process for an Amazon ECS service.
- type String
- The deployment controller type to use. There are three deployment controller types available: + ECS The rolling update (ECS) deployment type involves replacing the current running version of the container with the latest version. The number of containers Amazon ECS adds or removes from the service during a rolling update is controlled by adjusting the minimum and maximum number of healthy tasks allowed during a service deployment, as specified in the DeploymentConfiguration. + CODE_DEPLOY The blue/green (CODE_DEPLOY) deployment type uses the blue/green deployment model powered by , which allows you to verify a new deployment of a service before sending production traffic to it. + EXTERNAL The external (EXTERNAL) deployment type enables you to use any third-party deployment controller for full control over the deployment process for an Amazon ECS service.
- type string
- The deployment controller type to use. There are three deployment controller types available: + ECS The rolling update (ECS) deployment type involves replacing the current running version of the container with the latest version. The number of containers Amazon ECS adds or removes from the service during a rolling update is controlled by adjusting the minimum and maximum number of healthy tasks allowed during a service deployment, as specified in the DeploymentConfiguration. + CODE_DEPLOY The blue/green (CODE_DEPLOY) deployment type uses the blue/green deployment model powered by , which allows you to verify a new deployment of a service before sending production traffic to it. + EXTERNAL The external (EXTERNAL) deployment type enables you to use any third-party deployment controller for full control over the deployment process for an Amazon ECS service.
- type str
- The deployment controller type to use. There are three deployment controller types available: + ECS The rolling update (ECS) deployment type involves replacing the current running version of the container with the latest version. The number of containers Amazon ECS adds or removes from the service during a rolling update is controlled by adjusting the minimum and maximum number of healthy tasks allowed during a service deployment, as specified in the DeploymentConfiguration. + CODE_DEPLOY The blue/green (CODE_DEPLOY) deployment type uses the blue/green deployment model powered by , which allows you to verify a new deployment of a service before sending production traffic to it. + EXTERNAL The external (EXTERNAL) deployment type enables you to use any third-party deployment controller for full control over the deployment process for an Amazon ECS service.
- type String
- The deployment controller type to use. There are three deployment controller types available: + ECS The rolling update (ECS) deployment type involves replacing the current running version of the container with the latest version. The number of containers Amazon ECS adds or removes from the service during a rolling update is controlled by adjusting the minimum and maximum number of healthy tasks allowed during a service deployment, as specified in the DeploymentConfiguration. + CODE_DEPLOY The blue/green (CODE_DEPLOY) deployment type uses the blue/green deployment model powered by , which allows you to verify a new deployment of a service before sending production traffic to it. + EXTERNAL The external (EXTERNAL) deployment type enables you to use any third-party deployment controller for full control over the deployment process for an Amazon ECS service.
DeploymentControllerType, DeploymentControllerTypeArgs
, DeploymentControllerTypeArgs
- CODE_DEPLOY
- CODE_DEPLOYDeploymentControllerType enum CODE_DEPLOY
- ECS
- ECSDeploymentControllerType enum ECS
- EXTERNAL
- EXTERNALDeploymentControllerType enum EXTERNAL
- Deployment
Controller Type_CODE_DEPLOY - CODE_DEPLOYDeploymentControllerType enum CODE_DEPLOY
- Deployment
Controller Type ECS - ECSDeploymentControllerType enum ECS
- Deployment
Controller Type EXTERNAL - EXTERNALDeploymentControllerType enum EXTERNAL
- CODE_DEPLOY
- CODE_DEPLOYDeploymentControllerType enum CODE_DEPLOY
- ECS
- ECSDeploymentControllerType enum ECS
- EXTERNAL
- EXTERNALDeploymentControllerType enum EXTERNAL
- CODE_DEPLOY
- CODE_DEPLOYDeploymentControllerType enum CODE_DEPLOY
- ECS
- ECSDeploymentControllerType enum ECS
- EXTERNAL
- EXTERNALDeploymentControllerType enum EXTERNAL
- COD_E_DEPLOY
- CODE_DEPLOYDeploymentControllerType enum CODE_DEPLOY
- ECS
- ECSDeploymentControllerType enum ECS
- EXTERNAL
- EXTERNALDeploymentControllerType enum EXTERNAL
- "CODE_DEPLOY"
- CODE_DEPLOYDeploymentControllerType enum CODE_DEPLOY
- "ECS"
- ECSDeploymentControllerType enum ECS
- "EXTERNAL"
- EXTERNALDeploymentControllerType enum EXTERNAL
EBSTagSpecification, EBSTagSpecificationArgs
, EBSTagSpecificationArgs
-
string | Pulumi.
Azure Native. Aws Connector. EBSTag Specification Propagate Tags - Determines whether to propagate the tags from the task definition to the Amazon EBS volume. Tags can only propagate to a
SERVICEspecified inServiceVolumeConfiguration. If no value is specified, the tags aren't propagated. - Resource
Type string - The type of volume resource.
-
List<Pulumi.
Azure Native. Aws Connector. Inputs. Tag> - The tags applied to this Amazon EBS volume.
AmazonECSCreatedandAmazonECSManagedare reserved tags that can't be used.
-
string | EBSTag
Specification Propagate Tags - Determines whether to propagate the tags from the task definition to the Amazon EBS volume. Tags can only propagate to a
SERVICEspecified inServiceVolumeConfiguration. If no value is specified, the tags aren't propagated. - Resource
Type string - The type of volume resource.
- []Tag
- The tags applied to this Amazon EBS volume.
AmazonECSCreatedandAmazonECSManagedare reserved tags that can't be used.
-
String | EBSTag
Specification Propagate Tags - Determines whether to propagate the tags from the task definition to the Amazon EBS volume. Tags can only propagate to a
SERVICEspecified inServiceVolumeConfiguration. If no value is specified, the tags aren't propagated. - resource
Type String - The type of volume resource.
- List<Tag>
- The tags applied to this Amazon EBS volume.
AmazonECSCreatedandAmazonECSManagedare reserved tags that can't be used.
-
string | EBSTag
Specification Propagate Tags - Determines whether to propagate the tags from the task definition to the Amazon EBS volume. Tags can only propagate to a
SERVICEspecified inServiceVolumeConfiguration. If no value is specified, the tags aren't propagated. - resource
Type string - The type of volume resource.
- Tag[]
- The tags applied to this Amazon EBS volume.
AmazonECSCreatedandAmazonECSManagedare reserved tags that can't be used.
-
str | EBSTag
Specification Propagate Tags - Determines whether to propagate the tags from the task definition to the Amazon EBS volume. Tags can only propagate to a
SERVICEspecified inServiceVolumeConfiguration. If no value is specified, the tags aren't propagated. - resource_
type str - The type of volume resource.
- Sequence[Tag]
- The tags applied to this Amazon EBS volume.
AmazonECSCreatedandAmazonECSManagedare reserved tags that can't be used.
- String | "SERVICE" | "TASK_DEFINITION"
- Determines whether to propagate the tags from the task definition to the Amazon EBS volume. Tags can only propagate to a
SERVICEspecified inServiceVolumeConfiguration. If no value is specified, the tags aren't propagated. - resource
Type String - The type of volume resource.
- List<Property Map>
- The tags applied to this Amazon EBS volume.
AmazonECSCreatedandAmazonECSManagedare reserved tags that can't be used.
EBSTagSpecificationPropagateTags, EBSTagSpecificationPropagateTagsArgs
, EBSTagSpecificationPropagateTagsArgs
- SERVICE
- SERVICEEBSTagSpecificationPropagateTags enum SERVICE
- TASK_DEFINITION
- TASK_DEFINITIONEBSTagSpecificationPropagateTags enum TASK_DEFINITION
- EBSTag
Specification Propagate Tags SERVICE - SERVICEEBSTagSpecificationPropagateTags enum SERVICE
- EBSTag
Specification Propagate Tags_TASK_DEFINITION - TASK_DEFINITIONEBSTagSpecificationPropagateTags enum TASK_DEFINITION
- SERVICE
- SERVICEEBSTagSpecificationPropagateTags enum SERVICE
- TASK_DEFINITION
- TASK_DEFINITIONEBSTagSpecificationPropagateTags enum TASK_DEFINITION
- SERVICE
- SERVICEEBSTagSpecificationPropagateTags enum SERVICE
- TASK_DEFINITION
- TASK_DEFINITIONEBSTagSpecificationPropagateTags enum TASK_DEFINITION
- SERVICE
- SERVICEEBSTagSpecificationPropagateTags enum SERVICE
- TAS_K_DEFINITION
- TASK_DEFINITIONEBSTagSpecificationPropagateTags enum TASK_DEFINITION
- "SERVICE"
- SERVICEEBSTagSpecificationPropagateTags enum SERVICE
- "TASK_DEFINITION"
- TASK_DEFINITIONEBSTagSpecificationPropagateTags enum TASK_DEFINITION
EBSTagSpecificationResponse, EBSTagSpecificationResponseArgs
, EBSTagSpecificationResponseArgs
- string
- Determines whether to propagate the tags from the task definition to the Amazon EBS volume. Tags can only propagate to a
SERVICEspecified inServiceVolumeConfiguration. If no value is specified, the tags aren't propagated. - Resource
Type string - The type of volume resource.
-
List<Pulumi.
Azure Native. Aws Connector. Inputs. Tag Response> - The tags applied to this Amazon EBS volume.
AmazonECSCreatedandAmazonECSManagedare reserved tags that can't be used.
- string
- Determines whether to propagate the tags from the task definition to the Amazon EBS volume. Tags can only propagate to a
SERVICEspecified inServiceVolumeConfiguration. If no value is specified, the tags aren't propagated. - Resource
Type string - The type of volume resource.
-
[]Tag
Response - The tags applied to this Amazon EBS volume.
AmazonECSCreatedandAmazonECSManagedare reserved tags that can't be used.
- String
- Determines whether to propagate the tags from the task definition to the Amazon EBS volume. Tags can only propagate to a
SERVICEspecified inServiceVolumeConfiguration. If no value is specified, the tags aren't propagated. - resource
Type String - The type of volume resource.
-
List<Tag
Response> - The tags applied to this Amazon EBS volume.
AmazonECSCreatedandAmazonECSManagedare reserved tags that can't be used.
- string
- Determines whether to propagate the tags from the task definition to the Amazon EBS volume. Tags can only propagate to a
SERVICEspecified inServiceVolumeConfiguration. If no value is specified, the tags aren't propagated. - resource
Type string - The type of volume resource.
-
Tag
Response[] - The tags applied to this Amazon EBS volume.
AmazonECSCreatedandAmazonECSManagedare reserved tags that can't be used.
- str
- Determines whether to propagate the tags from the task definition to the Amazon EBS volume. Tags can only propagate to a
SERVICEspecified inServiceVolumeConfiguration. If no value is specified, the tags aren't propagated. - resource_
type str - The type of volume resource.
-
Sequence[Tag
Response] - The tags applied to this Amazon EBS volume.
AmazonECSCreatedandAmazonECSManagedare reserved tags that can't be used.
- String
- Determines whether to propagate the tags from the task definition to the Amazon EBS volume. Tags can only propagate to a
SERVICEspecified inServiceVolumeConfiguration. If no value is specified, the tags aren't propagated. - resource
Type String - The type of volume resource.
- List<Property Map>
- The tags applied to this Amazon EBS volume.
AmazonECSCreatedandAmazonECSManagedare reserved tags that can't be used.
EcsServiceProperties, EcsServicePropertiesArgs
, EcsServicePropertiesArgs
- Arn string
- Amazon Resource Name (ARN)
- Aws
Account stringId - AWS Account ID
- Aws
Properties Pulumi.Azure Native. Aws Connector. Inputs. Aws Ecs Service Properties - AWS Properties
- Aws
Region string - AWS Region
- Aws
Source stringSchema - AWS Source Schema
- Dictionary<string, string>
- AWS Tags
- Public
Cloud stringConnectors Resource Id - Public Cloud Connectors Resource ID
- Public
Cloud stringResource Name - Public Cloud Resource Name
- Arn string
- Amazon Resource Name (ARN)
- Aws
Account stringId - AWS Account ID
- Aws
Properties AwsEcs Service Properties - AWS Properties
- Aws
Region string - AWS Region
- Aws
Source stringSchema - AWS Source Schema
- map[string]string
- AWS Tags
- Public
Cloud stringConnectors Resource Id - Public Cloud Connectors Resource ID
- Public
Cloud stringResource Name - Public Cloud Resource Name
- arn String
- Amazon Resource Name (ARN)
- aws
Account StringId - AWS Account ID
- aws
Properties AwsEcs Service Properties - AWS Properties
- aws
Region String - AWS Region
- aws
Source StringSchema - AWS Source Schema
- Map<String,String>
- AWS Tags
- public
Cloud StringConnectors Resource Id - Public Cloud Connectors Resource ID
- public
Cloud StringResource Name - Public Cloud Resource Name
- arn string
- Amazon Resource Name (ARN)
- aws
Account stringId - AWS Account ID
- aws
Properties AwsEcs Service Properties - AWS Properties
- aws
Region string - AWS Region
- aws
Source stringSchema - AWS Source Schema
- {[key: string]: string}
- AWS Tags
- public
Cloud stringConnectors Resource Id - Public Cloud Connectors Resource ID
- public
Cloud stringResource Name - Public Cloud Resource Name
- arn str
- Amazon Resource Name (ARN)
- aws_
account_ strid - AWS Account ID
- aws_
properties AwsEcs Service Properties - AWS Properties
- aws_
region str - AWS Region
- aws_
source_ strschema - AWS Source Schema
- Mapping[str, str]
- AWS Tags
- public_
cloud_ strconnectors_ resource_ id - Public Cloud Connectors Resource ID
- public_
cloud_ strresource_ name - Public Cloud Resource Name
- arn String
- Amazon Resource Name (ARN)
- aws
Account StringId - AWS Account ID
- aws
Properties Property Map - AWS Properties
- aws
Region String - AWS Region
- aws
Source StringSchema - AWS Source Schema
- Map<String>
- AWS Tags
- public
Cloud StringConnectors Resource Id - Public Cloud Connectors Resource ID
- public
Cloud StringResource Name - Public Cloud Resource Name
EcsServicePropertiesResponse, EcsServicePropertiesResponseArgs
, EcsServicePropertiesResponseArgs
- Provisioning
State This property is required. string - The status of the last operation.
- Arn string
- Amazon Resource Name (ARN)
- Aws
Account stringId - AWS Account ID
- Aws
Properties Pulumi.Azure Native. Aws Connector. Inputs. Aws Ecs Service Properties Response - AWS Properties
- Aws
Region string - AWS Region
- Aws
Source stringSchema - AWS Source Schema
- Dictionary<string, string>
- AWS Tags
- Public
Cloud stringConnectors Resource Id - Public Cloud Connectors Resource ID
- Public
Cloud stringResource Name - Public Cloud Resource Name
- Provisioning
State This property is required. string - The status of the last operation.
- Arn string
- Amazon Resource Name (ARN)
- Aws
Account stringId - AWS Account ID
- Aws
Properties AwsEcs Service Properties Response - AWS Properties
- Aws
Region string - AWS Region
- Aws
Source stringSchema - AWS Source Schema
- map[string]string
- AWS Tags
- Public
Cloud stringConnectors Resource Id - Public Cloud Connectors Resource ID
- Public
Cloud stringResource Name - Public Cloud Resource Name
- provisioning
State This property is required. String - The status of the last operation.
- arn String
- Amazon Resource Name (ARN)
- aws
Account StringId - AWS Account ID
- aws
Properties AwsEcs Service Properties Response - AWS Properties
- aws
Region String - AWS Region
- aws
Source StringSchema - AWS Source Schema
- Map<String,String>
- AWS Tags
- public
Cloud StringConnectors Resource Id - Public Cloud Connectors Resource ID
- public
Cloud StringResource Name - Public Cloud Resource Name
- provisioning
State This property is required. string - The status of the last operation.
- arn string
- Amazon Resource Name (ARN)
- aws
Account stringId - AWS Account ID
- aws
Properties AwsEcs Service Properties Response - AWS Properties
- aws
Region string - AWS Region
- aws
Source stringSchema - AWS Source Schema
- {[key: string]: string}
- AWS Tags
- public
Cloud stringConnectors Resource Id - Public Cloud Connectors Resource ID
- public
Cloud stringResource Name - Public Cloud Resource Name
- provisioning_
state This property is required. str - The status of the last operation.
- arn str
- Amazon Resource Name (ARN)
- aws_
account_ strid - AWS Account ID
- aws_
properties AwsEcs Service Properties Response - AWS Properties
- aws_
region str - AWS Region
- aws_
source_ strschema - AWS Source Schema
- Mapping[str, str]
- AWS Tags
- public_
cloud_ strconnectors_ resource_ id - Public Cloud Connectors Resource ID
- public_
cloud_ strresource_ name - Public Cloud Resource Name
- provisioning
State This property is required. String - The status of the last operation.
- arn String
- Amazon Resource Name (ARN)
- aws
Account StringId - AWS Account ID
- aws
Properties Property Map - AWS Properties
- aws
Region String - AWS Region
- aws
Source StringSchema - AWS Source Schema
- Map<String>
- AWS Tags
- public
Cloud StringConnectors Resource Id - Public Cloud Connectors Resource ID
- public
Cloud StringResource Name - Public Cloud Resource Name
LaunchType, LaunchTypeArgs
, LaunchTypeArgs
- EC2
- EC2LaunchType enum EC2
- EXTERNAL
- EXTERNALLaunchType enum EXTERNAL
- FARGATE
- FARGATELaunchType enum FARGATE
- Launch
Type EC2 - EC2LaunchType enum EC2
- Launch
Type EXTERNAL - EXTERNALLaunchType enum EXTERNAL
- Launch
Type FARGATE - FARGATELaunchType enum FARGATE
- EC2
- EC2LaunchType enum EC2
- EXTERNAL
- EXTERNALLaunchType enum EXTERNAL
- FARGATE
- FARGATELaunchType enum FARGATE
- EC2
- EC2LaunchType enum EC2
- EXTERNAL
- EXTERNALLaunchType enum EXTERNAL
- FARGATE
- FARGATELaunchType enum FARGATE
- EC2
- EC2LaunchType enum EC2
- EXTERNAL
- EXTERNALLaunchType enum EXTERNAL
- FARGATE
- FARGATELaunchType enum FARGATE
- "EC2"
- EC2LaunchType enum EC2
- "EXTERNAL"
- EXTERNALLaunchType enum EXTERNAL
- "FARGATE"
- FARGATELaunchType enum FARGATE
LoadBalancer, LoadBalancerArgs
, LoadBalancerArgs
- Container
Name string - The name of the container (as it appears in a container definition) to associate with the load balancer. You need to specify the container name when configuring the target group for an Amazon ECS load balancer.
- Container
Port int - The port on the container to associate with the load balancer. This port must correspond to a
containerPortin the task definition the tasks in the service are using. For tasks that use the EC2 launch type, the container instance they're launched on must allow ingress traffic on thehostPortof the port mapping. - Load
Balancer stringName - The name of the load balancer to associate with the Amazon ECS service or task set. If you are using an Application Load Balancer or a Network Load Balancer the load balancer name parameter should be omitted.
- Target
Group stringArn - The full Amazon Resource Name (ARN) of the Elastic Load Balancing target group or groups associated with a service or task set. A target group ARN is only specified when using an Application Load Balancer or Network Load Balancer. For services using the
ECSdeployment controller, you can specify one or multiple target groups. For more information, see Registering multiple target groups with a service in the Amazon Elastic Container Service Developer Guide. For services using theCODE_DEPLOYdeployment controller, you're required to define two target groups for the load balancer. For more information, see Blue/green deployment with CodeDeploy in the Amazon Elastic Container Service Developer Guide. If your service's task definition uses theawsvpcnetwork mode, you must chooseipas the target type, notinstance. Do this when creating your target groups because tasks that use theawsvpcnetwork mode are associated with an elastic network interface, not an Amazon EC2 instance. This network mode is required for the Fargate launch type.
- Container
Name string - The name of the container (as it appears in a container definition) to associate with the load balancer. You need to specify the container name when configuring the target group for an Amazon ECS load balancer.
- Container
Port int - The port on the container to associate with the load balancer. This port must correspond to a
containerPortin the task definition the tasks in the service are using. For tasks that use the EC2 launch type, the container instance they're launched on must allow ingress traffic on thehostPortof the port mapping. - Load
Balancer stringName - The name of the load balancer to associate with the Amazon ECS service or task set. If you are using an Application Load Balancer or a Network Load Balancer the load balancer name parameter should be omitted.
- Target
Group stringArn - The full Amazon Resource Name (ARN) of the Elastic Load Balancing target group or groups associated with a service or task set. A target group ARN is only specified when using an Application Load Balancer or Network Load Balancer. For services using the
ECSdeployment controller, you can specify one or multiple target groups. For more information, see Registering multiple target groups with a service in the Amazon Elastic Container Service Developer Guide. For services using theCODE_DEPLOYdeployment controller, you're required to define two target groups for the load balancer. For more information, see Blue/green deployment with CodeDeploy in the Amazon Elastic Container Service Developer Guide. If your service's task definition uses theawsvpcnetwork mode, you must chooseipas the target type, notinstance. Do this when creating your target groups because tasks that use theawsvpcnetwork mode are associated with an elastic network interface, not an Amazon EC2 instance. This network mode is required for the Fargate launch type.
- container
Name String - The name of the container (as it appears in a container definition) to associate with the load balancer. You need to specify the container name when configuring the target group for an Amazon ECS load balancer.
- container
Port Integer - The port on the container to associate with the load balancer. This port must correspond to a
containerPortin the task definition the tasks in the service are using. For tasks that use the EC2 launch type, the container instance they're launched on must allow ingress traffic on thehostPortof the port mapping. - load
Balancer StringName - The name of the load balancer to associate with the Amazon ECS service or task set. If you are using an Application Load Balancer or a Network Load Balancer the load balancer name parameter should be omitted.
- target
Group StringArn - The full Amazon Resource Name (ARN) of the Elastic Load Balancing target group or groups associated with a service or task set. A target group ARN is only specified when using an Application Load Balancer or Network Load Balancer. For services using the
ECSdeployment controller, you can specify one or multiple target groups. For more information, see Registering multiple target groups with a service in the Amazon Elastic Container Service Developer Guide. For services using theCODE_DEPLOYdeployment controller, you're required to define two target groups for the load balancer. For more information, see Blue/green deployment with CodeDeploy in the Amazon Elastic Container Service Developer Guide. If your service's task definition uses theawsvpcnetwork mode, you must chooseipas the target type, notinstance. Do this when creating your target groups because tasks that use theawsvpcnetwork mode are associated with an elastic network interface, not an Amazon EC2 instance. This network mode is required for the Fargate launch type.
- container
Name string - The name of the container (as it appears in a container definition) to associate with the load balancer. You need to specify the container name when configuring the target group for an Amazon ECS load balancer.
- container
Port number - The port on the container to associate with the load balancer. This port must correspond to a
containerPortin the task definition the tasks in the service are using. For tasks that use the EC2 launch type, the container instance they're launched on must allow ingress traffic on thehostPortof the port mapping. - load
Balancer stringName - The name of the load balancer to associate with the Amazon ECS service or task set. If you are using an Application Load Balancer or a Network Load Balancer the load balancer name parameter should be omitted.
- target
Group stringArn - The full Amazon Resource Name (ARN) of the Elastic Load Balancing target group or groups associated with a service or task set. A target group ARN is only specified when using an Application Load Balancer or Network Load Balancer. For services using the
ECSdeployment controller, you can specify one or multiple target groups. For more information, see Registering multiple target groups with a service in the Amazon Elastic Container Service Developer Guide. For services using theCODE_DEPLOYdeployment controller, you're required to define two target groups for the load balancer. For more information, see Blue/green deployment with CodeDeploy in the Amazon Elastic Container Service Developer Guide. If your service's task definition uses theawsvpcnetwork mode, you must chooseipas the target type, notinstance. Do this when creating your target groups because tasks that use theawsvpcnetwork mode are associated with an elastic network interface, not an Amazon EC2 instance. This network mode is required for the Fargate launch type.
- container_
name str - The name of the container (as it appears in a container definition) to associate with the load balancer. You need to specify the container name when configuring the target group for an Amazon ECS load balancer.
- container_
port int - The port on the container to associate with the load balancer. This port must correspond to a
containerPortin the task definition the tasks in the service are using. For tasks that use the EC2 launch type, the container instance they're launched on must allow ingress traffic on thehostPortof the port mapping. - load_
balancer_ strname - The name of the load balancer to associate with the Amazon ECS service or task set. If you are using an Application Load Balancer or a Network Load Balancer the load balancer name parameter should be omitted.
- target_
group_ strarn - The full Amazon Resource Name (ARN) of the Elastic Load Balancing target group or groups associated with a service or task set. A target group ARN is only specified when using an Application Load Balancer or Network Load Balancer. For services using the
ECSdeployment controller, you can specify one or multiple target groups. For more information, see Registering multiple target groups with a service in the Amazon Elastic Container Service Developer Guide. For services using theCODE_DEPLOYdeployment controller, you're required to define two target groups for the load balancer. For more information, see Blue/green deployment with CodeDeploy in the Amazon Elastic Container Service Developer Guide. If your service's task definition uses theawsvpcnetwork mode, you must chooseipas the target type, notinstance. Do this when creating your target groups because tasks that use theawsvpcnetwork mode are associated with an elastic network interface, not an Amazon EC2 instance. This network mode is required for the Fargate launch type.
- container
Name String - The name of the container (as it appears in a container definition) to associate with the load balancer. You need to specify the container name when configuring the target group for an Amazon ECS load balancer.
- container
Port Number - The port on the container to associate with the load balancer. This port must correspond to a
containerPortin the task definition the tasks in the service are using. For tasks that use the EC2 launch type, the container instance they're launched on must allow ingress traffic on thehostPortof the port mapping. - load
Balancer StringName - The name of the load balancer to associate with the Amazon ECS service or task set. If you are using an Application Load Balancer or a Network Load Balancer the load balancer name parameter should be omitted.
- target
Group StringArn - The full Amazon Resource Name (ARN) of the Elastic Load Balancing target group or groups associated with a service or task set. A target group ARN is only specified when using an Application Load Balancer or Network Load Balancer. For services using the
ECSdeployment controller, you can specify one or multiple target groups. For more information, see Registering multiple target groups with a service in the Amazon Elastic Container Service Developer Guide. For services using theCODE_DEPLOYdeployment controller, you're required to define two target groups for the load balancer. For more information, see Blue/green deployment with CodeDeploy in the Amazon Elastic Container Service Developer Guide. If your service's task definition uses theawsvpcnetwork mode, you must chooseipas the target type, notinstance. Do this when creating your target groups because tasks that use theawsvpcnetwork mode are associated with an elastic network interface, not an Amazon EC2 instance. This network mode is required for the Fargate launch type.
LoadBalancerResponse, LoadBalancerResponseArgs
, LoadBalancerResponseArgs
- Container
Name string - The name of the container (as it appears in a container definition) to associate with the load balancer. You need to specify the container name when configuring the target group for an Amazon ECS load balancer.
- Container
Port int - The port on the container to associate with the load balancer. This port must correspond to a
containerPortin the task definition the tasks in the service are using. For tasks that use the EC2 launch type, the container instance they're launched on must allow ingress traffic on thehostPortof the port mapping. - Load
Balancer stringName - The name of the load balancer to associate with the Amazon ECS service or task set. If you are using an Application Load Balancer or a Network Load Balancer the load balancer name parameter should be omitted.
- Target
Group stringArn - The full Amazon Resource Name (ARN) of the Elastic Load Balancing target group or groups associated with a service or task set. A target group ARN is only specified when using an Application Load Balancer or Network Load Balancer. For services using the
ECSdeployment controller, you can specify one or multiple target groups. For more information, see Registering multiple target groups with a service in the Amazon Elastic Container Service Developer Guide. For services using theCODE_DEPLOYdeployment controller, you're required to define two target groups for the load balancer. For more information, see Blue/green deployment with CodeDeploy in the Amazon Elastic Container Service Developer Guide. If your service's task definition uses theawsvpcnetwork mode, you must chooseipas the target type, notinstance. Do this when creating your target groups because tasks that use theawsvpcnetwork mode are associated with an elastic network interface, not an Amazon EC2 instance. This network mode is required for the Fargate launch type.
- Container
Name string - The name of the container (as it appears in a container definition) to associate with the load balancer. You need to specify the container name when configuring the target group for an Amazon ECS load balancer.
- Container
Port int - The port on the container to associate with the load balancer. This port must correspond to a
containerPortin the task definition the tasks in the service are using. For tasks that use the EC2 launch type, the container instance they're launched on must allow ingress traffic on thehostPortof the port mapping. - Load
Balancer stringName - The name of the load balancer to associate with the Amazon ECS service or task set. If you are using an Application Load Balancer or a Network Load Balancer the load balancer name parameter should be omitted.
- Target
Group stringArn - The full Amazon Resource Name (ARN) of the Elastic Load Balancing target group or groups associated with a service or task set. A target group ARN is only specified when using an Application Load Balancer or Network Load Balancer. For services using the
ECSdeployment controller, you can specify one or multiple target groups. For more information, see Registering multiple target groups with a service in the Amazon Elastic Container Service Developer Guide. For services using theCODE_DEPLOYdeployment controller, you're required to define two target groups for the load balancer. For more information, see Blue/green deployment with CodeDeploy in the Amazon Elastic Container Service Developer Guide. If your service's task definition uses theawsvpcnetwork mode, you must chooseipas the target type, notinstance. Do this when creating your target groups because tasks that use theawsvpcnetwork mode are associated with an elastic network interface, not an Amazon EC2 instance. This network mode is required for the Fargate launch type.
- container
Name String - The name of the container (as it appears in a container definition) to associate with the load balancer. You need to specify the container name when configuring the target group for an Amazon ECS load balancer.
- container
Port Integer - The port on the container to associate with the load balancer. This port must correspond to a
containerPortin the task definition the tasks in the service are using. For tasks that use the EC2 launch type, the container instance they're launched on must allow ingress traffic on thehostPortof the port mapping. - load
Balancer StringName - The name of the load balancer to associate with the Amazon ECS service or task set. If you are using an Application Load Balancer or a Network Load Balancer the load balancer name parameter should be omitted.
- target
Group StringArn - The full Amazon Resource Name (ARN) of the Elastic Load Balancing target group or groups associated with a service or task set. A target group ARN is only specified when using an Application Load Balancer or Network Load Balancer. For services using the
ECSdeployment controller, you can specify one or multiple target groups. For more information, see Registering multiple target groups with a service in the Amazon Elastic Container Service Developer Guide. For services using theCODE_DEPLOYdeployment controller, you're required to define two target groups for the load balancer. For more information, see Blue/green deployment with CodeDeploy in the Amazon Elastic Container Service Developer Guide. If your service's task definition uses theawsvpcnetwork mode, you must chooseipas the target type, notinstance. Do this when creating your target groups because tasks that use theawsvpcnetwork mode are associated with an elastic network interface, not an Amazon EC2 instance. This network mode is required for the Fargate launch type.
- container
Name string - The name of the container (as it appears in a container definition) to associate with the load balancer. You need to specify the container name when configuring the target group for an Amazon ECS load balancer.
- container
Port number - The port on the container to associate with the load balancer. This port must correspond to a
containerPortin the task definition the tasks in the service are using. For tasks that use the EC2 launch type, the container instance they're launched on must allow ingress traffic on thehostPortof the port mapping. - load
Balancer stringName - The name of the load balancer to associate with the Amazon ECS service or task set. If you are using an Application Load Balancer or a Network Load Balancer the load balancer name parameter should be omitted.
- target
Group stringArn - The full Amazon Resource Name (ARN) of the Elastic Load Balancing target group or groups associated with a service or task set. A target group ARN is only specified when using an Application Load Balancer or Network Load Balancer. For services using the
ECSdeployment controller, you can specify one or multiple target groups. For more information, see Registering multiple target groups with a service in the Amazon Elastic Container Service Developer Guide. For services using theCODE_DEPLOYdeployment controller, you're required to define two target groups for the load balancer. For more information, see Blue/green deployment with CodeDeploy in the Amazon Elastic Container Service Developer Guide. If your service's task definition uses theawsvpcnetwork mode, you must chooseipas the target type, notinstance. Do this when creating your target groups because tasks that use theawsvpcnetwork mode are associated with an elastic network interface, not an Amazon EC2 instance. This network mode is required for the Fargate launch type.
- container_
name str - The name of the container (as it appears in a container definition) to associate with the load balancer. You need to specify the container name when configuring the target group for an Amazon ECS load balancer.
- container_
port int - The port on the container to associate with the load balancer. This port must correspond to a
containerPortin the task definition the tasks in the service are using. For tasks that use the EC2 launch type, the container instance they're launched on must allow ingress traffic on thehostPortof the port mapping. - load_
balancer_ strname - The name of the load balancer to associate with the Amazon ECS service or task set. If you are using an Application Load Balancer or a Network Load Balancer the load balancer name parameter should be omitted.
- target_
group_ strarn - The full Amazon Resource Name (ARN) of the Elastic Load Balancing target group or groups associated with a service or task set. A target group ARN is only specified when using an Application Load Balancer or Network Load Balancer. For services using the
ECSdeployment controller, you can specify one or multiple target groups. For more information, see Registering multiple target groups with a service in the Amazon Elastic Container Service Developer Guide. For services using theCODE_DEPLOYdeployment controller, you're required to define two target groups for the load balancer. For more information, see Blue/green deployment with CodeDeploy in the Amazon Elastic Container Service Developer Guide. If your service's task definition uses theawsvpcnetwork mode, you must chooseipas the target type, notinstance. Do this when creating your target groups because tasks that use theawsvpcnetwork mode are associated with an elastic network interface, not an Amazon EC2 instance. This network mode is required for the Fargate launch type.
- container
Name String - The name of the container (as it appears in a container definition) to associate with the load balancer. You need to specify the container name when configuring the target group for an Amazon ECS load balancer.
- container
Port Number - The port on the container to associate with the load balancer. This port must correspond to a
containerPortin the task definition the tasks in the service are using. For tasks that use the EC2 launch type, the container instance they're launched on must allow ingress traffic on thehostPortof the port mapping. - load
Balancer StringName - The name of the load balancer to associate with the Amazon ECS service or task set. If you are using an Application Load Balancer or a Network Load Balancer the load balancer name parameter should be omitted.
- target
Group StringArn - The full Amazon Resource Name (ARN) of the Elastic Load Balancing target group or groups associated with a service or task set. A target group ARN is only specified when using an Application Load Balancer or Network Load Balancer. For services using the
ECSdeployment controller, you can specify one or multiple target groups. For more information, see Registering multiple target groups with a service in the Amazon Elastic Container Service Developer Guide. For services using theCODE_DEPLOYdeployment controller, you're required to define two target groups for the load balancer. For more information, see Blue/green deployment with CodeDeploy in the Amazon Elastic Container Service Developer Guide. If your service's task definition uses theawsvpcnetwork mode, you must chooseipas the target type, notinstance. Do this when creating your target groups because tasks that use theawsvpcnetwork mode are associated with an elastic network interface, not an Amazon EC2 instance. This network mode is required for the Fargate launch type.
LogConfiguration, LogConfigurationArgs
, LogConfigurationArgs
- Log
Driver string - The log driver to use for the container. For tasks on FARGATElong, the supported log drivers are
awslogs,splunk, andawsfirelens. For tasks hosted on Amazon EC2 instances, the supported log drivers areawslogs,fluentd,gelf,json-file,journald,logentries,syslog,splunk, andawsfirelens. For more information about using theawslogslog driver, see Using the awslogs log driver in the Amazon Elastic Container Service Developer Guide. For more information about using theawsfirelenslog driver, see Custom log routing in the Amazon Elastic Container Service Developer Guide. If you have a custom driver that isn't listed, you can fork the Amazon ECS container agent project that's available on GitHub and customize it to work with that driver. We encourage you to submit pull requests for changes that you would like to have included. However, we don't currently provide support for running modified copies of this software. - Options object
- The configuration options to send to the log driver. This parameter requires version 1.19 of the Docker Remote API or greater on your container instance. To check the Docker Remote API version on your container instance, log in to your container instance and run the following command:
sudo docker version --format '{{.Server.APIVersion}}' - Secret
Options List<Pulumi.Azure Native. Aws Connector. Inputs. Secret> - The secrets to pass to the log configuration. For more information, see Specifying sensitive data in the Amazon Elastic Container Service Developer Guide.
- Log
Driver string - The log driver to use for the container. For tasks on FARGATElong, the supported log drivers are
awslogs,splunk, andawsfirelens. For tasks hosted on Amazon EC2 instances, the supported log drivers areawslogs,fluentd,gelf,json-file,journald,logentries,syslog,splunk, andawsfirelens. For more information about using theawslogslog driver, see Using the awslogs log driver in the Amazon Elastic Container Service Developer Guide. For more information about using theawsfirelenslog driver, see Custom log routing in the Amazon Elastic Container Service Developer Guide. If you have a custom driver that isn't listed, you can fork the Amazon ECS container agent project that's available on GitHub and customize it to work with that driver. We encourage you to submit pull requests for changes that you would like to have included. However, we don't currently provide support for running modified copies of this software. - Options interface{}
- The configuration options to send to the log driver. This parameter requires version 1.19 of the Docker Remote API or greater on your container instance. To check the Docker Remote API version on your container instance, log in to your container instance and run the following command:
sudo docker version --format '{{.Server.APIVersion}}' - Secret
Options []Secret - The secrets to pass to the log configuration. For more information, see Specifying sensitive data in the Amazon Elastic Container Service Developer Guide.
- log
Driver String - The log driver to use for the container. For tasks on FARGATElong, the supported log drivers are
awslogs,splunk, andawsfirelens. For tasks hosted on Amazon EC2 instances, the supported log drivers areawslogs,fluentd,gelf,json-file,journald,logentries,syslog,splunk, andawsfirelens. For more information about using theawslogslog driver, see Using the awslogs log driver in the Amazon Elastic Container Service Developer Guide. For more information about using theawsfirelenslog driver, see Custom log routing in the Amazon Elastic Container Service Developer Guide. If you have a custom driver that isn't listed, you can fork the Amazon ECS container agent project that's available on GitHub and customize it to work with that driver. We encourage you to submit pull requests for changes that you would like to have included. However, we don't currently provide support for running modified copies of this software. - options Object
- The configuration options to send to the log driver. This parameter requires version 1.19 of the Docker Remote API or greater on your container instance. To check the Docker Remote API version on your container instance, log in to your container instance and run the following command:
sudo docker version --format '{{.Server.APIVersion}}' - secret
Options List<Secret> - The secrets to pass to the log configuration. For more information, see Specifying sensitive data in the Amazon Elastic Container Service Developer Guide.
- log
Driver string - The log driver to use for the container. For tasks on FARGATElong, the supported log drivers are
awslogs,splunk, andawsfirelens. For tasks hosted on Amazon EC2 instances, the supported log drivers areawslogs,fluentd,gelf,json-file,journald,logentries,syslog,splunk, andawsfirelens. For more information about using theawslogslog driver, see Using the awslogs log driver in the Amazon Elastic Container Service Developer Guide. For more information about using theawsfirelenslog driver, see Custom log routing in the Amazon Elastic Container Service Developer Guide. If you have a custom driver that isn't listed, you can fork the Amazon ECS container agent project that's available on GitHub and customize it to work with that driver. We encourage you to submit pull requests for changes that you would like to have included. However, we don't currently provide support for running modified copies of this software. - options any
- The configuration options to send to the log driver. This parameter requires version 1.19 of the Docker Remote API or greater on your container instance. To check the Docker Remote API version on your container instance, log in to your container instance and run the following command:
sudo docker version --format '{{.Server.APIVersion}}' - secret
Options Secret[] - The secrets to pass to the log configuration. For more information, see Specifying sensitive data in the Amazon Elastic Container Service Developer Guide.
- log_
driver str - The log driver to use for the container. For tasks on FARGATElong, the supported log drivers are
awslogs,splunk, andawsfirelens. For tasks hosted on Amazon EC2 instances, the supported log drivers areawslogs,fluentd,gelf,json-file,journald,logentries,syslog,splunk, andawsfirelens. For more information about using theawslogslog driver, see Using the awslogs log driver in the Amazon Elastic Container Service Developer Guide. For more information about using theawsfirelenslog driver, see Custom log routing in the Amazon Elastic Container Service Developer Guide. If you have a custom driver that isn't listed, you can fork the Amazon ECS container agent project that's available on GitHub and customize it to work with that driver. We encourage you to submit pull requests for changes that you would like to have included. However, we don't currently provide support for running modified copies of this software. - options Any
- The configuration options to send to the log driver. This parameter requires version 1.19 of the Docker Remote API or greater on your container instance. To check the Docker Remote API version on your container instance, log in to your container instance and run the following command:
sudo docker version --format '{{.Server.APIVersion}}' - secret_
options Sequence[Secret] - The secrets to pass to the log configuration. For more information, see Specifying sensitive data in the Amazon Elastic Container Service Developer Guide.
- log
Driver String - The log driver to use for the container. For tasks on FARGATElong, the supported log drivers are
awslogs,splunk, andawsfirelens. For tasks hosted on Amazon EC2 instances, the supported log drivers areawslogs,fluentd,gelf,json-file,journald,logentries,syslog,splunk, andawsfirelens. For more information about using theawslogslog driver, see Using the awslogs log driver in the Amazon Elastic Container Service Developer Guide. For more information about using theawsfirelenslog driver, see Custom log routing in the Amazon Elastic Container Service Developer Guide. If you have a custom driver that isn't listed, you can fork the Amazon ECS container agent project that's available on GitHub and customize it to work with that driver. We encourage you to submit pull requests for changes that you would like to have included. However, we don't currently provide support for running modified copies of this software. - options Any
- The configuration options to send to the log driver. This parameter requires version 1.19 of the Docker Remote API or greater on your container instance. To check the Docker Remote API version on your container instance, log in to your container instance and run the following command:
sudo docker version --format '{{.Server.APIVersion}}' - secret
Options List<Property Map> - The secrets to pass to the log configuration. For more information, see Specifying sensitive data in the Amazon Elastic Container Service Developer Guide.
LogConfigurationResponse, LogConfigurationResponseArgs
, LogConfigurationResponseArgs
- Log
Driver string - The log driver to use for the container. For tasks on FARGATElong, the supported log drivers are
awslogs,splunk, andawsfirelens. For tasks hosted on Amazon EC2 instances, the supported log drivers areawslogs,fluentd,gelf,json-file,journald,logentries,syslog,splunk, andawsfirelens. For more information about using theawslogslog driver, see Using the awslogs log driver in the Amazon Elastic Container Service Developer Guide. For more information about using theawsfirelenslog driver, see Custom log routing in the Amazon Elastic Container Service Developer Guide. If you have a custom driver that isn't listed, you can fork the Amazon ECS container agent project that's available on GitHub and customize it to work with that driver. We encourage you to submit pull requests for changes that you would like to have included. However, we don't currently provide support for running modified copies of this software. - Options object
- The configuration options to send to the log driver. This parameter requires version 1.19 of the Docker Remote API or greater on your container instance. To check the Docker Remote API version on your container instance, log in to your container instance and run the following command:
sudo docker version --format '{{.Server.APIVersion}}' - Secret
Options List<Pulumi.Azure Native. Aws Connector. Inputs. Secret Response> - The secrets to pass to the log configuration. For more information, see Specifying sensitive data in the Amazon Elastic Container Service Developer Guide.
- Log
Driver string - The log driver to use for the container. For tasks on FARGATElong, the supported log drivers are
awslogs,splunk, andawsfirelens. For tasks hosted on Amazon EC2 instances, the supported log drivers areawslogs,fluentd,gelf,json-file,journald,logentries,syslog,splunk, andawsfirelens. For more information about using theawslogslog driver, see Using the awslogs log driver in the Amazon Elastic Container Service Developer Guide. For more information about using theawsfirelenslog driver, see Custom log routing in the Amazon Elastic Container Service Developer Guide. If you have a custom driver that isn't listed, you can fork the Amazon ECS container agent project that's available on GitHub and customize it to work with that driver. We encourage you to submit pull requests for changes that you would like to have included. However, we don't currently provide support for running modified copies of this software. - Options interface{}
- The configuration options to send to the log driver. This parameter requires version 1.19 of the Docker Remote API or greater on your container instance. To check the Docker Remote API version on your container instance, log in to your container instance and run the following command:
sudo docker version --format '{{.Server.APIVersion}}' - Secret
Options []SecretResponse - The secrets to pass to the log configuration. For more information, see Specifying sensitive data in the Amazon Elastic Container Service Developer Guide.
- log
Driver String - The log driver to use for the container. For tasks on FARGATElong, the supported log drivers are
awslogs,splunk, andawsfirelens. For tasks hosted on Amazon EC2 instances, the supported log drivers areawslogs,fluentd,gelf,json-file,journald,logentries,syslog,splunk, andawsfirelens. For more information about using theawslogslog driver, see Using the awslogs log driver in the Amazon Elastic Container Service Developer Guide. For more information about using theawsfirelenslog driver, see Custom log routing in the Amazon Elastic Container Service Developer Guide. If you have a custom driver that isn't listed, you can fork the Amazon ECS container agent project that's available on GitHub and customize it to work with that driver. We encourage you to submit pull requests for changes that you would like to have included. However, we don't currently provide support for running modified copies of this software. - options Object
- The configuration options to send to the log driver. This parameter requires version 1.19 of the Docker Remote API or greater on your container instance. To check the Docker Remote API version on your container instance, log in to your container instance and run the following command:
sudo docker version --format '{{.Server.APIVersion}}' - secret
Options List<SecretResponse> - The secrets to pass to the log configuration. For more information, see Specifying sensitive data in the Amazon Elastic Container Service Developer Guide.
- log
Driver string - The log driver to use for the container. For tasks on FARGATElong, the supported log drivers are
awslogs,splunk, andawsfirelens. For tasks hosted on Amazon EC2 instances, the supported log drivers areawslogs,fluentd,gelf,json-file,journald,logentries,syslog,splunk, andawsfirelens. For more information about using theawslogslog driver, see Using the awslogs log driver in the Amazon Elastic Container Service Developer Guide. For more information about using theawsfirelenslog driver, see Custom log routing in the Amazon Elastic Container Service Developer Guide. If you have a custom driver that isn't listed, you can fork the Amazon ECS container agent project that's available on GitHub and customize it to work with that driver. We encourage you to submit pull requests for changes that you would like to have included. However, we don't currently provide support for running modified copies of this software. - options any
- The configuration options to send to the log driver. This parameter requires version 1.19 of the Docker Remote API or greater on your container instance. To check the Docker Remote API version on your container instance, log in to your container instance and run the following command:
sudo docker version --format '{{.Server.APIVersion}}' - secret
Options SecretResponse[] - The secrets to pass to the log configuration. For more information, see Specifying sensitive data in the Amazon Elastic Container Service Developer Guide.
- log_
driver str - The log driver to use for the container. For tasks on FARGATElong, the supported log drivers are
awslogs,splunk, andawsfirelens. For tasks hosted on Amazon EC2 instances, the supported log drivers areawslogs,fluentd,gelf,json-file,journald,logentries,syslog,splunk, andawsfirelens. For more information about using theawslogslog driver, see Using the awslogs log driver in the Amazon Elastic Container Service Developer Guide. For more information about using theawsfirelenslog driver, see Custom log routing in the Amazon Elastic Container Service Developer Guide. If you have a custom driver that isn't listed, you can fork the Amazon ECS container agent project that's available on GitHub and customize it to work with that driver. We encourage you to submit pull requests for changes that you would like to have included. However, we don't currently provide support for running modified copies of this software. - options Any
- The configuration options to send to the log driver. This parameter requires version 1.19 of the Docker Remote API or greater on your container instance. To check the Docker Remote API version on your container instance, log in to your container instance and run the following command:
sudo docker version --format '{{.Server.APIVersion}}' - secret_
options Sequence[SecretResponse] - The secrets to pass to the log configuration. For more information, see Specifying sensitive data in the Amazon Elastic Container Service Developer Guide.
- log
Driver String - The log driver to use for the container. For tasks on FARGATElong, the supported log drivers are
awslogs,splunk, andawsfirelens. For tasks hosted on Amazon EC2 instances, the supported log drivers areawslogs,fluentd,gelf,json-file,journald,logentries,syslog,splunk, andawsfirelens. For more information about using theawslogslog driver, see Using the awslogs log driver in the Amazon Elastic Container Service Developer Guide. For more information about using theawsfirelenslog driver, see Custom log routing in the Amazon Elastic Container Service Developer Guide. If you have a custom driver that isn't listed, you can fork the Amazon ECS container agent project that's available on GitHub and customize it to work with that driver. We encourage you to submit pull requests for changes that you would like to have included. However, we don't currently provide support for running modified copies of this software. - options Any
- The configuration options to send to the log driver. This parameter requires version 1.19 of the Docker Remote API or greater on your container instance. To check the Docker Remote API version on your container instance, log in to your container instance and run the following command:
sudo docker version --format '{{.Server.APIVersion}}' - secret
Options List<Property Map> - The secrets to pass to the log configuration. For more information, see Specifying sensitive data in the Amazon Elastic Container Service Developer Guide.
NetworkConfiguration, NetworkConfigurationArgs
, NetworkConfigurationArgs
- Awsvpc
Configuration Pulumi.Azure Native. Aws Connector. Inputs. Aws Vpc Configuration - The VPC subnets and security groups that are associated with a task. All specified subnets and security groups must be from the same VPC. An object representing the networking details for a task or service. For example
awsvpcConfiguration={subnets=['subnet-12344321'],securityGroups=['sg-12344321']}
- Awsvpc
Configuration AwsVpc Configuration - The VPC subnets and security groups that are associated with a task. All specified subnets and security groups must be from the same VPC. An object representing the networking details for a task or service. For example
awsvpcConfiguration={subnets=['subnet-12344321'],securityGroups=['sg-12344321']}
- awsvpc
Configuration AwsVpc Configuration - The VPC subnets and security groups that are associated with a task. All specified subnets and security groups must be from the same VPC. An object representing the networking details for a task or service. For example
awsvpcConfiguration={subnets=['subnet-12344321'],securityGroups=['sg-12344321']}
- awsvpc
Configuration AwsVpc Configuration - The VPC subnets and security groups that are associated with a task. All specified subnets and security groups must be from the same VPC. An object representing the networking details for a task or service. For example
awsvpcConfiguration={subnets=['subnet-12344321'],securityGroups=['sg-12344321']}
- awsvpc_
configuration AwsVpc Configuration - The VPC subnets and security groups that are associated with a task. All specified subnets and security groups must be from the same VPC. An object representing the networking details for a task or service. For example
awsvpcConfiguration={subnets=['subnet-12344321'],securityGroups=['sg-12344321']}
- awsvpc
Configuration Property Map - The VPC subnets and security groups that are associated with a task. All specified subnets and security groups must be from the same VPC. An object representing the networking details for a task or service. For example
awsvpcConfiguration={subnets=['subnet-12344321'],securityGroups=['sg-12344321']}
NetworkConfigurationResponse, NetworkConfigurationResponseArgs
, NetworkConfigurationResponseArgs
- Awsvpc
Configuration Pulumi.Azure Native. Aws Connector. Inputs. Aws Vpc Configuration Response - The VPC subnets and security groups that are associated with a task. All specified subnets and security groups must be from the same VPC. An object representing the networking details for a task or service. For example
awsvpcConfiguration={subnets=['subnet-12344321'],securityGroups=['sg-12344321']}
- Awsvpc
Configuration AwsVpc Configuration Response - The VPC subnets and security groups that are associated with a task. All specified subnets and security groups must be from the same VPC. An object representing the networking details for a task or service. For example
awsvpcConfiguration={subnets=['subnet-12344321'],securityGroups=['sg-12344321']}
- awsvpc
Configuration AwsVpc Configuration Response - The VPC subnets and security groups that are associated with a task. All specified subnets and security groups must be from the same VPC. An object representing the networking details for a task or service. For example
awsvpcConfiguration={subnets=['subnet-12344321'],securityGroups=['sg-12344321']}
- awsvpc
Configuration AwsVpc Configuration Response - The VPC subnets and security groups that are associated with a task. All specified subnets and security groups must be from the same VPC. An object representing the networking details for a task or service. For example
awsvpcConfiguration={subnets=['subnet-12344321'],securityGroups=['sg-12344321']}
- awsvpc_
configuration AwsVpc Configuration Response - The VPC subnets and security groups that are associated with a task. All specified subnets and security groups must be from the same VPC. An object representing the networking details for a task or service. For example
awsvpcConfiguration={subnets=['subnet-12344321'],securityGroups=['sg-12344321']}
- awsvpc
Configuration Property Map - The VPC subnets and security groups that are associated with a task. All specified subnets and security groups must be from the same VPC. An object representing the networking details for a task or service. For example
awsvpcConfiguration={subnets=['subnet-12344321'],securityGroups=['sg-12344321']}
PlacementConstraint, PlacementConstraintArgs
, PlacementConstraintArgs
- Expression string
- A cluster query language expression to apply to the constraint. The expression can have a maximum length of 2000 characters. You can't specify an expression if the constraint type is
distinctInstance. For more information, see Cluster query language in the Amazon Elastic Container Service Developer Guide. - Type
string | Pulumi.
Azure Native. Aws Connector. Placement Constraint Type - The type of constraint. Use
distinctInstanceto ensure that each task in a particular group is running on a different container instance. UsememberOfto restrict the selection to a group of valid candidates.
- Expression string
- A cluster query language expression to apply to the constraint. The expression can have a maximum length of 2000 characters. You can't specify an expression if the constraint type is
distinctInstance. For more information, see Cluster query language in the Amazon Elastic Container Service Developer Guide. - Type
string | Placement
Constraint Type - The type of constraint. Use
distinctInstanceto ensure that each task in a particular group is running on a different container instance. UsememberOfto restrict the selection to a group of valid candidates.
- expression String
- A cluster query language expression to apply to the constraint. The expression can have a maximum length of 2000 characters. You can't specify an expression if the constraint type is
distinctInstance. For more information, see Cluster query language in the Amazon Elastic Container Service Developer Guide. - type
String | Placement
Constraint Type - The type of constraint. Use
distinctInstanceto ensure that each task in a particular group is running on a different container instance. UsememberOfto restrict the selection to a group of valid candidates.
- expression string
- A cluster query language expression to apply to the constraint. The expression can have a maximum length of 2000 characters. You can't specify an expression if the constraint type is
distinctInstance. For more information, see Cluster query language in the Amazon Elastic Container Service Developer Guide. - type
string | Placement
Constraint Type - The type of constraint. Use
distinctInstanceto ensure that each task in a particular group is running on a different container instance. UsememberOfto restrict the selection to a group of valid candidates.
- expression str
- A cluster query language expression to apply to the constraint. The expression can have a maximum length of 2000 characters. You can't specify an expression if the constraint type is
distinctInstance. For more information, see Cluster query language in the Amazon Elastic Container Service Developer Guide. - type
str | Placement
Constraint Type - The type of constraint. Use
distinctInstanceto ensure that each task in a particular group is running on a different container instance. UsememberOfto restrict the selection to a group of valid candidates.
- expression String
- A cluster query language expression to apply to the constraint. The expression can have a maximum length of 2000 characters. You can't specify an expression if the constraint type is
distinctInstance. For more information, see Cluster query language in the Amazon Elastic Container Service Developer Guide. - type
String | "distinct
Instance" | "member Of" - The type of constraint. Use
distinctInstanceto ensure that each task in a particular group is running on a different container instance. UsememberOfto restrict the selection to a group of valid candidates.
PlacementConstraintResponse, PlacementConstraintResponseArgs
, PlacementConstraintResponseArgs
- Expression string
- A cluster query language expression to apply to the constraint. The expression can have a maximum length of 2000 characters. You can't specify an expression if the constraint type is
distinctInstance. For more information, see Cluster query language in the Amazon Elastic Container Service Developer Guide. - Type string
- The type of constraint. Use
distinctInstanceto ensure that each task in a particular group is running on a different container instance. UsememberOfto restrict the selection to a group of valid candidates.
- Expression string
- A cluster query language expression to apply to the constraint. The expression can have a maximum length of 2000 characters. You can't specify an expression if the constraint type is
distinctInstance. For more information, see Cluster query language in the Amazon Elastic Container Service Developer Guide. - Type string
- The type of constraint. Use
distinctInstanceto ensure that each task in a particular group is running on a different container instance. UsememberOfto restrict the selection to a group of valid candidates.
- expression String
- A cluster query language expression to apply to the constraint. The expression can have a maximum length of 2000 characters. You can't specify an expression if the constraint type is
distinctInstance. For more information, see Cluster query language in the Amazon Elastic Container Service Developer Guide. - type String
- The type of constraint. Use
distinctInstanceto ensure that each task in a particular group is running on a different container instance. UsememberOfto restrict the selection to a group of valid candidates.
- expression string
- A cluster query language expression to apply to the constraint. The expression can have a maximum length of 2000 characters. You can't specify an expression if the constraint type is
distinctInstance. For more information, see Cluster query language in the Amazon Elastic Container Service Developer Guide. - type string
- The type of constraint. Use
distinctInstanceto ensure that each task in a particular group is running on a different container instance. UsememberOfto restrict the selection to a group of valid candidates.
- expression str
- A cluster query language expression to apply to the constraint. The expression can have a maximum length of 2000 characters. You can't specify an expression if the constraint type is
distinctInstance. For more information, see Cluster query language in the Amazon Elastic Container Service Developer Guide. - type str
- The type of constraint. Use
distinctInstanceto ensure that each task in a particular group is running on a different container instance. UsememberOfto restrict the selection to a group of valid candidates.
- expression String
- A cluster query language expression to apply to the constraint. The expression can have a maximum length of 2000 characters. You can't specify an expression if the constraint type is
distinctInstance. For more information, see Cluster query language in the Amazon Elastic Container Service Developer Guide. - type String
- The type of constraint. Use
distinctInstanceto ensure that each task in a particular group is running on a different container instance. UsememberOfto restrict the selection to a group of valid candidates.
PlacementConstraintType, PlacementConstraintTypeArgs
, PlacementConstraintTypeArgs
- Distinct
Instance - distinctInstancePlacementConstraintType enum distinctInstance
- Member
Of - memberOfPlacementConstraintType enum memberOf
- Placement
Constraint Type Distinct Instance - distinctInstancePlacementConstraintType enum distinctInstance
- Placement
Constraint Type Member Of - memberOfPlacementConstraintType enum memberOf
- Distinct
Instance - distinctInstancePlacementConstraintType enum distinctInstance
- Member
Of - memberOfPlacementConstraintType enum memberOf
- Distinct
Instance - distinctInstancePlacementConstraintType enum distinctInstance
- Member
Of - memberOfPlacementConstraintType enum memberOf
- DISTINCT_INSTANCE
- distinctInstancePlacementConstraintType enum distinctInstance
- MEMBER_OF
- memberOfPlacementConstraintType enum memberOf
- "distinct
Instance" - distinctInstancePlacementConstraintType enum distinctInstance
- "member
Of" - memberOfPlacementConstraintType enum memberOf
PlacementStrategy, PlacementStrategyArgs
, PlacementStrategyArgs
- Field string
- The field to apply the placement strategy against. For the
spreadplacement strategy, valid values areinstanceId(orhost, which has the same effect), or any platform or custom attribute that is applied to a container instance, such asattribute:ecs.availability-zone. For thebinpackplacement strategy, valid values areCPUandMEMORY. For therandomplacement strategy, this field is not used. - Type
string | Pulumi.
Azure Native. Aws Connector. Placement Strategy Type - The type of placement strategy. The
randomplacement strategy randomly places tasks on available candidates. Thespreadplacement strategy spreads placement across available candidates evenly based on thefieldparameter. Thebinpackstrategy places tasks on available candidates that have the least available amount of the resource that's specified with thefieldparameter. For example, if you binpack on memory, a task is placed on the instance with the least amount of remaining memory but still enough to run the task.
- Field string
- The field to apply the placement strategy against. For the
spreadplacement strategy, valid values areinstanceId(orhost, which has the same effect), or any platform or custom attribute that is applied to a container instance, such asattribute:ecs.availability-zone. For thebinpackplacement strategy, valid values areCPUandMEMORY. For therandomplacement strategy, this field is not used. - Type
string | Placement
Strategy Type - The type of placement strategy. The
randomplacement strategy randomly places tasks on available candidates. Thespreadplacement strategy spreads placement across available candidates evenly based on thefieldparameter. Thebinpackstrategy places tasks on available candidates that have the least available amount of the resource that's specified with thefieldparameter. For example, if you binpack on memory, a task is placed on the instance with the least amount of remaining memory but still enough to run the task.
- field String
- The field to apply the placement strategy against. For the
spreadplacement strategy, valid values areinstanceId(orhost, which has the same effect), or any platform or custom attribute that is applied to a container instance, such asattribute:ecs.availability-zone. For thebinpackplacement strategy, valid values areCPUandMEMORY. For therandomplacement strategy, this field is not used. - type
String | Placement
Strategy Type - The type of placement strategy. The
randomplacement strategy randomly places tasks on available candidates. Thespreadplacement strategy spreads placement across available candidates evenly based on thefieldparameter. Thebinpackstrategy places tasks on available candidates that have the least available amount of the resource that's specified with thefieldparameter. For example, if you binpack on memory, a task is placed on the instance with the least amount of remaining memory but still enough to run the task.
- field string
- The field to apply the placement strategy against. For the
spreadplacement strategy, valid values areinstanceId(orhost, which has the same effect), or any platform or custom attribute that is applied to a container instance, such asattribute:ecs.availability-zone. For thebinpackplacement strategy, valid values areCPUandMEMORY. For therandomplacement strategy, this field is not used. - type
string | Placement
Strategy Type - The type of placement strategy. The
randomplacement strategy randomly places tasks on available candidates. Thespreadplacement strategy spreads placement across available candidates evenly based on thefieldparameter. Thebinpackstrategy places tasks on available candidates that have the least available amount of the resource that's specified with thefieldparameter. For example, if you binpack on memory, a task is placed on the instance with the least amount of remaining memory but still enough to run the task.
- field str
- The field to apply the placement strategy against. For the
spreadplacement strategy, valid values areinstanceId(orhost, which has the same effect), or any platform or custom attribute that is applied to a container instance, such asattribute:ecs.availability-zone. For thebinpackplacement strategy, valid values areCPUandMEMORY. For therandomplacement strategy, this field is not used. - type
str | Placement
Strategy Type - The type of placement strategy. The
randomplacement strategy randomly places tasks on available candidates. Thespreadplacement strategy spreads placement across available candidates evenly based on thefieldparameter. Thebinpackstrategy places tasks on available candidates that have the least available amount of the resource that's specified with thefieldparameter. For example, if you binpack on memory, a task is placed on the instance with the least amount of remaining memory but still enough to run the task.
- field String
- The field to apply the placement strategy against. For the
spreadplacement strategy, valid values areinstanceId(orhost, which has the same effect), or any platform or custom attribute that is applied to a container instance, such asattribute:ecs.availability-zone. For thebinpackplacement strategy, valid values areCPUandMEMORY. For therandomplacement strategy, this field is not used. - type String | "binpack" | "random" | "spread"
- The type of placement strategy. The
randomplacement strategy randomly places tasks on available candidates. Thespreadplacement strategy spreads placement across available candidates evenly based on thefieldparameter. Thebinpackstrategy places tasks on available candidates that have the least available amount of the resource that's specified with thefieldparameter. For example, if you binpack on memory, a task is placed on the instance with the least amount of remaining memory but still enough to run the task.
PlacementStrategyResponse, PlacementStrategyResponseArgs
, PlacementStrategyResponseArgs
- Field string
- The field to apply the placement strategy against. For the
spreadplacement strategy, valid values areinstanceId(orhost, which has the same effect), or any platform or custom attribute that is applied to a container instance, such asattribute:ecs.availability-zone. For thebinpackplacement strategy, valid values areCPUandMEMORY. For therandomplacement strategy, this field is not used. - Type string
- The type of placement strategy. The
randomplacement strategy randomly places tasks on available candidates. Thespreadplacement strategy spreads placement across available candidates evenly based on thefieldparameter. Thebinpackstrategy places tasks on available candidates that have the least available amount of the resource that's specified with thefieldparameter. For example, if you binpack on memory, a task is placed on the instance with the least amount of remaining memory but still enough to run the task.
- Field string
- The field to apply the placement strategy against. For the
spreadplacement strategy, valid values areinstanceId(orhost, which has the same effect), or any platform or custom attribute that is applied to a container instance, such asattribute:ecs.availability-zone. For thebinpackplacement strategy, valid values areCPUandMEMORY. For therandomplacement strategy, this field is not used. - Type string
- The type of placement strategy. The
randomplacement strategy randomly places tasks on available candidates. Thespreadplacement strategy spreads placement across available candidates evenly based on thefieldparameter. Thebinpackstrategy places tasks on available candidates that have the least available amount of the resource that's specified with thefieldparameter. For example, if you binpack on memory, a task is placed on the instance with the least amount of remaining memory but still enough to run the task.
- field String
- The field to apply the placement strategy against. For the
spreadplacement strategy, valid values areinstanceId(orhost, which has the same effect), or any platform or custom attribute that is applied to a container instance, such asattribute:ecs.availability-zone. For thebinpackplacement strategy, valid values areCPUandMEMORY. For therandomplacement strategy, this field is not used. - type String
- The type of placement strategy. The
randomplacement strategy randomly places tasks on available candidates. Thespreadplacement strategy spreads placement across available candidates evenly based on thefieldparameter. Thebinpackstrategy places tasks on available candidates that have the least available amount of the resource that's specified with thefieldparameter. For example, if you binpack on memory, a task is placed on the instance with the least amount of remaining memory but still enough to run the task.
- field string
- The field to apply the placement strategy against. For the
spreadplacement strategy, valid values areinstanceId(orhost, which has the same effect), or any platform or custom attribute that is applied to a container instance, such asattribute:ecs.availability-zone. For thebinpackplacement strategy, valid values areCPUandMEMORY. For therandomplacement strategy, this field is not used. - type string
- The type of placement strategy. The
randomplacement strategy randomly places tasks on available candidates. Thespreadplacement strategy spreads placement across available candidates evenly based on thefieldparameter. Thebinpackstrategy places tasks on available candidates that have the least available amount of the resource that's specified with thefieldparameter. For example, if you binpack on memory, a task is placed on the instance with the least amount of remaining memory but still enough to run the task.
- field str
- The field to apply the placement strategy against. For the
spreadplacement strategy, valid values areinstanceId(orhost, which has the same effect), or any platform or custom attribute that is applied to a container instance, such asattribute:ecs.availability-zone. For thebinpackplacement strategy, valid values areCPUandMEMORY. For therandomplacement strategy, this field is not used. - type str
- The type of placement strategy. The
randomplacement strategy randomly places tasks on available candidates. Thespreadplacement strategy spreads placement across available candidates evenly based on thefieldparameter. Thebinpackstrategy places tasks on available candidates that have the least available amount of the resource that's specified with thefieldparameter. For example, if you binpack on memory, a task is placed on the instance with the least amount of remaining memory but still enough to run the task.
- field String
- The field to apply the placement strategy against. For the
spreadplacement strategy, valid values areinstanceId(orhost, which has the same effect), or any platform or custom attribute that is applied to a container instance, such asattribute:ecs.availability-zone. For thebinpackplacement strategy, valid values areCPUandMEMORY. For therandomplacement strategy, this field is not used. - type String
- The type of placement strategy. The
randomplacement strategy randomly places tasks on available candidates. Thespreadplacement strategy spreads placement across available candidates evenly based on thefieldparameter. Thebinpackstrategy places tasks on available candidates that have the least available amount of the resource that's specified with thefieldparameter. For example, if you binpack on memory, a task is placed on the instance with the least amount of remaining memory but still enough to run the task.
PlacementStrategyType, PlacementStrategyTypeArgs
, PlacementStrategyTypeArgs
- Binpack
- binpackPlacementStrategyType enum binpack
- Random
- randomPlacementStrategyType enum random
- Spread
- spreadPlacementStrategyType enum spread
- Placement
Strategy Type Binpack - binpackPlacementStrategyType enum binpack
- Placement
Strategy Type Random - randomPlacementStrategyType enum random
- Placement
Strategy Type Spread - spreadPlacementStrategyType enum spread
- Binpack
- binpackPlacementStrategyType enum binpack
- Random
- randomPlacementStrategyType enum random
- Spread
- spreadPlacementStrategyType enum spread
- Binpack
- binpackPlacementStrategyType enum binpack
- Random
- randomPlacementStrategyType enum random
- Spread
- spreadPlacementStrategyType enum spread
- BINPACK
- binpackPlacementStrategyType enum binpack
- RANDOM
- randomPlacementStrategyType enum random
- SPREAD
- spreadPlacementStrategyType enum spread
- "binpack"
- binpackPlacementStrategyType enum binpack
- "random"
- randomPlacementStrategyType enum random
- "spread"
- spreadPlacementStrategyType enum spread
PropagateTags, PropagateTagsArgs
, PropagateTagsArgs
- SERVICE
- SERVICEPropagateTags enum SERVICE
- TASK_DEFINITION
- TASK_DEFINITIONPropagateTags enum TASK_DEFINITION
- Propagate
Tags SERVICE - SERVICEPropagateTags enum SERVICE
- Propagate
Tags_TASK_DEFINITION - TASK_DEFINITIONPropagateTags enum TASK_DEFINITION
- SERVICE
- SERVICEPropagateTags enum SERVICE
- TASK_DEFINITION
- TASK_DEFINITIONPropagateTags enum TASK_DEFINITION
- SERVICE
- SERVICEPropagateTags enum SERVICE
- TASK_DEFINITION
- TASK_DEFINITIONPropagateTags enum TASK_DEFINITION
- SERVICE
- SERVICEPropagateTags enum SERVICE
- TAS_K_DEFINITION
- TASK_DEFINITIONPropagateTags enum TASK_DEFINITION
- "SERVICE"
- SERVICEPropagateTags enum SERVICE
- "TASK_DEFINITION"
- TASK_DEFINITIONPropagateTags enum TASK_DEFINITION
SchedulingStrategy, SchedulingStrategyArgs
, SchedulingStrategyArgs
- DAEMON
- DAEMONSchedulingStrategy enum DAEMON
- REPLICA
- REPLICASchedulingStrategy enum REPLICA
- Scheduling
Strategy DAEMON - DAEMONSchedulingStrategy enum DAEMON
- Scheduling
Strategy REPLICA - REPLICASchedulingStrategy enum REPLICA
- DAEMON
- DAEMONSchedulingStrategy enum DAEMON
- REPLICA
- REPLICASchedulingStrategy enum REPLICA
- DAEMON
- DAEMONSchedulingStrategy enum DAEMON
- REPLICA
- REPLICASchedulingStrategy enum REPLICA
- DAEMON
- DAEMONSchedulingStrategy enum DAEMON
- REPLICA
- REPLICASchedulingStrategy enum REPLICA
- "DAEMON"
- DAEMONSchedulingStrategy enum DAEMON
- "REPLICA"
- REPLICASchedulingStrategy enum REPLICA
Secret, SecretArgs
, SecretArgs
- Name string
- The name of the secret.
- Value
From string - The secret to expose to the container. The supported values are either the full ARN of the ASMlong secret or the full ARN of the parameter in the SSM Parameter Store. For information about the require IAMlong permissions, see Required IAM permissions for Amazon ECS secrets (for Secrets Manager) or Required IAM permissions for Amazon ECS secrets (for Systems Manager Parameter store) in the Amazon Elastic Container Service Developer Guide. If the SSM Parameter Store parameter exists in the same Region as the task you're launching, then you can use either the full ARN or name of the parameter. If the parameter exists in a different Region, then the full ARN must be specified.
- Name string
- The name of the secret.
- Value
From string - The secret to expose to the container. The supported values are either the full ARN of the ASMlong secret or the full ARN of the parameter in the SSM Parameter Store. For information about the require IAMlong permissions, see Required IAM permissions for Amazon ECS secrets (for Secrets Manager) or Required IAM permissions for Amazon ECS secrets (for Systems Manager Parameter store) in the Amazon Elastic Container Service Developer Guide. If the SSM Parameter Store parameter exists in the same Region as the task you're launching, then you can use either the full ARN or name of the parameter. If the parameter exists in a different Region, then the full ARN must be specified.
- name String
- The name of the secret.
- value
From String - The secret to expose to the container. The supported values are either the full ARN of the ASMlong secret or the full ARN of the parameter in the SSM Parameter Store. For information about the require IAMlong permissions, see Required IAM permissions for Amazon ECS secrets (for Secrets Manager) or Required IAM permissions for Amazon ECS secrets (for Systems Manager Parameter store) in the Amazon Elastic Container Service Developer Guide. If the SSM Parameter Store parameter exists in the same Region as the task you're launching, then you can use either the full ARN or name of the parameter. If the parameter exists in a different Region, then the full ARN must be specified.
- name string
- The name of the secret.
- value
From string - The secret to expose to the container. The supported values are either the full ARN of the ASMlong secret or the full ARN of the parameter in the SSM Parameter Store. For information about the require IAMlong permissions, see Required IAM permissions for Amazon ECS secrets (for Secrets Manager) or Required IAM permissions for Amazon ECS secrets (for Systems Manager Parameter store) in the Amazon Elastic Container Service Developer Guide. If the SSM Parameter Store parameter exists in the same Region as the task you're launching, then you can use either the full ARN or name of the parameter. If the parameter exists in a different Region, then the full ARN must be specified.
- name str
- The name of the secret.
- value_
from str - The secret to expose to the container. The supported values are either the full ARN of the ASMlong secret or the full ARN of the parameter in the SSM Parameter Store. For information about the require IAMlong permissions, see Required IAM permissions for Amazon ECS secrets (for Secrets Manager) or Required IAM permissions for Amazon ECS secrets (for Systems Manager Parameter store) in the Amazon Elastic Container Service Developer Guide. If the SSM Parameter Store parameter exists in the same Region as the task you're launching, then you can use either the full ARN or name of the parameter. If the parameter exists in a different Region, then the full ARN must be specified.
- name String
- The name of the secret.
- value
From String - The secret to expose to the container. The supported values are either the full ARN of the ASMlong secret or the full ARN of the parameter in the SSM Parameter Store. For information about the require IAMlong permissions, see Required IAM permissions for Amazon ECS secrets (for Secrets Manager) or Required IAM permissions for Amazon ECS secrets (for Systems Manager Parameter store) in the Amazon Elastic Container Service Developer Guide. If the SSM Parameter Store parameter exists in the same Region as the task you're launching, then you can use either the full ARN or name of the parameter. If the parameter exists in a different Region, then the full ARN must be specified.
SecretResponse, SecretResponseArgs
, SecretResponseArgs
- Name string
- The name of the secret.
- Value
From string - The secret to expose to the container. The supported values are either the full ARN of the ASMlong secret or the full ARN of the parameter in the SSM Parameter Store. For information about the require IAMlong permissions, see Required IAM permissions for Amazon ECS secrets (for Secrets Manager) or Required IAM permissions for Amazon ECS secrets (for Systems Manager Parameter store) in the Amazon Elastic Container Service Developer Guide. If the SSM Parameter Store parameter exists in the same Region as the task you're launching, then you can use either the full ARN or name of the parameter. If the parameter exists in a different Region, then the full ARN must be specified.
- Name string
- The name of the secret.
- Value
From string - The secret to expose to the container. The supported values are either the full ARN of the ASMlong secret or the full ARN of the parameter in the SSM Parameter Store. For information about the require IAMlong permissions, see Required IAM permissions for Amazon ECS secrets (for Secrets Manager) or Required IAM permissions for Amazon ECS secrets (for Systems Manager Parameter store) in the Amazon Elastic Container Service Developer Guide. If the SSM Parameter Store parameter exists in the same Region as the task you're launching, then you can use either the full ARN or name of the parameter. If the parameter exists in a different Region, then the full ARN must be specified.
- name String
- The name of the secret.
- value
From String - The secret to expose to the container. The supported values are either the full ARN of the ASMlong secret or the full ARN of the parameter in the SSM Parameter Store. For information about the require IAMlong permissions, see Required IAM permissions for Amazon ECS secrets (for Secrets Manager) or Required IAM permissions for Amazon ECS secrets (for Systems Manager Parameter store) in the Amazon Elastic Container Service Developer Guide. If the SSM Parameter Store parameter exists in the same Region as the task you're launching, then you can use either the full ARN or name of the parameter. If the parameter exists in a different Region, then the full ARN must be specified.
- name string
- The name of the secret.
- value
From string - The secret to expose to the container. The supported values are either the full ARN of the ASMlong secret or the full ARN of the parameter in the SSM Parameter Store. For information about the require IAMlong permissions, see Required IAM permissions for Amazon ECS secrets (for Secrets Manager) or Required IAM permissions for Amazon ECS secrets (for Systems Manager Parameter store) in the Amazon Elastic Container Service Developer Guide. If the SSM Parameter Store parameter exists in the same Region as the task you're launching, then you can use either the full ARN or name of the parameter. If the parameter exists in a different Region, then the full ARN must be specified.
- name str
- The name of the secret.
- value_
from str - The secret to expose to the container. The supported values are either the full ARN of the ASMlong secret or the full ARN of the parameter in the SSM Parameter Store. For information about the require IAMlong permissions, see Required IAM permissions for Amazon ECS secrets (for Secrets Manager) or Required IAM permissions for Amazon ECS secrets (for Systems Manager Parameter store) in the Amazon Elastic Container Service Developer Guide. If the SSM Parameter Store parameter exists in the same Region as the task you're launching, then you can use either the full ARN or name of the parameter. If the parameter exists in a different Region, then the full ARN must be specified.
- name String
- The name of the secret.
- value
From String - The secret to expose to the container. The supported values are either the full ARN of the ASMlong secret or the full ARN of the parameter in the SSM Parameter Store. For information about the require IAMlong permissions, see Required IAM permissions for Amazon ECS secrets (for Secrets Manager) or Required IAM permissions for Amazon ECS secrets (for Systems Manager Parameter store) in the Amazon Elastic Container Service Developer Guide. If the SSM Parameter Store parameter exists in the same Region as the task you're launching, then you can use either the full ARN or name of the parameter. If the parameter exists in a different Region, then the full ARN must be specified.
ServiceConnectClientAlias, ServiceConnectClientAliasArgs
, ServiceConnectClientAliasArgs
- Dns
Name string - The
dnsNameis the name that you use in the applications of client tasks to connect to this service. The name must be a valid DNS name but doesn't need to be fully-qualified. The name can include up to 127 characters. The name can include lowercase letters, numbers, underscores (_), hyphens (-), and periods (.). The name can't start with a hyphen. If this parameter isn't specified, the default value ofdiscoveryName.namespaceis used. If thediscoveryNameisn't specified, the port mapping name from the task definition is used inportName.namespace. To avoid changing your applications in client Amazon ECS services, set this to the same name that the client application uses by default. For example, a few common names aredatabase,db, or the lowercase name of a database, such asmysqlorredis. For more information, see Service Connect in the Amazon Elastic Container Service Developer Guide. - Port int
- The listening port number for the Service Connect proxy. This port is available inside of all of the tasks within the same namespace. To avoid changing your applications in client Amazon ECS services, set this to the same port that the client application uses by default. For more information, see Service Connect in the Amazon Elastic Container Service Developer Guide.
- Dns
Name string - The
dnsNameis the name that you use in the applications of client tasks to connect to this service. The name must be a valid DNS name but doesn't need to be fully-qualified. The name can include up to 127 characters. The name can include lowercase letters, numbers, underscores (_), hyphens (-), and periods (.). The name can't start with a hyphen. If this parameter isn't specified, the default value ofdiscoveryName.namespaceis used. If thediscoveryNameisn't specified, the port mapping name from the task definition is used inportName.namespace. To avoid changing your applications in client Amazon ECS services, set this to the same name that the client application uses by default. For example, a few common names aredatabase,db, or the lowercase name of a database, such asmysqlorredis. For more information, see Service Connect in the Amazon Elastic Container Service Developer Guide. - Port int
- The listening port number for the Service Connect proxy. This port is available inside of all of the tasks within the same namespace. To avoid changing your applications in client Amazon ECS services, set this to the same port that the client application uses by default. For more information, see Service Connect in the Amazon Elastic Container Service Developer Guide.
- dns
Name String - The
dnsNameis the name that you use in the applications of client tasks to connect to this service. The name must be a valid DNS name but doesn't need to be fully-qualified. The name can include up to 127 characters. The name can include lowercase letters, numbers, underscores (_), hyphens (-), and periods (.). The name can't start with a hyphen. If this parameter isn't specified, the default value ofdiscoveryName.namespaceis used. If thediscoveryNameisn't specified, the port mapping name from the task definition is used inportName.namespace. To avoid changing your applications in client Amazon ECS services, set this to the same name that the client application uses by default. For example, a few common names aredatabase,db, or the lowercase name of a database, such asmysqlorredis. For more information, see Service Connect in the Amazon Elastic Container Service Developer Guide. - port Integer
- The listening port number for the Service Connect proxy. This port is available inside of all of the tasks within the same namespace. To avoid changing your applications in client Amazon ECS services, set this to the same port that the client application uses by default. For more information, see Service Connect in the Amazon Elastic Container Service Developer Guide.
- dns
Name string - The
dnsNameis the name that you use in the applications of client tasks to connect to this service. The name must be a valid DNS name but doesn't need to be fully-qualified. The name can include up to 127 characters. The name can include lowercase letters, numbers, underscores (_), hyphens (-), and periods (.). The name can't start with a hyphen. If this parameter isn't specified, the default value ofdiscoveryName.namespaceis used. If thediscoveryNameisn't specified, the port mapping name from the task definition is used inportName.namespace. To avoid changing your applications in client Amazon ECS services, set this to the same name that the client application uses by default. For example, a few common names aredatabase,db, or the lowercase name of a database, such asmysqlorredis. For more information, see Service Connect in the Amazon Elastic Container Service Developer Guide. - port number
- The listening port number for the Service Connect proxy. This port is available inside of all of the tasks within the same namespace. To avoid changing your applications in client Amazon ECS services, set this to the same port that the client application uses by default. For more information, see Service Connect in the Amazon Elastic Container Service Developer Guide.
- dns_
name str - The
dnsNameis the name that you use in the applications of client tasks to connect to this service. The name must be a valid DNS name but doesn't need to be fully-qualified. The name can include up to 127 characters. The name can include lowercase letters, numbers, underscores (_), hyphens (-), and periods (.). The name can't start with a hyphen. If this parameter isn't specified, the default value ofdiscoveryName.namespaceis used. If thediscoveryNameisn't specified, the port mapping name from the task definition is used inportName.namespace. To avoid changing your applications in client Amazon ECS services, set this to the same name that the client application uses by default. For example, a few common names aredatabase,db, or the lowercase name of a database, such asmysqlorredis. For more information, see Service Connect in the Amazon Elastic Container Service Developer Guide. - port int
- The listening port number for the Service Connect proxy. This port is available inside of all of the tasks within the same namespace. To avoid changing your applications in client Amazon ECS services, set this to the same port that the client application uses by default. For more information, see Service Connect in the Amazon Elastic Container Service Developer Guide.
- dns
Name String - The
dnsNameis the name that you use in the applications of client tasks to connect to this service. The name must be a valid DNS name but doesn't need to be fully-qualified. The name can include up to 127 characters. The name can include lowercase letters, numbers, underscores (_), hyphens (-), and periods (.). The name can't start with a hyphen. If this parameter isn't specified, the default value ofdiscoveryName.namespaceis used. If thediscoveryNameisn't specified, the port mapping name from the task definition is used inportName.namespace. To avoid changing your applications in client Amazon ECS services, set this to the same name that the client application uses by default. For example, a few common names aredatabase,db, or the lowercase name of a database, such asmysqlorredis. For more information, see Service Connect in the Amazon Elastic Container Service Developer Guide. - port Number
- The listening port number for the Service Connect proxy. This port is available inside of all of the tasks within the same namespace. To avoid changing your applications in client Amazon ECS services, set this to the same port that the client application uses by default. For more information, see Service Connect in the Amazon Elastic Container Service Developer Guide.
ServiceConnectClientAliasResponse, ServiceConnectClientAliasResponseArgs
, ServiceConnectClientAliasResponseArgs
- Dns
Name string - The
dnsNameis the name that you use in the applications of client tasks to connect to this service. The name must be a valid DNS name but doesn't need to be fully-qualified. The name can include up to 127 characters. The name can include lowercase letters, numbers, underscores (_), hyphens (-), and periods (.). The name can't start with a hyphen. If this parameter isn't specified, the default value ofdiscoveryName.namespaceis used. If thediscoveryNameisn't specified, the port mapping name from the task definition is used inportName.namespace. To avoid changing your applications in client Amazon ECS services, set this to the same name that the client application uses by default. For example, a few common names aredatabase,db, or the lowercase name of a database, such asmysqlorredis. For more information, see Service Connect in the Amazon Elastic Container Service Developer Guide. - Port int
- The listening port number for the Service Connect proxy. This port is available inside of all of the tasks within the same namespace. To avoid changing your applications in client Amazon ECS services, set this to the same port that the client application uses by default. For more information, see Service Connect in the Amazon Elastic Container Service Developer Guide.
- Dns
Name string - The
dnsNameis the name that you use in the applications of client tasks to connect to this service. The name must be a valid DNS name but doesn't need to be fully-qualified. The name can include up to 127 characters. The name can include lowercase letters, numbers, underscores (_), hyphens (-), and periods (.). The name can't start with a hyphen. If this parameter isn't specified, the default value ofdiscoveryName.namespaceis used. If thediscoveryNameisn't specified, the port mapping name from the task definition is used inportName.namespace. To avoid changing your applications in client Amazon ECS services, set this to the same name that the client application uses by default. For example, a few common names aredatabase,db, or the lowercase name of a database, such asmysqlorredis. For more information, see Service Connect in the Amazon Elastic Container Service Developer Guide. - Port int
- The listening port number for the Service Connect proxy. This port is available inside of all of the tasks within the same namespace. To avoid changing your applications in client Amazon ECS services, set this to the same port that the client application uses by default. For more information, see Service Connect in the Amazon Elastic Container Service Developer Guide.
- dns
Name String - The
dnsNameis the name that you use in the applications of client tasks to connect to this service. The name must be a valid DNS name but doesn't need to be fully-qualified. The name can include up to 127 characters. The name can include lowercase letters, numbers, underscores (_), hyphens (-), and periods (.). The name can't start with a hyphen. If this parameter isn't specified, the default value ofdiscoveryName.namespaceis used. If thediscoveryNameisn't specified, the port mapping name from the task definition is used inportName.namespace. To avoid changing your applications in client Amazon ECS services, set this to the same name that the client application uses by default. For example, a few common names aredatabase,db, or the lowercase name of a database, such asmysqlorredis. For more information, see Service Connect in the Amazon Elastic Container Service Developer Guide. - port Integer
- The listening port number for the Service Connect proxy. This port is available inside of all of the tasks within the same namespace. To avoid changing your applications in client Amazon ECS services, set this to the same port that the client application uses by default. For more information, see Service Connect in the Amazon Elastic Container Service Developer Guide.
- dns
Name string - The
dnsNameis the name that you use in the applications of client tasks to connect to this service. The name must be a valid DNS name but doesn't need to be fully-qualified. The name can include up to 127 characters. The name can include lowercase letters, numbers, underscores (_), hyphens (-), and periods (.). The name can't start with a hyphen. If this parameter isn't specified, the default value ofdiscoveryName.namespaceis used. If thediscoveryNameisn't specified, the port mapping name from the task definition is used inportName.namespace. To avoid changing your applications in client Amazon ECS services, set this to the same name that the client application uses by default. For example, a few common names aredatabase,db, or the lowercase name of a database, such asmysqlorredis. For more information, see Service Connect in the Amazon Elastic Container Service Developer Guide. - port number
- The listening port number for the Service Connect proxy. This port is available inside of all of the tasks within the same namespace. To avoid changing your applications in client Amazon ECS services, set this to the same port that the client application uses by default. For more information, see Service Connect in the Amazon Elastic Container Service Developer Guide.
- dns_
name str - The
dnsNameis the name that you use in the applications of client tasks to connect to this service. The name must be a valid DNS name but doesn't need to be fully-qualified. The name can include up to 127 characters. The name can include lowercase letters, numbers, underscores (_), hyphens (-), and periods (.). The name can't start with a hyphen. If this parameter isn't specified, the default value ofdiscoveryName.namespaceis used. If thediscoveryNameisn't specified, the port mapping name from the task definition is used inportName.namespace. To avoid changing your applications in client Amazon ECS services, set this to the same name that the client application uses by default. For example, a few common names aredatabase,db, or the lowercase name of a database, such asmysqlorredis. For more information, see Service Connect in the Amazon Elastic Container Service Developer Guide. - port int
- The listening port number for the Service Connect proxy. This port is available inside of all of the tasks within the same namespace. To avoid changing your applications in client Amazon ECS services, set this to the same port that the client application uses by default. For more information, see Service Connect in the Amazon Elastic Container Service Developer Guide.
- dns
Name String - The
dnsNameis the name that you use in the applications of client tasks to connect to this service. The name must be a valid DNS name but doesn't need to be fully-qualified. The name can include up to 127 characters. The name can include lowercase letters, numbers, underscores (_), hyphens (-), and periods (.). The name can't start with a hyphen. If this parameter isn't specified, the default value ofdiscoveryName.namespaceis used. If thediscoveryNameisn't specified, the port mapping name from the task definition is used inportName.namespace. To avoid changing your applications in client Amazon ECS services, set this to the same name that the client application uses by default. For example, a few common names aredatabase,db, or the lowercase name of a database, such asmysqlorredis. For more information, see Service Connect in the Amazon Elastic Container Service Developer Guide. - port Number
- The listening port number for the Service Connect proxy. This port is available inside of all of the tasks within the same namespace. To avoid changing your applications in client Amazon ECS services, set this to the same port that the client application uses by default. For more information, see Service Connect in the Amazon Elastic Container Service Developer Guide.
ServiceConnectConfiguration, ServiceConnectConfigurationArgs
, ServiceConnectConfigurationArgs
- Enabled bool
- Specifies whether to use Service Connect with this service.
- Log
Configuration Pulumi.Azure Native. Aws Connector. Inputs. Log Configuration - The log configuration for the container. This parameter maps to
LogConfigin the Create a container section of the Docker Remote API and the--log-driveroption to docker run. By default, containers use the same logging driver that the Docker daemon uses. However, the container might use a different logging driver than the Docker daemon by specifying a log driver configuration in the container definition. For more information about the options for different supported log drivers, see Configure logging drivers in the Docker documentation. Understand the following when specifying a log configuration for your containers. + Amazon ECS currently supports a subset of the logging drivers available to the Docker daemon. Additional log drivers may be available in future releases of the Amazon ECS container agent. For tasks on FARGATElong, the supported log drivers areawslogs,splunk, andawsfirelens. For tasks hosted on Amazon EC2 instances, the supported log drivers areawslogs,fluentd,gelf,json-file,journald,logentries,syslog,splunk, andawsfirelens. + This parameter requires version 1.18 of the Docker Remote API or greater on your container instance. + For tasks that are hosted on Amazon EC2 instances, the Amazon ECS container agent must register the available logging drivers with theECS_AVAILABLE_LOGGING_DRIVERSenvironment variable before containers placed on that instance can use these log configuration options. For more information, see Amazon ECS container agent configuration in the Amazon Elastic Container Service Developer Guide. + For tasks that are on FARGATElong, because you don't have access to the underlying infrastructure your tasks are hosted on, any additional software needed must be installed outside of the task. For example, the Fluentd output aggregators or a remote host running Logstash to send Gelf logs to. The log configuration for the container. This parameter maps toLogConfigin the Create a container section of the Docker Remote API and the--log-driveroption to docker run. By default, containers use the same logging driver that the Docker daemon uses. However, the container might use a different logging driver than the Docker daemon by specifying a log driver configuration in the container definition. For more information about the options for different supported log drivers, see Configure logging drivers in the Docker documentation. Understand the following when specifying a log configuration for your containers. + Amazon ECS currently supports a subset of the logging drivers available to the Docker daemon. Additional log drivers may be available in future releases of the Amazon ECS container agent. For tasks on FARGATElong, the supported log drivers areawslogs,splunk, andawsfirelens. For tasks hosted on Amazon EC2 instances, the supported log drivers areawslogs,fluentd,gelf,json-file,journald,logentries,syslog,splunk, andawsfirelens. + This parameter requires version 1.18 of the Docker Remote API or greater on your container instance. + For tasks that are hosted on Amazon EC2 instances, the Amazon ECS container agent must register the available logging drivers with theECS_AVAILABLE_LOGGING_DRIVERSenvironment variable before containers placed on that instance can use these log configuration options. For more information, see Amazon ECS container agent configuration in the Amazon Elastic Container Service Developer Guide. + For tasks that are on FARGATElong, because you don't have access to the underlying infrastructure your tasks are hosted on, any additional software needed must be installed outside of the task. For example, the Fluentd output aggregators or a remote host running Logstash to send Gelf logs to. - Namespace string
- The namespace name or full Amazon Resource Name (ARN) of the CMAPlong namespace for use with Service Connect. The namespace must be in the same AWS Region as the Amazon ECS service and cluster. The type of namespace doesn't affect Service Connect. For more information about CMAPlong, see Working with Services in the Developer Guide.
- Services
List<Pulumi.
Azure Native. Aws Connector. Inputs. Service Connect Service> - The list of Service Connect service objects. These are names and aliases (also known as endpoints) that are used by other Amazon ECS services to connect to this service. This field is not required for a 'client' Amazon ECS service that's a member of a namespace only to connect to other services within the namespace. An example of this would be a frontend application that accepts incoming requests from either a load balancer that's attached to the service or by other means. An object selects a port from the task definition, assigns a name for the CMAPlong service, and a list of aliases (endpoints) and ports for client applications to refer to this service.
- Enabled bool
- Specifies whether to use Service Connect with this service.
- Log
Configuration LogConfiguration - The log configuration for the container. This parameter maps to
LogConfigin the Create a container section of the Docker Remote API and the--log-driveroption to docker run. By default, containers use the same logging driver that the Docker daemon uses. However, the container might use a different logging driver than the Docker daemon by specifying a log driver configuration in the container definition. For more information about the options for different supported log drivers, see Configure logging drivers in the Docker documentation. Understand the following when specifying a log configuration for your containers. + Amazon ECS currently supports a subset of the logging drivers available to the Docker daemon. Additional log drivers may be available in future releases of the Amazon ECS container agent. For tasks on FARGATElong, the supported log drivers areawslogs,splunk, andawsfirelens. For tasks hosted on Amazon EC2 instances, the supported log drivers areawslogs,fluentd,gelf,json-file,journald,logentries,syslog,splunk, andawsfirelens. + This parameter requires version 1.18 of the Docker Remote API or greater on your container instance. + For tasks that are hosted on Amazon EC2 instances, the Amazon ECS container agent must register the available logging drivers with theECS_AVAILABLE_LOGGING_DRIVERSenvironment variable before containers placed on that instance can use these log configuration options. For more information, see Amazon ECS container agent configuration in the Amazon Elastic Container Service Developer Guide. + For tasks that are on FARGATElong, because you don't have access to the underlying infrastructure your tasks are hosted on, any additional software needed must be installed outside of the task. For example, the Fluentd output aggregators or a remote host running Logstash to send Gelf logs to. The log configuration for the container. This parameter maps toLogConfigin the Create a container section of the Docker Remote API and the--log-driveroption to docker run. By default, containers use the same logging driver that the Docker daemon uses. However, the container might use a different logging driver than the Docker daemon by specifying a log driver configuration in the container definition. For more information about the options for different supported log drivers, see Configure logging drivers in the Docker documentation. Understand the following when specifying a log configuration for your containers. + Amazon ECS currently supports a subset of the logging drivers available to the Docker daemon. Additional log drivers may be available in future releases of the Amazon ECS container agent. For tasks on FARGATElong, the supported log drivers areawslogs,splunk, andawsfirelens. For tasks hosted on Amazon EC2 instances, the supported log drivers areawslogs,fluentd,gelf,json-file,journald,logentries,syslog,splunk, andawsfirelens. + This parameter requires version 1.18 of the Docker Remote API or greater on your container instance. + For tasks that are hosted on Amazon EC2 instances, the Amazon ECS container agent must register the available logging drivers with theECS_AVAILABLE_LOGGING_DRIVERSenvironment variable before containers placed on that instance can use these log configuration options. For more information, see Amazon ECS container agent configuration in the Amazon Elastic Container Service Developer Guide. + For tasks that are on FARGATElong, because you don't have access to the underlying infrastructure your tasks are hosted on, any additional software needed must be installed outside of the task. For example, the Fluentd output aggregators or a remote host running Logstash to send Gelf logs to. - Namespace string
- The namespace name or full Amazon Resource Name (ARN) of the CMAPlong namespace for use with Service Connect. The namespace must be in the same AWS Region as the Amazon ECS service and cluster. The type of namespace doesn't affect Service Connect. For more information about CMAPlong, see Working with Services in the Developer Guide.
- Services
[]Service
Connect Service - The list of Service Connect service objects. These are names and aliases (also known as endpoints) that are used by other Amazon ECS services to connect to this service. This field is not required for a 'client' Amazon ECS service that's a member of a namespace only to connect to other services within the namespace. An example of this would be a frontend application that accepts incoming requests from either a load balancer that's attached to the service or by other means. An object selects a port from the task definition, assigns a name for the CMAPlong service, and a list of aliases (endpoints) and ports for client applications to refer to this service.
- enabled Boolean
- Specifies whether to use Service Connect with this service.
- log
Configuration LogConfiguration - The log configuration for the container. This parameter maps to
LogConfigin the Create a container section of the Docker Remote API and the--log-driveroption to docker run. By default, containers use the same logging driver that the Docker daemon uses. However, the container might use a different logging driver than the Docker daemon by specifying a log driver configuration in the container definition. For more information about the options for different supported log drivers, see Configure logging drivers in the Docker documentation. Understand the following when specifying a log configuration for your containers. + Amazon ECS currently supports a subset of the logging drivers available to the Docker daemon. Additional log drivers may be available in future releases of the Amazon ECS container agent. For tasks on FARGATElong, the supported log drivers areawslogs,splunk, andawsfirelens. For tasks hosted on Amazon EC2 instances, the supported log drivers areawslogs,fluentd,gelf,json-file,journald,logentries,syslog,splunk, andawsfirelens. + This parameter requires version 1.18 of the Docker Remote API or greater on your container instance. + For tasks that are hosted on Amazon EC2 instances, the Amazon ECS container agent must register the available logging drivers with theECS_AVAILABLE_LOGGING_DRIVERSenvironment variable before containers placed on that instance can use these log configuration options. For more information, see Amazon ECS container agent configuration in the Amazon Elastic Container Service Developer Guide. + For tasks that are on FARGATElong, because you don't have access to the underlying infrastructure your tasks are hosted on, any additional software needed must be installed outside of the task. For example, the Fluentd output aggregators or a remote host running Logstash to send Gelf logs to. The log configuration for the container. This parameter maps toLogConfigin the Create a container section of the Docker Remote API and the--log-driveroption to docker run. By default, containers use the same logging driver that the Docker daemon uses. However, the container might use a different logging driver than the Docker daemon by specifying a log driver configuration in the container definition. For more information about the options for different supported log drivers, see Configure logging drivers in the Docker documentation. Understand the following when specifying a log configuration for your containers. + Amazon ECS currently supports a subset of the logging drivers available to the Docker daemon. Additional log drivers may be available in future releases of the Amazon ECS container agent. For tasks on FARGATElong, the supported log drivers areawslogs,splunk, andawsfirelens. For tasks hosted on Amazon EC2 instances, the supported log drivers areawslogs,fluentd,gelf,json-file,journald,logentries,syslog,splunk, andawsfirelens. + This parameter requires version 1.18 of the Docker Remote API or greater on your container instance. + For tasks that are hosted on Amazon EC2 instances, the Amazon ECS container agent must register the available logging drivers with theECS_AVAILABLE_LOGGING_DRIVERSenvironment variable before containers placed on that instance can use these log configuration options. For more information, see Amazon ECS container agent configuration in the Amazon Elastic Container Service Developer Guide. + For tasks that are on FARGATElong, because you don't have access to the underlying infrastructure your tasks are hosted on, any additional software needed must be installed outside of the task. For example, the Fluentd output aggregators or a remote host running Logstash to send Gelf logs to. - namespace String
- The namespace name or full Amazon Resource Name (ARN) of the CMAPlong namespace for use with Service Connect. The namespace must be in the same AWS Region as the Amazon ECS service and cluster. The type of namespace doesn't affect Service Connect. For more information about CMAPlong, see Working with Services in the Developer Guide.
- services
List<Service
Connect Service> - The list of Service Connect service objects. These are names and aliases (also known as endpoints) that are used by other Amazon ECS services to connect to this service. This field is not required for a 'client' Amazon ECS service that's a member of a namespace only to connect to other services within the namespace. An example of this would be a frontend application that accepts incoming requests from either a load balancer that's attached to the service or by other means. An object selects a port from the task definition, assigns a name for the CMAPlong service, and a list of aliases (endpoints) and ports for client applications to refer to this service.
- enabled boolean
- Specifies whether to use Service Connect with this service.
- log
Configuration LogConfiguration - The log configuration for the container. This parameter maps to
LogConfigin the Create a container section of the Docker Remote API and the--log-driveroption to docker run. By default, containers use the same logging driver that the Docker daemon uses. However, the container might use a different logging driver than the Docker daemon by specifying a log driver configuration in the container definition. For more information about the options for different supported log drivers, see Configure logging drivers in the Docker documentation. Understand the following when specifying a log configuration for your containers. + Amazon ECS currently supports a subset of the logging drivers available to the Docker daemon. Additional log drivers may be available in future releases of the Amazon ECS container agent. For tasks on FARGATElong, the supported log drivers areawslogs,splunk, andawsfirelens. For tasks hosted on Amazon EC2 instances, the supported log drivers areawslogs,fluentd,gelf,json-file,journald,logentries,syslog,splunk, andawsfirelens. + This parameter requires version 1.18 of the Docker Remote API or greater on your container instance. + For tasks that are hosted on Amazon EC2 instances, the Amazon ECS container agent must register the available logging drivers with theECS_AVAILABLE_LOGGING_DRIVERSenvironment variable before containers placed on that instance can use these log configuration options. For more information, see Amazon ECS container agent configuration in the Amazon Elastic Container Service Developer Guide. + For tasks that are on FARGATElong, because you don't have access to the underlying infrastructure your tasks are hosted on, any additional software needed must be installed outside of the task. For example, the Fluentd output aggregators or a remote host running Logstash to send Gelf logs to. The log configuration for the container. This parameter maps toLogConfigin the Create a container section of the Docker Remote API and the--log-driveroption to docker run. By default, containers use the same logging driver that the Docker daemon uses. However, the container might use a different logging driver than the Docker daemon by specifying a log driver configuration in the container definition. For more information about the options for different supported log drivers, see Configure logging drivers in the Docker documentation. Understand the following when specifying a log configuration for your containers. + Amazon ECS currently supports a subset of the logging drivers available to the Docker daemon. Additional log drivers may be available in future releases of the Amazon ECS container agent. For tasks on FARGATElong, the supported log drivers areawslogs,splunk, andawsfirelens. For tasks hosted on Amazon EC2 instances, the supported log drivers areawslogs,fluentd,gelf,json-file,journald,logentries,syslog,splunk, andawsfirelens. + This parameter requires version 1.18 of the Docker Remote API or greater on your container instance. + For tasks that are hosted on Amazon EC2 instances, the Amazon ECS container agent must register the available logging drivers with theECS_AVAILABLE_LOGGING_DRIVERSenvironment variable before containers placed on that instance can use these log configuration options. For more information, see Amazon ECS container agent configuration in the Amazon Elastic Container Service Developer Guide. + For tasks that are on FARGATElong, because you don't have access to the underlying infrastructure your tasks are hosted on, any additional software needed must be installed outside of the task. For example, the Fluentd output aggregators or a remote host running Logstash to send Gelf logs to. - namespace string
- The namespace name or full Amazon Resource Name (ARN) of the CMAPlong namespace for use with Service Connect. The namespace must be in the same AWS Region as the Amazon ECS service and cluster. The type of namespace doesn't affect Service Connect. For more information about CMAPlong, see Working with Services in the Developer Guide.
- services
Service
Connect Service[] - The list of Service Connect service objects. These are names and aliases (also known as endpoints) that are used by other Amazon ECS services to connect to this service. This field is not required for a 'client' Amazon ECS service that's a member of a namespace only to connect to other services within the namespace. An example of this would be a frontend application that accepts incoming requests from either a load balancer that's attached to the service or by other means. An object selects a port from the task definition, assigns a name for the CMAPlong service, and a list of aliases (endpoints) and ports for client applications to refer to this service.
- enabled bool
- Specifies whether to use Service Connect with this service.
- log_
configuration LogConfiguration - The log configuration for the container. This parameter maps to
LogConfigin the Create a container section of the Docker Remote API and the--log-driveroption to docker run. By default, containers use the same logging driver that the Docker daemon uses. However, the container might use a different logging driver than the Docker daemon by specifying a log driver configuration in the container definition. For more information about the options for different supported log drivers, see Configure logging drivers in the Docker documentation. Understand the following when specifying a log configuration for your containers. + Amazon ECS currently supports a subset of the logging drivers available to the Docker daemon. Additional log drivers may be available in future releases of the Amazon ECS container agent. For tasks on FARGATElong, the supported log drivers areawslogs,splunk, andawsfirelens. For tasks hosted on Amazon EC2 instances, the supported log drivers areawslogs,fluentd,gelf,json-file,journald,logentries,syslog,splunk, andawsfirelens. + This parameter requires version 1.18 of the Docker Remote API or greater on your container instance. + For tasks that are hosted on Amazon EC2 instances, the Amazon ECS container agent must register the available logging drivers with theECS_AVAILABLE_LOGGING_DRIVERSenvironment variable before containers placed on that instance can use these log configuration options. For more information, see Amazon ECS container agent configuration in the Amazon Elastic Container Service Developer Guide. + For tasks that are on FARGATElong, because you don't have access to the underlying infrastructure your tasks are hosted on, any additional software needed must be installed outside of the task. For example, the Fluentd output aggregators or a remote host running Logstash to send Gelf logs to. The log configuration for the container. This parameter maps toLogConfigin the Create a container section of the Docker Remote API and the--log-driveroption to docker run. By default, containers use the same logging driver that the Docker daemon uses. However, the container might use a different logging driver than the Docker daemon by specifying a log driver configuration in the container definition. For more information about the options for different supported log drivers, see Configure logging drivers in the Docker documentation. Understand the following when specifying a log configuration for your containers. + Amazon ECS currently supports a subset of the logging drivers available to the Docker daemon. Additional log drivers may be available in future releases of the Amazon ECS container agent. For tasks on FARGATElong, the supported log drivers areawslogs,splunk, andawsfirelens. For tasks hosted on Amazon EC2 instances, the supported log drivers areawslogs,fluentd,gelf,json-file,journald,logentries,syslog,splunk, andawsfirelens. + This parameter requires version 1.18 of the Docker Remote API or greater on your container instance. + For tasks that are hosted on Amazon EC2 instances, the Amazon ECS container agent must register the available logging drivers with theECS_AVAILABLE_LOGGING_DRIVERSenvironment variable before containers placed on that instance can use these log configuration options. For more information, see Amazon ECS container agent configuration in the Amazon Elastic Container Service Developer Guide. + For tasks that are on FARGATElong, because you don't have access to the underlying infrastructure your tasks are hosted on, any additional software needed must be installed outside of the task. For example, the Fluentd output aggregators or a remote host running Logstash to send Gelf logs to. - namespace str
- The namespace name or full Amazon Resource Name (ARN) of the CMAPlong namespace for use with Service Connect. The namespace must be in the same AWS Region as the Amazon ECS service and cluster. The type of namespace doesn't affect Service Connect. For more information about CMAPlong, see Working with Services in the Developer Guide.
- services
Sequence[Service
Connect Service] - The list of Service Connect service objects. These are names and aliases (also known as endpoints) that are used by other Amazon ECS services to connect to this service. This field is not required for a 'client' Amazon ECS service that's a member of a namespace only to connect to other services within the namespace. An example of this would be a frontend application that accepts incoming requests from either a load balancer that's attached to the service or by other means. An object selects a port from the task definition, assigns a name for the CMAPlong service, and a list of aliases (endpoints) and ports for client applications to refer to this service.
- enabled Boolean
- Specifies whether to use Service Connect with this service.
- log
Configuration Property Map - The log configuration for the container. This parameter maps to
LogConfigin the Create a container section of the Docker Remote API and the--log-driveroption to docker run. By default, containers use the same logging driver that the Docker daemon uses. However, the container might use a different logging driver than the Docker daemon by specifying a log driver configuration in the container definition. For more information about the options for different supported log drivers, see Configure logging drivers in the Docker documentation. Understand the following when specifying a log configuration for your containers. + Amazon ECS currently supports a subset of the logging drivers available to the Docker daemon. Additional log drivers may be available in future releases of the Amazon ECS container agent. For tasks on FARGATElong, the supported log drivers areawslogs,splunk, andawsfirelens. For tasks hosted on Amazon EC2 instances, the supported log drivers areawslogs,fluentd,gelf,json-file,journald,logentries,syslog,splunk, andawsfirelens. + This parameter requires version 1.18 of the Docker Remote API or greater on your container instance. + For tasks that are hosted on Amazon EC2 instances, the Amazon ECS container agent must register the available logging drivers with theECS_AVAILABLE_LOGGING_DRIVERSenvironment variable before containers placed on that instance can use these log configuration options. For more information, see Amazon ECS container agent configuration in the Amazon Elastic Container Service Developer Guide. + For tasks that are on FARGATElong, because you don't have access to the underlying infrastructure your tasks are hosted on, any additional software needed must be installed outside of the task. For example, the Fluentd output aggregators or a remote host running Logstash to send Gelf logs to. The log configuration for the container. This parameter maps toLogConfigin the Create a container section of the Docker Remote API and the--log-driveroption to docker run. By default, containers use the same logging driver that the Docker daemon uses. However, the container might use a different logging driver than the Docker daemon by specifying a log driver configuration in the container definition. For more information about the options for different supported log drivers, see Configure logging drivers in the Docker documentation. Understand the following when specifying a log configuration for your containers. + Amazon ECS currently supports a subset of the logging drivers available to the Docker daemon. Additional log drivers may be available in future releases of the Amazon ECS container agent. For tasks on FARGATElong, the supported log drivers areawslogs,splunk, andawsfirelens. For tasks hosted on Amazon EC2 instances, the supported log drivers areawslogs,fluentd,gelf,json-file,journald,logentries,syslog,splunk, andawsfirelens. + This parameter requires version 1.18 of the Docker Remote API or greater on your container instance. + For tasks that are hosted on Amazon EC2 instances, the Amazon ECS container agent must register the available logging drivers with theECS_AVAILABLE_LOGGING_DRIVERSenvironment variable before containers placed on that instance can use these log configuration options. For more information, see Amazon ECS container agent configuration in the Amazon Elastic Container Service Developer Guide. + For tasks that are on FARGATElong, because you don't have access to the underlying infrastructure your tasks are hosted on, any additional software needed must be installed outside of the task. For example, the Fluentd output aggregators or a remote host running Logstash to send Gelf logs to. - namespace String
- The namespace name or full Amazon Resource Name (ARN) of the CMAPlong namespace for use with Service Connect. The namespace must be in the same AWS Region as the Amazon ECS service and cluster. The type of namespace doesn't affect Service Connect. For more information about CMAPlong, see Working with Services in the Developer Guide.
- services List<Property Map>
- The list of Service Connect service objects. These are names and aliases (also known as endpoints) that are used by other Amazon ECS services to connect to this service. This field is not required for a 'client' Amazon ECS service that's a member of a namespace only to connect to other services within the namespace. An example of this would be a frontend application that accepts incoming requests from either a load balancer that's attached to the service or by other means. An object selects a port from the task definition, assigns a name for the CMAPlong service, and a list of aliases (endpoints) and ports for client applications to refer to this service.
ServiceConnectConfigurationResponse, ServiceConnectConfigurationResponseArgs
, ServiceConnectConfigurationResponseArgs
- Enabled bool
- Specifies whether to use Service Connect with this service.
- Log
Configuration Pulumi.Azure Native. Aws Connector. Inputs. Log Configuration Response - The log configuration for the container. This parameter maps to
LogConfigin the Create a container section of the Docker Remote API and the--log-driveroption to docker run. By default, containers use the same logging driver that the Docker daemon uses. However, the container might use a different logging driver than the Docker daemon by specifying a log driver configuration in the container definition. For more information about the options for different supported log drivers, see Configure logging drivers in the Docker documentation. Understand the following when specifying a log configuration for your containers. + Amazon ECS currently supports a subset of the logging drivers available to the Docker daemon. Additional log drivers may be available in future releases of the Amazon ECS container agent. For tasks on FARGATElong, the supported log drivers areawslogs,splunk, andawsfirelens. For tasks hosted on Amazon EC2 instances, the supported log drivers areawslogs,fluentd,gelf,json-file,journald,logentries,syslog,splunk, andawsfirelens. + This parameter requires version 1.18 of the Docker Remote API or greater on your container instance. + For tasks that are hosted on Amazon EC2 instances, the Amazon ECS container agent must register the available logging drivers with theECS_AVAILABLE_LOGGING_DRIVERSenvironment variable before containers placed on that instance can use these log configuration options. For more information, see Amazon ECS container agent configuration in the Amazon Elastic Container Service Developer Guide. + For tasks that are on FARGATElong, because you don't have access to the underlying infrastructure your tasks are hosted on, any additional software needed must be installed outside of the task. For example, the Fluentd output aggregators or a remote host running Logstash to send Gelf logs to. The log configuration for the container. This parameter maps toLogConfigin the Create a container section of the Docker Remote API and the--log-driveroption to docker run. By default, containers use the same logging driver that the Docker daemon uses. However, the container might use a different logging driver than the Docker daemon by specifying a log driver configuration in the container definition. For more information about the options for different supported log drivers, see Configure logging drivers in the Docker documentation. Understand the following when specifying a log configuration for your containers. + Amazon ECS currently supports a subset of the logging drivers available to the Docker daemon. Additional log drivers may be available in future releases of the Amazon ECS container agent. For tasks on FARGATElong, the supported log drivers areawslogs,splunk, andawsfirelens. For tasks hosted on Amazon EC2 instances, the supported log drivers areawslogs,fluentd,gelf,json-file,journald,logentries,syslog,splunk, andawsfirelens. + This parameter requires version 1.18 of the Docker Remote API or greater on your container instance. + For tasks that are hosted on Amazon EC2 instances, the Amazon ECS container agent must register the available logging drivers with theECS_AVAILABLE_LOGGING_DRIVERSenvironment variable before containers placed on that instance can use these log configuration options. For more information, see Amazon ECS container agent configuration in the Amazon Elastic Container Service Developer Guide. + For tasks that are on FARGATElong, because you don't have access to the underlying infrastructure your tasks are hosted on, any additional software needed must be installed outside of the task. For example, the Fluentd output aggregators or a remote host running Logstash to send Gelf logs to. - Namespace string
- The namespace name or full Amazon Resource Name (ARN) of the CMAPlong namespace for use with Service Connect. The namespace must be in the same AWS Region as the Amazon ECS service and cluster. The type of namespace doesn't affect Service Connect. For more information about CMAPlong, see Working with Services in the Developer Guide.
- Services
List<Pulumi.
Azure Native. Aws Connector. Inputs. Service Connect Service Response> - The list of Service Connect service objects. These are names and aliases (also known as endpoints) that are used by other Amazon ECS services to connect to this service. This field is not required for a 'client' Amazon ECS service that's a member of a namespace only to connect to other services within the namespace. An example of this would be a frontend application that accepts incoming requests from either a load balancer that's attached to the service or by other means. An object selects a port from the task definition, assigns a name for the CMAPlong service, and a list of aliases (endpoints) and ports for client applications to refer to this service.
- Enabled bool
- Specifies whether to use Service Connect with this service.
- Log
Configuration LogConfiguration Response - The log configuration for the container. This parameter maps to
LogConfigin the Create a container section of the Docker Remote API and the--log-driveroption to docker run. By default, containers use the same logging driver that the Docker daemon uses. However, the container might use a different logging driver than the Docker daemon by specifying a log driver configuration in the container definition. For more information about the options for different supported log drivers, see Configure logging drivers in the Docker documentation. Understand the following when specifying a log configuration for your containers. + Amazon ECS currently supports a subset of the logging drivers available to the Docker daemon. Additional log drivers may be available in future releases of the Amazon ECS container agent. For tasks on FARGATElong, the supported log drivers areawslogs,splunk, andawsfirelens. For tasks hosted on Amazon EC2 instances, the supported log drivers areawslogs,fluentd,gelf,json-file,journald,logentries,syslog,splunk, andawsfirelens. + This parameter requires version 1.18 of the Docker Remote API or greater on your container instance. + For tasks that are hosted on Amazon EC2 instances, the Amazon ECS container agent must register the available logging drivers with theECS_AVAILABLE_LOGGING_DRIVERSenvironment variable before containers placed on that instance can use these log configuration options. For more information, see Amazon ECS container agent configuration in the Amazon Elastic Container Service Developer Guide. + For tasks that are on FARGATElong, because you don't have access to the underlying infrastructure your tasks are hosted on, any additional software needed must be installed outside of the task. For example, the Fluentd output aggregators or a remote host running Logstash to send Gelf logs to. The log configuration for the container. This parameter maps toLogConfigin the Create a container section of the Docker Remote API and the--log-driveroption to docker run. By default, containers use the same logging driver that the Docker daemon uses. However, the container might use a different logging driver than the Docker daemon by specifying a log driver configuration in the container definition. For more information about the options for different supported log drivers, see Configure logging drivers in the Docker documentation. Understand the following when specifying a log configuration for your containers. + Amazon ECS currently supports a subset of the logging drivers available to the Docker daemon. Additional log drivers may be available in future releases of the Amazon ECS container agent. For tasks on FARGATElong, the supported log drivers areawslogs,splunk, andawsfirelens. For tasks hosted on Amazon EC2 instances, the supported log drivers areawslogs,fluentd,gelf,json-file,journald,logentries,syslog,splunk, andawsfirelens. + This parameter requires version 1.18 of the Docker Remote API or greater on your container instance. + For tasks that are hosted on Amazon EC2 instances, the Amazon ECS container agent must register the available logging drivers with theECS_AVAILABLE_LOGGING_DRIVERSenvironment variable before containers placed on that instance can use these log configuration options. For more information, see Amazon ECS container agent configuration in the Amazon Elastic Container Service Developer Guide. + For tasks that are on FARGATElong, because you don't have access to the underlying infrastructure your tasks are hosted on, any additional software needed must be installed outside of the task. For example, the Fluentd output aggregators or a remote host running Logstash to send Gelf logs to. - Namespace string
- The namespace name or full Amazon Resource Name (ARN) of the CMAPlong namespace for use with Service Connect. The namespace must be in the same AWS Region as the Amazon ECS service and cluster. The type of namespace doesn't affect Service Connect. For more information about CMAPlong, see Working with Services in the Developer Guide.
- Services
[]Service
Connect Service Response - The list of Service Connect service objects. These are names and aliases (also known as endpoints) that are used by other Amazon ECS services to connect to this service. This field is not required for a 'client' Amazon ECS service that's a member of a namespace only to connect to other services within the namespace. An example of this would be a frontend application that accepts incoming requests from either a load balancer that's attached to the service or by other means. An object selects a port from the task definition, assigns a name for the CMAPlong service, and a list of aliases (endpoints) and ports for client applications to refer to this service.
- enabled Boolean
- Specifies whether to use Service Connect with this service.
- log
Configuration LogConfiguration Response - The log configuration for the container. This parameter maps to
LogConfigin the Create a container section of the Docker Remote API and the--log-driveroption to docker run. By default, containers use the same logging driver that the Docker daemon uses. However, the container might use a different logging driver than the Docker daemon by specifying a log driver configuration in the container definition. For more information about the options for different supported log drivers, see Configure logging drivers in the Docker documentation. Understand the following when specifying a log configuration for your containers. + Amazon ECS currently supports a subset of the logging drivers available to the Docker daemon. Additional log drivers may be available in future releases of the Amazon ECS container agent. For tasks on FARGATElong, the supported log drivers areawslogs,splunk, andawsfirelens. For tasks hosted on Amazon EC2 instances, the supported log drivers areawslogs,fluentd,gelf,json-file,journald,logentries,syslog,splunk, andawsfirelens. + This parameter requires version 1.18 of the Docker Remote API or greater on your container instance. + For tasks that are hosted on Amazon EC2 instances, the Amazon ECS container agent must register the available logging drivers with theECS_AVAILABLE_LOGGING_DRIVERSenvironment variable before containers placed on that instance can use these log configuration options. For more information, see Amazon ECS container agent configuration in the Amazon Elastic Container Service Developer Guide. + For tasks that are on FARGATElong, because you don't have access to the underlying infrastructure your tasks are hosted on, any additional software needed must be installed outside of the task. For example, the Fluentd output aggregators or a remote host running Logstash to send Gelf logs to. The log configuration for the container. This parameter maps toLogConfigin the Create a container section of the Docker Remote API and the--log-driveroption to docker run. By default, containers use the same logging driver that the Docker daemon uses. However, the container might use a different logging driver than the Docker daemon by specifying a log driver configuration in the container definition. For more information about the options for different supported log drivers, see Configure logging drivers in the Docker documentation. Understand the following when specifying a log configuration for your containers. + Amazon ECS currently supports a subset of the logging drivers available to the Docker daemon. Additional log drivers may be available in future releases of the Amazon ECS container agent. For tasks on FARGATElong, the supported log drivers areawslogs,splunk, andawsfirelens. For tasks hosted on Amazon EC2 instances, the supported log drivers areawslogs,fluentd,gelf,json-file,journald,logentries,syslog,splunk, andawsfirelens. + This parameter requires version 1.18 of the Docker Remote API or greater on your container instance. + For tasks that are hosted on Amazon EC2 instances, the Amazon ECS container agent must register the available logging drivers with theECS_AVAILABLE_LOGGING_DRIVERSenvironment variable before containers placed on that instance can use these log configuration options. For more information, see Amazon ECS container agent configuration in the Amazon Elastic Container Service Developer Guide. + For tasks that are on FARGATElong, because you don't have access to the underlying infrastructure your tasks are hosted on, any additional software needed must be installed outside of the task. For example, the Fluentd output aggregators or a remote host running Logstash to send Gelf logs to. - namespace String
- The namespace name or full Amazon Resource Name (ARN) of the CMAPlong namespace for use with Service Connect. The namespace must be in the same AWS Region as the Amazon ECS service and cluster. The type of namespace doesn't affect Service Connect. For more information about CMAPlong, see Working with Services in the Developer Guide.
- services
List<Service
Connect Service Response> - The list of Service Connect service objects. These are names and aliases (also known as endpoints) that are used by other Amazon ECS services to connect to this service. This field is not required for a 'client' Amazon ECS service that's a member of a namespace only to connect to other services within the namespace. An example of this would be a frontend application that accepts incoming requests from either a load balancer that's attached to the service or by other means. An object selects a port from the task definition, assigns a name for the CMAPlong service, and a list of aliases (endpoints) and ports for client applications to refer to this service.
- enabled boolean
- Specifies whether to use Service Connect with this service.
- log
Configuration LogConfiguration Response - The log configuration for the container. This parameter maps to
LogConfigin the Create a container section of the Docker Remote API and the--log-driveroption to docker run. By default, containers use the same logging driver that the Docker daemon uses. However, the container might use a different logging driver than the Docker daemon by specifying a log driver configuration in the container definition. For more information about the options for different supported log drivers, see Configure logging drivers in the Docker documentation. Understand the following when specifying a log configuration for your containers. + Amazon ECS currently supports a subset of the logging drivers available to the Docker daemon. Additional log drivers may be available in future releases of the Amazon ECS container agent. For tasks on FARGATElong, the supported log drivers areawslogs,splunk, andawsfirelens. For tasks hosted on Amazon EC2 instances, the supported log drivers areawslogs,fluentd,gelf,json-file,journald,logentries,syslog,splunk, andawsfirelens. + This parameter requires version 1.18 of the Docker Remote API or greater on your container instance. + For tasks that are hosted on Amazon EC2 instances, the Amazon ECS container agent must register the available logging drivers with theECS_AVAILABLE_LOGGING_DRIVERSenvironment variable before containers placed on that instance can use these log configuration options. For more information, see Amazon ECS container agent configuration in the Amazon Elastic Container Service Developer Guide. + For tasks that are on FARGATElong, because you don't have access to the underlying infrastructure your tasks are hosted on, any additional software needed must be installed outside of the task. For example, the Fluentd output aggregators or a remote host running Logstash to send Gelf logs to. The log configuration for the container. This parameter maps toLogConfigin the Create a container section of the Docker Remote API and the--log-driveroption to docker run. By default, containers use the same logging driver that the Docker daemon uses. However, the container might use a different logging driver than the Docker daemon by specifying a log driver configuration in the container definition. For more information about the options for different supported log drivers, see Configure logging drivers in the Docker documentation. Understand the following when specifying a log configuration for your containers. + Amazon ECS currently supports a subset of the logging drivers available to the Docker daemon. Additional log drivers may be available in future releases of the Amazon ECS container agent. For tasks on FARGATElong, the supported log drivers areawslogs,splunk, andawsfirelens. For tasks hosted on Amazon EC2 instances, the supported log drivers areawslogs,fluentd,gelf,json-file,journald,logentries,syslog,splunk, andawsfirelens. + This parameter requires version 1.18 of the Docker Remote API or greater on your container instance. + For tasks that are hosted on Amazon EC2 instances, the Amazon ECS container agent must register the available logging drivers with theECS_AVAILABLE_LOGGING_DRIVERSenvironment variable before containers placed on that instance can use these log configuration options. For more information, see Amazon ECS container agent configuration in the Amazon Elastic Container Service Developer Guide. + For tasks that are on FARGATElong, because you don't have access to the underlying infrastructure your tasks are hosted on, any additional software needed must be installed outside of the task. For example, the Fluentd output aggregators or a remote host running Logstash to send Gelf logs to. - namespace string
- The namespace name or full Amazon Resource Name (ARN) of the CMAPlong namespace for use with Service Connect. The namespace must be in the same AWS Region as the Amazon ECS service and cluster. The type of namespace doesn't affect Service Connect. For more information about CMAPlong, see Working with Services in the Developer Guide.
- services
Service
Connect Service Response[] - The list of Service Connect service objects. These are names and aliases (also known as endpoints) that are used by other Amazon ECS services to connect to this service. This field is not required for a 'client' Amazon ECS service that's a member of a namespace only to connect to other services within the namespace. An example of this would be a frontend application that accepts incoming requests from either a load balancer that's attached to the service or by other means. An object selects a port from the task definition, assigns a name for the CMAPlong service, and a list of aliases (endpoints) and ports for client applications to refer to this service.
- enabled bool
- Specifies whether to use Service Connect with this service.
- log_
configuration LogConfiguration Response - The log configuration for the container. This parameter maps to
LogConfigin the Create a container section of the Docker Remote API and the--log-driveroption to docker run. By default, containers use the same logging driver that the Docker daemon uses. However, the container might use a different logging driver than the Docker daemon by specifying a log driver configuration in the container definition. For more information about the options for different supported log drivers, see Configure logging drivers in the Docker documentation. Understand the following when specifying a log configuration for your containers. + Amazon ECS currently supports a subset of the logging drivers available to the Docker daemon. Additional log drivers may be available in future releases of the Amazon ECS container agent. For tasks on FARGATElong, the supported log drivers areawslogs,splunk, andawsfirelens. For tasks hosted on Amazon EC2 instances, the supported log drivers areawslogs,fluentd,gelf,json-file,journald,logentries,syslog,splunk, andawsfirelens. + This parameter requires version 1.18 of the Docker Remote API or greater on your container instance. + For tasks that are hosted on Amazon EC2 instances, the Amazon ECS container agent must register the available logging drivers with theECS_AVAILABLE_LOGGING_DRIVERSenvironment variable before containers placed on that instance can use these log configuration options. For more information, see Amazon ECS container agent configuration in the Amazon Elastic Container Service Developer Guide. + For tasks that are on FARGATElong, because you don't have access to the underlying infrastructure your tasks are hosted on, any additional software needed must be installed outside of the task. For example, the Fluentd output aggregators or a remote host running Logstash to send Gelf logs to. The log configuration for the container. This parameter maps toLogConfigin the Create a container section of the Docker Remote API and the--log-driveroption to docker run. By default, containers use the same logging driver that the Docker daemon uses. However, the container might use a different logging driver than the Docker daemon by specifying a log driver configuration in the container definition. For more information about the options for different supported log drivers, see Configure logging drivers in the Docker documentation. Understand the following when specifying a log configuration for your containers. + Amazon ECS currently supports a subset of the logging drivers available to the Docker daemon. Additional log drivers may be available in future releases of the Amazon ECS container agent. For tasks on FARGATElong, the supported log drivers areawslogs,splunk, andawsfirelens. For tasks hosted on Amazon EC2 instances, the supported log drivers areawslogs,fluentd,gelf,json-file,journald,logentries,syslog,splunk, andawsfirelens. + This parameter requires version 1.18 of the Docker Remote API or greater on your container instance. + For tasks that are hosted on Amazon EC2 instances, the Amazon ECS container agent must register the available logging drivers with theECS_AVAILABLE_LOGGING_DRIVERSenvironment variable before containers placed on that instance can use these log configuration options. For more information, see Amazon ECS container agent configuration in the Amazon Elastic Container Service Developer Guide. + For tasks that are on FARGATElong, because you don't have access to the underlying infrastructure your tasks are hosted on, any additional software needed must be installed outside of the task. For example, the Fluentd output aggregators or a remote host running Logstash to send Gelf logs to. - namespace str
- The namespace name or full Amazon Resource Name (ARN) of the CMAPlong namespace for use with Service Connect. The namespace must be in the same AWS Region as the Amazon ECS service and cluster. The type of namespace doesn't affect Service Connect. For more information about CMAPlong, see Working with Services in the Developer Guide.
- services
Sequence[Service
Connect Service Response] - The list of Service Connect service objects. These are names and aliases (also known as endpoints) that are used by other Amazon ECS services to connect to this service. This field is not required for a 'client' Amazon ECS service that's a member of a namespace only to connect to other services within the namespace. An example of this would be a frontend application that accepts incoming requests from either a load balancer that's attached to the service or by other means. An object selects a port from the task definition, assigns a name for the CMAPlong service, and a list of aliases (endpoints) and ports for client applications to refer to this service.
- enabled Boolean
- Specifies whether to use Service Connect with this service.
- log
Configuration Property Map - The log configuration for the container. This parameter maps to
LogConfigin the Create a container section of the Docker Remote API and the--log-driveroption to docker run. By default, containers use the same logging driver that the Docker daemon uses. However, the container might use a different logging driver than the Docker daemon by specifying a log driver configuration in the container definition. For more information about the options for different supported log drivers, see Configure logging drivers in the Docker documentation. Understand the following when specifying a log configuration for your containers. + Amazon ECS currently supports a subset of the logging drivers available to the Docker daemon. Additional log drivers may be available in future releases of the Amazon ECS container agent. For tasks on FARGATElong, the supported log drivers areawslogs,splunk, andawsfirelens. For tasks hosted on Amazon EC2 instances, the supported log drivers areawslogs,fluentd,gelf,json-file,journald,logentries,syslog,splunk, andawsfirelens. + This parameter requires version 1.18 of the Docker Remote API or greater on your container instance. + For tasks that are hosted on Amazon EC2 instances, the Amazon ECS container agent must register the available logging drivers with theECS_AVAILABLE_LOGGING_DRIVERSenvironment variable before containers placed on that instance can use these log configuration options. For more information, see Amazon ECS container agent configuration in the Amazon Elastic Container Service Developer Guide. + For tasks that are on FARGATElong, because you don't have access to the underlying infrastructure your tasks are hosted on, any additional software needed must be installed outside of the task. For example, the Fluentd output aggregators or a remote host running Logstash to send Gelf logs to. The log configuration for the container. This parameter maps toLogConfigin the Create a container section of the Docker Remote API and the--log-driveroption to docker run. By default, containers use the same logging driver that the Docker daemon uses. However, the container might use a different logging driver than the Docker daemon by specifying a log driver configuration in the container definition. For more information about the options for different supported log drivers, see Configure logging drivers in the Docker documentation. Understand the following when specifying a log configuration for your containers. + Amazon ECS currently supports a subset of the logging drivers available to the Docker daemon. Additional log drivers may be available in future releases of the Amazon ECS container agent. For tasks on FARGATElong, the supported log drivers areawslogs,splunk, andawsfirelens. For tasks hosted on Amazon EC2 instances, the supported log drivers areawslogs,fluentd,gelf,json-file,journald,logentries,syslog,splunk, andawsfirelens. + This parameter requires version 1.18 of the Docker Remote API or greater on your container instance. + For tasks that are hosted on Amazon EC2 instances, the Amazon ECS container agent must register the available logging drivers with theECS_AVAILABLE_LOGGING_DRIVERSenvironment variable before containers placed on that instance can use these log configuration options. For more information, see Amazon ECS container agent configuration in the Amazon Elastic Container Service Developer Guide. + For tasks that are on FARGATElong, because you don't have access to the underlying infrastructure your tasks are hosted on, any additional software needed must be installed outside of the task. For example, the Fluentd output aggregators or a remote host running Logstash to send Gelf logs to. - namespace String
- The namespace name or full Amazon Resource Name (ARN) of the CMAPlong namespace for use with Service Connect. The namespace must be in the same AWS Region as the Amazon ECS service and cluster. The type of namespace doesn't affect Service Connect. For more information about CMAPlong, see Working with Services in the Developer Guide.
- services List<Property Map>
- The list of Service Connect service objects. These are names and aliases (also known as endpoints) that are used by other Amazon ECS services to connect to this service. This field is not required for a 'client' Amazon ECS service that's a member of a namespace only to connect to other services within the namespace. An example of this would be a frontend application that accepts incoming requests from either a load balancer that's attached to the service or by other means. An object selects a port from the task definition, assigns a name for the CMAPlong service, and a list of aliases (endpoints) and ports for client applications to refer to this service.
ServiceConnectService, ServiceConnectServiceArgs
, ServiceConnectServiceArgs
- Client
Aliases List<Pulumi.Azure Native. Aws Connector. Inputs. Service Connect Client Alias> - The list of client aliases for this Service Connect service. You use these to assign names that can be used by client applications. The maximum number of client aliases that you can have in this list is 1. Each alias ('endpoint') is a fully-qualified name and port number that other Amazon ECS tasks ('clients') can use to connect to this service. Each name and port mapping must be unique within the namespace. For each
ServiceConnectService, you must provide at least oneclientAliaswith oneport. - Discovery
Name string - The
discoveryNameis the name of the new CMAP service that Amazon ECS creates for this Amazon ECS service. This must be unique within the CMAP namespace. The name can contain up to 64 characters. The name can include lowercase letters, numbers, underscores (_), and hyphens (-). The name can't start with a hyphen. If thediscoveryNameisn't specified, the port mapping name from the task definition is used inportName.namespace. - Ingress
Port intOverride - The port number for the Service Connect proxy to listen on. Use the value of this field to bypass the proxy for traffic on the port number specified in the named
portMappingin the task definition of this application, and then use it in your VPC security groups to allow traffic into the proxy for this Amazon ECS service. Inawsvpcmode and Fargate, the default value is the container port number. The container port number is in theportMappingin the task definition. In bridge mode, the default value is the ephemeral port of the Service Connect proxy. - Port
Name string - The
portNamemust match the name of one of theportMappingsfrom all the containers in the task definition of this Amazon ECS service. - Timeout
Pulumi.
Azure Native. Aws Connector. Inputs. Timeout Configuration - A reference to an object that represents the configured timeouts for Service Connect. An object that represents the timeout configurations for Service Connect. If
idleTimeoutis set to a time that is less thanperRequestTimeout, the connection will close when theidleTimeoutis reached and not theperRequestTimeout. - Tls
Pulumi.
Azure Native. Aws Connector. Inputs. Service Connect Tls Configuration - A reference to an object that represents a Transport Layer Security (TLS) configuration. An object that represents the configuration for Service Connect TLS.
- Client
Aliases []ServiceConnect Client Alias - The list of client aliases for this Service Connect service. You use these to assign names that can be used by client applications. The maximum number of client aliases that you can have in this list is 1. Each alias ('endpoint') is a fully-qualified name and port number that other Amazon ECS tasks ('clients') can use to connect to this service. Each name and port mapping must be unique within the namespace. For each
ServiceConnectService, you must provide at least oneclientAliaswith oneport. - Discovery
Name string - The
discoveryNameis the name of the new CMAP service that Amazon ECS creates for this Amazon ECS service. This must be unique within the CMAP namespace. The name can contain up to 64 characters. The name can include lowercase letters, numbers, underscores (_), and hyphens (-). The name can't start with a hyphen. If thediscoveryNameisn't specified, the port mapping name from the task definition is used inportName.namespace. - Ingress
Port intOverride - The port number for the Service Connect proxy to listen on. Use the value of this field to bypass the proxy for traffic on the port number specified in the named
portMappingin the task definition of this application, and then use it in your VPC security groups to allow traffic into the proxy for this Amazon ECS service. Inawsvpcmode and Fargate, the default value is the container port number. The container port number is in theportMappingin the task definition. In bridge mode, the default value is the ephemeral port of the Service Connect proxy. - Port
Name string - The
portNamemust match the name of one of theportMappingsfrom all the containers in the task definition of this Amazon ECS service. - Timeout
Timeout
Configuration - A reference to an object that represents the configured timeouts for Service Connect. An object that represents the timeout configurations for Service Connect. If
idleTimeoutis set to a time that is less thanperRequestTimeout, the connection will close when theidleTimeoutis reached and not theperRequestTimeout. - Tls
Service
Connect Tls Configuration - A reference to an object that represents a Transport Layer Security (TLS) configuration. An object that represents the configuration for Service Connect TLS.
- client
Aliases List<ServiceConnect Client Alias> - The list of client aliases for this Service Connect service. You use these to assign names that can be used by client applications. The maximum number of client aliases that you can have in this list is 1. Each alias ('endpoint') is a fully-qualified name and port number that other Amazon ECS tasks ('clients') can use to connect to this service. Each name and port mapping must be unique within the namespace. For each
ServiceConnectService, you must provide at least oneclientAliaswith oneport. - discovery
Name String - The
discoveryNameis the name of the new CMAP service that Amazon ECS creates for this Amazon ECS service. This must be unique within the CMAP namespace. The name can contain up to 64 characters. The name can include lowercase letters, numbers, underscores (_), and hyphens (-). The name can't start with a hyphen. If thediscoveryNameisn't specified, the port mapping name from the task definition is used inportName.namespace. - ingress
Port IntegerOverride - The port number for the Service Connect proxy to listen on. Use the value of this field to bypass the proxy for traffic on the port number specified in the named
portMappingin the task definition of this application, and then use it in your VPC security groups to allow traffic into the proxy for this Amazon ECS service. Inawsvpcmode and Fargate, the default value is the container port number. The container port number is in theportMappingin the task definition. In bridge mode, the default value is the ephemeral port of the Service Connect proxy. - port
Name String - The
portNamemust match the name of one of theportMappingsfrom all the containers in the task definition of this Amazon ECS service. - timeout
Timeout
Configuration - A reference to an object that represents the configured timeouts for Service Connect. An object that represents the timeout configurations for Service Connect. If
idleTimeoutis set to a time that is less thanperRequestTimeout, the connection will close when theidleTimeoutis reached and not theperRequestTimeout. - tls
Service
Connect Tls Configuration - A reference to an object that represents a Transport Layer Security (TLS) configuration. An object that represents the configuration for Service Connect TLS.
- client
Aliases ServiceConnect Client Alias[] - The list of client aliases for this Service Connect service. You use these to assign names that can be used by client applications. The maximum number of client aliases that you can have in this list is 1. Each alias ('endpoint') is a fully-qualified name and port number that other Amazon ECS tasks ('clients') can use to connect to this service. Each name and port mapping must be unique within the namespace. For each
ServiceConnectService, you must provide at least oneclientAliaswith oneport. - discovery
Name string - The
discoveryNameis the name of the new CMAP service that Amazon ECS creates for this Amazon ECS service. This must be unique within the CMAP namespace. The name can contain up to 64 characters. The name can include lowercase letters, numbers, underscores (_), and hyphens (-). The name can't start with a hyphen. If thediscoveryNameisn't specified, the port mapping name from the task definition is used inportName.namespace. - ingress
Port numberOverride - The port number for the Service Connect proxy to listen on. Use the value of this field to bypass the proxy for traffic on the port number specified in the named
portMappingin the task definition of this application, and then use it in your VPC security groups to allow traffic into the proxy for this Amazon ECS service. Inawsvpcmode and Fargate, the default value is the container port number. The container port number is in theportMappingin the task definition. In bridge mode, the default value is the ephemeral port of the Service Connect proxy. - port
Name string - The
portNamemust match the name of one of theportMappingsfrom all the containers in the task definition of this Amazon ECS service. - timeout
Timeout
Configuration - A reference to an object that represents the configured timeouts for Service Connect. An object that represents the timeout configurations for Service Connect. If
idleTimeoutis set to a time that is less thanperRequestTimeout, the connection will close when theidleTimeoutis reached and not theperRequestTimeout. - tls
Service
Connect Tls Configuration - A reference to an object that represents a Transport Layer Security (TLS) configuration. An object that represents the configuration for Service Connect TLS.
- client_
aliases Sequence[ServiceConnect Client Alias] - The list of client aliases for this Service Connect service. You use these to assign names that can be used by client applications. The maximum number of client aliases that you can have in this list is 1. Each alias ('endpoint') is a fully-qualified name and port number that other Amazon ECS tasks ('clients') can use to connect to this service. Each name and port mapping must be unique within the namespace. For each
ServiceConnectService, you must provide at least oneclientAliaswith oneport. - discovery_
name str - The
discoveryNameis the name of the new CMAP service that Amazon ECS creates for this Amazon ECS service. This must be unique within the CMAP namespace. The name can contain up to 64 characters. The name can include lowercase letters, numbers, underscores (_), and hyphens (-). The name can't start with a hyphen. If thediscoveryNameisn't specified, the port mapping name from the task definition is used inportName.namespace. - ingress_
port_ intoverride - The port number for the Service Connect proxy to listen on. Use the value of this field to bypass the proxy for traffic on the port number specified in the named
portMappingin the task definition of this application, and then use it in your VPC security groups to allow traffic into the proxy for this Amazon ECS service. Inawsvpcmode and Fargate, the default value is the container port number. The container port number is in theportMappingin the task definition. In bridge mode, the default value is the ephemeral port of the Service Connect proxy. - port_
name str - The
portNamemust match the name of one of theportMappingsfrom all the containers in the task definition of this Amazon ECS service. - timeout
Timeout
Configuration - A reference to an object that represents the configured timeouts for Service Connect. An object that represents the timeout configurations for Service Connect. If
idleTimeoutis set to a time that is less thanperRequestTimeout, the connection will close when theidleTimeoutis reached and not theperRequestTimeout. - tls
Service
Connect Tls Configuration - A reference to an object that represents a Transport Layer Security (TLS) configuration. An object that represents the configuration for Service Connect TLS.
- client
Aliases List<Property Map> - The list of client aliases for this Service Connect service. You use these to assign names that can be used by client applications. The maximum number of client aliases that you can have in this list is 1. Each alias ('endpoint') is a fully-qualified name and port number that other Amazon ECS tasks ('clients') can use to connect to this service. Each name and port mapping must be unique within the namespace. For each
ServiceConnectService, you must provide at least oneclientAliaswith oneport. - discovery
Name String - The
discoveryNameis the name of the new CMAP service that Amazon ECS creates for this Amazon ECS service. This must be unique within the CMAP namespace. The name can contain up to 64 characters. The name can include lowercase letters, numbers, underscores (_), and hyphens (-). The name can't start with a hyphen. If thediscoveryNameisn't specified, the port mapping name from the task definition is used inportName.namespace. - ingress
Port NumberOverride - The port number for the Service Connect proxy to listen on. Use the value of this field to bypass the proxy for traffic on the port number specified in the named
portMappingin the task definition of this application, and then use it in your VPC security groups to allow traffic into the proxy for this Amazon ECS service. Inawsvpcmode and Fargate, the default value is the container port number. The container port number is in theportMappingin the task definition. In bridge mode, the default value is the ephemeral port of the Service Connect proxy. - port
Name String - The
portNamemust match the name of one of theportMappingsfrom all the containers in the task definition of this Amazon ECS service. - timeout Property Map
- A reference to an object that represents the configured timeouts for Service Connect. An object that represents the timeout configurations for Service Connect. If
idleTimeoutis set to a time that is less thanperRequestTimeout, the connection will close when theidleTimeoutis reached and not theperRequestTimeout. - tls Property Map
- A reference to an object that represents a Transport Layer Security (TLS) configuration. An object that represents the configuration for Service Connect TLS.
ServiceConnectServiceResponse, ServiceConnectServiceResponseArgs
, ServiceConnectServiceResponseArgs
- Client
Aliases List<Pulumi.Azure Native. Aws Connector. Inputs. Service Connect Client Alias Response> - The list of client aliases for this Service Connect service. You use these to assign names that can be used by client applications. The maximum number of client aliases that you can have in this list is 1. Each alias ('endpoint') is a fully-qualified name and port number that other Amazon ECS tasks ('clients') can use to connect to this service. Each name and port mapping must be unique within the namespace. For each
ServiceConnectService, you must provide at least oneclientAliaswith oneport. - Discovery
Name string - The
discoveryNameis the name of the new CMAP service that Amazon ECS creates for this Amazon ECS service. This must be unique within the CMAP namespace. The name can contain up to 64 characters. The name can include lowercase letters, numbers, underscores (_), and hyphens (-). The name can't start with a hyphen. If thediscoveryNameisn't specified, the port mapping name from the task definition is used inportName.namespace. - Ingress
Port intOverride - The port number for the Service Connect proxy to listen on. Use the value of this field to bypass the proxy for traffic on the port number specified in the named
portMappingin the task definition of this application, and then use it in your VPC security groups to allow traffic into the proxy for this Amazon ECS service. Inawsvpcmode and Fargate, the default value is the container port number. The container port number is in theportMappingin the task definition. In bridge mode, the default value is the ephemeral port of the Service Connect proxy. - Port
Name string - The
portNamemust match the name of one of theportMappingsfrom all the containers in the task definition of this Amazon ECS service. - Timeout
Pulumi.
Azure Native. Aws Connector. Inputs. Timeout Configuration Response - A reference to an object that represents the configured timeouts for Service Connect. An object that represents the timeout configurations for Service Connect. If
idleTimeoutis set to a time that is less thanperRequestTimeout, the connection will close when theidleTimeoutis reached and not theperRequestTimeout. - Tls
Pulumi.
Azure Native. Aws Connector. Inputs. Service Connect Tls Configuration Response - A reference to an object that represents a Transport Layer Security (TLS) configuration. An object that represents the configuration for Service Connect TLS.
- Client
Aliases []ServiceConnect Client Alias Response - The list of client aliases for this Service Connect service. You use these to assign names that can be used by client applications. The maximum number of client aliases that you can have in this list is 1. Each alias ('endpoint') is a fully-qualified name and port number that other Amazon ECS tasks ('clients') can use to connect to this service. Each name and port mapping must be unique within the namespace. For each
ServiceConnectService, you must provide at least oneclientAliaswith oneport. - Discovery
Name string - The
discoveryNameis the name of the new CMAP service that Amazon ECS creates for this Amazon ECS service. This must be unique within the CMAP namespace. The name can contain up to 64 characters. The name can include lowercase letters, numbers, underscores (_), and hyphens (-). The name can't start with a hyphen. If thediscoveryNameisn't specified, the port mapping name from the task definition is used inportName.namespace. - Ingress
Port intOverride - The port number for the Service Connect proxy to listen on. Use the value of this field to bypass the proxy for traffic on the port number specified in the named
portMappingin the task definition of this application, and then use it in your VPC security groups to allow traffic into the proxy for this Amazon ECS service. Inawsvpcmode and Fargate, the default value is the container port number. The container port number is in theportMappingin the task definition. In bridge mode, the default value is the ephemeral port of the Service Connect proxy. - Port
Name string - The
portNamemust match the name of one of theportMappingsfrom all the containers in the task definition of this Amazon ECS service. - Timeout
Timeout
Configuration Response - A reference to an object that represents the configured timeouts for Service Connect. An object that represents the timeout configurations for Service Connect. If
idleTimeoutis set to a time that is less thanperRequestTimeout, the connection will close when theidleTimeoutis reached and not theperRequestTimeout. - Tls
Service
Connect Tls Configuration Response - A reference to an object that represents a Transport Layer Security (TLS) configuration. An object that represents the configuration for Service Connect TLS.
- client
Aliases List<ServiceConnect Client Alias Response> - The list of client aliases for this Service Connect service. You use these to assign names that can be used by client applications. The maximum number of client aliases that you can have in this list is 1. Each alias ('endpoint') is a fully-qualified name and port number that other Amazon ECS tasks ('clients') can use to connect to this service. Each name and port mapping must be unique within the namespace. For each
ServiceConnectService, you must provide at least oneclientAliaswith oneport. - discovery
Name String - The
discoveryNameis the name of the new CMAP service that Amazon ECS creates for this Amazon ECS service. This must be unique within the CMAP namespace. The name can contain up to 64 characters. The name can include lowercase letters, numbers, underscores (_), and hyphens (-). The name can't start with a hyphen. If thediscoveryNameisn't specified, the port mapping name from the task definition is used inportName.namespace. - ingress
Port IntegerOverride - The port number for the Service Connect proxy to listen on. Use the value of this field to bypass the proxy for traffic on the port number specified in the named
portMappingin the task definition of this application, and then use it in your VPC security groups to allow traffic into the proxy for this Amazon ECS service. Inawsvpcmode and Fargate, the default value is the container port number. The container port number is in theportMappingin the task definition. In bridge mode, the default value is the ephemeral port of the Service Connect proxy. - port
Name String - The
portNamemust match the name of one of theportMappingsfrom all the containers in the task definition of this Amazon ECS service. - timeout
Timeout
Configuration Response - A reference to an object that represents the configured timeouts for Service Connect. An object that represents the timeout configurations for Service Connect. If
idleTimeoutis set to a time that is less thanperRequestTimeout, the connection will close when theidleTimeoutis reached and not theperRequestTimeout. - tls
Service
Connect Tls Configuration Response - A reference to an object that represents a Transport Layer Security (TLS) configuration. An object that represents the configuration for Service Connect TLS.
- client
Aliases ServiceConnect Client Alias Response[] - The list of client aliases for this Service Connect service. You use these to assign names that can be used by client applications. The maximum number of client aliases that you can have in this list is 1. Each alias ('endpoint') is a fully-qualified name and port number that other Amazon ECS tasks ('clients') can use to connect to this service. Each name and port mapping must be unique within the namespace. For each
ServiceConnectService, you must provide at least oneclientAliaswith oneport. - discovery
Name string - The
discoveryNameis the name of the new CMAP service that Amazon ECS creates for this Amazon ECS service. This must be unique within the CMAP namespace. The name can contain up to 64 characters. The name can include lowercase letters, numbers, underscores (_), and hyphens (-). The name can't start with a hyphen. If thediscoveryNameisn't specified, the port mapping name from the task definition is used inportName.namespace. - ingress
Port numberOverride - The port number for the Service Connect proxy to listen on. Use the value of this field to bypass the proxy for traffic on the port number specified in the named
portMappingin the task definition of this application, and then use it in your VPC security groups to allow traffic into the proxy for this Amazon ECS service. Inawsvpcmode and Fargate, the default value is the container port number. The container port number is in theportMappingin the task definition. In bridge mode, the default value is the ephemeral port of the Service Connect proxy. - port
Name string - The
portNamemust match the name of one of theportMappingsfrom all the containers in the task definition of this Amazon ECS service. - timeout
Timeout
Configuration Response - A reference to an object that represents the configured timeouts for Service Connect. An object that represents the timeout configurations for Service Connect. If
idleTimeoutis set to a time that is less thanperRequestTimeout, the connection will close when theidleTimeoutis reached and not theperRequestTimeout. - tls
Service
Connect Tls Configuration Response - A reference to an object that represents a Transport Layer Security (TLS) configuration. An object that represents the configuration for Service Connect TLS.
- client_
aliases Sequence[ServiceConnect Client Alias Response] - The list of client aliases for this Service Connect service. You use these to assign names that can be used by client applications. The maximum number of client aliases that you can have in this list is 1. Each alias ('endpoint') is a fully-qualified name and port number that other Amazon ECS tasks ('clients') can use to connect to this service. Each name and port mapping must be unique within the namespace. For each
ServiceConnectService, you must provide at least oneclientAliaswith oneport. - discovery_
name str - The
discoveryNameis the name of the new CMAP service that Amazon ECS creates for this Amazon ECS service. This must be unique within the CMAP namespace. The name can contain up to 64 characters. The name can include lowercase letters, numbers, underscores (_), and hyphens (-). The name can't start with a hyphen. If thediscoveryNameisn't specified, the port mapping name from the task definition is used inportName.namespace. - ingress_
port_ intoverride - The port number for the Service Connect proxy to listen on. Use the value of this field to bypass the proxy for traffic on the port number specified in the named
portMappingin the task definition of this application, and then use it in your VPC security groups to allow traffic into the proxy for this Amazon ECS service. Inawsvpcmode and Fargate, the default value is the container port number. The container port number is in theportMappingin the task definition. In bridge mode, the default value is the ephemeral port of the Service Connect proxy. - port_
name str - The
portNamemust match the name of one of theportMappingsfrom all the containers in the task definition of this Amazon ECS service. - timeout
Timeout
Configuration Response - A reference to an object that represents the configured timeouts for Service Connect. An object that represents the timeout configurations for Service Connect. If
idleTimeoutis set to a time that is less thanperRequestTimeout, the connection will close when theidleTimeoutis reached and not theperRequestTimeout. - tls
Service
Connect Tls Configuration Response - A reference to an object that represents a Transport Layer Security (TLS) configuration. An object that represents the configuration for Service Connect TLS.
- client
Aliases List<Property Map> - The list of client aliases for this Service Connect service. You use these to assign names that can be used by client applications. The maximum number of client aliases that you can have in this list is 1. Each alias ('endpoint') is a fully-qualified name and port number that other Amazon ECS tasks ('clients') can use to connect to this service. Each name and port mapping must be unique within the namespace. For each
ServiceConnectService, you must provide at least oneclientAliaswith oneport. - discovery
Name String - The
discoveryNameis the name of the new CMAP service that Amazon ECS creates for this Amazon ECS service. This must be unique within the CMAP namespace. The name can contain up to 64 characters. The name can include lowercase letters, numbers, underscores (_), and hyphens (-). The name can't start with a hyphen. If thediscoveryNameisn't specified, the port mapping name from the task definition is used inportName.namespace. - ingress
Port NumberOverride - The port number for the Service Connect proxy to listen on. Use the value of this field to bypass the proxy for traffic on the port number specified in the named
portMappingin the task definition of this application, and then use it in your VPC security groups to allow traffic into the proxy for this Amazon ECS service. Inawsvpcmode and Fargate, the default value is the container port number. The container port number is in theportMappingin the task definition. In bridge mode, the default value is the ephemeral port of the Service Connect proxy. - port
Name String - The
portNamemust match the name of one of theportMappingsfrom all the containers in the task definition of this Amazon ECS service. - timeout Property Map
- A reference to an object that represents the configured timeouts for Service Connect. An object that represents the timeout configurations for Service Connect. If
idleTimeoutis set to a time that is less thanperRequestTimeout, the connection will close when theidleTimeoutis reached and not theperRequestTimeout. - tls Property Map
- A reference to an object that represents a Transport Layer Security (TLS) configuration. An object that represents the configuration for Service Connect TLS.
ServiceConnectTlsCertificateAuthority, ServiceConnectTlsCertificateAuthorityArgs
, ServiceConnectTlsCertificateAuthorityArgs
- string
- The ARN of the AWS Private Certificate Authority certificate.
- string
- The ARN of the AWS Private Certificate Authority certificate.
- String
- The ARN of the AWS Private Certificate Authority certificate.
- string
- The ARN of the AWS Private Certificate Authority certificate.
- str
- The ARN of the AWS Private Certificate Authority certificate.
- String
- The ARN of the AWS Private Certificate Authority certificate.
ServiceConnectTlsCertificateAuthorityResponse, ServiceConnectTlsCertificateAuthorityResponseArgs
, ServiceConnectTlsCertificateAuthorityResponseArgs
- string
- The ARN of the AWS Private Certificate Authority certificate.
- string
- The ARN of the AWS Private Certificate Authority certificate.
- String
- The ARN of the AWS Private Certificate Authority certificate.
- string
- The ARN of the AWS Private Certificate Authority certificate.
- str
- The ARN of the AWS Private Certificate Authority certificate.
- String
- The ARN of the AWS Private Certificate Authority certificate.
ServiceConnectTlsConfiguration, ServiceConnectTlsConfigurationArgs
, ServiceConnectTlsConfigurationArgs
-
Pulumi.
Azure Native. Aws Connector. Inputs. Service Connect Tls Certificate Authority - The signer certificate authority. An object that represents the AWS Private Certificate Authority certificate.
- Kms
Key string - The AWS Key Management Service key.
- Role
Arn string - The Amazon Resource Name (ARN) of the IAM role that's associated with the Service Connect TLS.
-
Service
Connect Tls Certificate Authority - The signer certificate authority. An object that represents the AWS Private Certificate Authority certificate.
- Kms
Key string - The AWS Key Management Service key.
- Role
Arn string - The Amazon Resource Name (ARN) of the IAM role that's associated with the Service Connect TLS.
-
Service
Connect Tls Certificate Authority - The signer certificate authority. An object that represents the AWS Private Certificate Authority certificate.
- kms
Key String - The AWS Key Management Service key.
- role
Arn String - The Amazon Resource Name (ARN) of the IAM role that's associated with the Service Connect TLS.
-
Service
Connect Tls Certificate Authority - The signer certificate authority. An object that represents the AWS Private Certificate Authority certificate.
- kms
Key string - The AWS Key Management Service key.
- role
Arn string - The Amazon Resource Name (ARN) of the IAM role that's associated with the Service Connect TLS.
-
Service
Connect Tls Certificate Authority - The signer certificate authority. An object that represents the AWS Private Certificate Authority certificate.
- kms_
key str - The AWS Key Management Service key.
- role_
arn str - The Amazon Resource Name (ARN) of the IAM role that's associated with the Service Connect TLS.
- Property Map
- The signer certificate authority. An object that represents the AWS Private Certificate Authority certificate.
- kms
Key String - The AWS Key Management Service key.
- role
Arn String - The Amazon Resource Name (ARN) of the IAM role that's associated with the Service Connect TLS.
ServiceConnectTlsConfigurationResponse, ServiceConnectTlsConfigurationResponseArgs
, ServiceConnectTlsConfigurationResponseArgs
-
Pulumi.
Azure Native. Aws Connector. Inputs. Service Connect Tls Certificate Authority Response - The signer certificate authority. An object that represents the AWS Private Certificate Authority certificate.
- Kms
Key string - The AWS Key Management Service key.
- Role
Arn string - The Amazon Resource Name (ARN) of the IAM role that's associated with the Service Connect TLS.
-
Service
Connect Tls Certificate Authority Response - The signer certificate authority. An object that represents the AWS Private Certificate Authority certificate.
- Kms
Key string - The AWS Key Management Service key.
- Role
Arn string - The Amazon Resource Name (ARN) of the IAM role that's associated with the Service Connect TLS.
-
Service
Connect Tls Certificate Authority Response - The signer certificate authority. An object that represents the AWS Private Certificate Authority certificate.
- kms
Key String - The AWS Key Management Service key.
- role
Arn String - The Amazon Resource Name (ARN) of the IAM role that's associated with the Service Connect TLS.
-
Service
Connect Tls Certificate Authority Response - The signer certificate authority. An object that represents the AWS Private Certificate Authority certificate.
- kms
Key string - The AWS Key Management Service key.
- role
Arn string - The Amazon Resource Name (ARN) of the IAM role that's associated with the Service Connect TLS.
-
Service
Connect Tls Certificate Authority Response - The signer certificate authority. An object that represents the AWS Private Certificate Authority certificate.
- kms_
key str - The AWS Key Management Service key.
- role_
arn str - The Amazon Resource Name (ARN) of the IAM role that's associated with the Service Connect TLS.
- Property Map
- The signer certificate authority. An object that represents the AWS Private Certificate Authority certificate.
- kms
Key String - The AWS Key Management Service key.
- role
Arn String - The Amazon Resource Name (ARN) of the IAM role that's associated with the Service Connect TLS.
ServiceManagedEBSVolumeConfiguration, ServiceManagedEBSVolumeConfigurationArgs
, ServiceManagedEBSVolumeConfigurationArgs
- Encrypted bool
- Indicates whether the volume should be encrypted. If no value is specified, encryption is turned on by default. This parameter maps 1:1 with the
Encryptedparameter of the CreateVolume API in the Amazon EC2 API Reference. - Filesystem
Type string - The Linux filesystem type for the volume. For volumes created from a snapshot, you must specify the same filesystem type that the volume was using when the snapshot was created. If there is a filesystem type mismatch, the task will fail to start. The available filesystem types are
ext3,ext4, andxfs. If no value is specified, thexfsfilesystem type is used by default. - Iops int
- The number of I/O operations per second (IOPS). For
gp3,io1, andio2volumes, this represents the number of IOPS that are provisioned for the volume. Forgp2volumes, this represents the baseline performance of the volume and the rate at which the volume accumulates I/O credits for bursting. The following are the supported values for each volume type. +gp3: 3,000 - 16,000 IOPS +io1: 100 - 64,000 IOPS +io2: 100 - 256,000 IOPS This parameter is required forio1andio2volume types. The default forgp3volumes is3,000 IOPS. This parameter is not supported forst1,sc1, orstandardvolume types. This parameter maps 1:1 with theIopsparameter of the CreateVolume API in the Amazon EC2 API Reference. - Kms
Key stringId - The Amazon Resource Name (ARN) identifier of the AWS Key Management Service key to use for Amazon EBS encryption. When encryption is turned on and no AWS Key Management Service key is specified, the default AWS managed key for Amazon EBS volumes is used. This parameter maps 1:1 with the
KmsKeyIdparameter of the CreateVolume API in the Amazon EC2 API Reference. AWS authenticates the AWS Key Management Service key asynchronously. Therefore, if you specify an ID, alias, or ARN that is invalid, the action can appear to complete, but eventually fails. - Role
Arn string - The ARN of the IAM role to associate with this volume. This is the Amazon ECS infrastructure IAM role that is used to manage your AWS infrastructure. We recommend using the Amazon ECS-managed
AmazonECSInfrastructureRolePolicyForVolumesIAM policy with this role. For more information, see Amazon ECS infrastructure IAM role in the Amazon ECS Developer Guide. - Size
In intGi B - The size of the volume in GiB. You must specify either a volume size or a snapshot ID. If you specify a snapshot ID, the snapshot size is used for the volume size by default. You can optionally specify a volume size greater than or equal to the snapshot size. This parameter maps 1:1 with the
Sizeparameter of the CreateVolume API in the Amazon EC2 API Reference. The following are the supported volume size values for each volume type. +gp2andgp3: 1-16,384 +io1andio2: 4-16,384 +st1andsc1: 125-16,384 +standard: 1-1,024 - Snapshot
Id string - The snapshot that Amazon ECS uses to create the volume. You must specify either a snapshot ID or a volume size. This parameter maps 1:1 with the
SnapshotIdparameter of the CreateVolume API in the Amazon EC2 API Reference. -
List<Pulumi.
Azure Native. Aws Connector. Inputs. EBSTag Specification> - The tags to apply to the volume. Amazon ECS applies service-managed tags by default. This parameter maps 1:1 with the
TagSpecifications.Nparameter of the CreateVolume API in the Amazon EC2 API Reference. - Throughput int
- The throughput to provision for a volume, in MiB/s, with a maximum of 1,000 MiB/s. This parameter maps 1:1 with the
Throughputparameter of the CreateVolume API in the Amazon EC2 API Reference. This parameter is only supported for thegp3volume type. - Volume
Type string - The volume type. This parameter maps 1:1 with the
VolumeTypeparameter of the CreateVolume API in the Amazon EC2 API Reference. For more information, see Amazon EBS volume types in the Amazon EC2 User Guide. The following are the supported volume types. + General Purpose SSD:gp2|gp3+ Provisioned IOPS SSD:io1|io2+ Throughput Optimized HDD:st1+ Cold HDD:sc1+ Magnetic:standardThe magnetic volume type is not supported on Fargate.
- Encrypted bool
- Indicates whether the volume should be encrypted. If no value is specified, encryption is turned on by default. This parameter maps 1:1 with the
Encryptedparameter of the CreateVolume API in the Amazon EC2 API Reference. - Filesystem
Type string - The Linux filesystem type for the volume. For volumes created from a snapshot, you must specify the same filesystem type that the volume was using when the snapshot was created. If there is a filesystem type mismatch, the task will fail to start. The available filesystem types are
ext3,ext4, andxfs. If no value is specified, thexfsfilesystem type is used by default. - Iops int
- The number of I/O operations per second (IOPS). For
gp3,io1, andio2volumes, this represents the number of IOPS that are provisioned for the volume. Forgp2volumes, this represents the baseline performance of the volume and the rate at which the volume accumulates I/O credits for bursting. The following are the supported values for each volume type. +gp3: 3,000 - 16,000 IOPS +io1: 100 - 64,000 IOPS +io2: 100 - 256,000 IOPS This parameter is required forio1andio2volume types. The default forgp3volumes is3,000 IOPS. This parameter is not supported forst1,sc1, orstandardvolume types. This parameter maps 1:1 with theIopsparameter of the CreateVolume API in the Amazon EC2 API Reference. - Kms
Key stringId - The Amazon Resource Name (ARN) identifier of the AWS Key Management Service key to use for Amazon EBS encryption. When encryption is turned on and no AWS Key Management Service key is specified, the default AWS managed key for Amazon EBS volumes is used. This parameter maps 1:1 with the
KmsKeyIdparameter of the CreateVolume API in the Amazon EC2 API Reference. AWS authenticates the AWS Key Management Service key asynchronously. Therefore, if you specify an ID, alias, or ARN that is invalid, the action can appear to complete, but eventually fails. - Role
Arn string - The ARN of the IAM role to associate with this volume. This is the Amazon ECS infrastructure IAM role that is used to manage your AWS infrastructure. We recommend using the Amazon ECS-managed
AmazonECSInfrastructureRolePolicyForVolumesIAM policy with this role. For more information, see Amazon ECS infrastructure IAM role in the Amazon ECS Developer Guide. - Size
In intGi B - The size of the volume in GiB. You must specify either a volume size or a snapshot ID. If you specify a snapshot ID, the snapshot size is used for the volume size by default. You can optionally specify a volume size greater than or equal to the snapshot size. This parameter maps 1:1 with the
Sizeparameter of the CreateVolume API in the Amazon EC2 API Reference. The following are the supported volume size values for each volume type. +gp2andgp3: 1-16,384 +io1andio2: 4-16,384 +st1andsc1: 125-16,384 +standard: 1-1,024 - Snapshot
Id string - The snapshot that Amazon ECS uses to create the volume. You must specify either a snapshot ID or a volume size. This parameter maps 1:1 with the
SnapshotIdparameter of the CreateVolume API in the Amazon EC2 API Reference. -
[]EBSTag
Specification - The tags to apply to the volume. Amazon ECS applies service-managed tags by default. This parameter maps 1:1 with the
TagSpecifications.Nparameter of the CreateVolume API in the Amazon EC2 API Reference. - Throughput int
- The throughput to provision for a volume, in MiB/s, with a maximum of 1,000 MiB/s. This parameter maps 1:1 with the
Throughputparameter of the CreateVolume API in the Amazon EC2 API Reference. This parameter is only supported for thegp3volume type. - Volume
Type string - The volume type. This parameter maps 1:1 with the
VolumeTypeparameter of the CreateVolume API in the Amazon EC2 API Reference. For more information, see Amazon EBS volume types in the Amazon EC2 User Guide. The following are the supported volume types. + General Purpose SSD:gp2|gp3+ Provisioned IOPS SSD:io1|io2+ Throughput Optimized HDD:st1+ Cold HDD:sc1+ Magnetic:standardThe magnetic volume type is not supported on Fargate.
- encrypted Boolean
- Indicates whether the volume should be encrypted. If no value is specified, encryption is turned on by default. This parameter maps 1:1 with the
Encryptedparameter of the CreateVolume API in the Amazon EC2 API Reference. - filesystem
Type String - The Linux filesystem type for the volume. For volumes created from a snapshot, you must specify the same filesystem type that the volume was using when the snapshot was created. If there is a filesystem type mismatch, the task will fail to start. The available filesystem types are
ext3,ext4, andxfs. If no value is specified, thexfsfilesystem type is used by default. - iops Integer
- The number of I/O operations per second (IOPS). For
gp3,io1, andio2volumes, this represents the number of IOPS that are provisioned for the volume. Forgp2volumes, this represents the baseline performance of the volume and the rate at which the volume accumulates I/O credits for bursting. The following are the supported values for each volume type. +gp3: 3,000 - 16,000 IOPS +io1: 100 - 64,000 IOPS +io2: 100 - 256,000 IOPS This parameter is required forio1andio2volume types. The default forgp3volumes is3,000 IOPS. This parameter is not supported forst1,sc1, orstandardvolume types. This parameter maps 1:1 with theIopsparameter of the CreateVolume API in the Amazon EC2 API Reference. - kms
Key StringId - The Amazon Resource Name (ARN) identifier of the AWS Key Management Service key to use for Amazon EBS encryption. When encryption is turned on and no AWS Key Management Service key is specified, the default AWS managed key for Amazon EBS volumes is used. This parameter maps 1:1 with the
KmsKeyIdparameter of the CreateVolume API in the Amazon EC2 API Reference. AWS authenticates the AWS Key Management Service key asynchronously. Therefore, if you specify an ID, alias, or ARN that is invalid, the action can appear to complete, but eventually fails. - role
Arn String - The ARN of the IAM role to associate with this volume. This is the Amazon ECS infrastructure IAM role that is used to manage your AWS infrastructure. We recommend using the Amazon ECS-managed
AmazonECSInfrastructureRolePolicyForVolumesIAM policy with this role. For more information, see Amazon ECS infrastructure IAM role in the Amazon ECS Developer Guide. - size
In IntegerGi B - The size of the volume in GiB. You must specify either a volume size or a snapshot ID. If you specify a snapshot ID, the snapshot size is used for the volume size by default. You can optionally specify a volume size greater than or equal to the snapshot size. This parameter maps 1:1 with the
Sizeparameter of the CreateVolume API in the Amazon EC2 API Reference. The following are the supported volume size values for each volume type. +gp2andgp3: 1-16,384 +io1andio2: 4-16,384 +st1andsc1: 125-16,384 +standard: 1-1,024 - snapshot
Id String - The snapshot that Amazon ECS uses to create the volume. You must specify either a snapshot ID or a volume size. This parameter maps 1:1 with the
SnapshotIdparameter of the CreateVolume API in the Amazon EC2 API Reference. -
List<EBSTag
Specification> - The tags to apply to the volume. Amazon ECS applies service-managed tags by default. This parameter maps 1:1 with the
TagSpecifications.Nparameter of the CreateVolume API in the Amazon EC2 API Reference. - throughput Integer
- The throughput to provision for a volume, in MiB/s, with a maximum of 1,000 MiB/s. This parameter maps 1:1 with the
Throughputparameter of the CreateVolume API in the Amazon EC2 API Reference. This parameter is only supported for thegp3volume type. - volume
Type String - The volume type. This parameter maps 1:1 with the
VolumeTypeparameter of the CreateVolume API in the Amazon EC2 API Reference. For more information, see Amazon EBS volume types in the Amazon EC2 User Guide. The following are the supported volume types. + General Purpose SSD:gp2|gp3+ Provisioned IOPS SSD:io1|io2+ Throughput Optimized HDD:st1+ Cold HDD:sc1+ Magnetic:standardThe magnetic volume type is not supported on Fargate.
- encrypted boolean
- Indicates whether the volume should be encrypted. If no value is specified, encryption is turned on by default. This parameter maps 1:1 with the
Encryptedparameter of the CreateVolume API in the Amazon EC2 API Reference. - filesystem
Type string - The Linux filesystem type for the volume. For volumes created from a snapshot, you must specify the same filesystem type that the volume was using when the snapshot was created. If there is a filesystem type mismatch, the task will fail to start. The available filesystem types are
ext3,ext4, andxfs. If no value is specified, thexfsfilesystem type is used by default. - iops number
- The number of I/O operations per second (IOPS). For
gp3,io1, andio2volumes, this represents the number of IOPS that are provisioned for the volume. Forgp2volumes, this represents the baseline performance of the volume and the rate at which the volume accumulates I/O credits for bursting. The following are the supported values for each volume type. +gp3: 3,000 - 16,000 IOPS +io1: 100 - 64,000 IOPS +io2: 100 - 256,000 IOPS This parameter is required forio1andio2volume types. The default forgp3volumes is3,000 IOPS. This parameter is not supported forst1,sc1, orstandardvolume types. This parameter maps 1:1 with theIopsparameter of the CreateVolume API in the Amazon EC2 API Reference. - kms
Key stringId - The Amazon Resource Name (ARN) identifier of the AWS Key Management Service key to use for Amazon EBS encryption. When encryption is turned on and no AWS Key Management Service key is specified, the default AWS managed key for Amazon EBS volumes is used. This parameter maps 1:1 with the
KmsKeyIdparameter of the CreateVolume API in the Amazon EC2 API Reference. AWS authenticates the AWS Key Management Service key asynchronously. Therefore, if you specify an ID, alias, or ARN that is invalid, the action can appear to complete, but eventually fails. - role
Arn string - The ARN of the IAM role to associate with this volume. This is the Amazon ECS infrastructure IAM role that is used to manage your AWS infrastructure. We recommend using the Amazon ECS-managed
AmazonECSInfrastructureRolePolicyForVolumesIAM policy with this role. For more information, see Amazon ECS infrastructure IAM role in the Amazon ECS Developer Guide. - size
In numberGi B - The size of the volume in GiB. You must specify either a volume size or a snapshot ID. If you specify a snapshot ID, the snapshot size is used for the volume size by default. You can optionally specify a volume size greater than or equal to the snapshot size. This parameter maps 1:1 with the
Sizeparameter of the CreateVolume API in the Amazon EC2 API Reference. The following are the supported volume size values for each volume type. +gp2andgp3: 1-16,384 +io1andio2: 4-16,384 +st1andsc1: 125-16,384 +standard: 1-1,024 - snapshot
Id string - The snapshot that Amazon ECS uses to create the volume. You must specify either a snapshot ID or a volume size. This parameter maps 1:1 with the
SnapshotIdparameter of the CreateVolume API in the Amazon EC2 API Reference. -
EBSTag
Specification[] - The tags to apply to the volume. Amazon ECS applies service-managed tags by default. This parameter maps 1:1 with the
TagSpecifications.Nparameter of the CreateVolume API in the Amazon EC2 API Reference. - throughput number
- The throughput to provision for a volume, in MiB/s, with a maximum of 1,000 MiB/s. This parameter maps 1:1 with the
Throughputparameter of the CreateVolume API in the Amazon EC2 API Reference. This parameter is only supported for thegp3volume type. - volume
Type string - The volume type. This parameter maps 1:1 with the
VolumeTypeparameter of the CreateVolume API in the Amazon EC2 API Reference. For more information, see Amazon EBS volume types in the Amazon EC2 User Guide. The following are the supported volume types. + General Purpose SSD:gp2|gp3+ Provisioned IOPS SSD:io1|io2+ Throughput Optimized HDD:st1+ Cold HDD:sc1+ Magnetic:standardThe magnetic volume type is not supported on Fargate.
- encrypted bool
- Indicates whether the volume should be encrypted. If no value is specified, encryption is turned on by default. This parameter maps 1:1 with the
Encryptedparameter of the CreateVolume API in the Amazon EC2 API Reference. - filesystem_
type str - The Linux filesystem type for the volume. For volumes created from a snapshot, you must specify the same filesystem type that the volume was using when the snapshot was created. If there is a filesystem type mismatch, the task will fail to start. The available filesystem types are
ext3,ext4, andxfs. If no value is specified, thexfsfilesystem type is used by default. - iops int
- The number of I/O operations per second (IOPS). For
gp3,io1, andio2volumes, this represents the number of IOPS that are provisioned for the volume. Forgp2volumes, this represents the baseline performance of the volume and the rate at which the volume accumulates I/O credits for bursting. The following are the supported values for each volume type. +gp3: 3,000 - 16,000 IOPS +io1: 100 - 64,000 IOPS +io2: 100 - 256,000 IOPS This parameter is required forio1andio2volume types. The default forgp3volumes is3,000 IOPS. This parameter is not supported forst1,sc1, orstandardvolume types. This parameter maps 1:1 with theIopsparameter of the CreateVolume API in the Amazon EC2 API Reference. - kms_
key_ strid - The Amazon Resource Name (ARN) identifier of the AWS Key Management Service key to use for Amazon EBS encryption. When encryption is turned on and no AWS Key Management Service key is specified, the default AWS managed key for Amazon EBS volumes is used. This parameter maps 1:1 with the
KmsKeyIdparameter of the CreateVolume API in the Amazon EC2 API Reference. AWS authenticates the AWS Key Management Service key asynchronously. Therefore, if you specify an ID, alias, or ARN that is invalid, the action can appear to complete, but eventually fails. - role_
arn str - The ARN of the IAM role to associate with this volume. This is the Amazon ECS infrastructure IAM role that is used to manage your AWS infrastructure. We recommend using the Amazon ECS-managed
AmazonECSInfrastructureRolePolicyForVolumesIAM policy with this role. For more information, see Amazon ECS infrastructure IAM role in the Amazon ECS Developer Guide. - size_
in_ intgi_ b - The size of the volume in GiB. You must specify either a volume size or a snapshot ID. If you specify a snapshot ID, the snapshot size is used for the volume size by default. You can optionally specify a volume size greater than or equal to the snapshot size. This parameter maps 1:1 with the
Sizeparameter of the CreateVolume API in the Amazon EC2 API Reference. The following are the supported volume size values for each volume type. +gp2andgp3: 1-16,384 +io1andio2: 4-16,384 +st1andsc1: 125-16,384 +standard: 1-1,024 - snapshot_
id str - The snapshot that Amazon ECS uses to create the volume. You must specify either a snapshot ID or a volume size. This parameter maps 1:1 with the
SnapshotIdparameter of the CreateVolume API in the Amazon EC2 API Reference. - tag_
specifications Sequence[EBSTagSpecification] - The tags to apply to the volume. Amazon ECS applies service-managed tags by default. This parameter maps 1:1 with the
TagSpecifications.Nparameter of the CreateVolume API in the Amazon EC2 API Reference. - throughput int
- The throughput to provision for a volume, in MiB/s, with a maximum of 1,000 MiB/s. This parameter maps 1:1 with the
Throughputparameter of the CreateVolume API in the Amazon EC2 API Reference. This parameter is only supported for thegp3volume type. - volume_
type str - The volume type. This parameter maps 1:1 with the
VolumeTypeparameter of the CreateVolume API in the Amazon EC2 API Reference. For more information, see Amazon EBS volume types in the Amazon EC2 User Guide. The following are the supported volume types. + General Purpose SSD:gp2|gp3+ Provisioned IOPS SSD:io1|io2+ Throughput Optimized HDD:st1+ Cold HDD:sc1+ Magnetic:standardThe magnetic volume type is not supported on Fargate.
- encrypted Boolean
- Indicates whether the volume should be encrypted. If no value is specified, encryption is turned on by default. This parameter maps 1:1 with the
Encryptedparameter of the CreateVolume API in the Amazon EC2 API Reference. - filesystem
Type String - The Linux filesystem type for the volume. For volumes created from a snapshot, you must specify the same filesystem type that the volume was using when the snapshot was created. If there is a filesystem type mismatch, the task will fail to start. The available filesystem types are
ext3,ext4, andxfs. If no value is specified, thexfsfilesystem type is used by default. - iops Number
- The number of I/O operations per second (IOPS). For
gp3,io1, andio2volumes, this represents the number of IOPS that are provisioned for the volume. Forgp2volumes, this represents the baseline performance of the volume and the rate at which the volume accumulates I/O credits for bursting. The following are the supported values for each volume type. +gp3: 3,000 - 16,000 IOPS +io1: 100 - 64,000 IOPS +io2: 100 - 256,000 IOPS This parameter is required forio1andio2volume types. The default forgp3volumes is3,000 IOPS. This parameter is not supported forst1,sc1, orstandardvolume types. This parameter maps 1:1 with theIopsparameter of the CreateVolume API in the Amazon EC2 API Reference. - kms
Key StringId - The Amazon Resource Name (ARN) identifier of the AWS Key Management Service key to use for Amazon EBS encryption. When encryption is turned on and no AWS Key Management Service key is specified, the default AWS managed key for Amazon EBS volumes is used. This parameter maps 1:1 with the
KmsKeyIdparameter of the CreateVolume API in the Amazon EC2 API Reference. AWS authenticates the AWS Key Management Service key asynchronously. Therefore, if you specify an ID, alias, or ARN that is invalid, the action can appear to complete, but eventually fails. - role
Arn String - The ARN of the IAM role to associate with this volume. This is the Amazon ECS infrastructure IAM role that is used to manage your AWS infrastructure. We recommend using the Amazon ECS-managed
AmazonECSInfrastructureRolePolicyForVolumesIAM policy with this role. For more information, see Amazon ECS infrastructure IAM role in the Amazon ECS Developer Guide. - size
In NumberGi B - The size of the volume in GiB. You must specify either a volume size or a snapshot ID. If you specify a snapshot ID, the snapshot size is used for the volume size by default. You can optionally specify a volume size greater than or equal to the snapshot size. This parameter maps 1:1 with the
Sizeparameter of the CreateVolume API in the Amazon EC2 API Reference. The following are the supported volume size values for each volume type. +gp2andgp3: 1-16,384 +io1andio2: 4-16,384 +st1andsc1: 125-16,384 +standard: 1-1,024 - snapshot
Id String - The snapshot that Amazon ECS uses to create the volume. You must specify either a snapshot ID or a volume size. This parameter maps 1:1 with the
SnapshotIdparameter of the CreateVolume API in the Amazon EC2 API Reference. - List<Property Map>
- The tags to apply to the volume. Amazon ECS applies service-managed tags by default. This parameter maps 1:1 with the
TagSpecifications.Nparameter of the CreateVolume API in the Amazon EC2 API Reference. - throughput Number
- The throughput to provision for a volume, in MiB/s, with a maximum of 1,000 MiB/s. This parameter maps 1:1 with the
Throughputparameter of the CreateVolume API in the Amazon EC2 API Reference. This parameter is only supported for thegp3volume type. - volume
Type String - The volume type. This parameter maps 1:1 with the
VolumeTypeparameter of the CreateVolume API in the Amazon EC2 API Reference. For more information, see Amazon EBS volume types in the Amazon EC2 User Guide. The following are the supported volume types. + General Purpose SSD:gp2|gp3+ Provisioned IOPS SSD:io1|io2+ Throughput Optimized HDD:st1+ Cold HDD:sc1+ Magnetic:standardThe magnetic volume type is not supported on Fargate.
ServiceManagedEBSVolumeConfigurationResponse, ServiceManagedEBSVolumeConfigurationResponseArgs
, ServiceManagedEBSVolumeConfigurationResponseArgs
- Encrypted bool
- Indicates whether the volume should be encrypted. If no value is specified, encryption is turned on by default. This parameter maps 1:1 with the
Encryptedparameter of the CreateVolume API in the Amazon EC2 API Reference. - Filesystem
Type string - The Linux filesystem type for the volume. For volumes created from a snapshot, you must specify the same filesystem type that the volume was using when the snapshot was created. If there is a filesystem type mismatch, the task will fail to start. The available filesystem types are
ext3,ext4, andxfs. If no value is specified, thexfsfilesystem type is used by default. - Iops int
- The number of I/O operations per second (IOPS). For
gp3,io1, andio2volumes, this represents the number of IOPS that are provisioned for the volume. Forgp2volumes, this represents the baseline performance of the volume and the rate at which the volume accumulates I/O credits for bursting. The following are the supported values for each volume type. +gp3: 3,000 - 16,000 IOPS +io1: 100 - 64,000 IOPS +io2: 100 - 256,000 IOPS This parameter is required forio1andio2volume types. The default forgp3volumes is3,000 IOPS. This parameter is not supported forst1,sc1, orstandardvolume types. This parameter maps 1:1 with theIopsparameter of the CreateVolume API in the Amazon EC2 API Reference. - Kms
Key stringId - The Amazon Resource Name (ARN) identifier of the AWS Key Management Service key to use for Amazon EBS encryption. When encryption is turned on and no AWS Key Management Service key is specified, the default AWS managed key for Amazon EBS volumes is used. This parameter maps 1:1 with the
KmsKeyIdparameter of the CreateVolume API in the Amazon EC2 API Reference. AWS authenticates the AWS Key Management Service key asynchronously. Therefore, if you specify an ID, alias, or ARN that is invalid, the action can appear to complete, but eventually fails. - Role
Arn string - The ARN of the IAM role to associate with this volume. This is the Amazon ECS infrastructure IAM role that is used to manage your AWS infrastructure. We recommend using the Amazon ECS-managed
AmazonECSInfrastructureRolePolicyForVolumesIAM policy with this role. For more information, see Amazon ECS infrastructure IAM role in the Amazon ECS Developer Guide. - Size
In intGi B - The size of the volume in GiB. You must specify either a volume size or a snapshot ID. If you specify a snapshot ID, the snapshot size is used for the volume size by default. You can optionally specify a volume size greater than or equal to the snapshot size. This parameter maps 1:1 with the
Sizeparameter of the CreateVolume API in the Amazon EC2 API Reference. The following are the supported volume size values for each volume type. +gp2andgp3: 1-16,384 +io1andio2: 4-16,384 +st1andsc1: 125-16,384 +standard: 1-1,024 - Snapshot
Id string - The snapshot that Amazon ECS uses to create the volume. You must specify either a snapshot ID or a volume size. This parameter maps 1:1 with the
SnapshotIdparameter of the CreateVolume API in the Amazon EC2 API Reference. -
List<Pulumi.
Azure Native. Aws Connector. Inputs. EBSTag Specification Response> - The tags to apply to the volume. Amazon ECS applies service-managed tags by default. This parameter maps 1:1 with the
TagSpecifications.Nparameter of the CreateVolume API in the Amazon EC2 API Reference. - Throughput int
- The throughput to provision for a volume, in MiB/s, with a maximum of 1,000 MiB/s. This parameter maps 1:1 with the
Throughputparameter of the CreateVolume API in the Amazon EC2 API Reference. This parameter is only supported for thegp3volume type. - Volume
Type string - The volume type. This parameter maps 1:1 with the
VolumeTypeparameter of the CreateVolume API in the Amazon EC2 API Reference. For more information, see Amazon EBS volume types in the Amazon EC2 User Guide. The following are the supported volume types. + General Purpose SSD:gp2|gp3+ Provisioned IOPS SSD:io1|io2+ Throughput Optimized HDD:st1+ Cold HDD:sc1+ Magnetic:standardThe magnetic volume type is not supported on Fargate.
- Encrypted bool
- Indicates whether the volume should be encrypted. If no value is specified, encryption is turned on by default. This parameter maps 1:1 with the
Encryptedparameter of the CreateVolume API in the Amazon EC2 API Reference. - Filesystem
Type string - The Linux filesystem type for the volume. For volumes created from a snapshot, you must specify the same filesystem type that the volume was using when the snapshot was created. If there is a filesystem type mismatch, the task will fail to start. The available filesystem types are
ext3,ext4, andxfs. If no value is specified, thexfsfilesystem type is used by default. - Iops int
- The number of I/O operations per second (IOPS). For
gp3,io1, andio2volumes, this represents the number of IOPS that are provisioned for the volume. Forgp2volumes, this represents the baseline performance of the volume and the rate at which the volume accumulates I/O credits for bursting. The following are the supported values for each volume type. +gp3: 3,000 - 16,000 IOPS +io1: 100 - 64,000 IOPS +io2: 100 - 256,000 IOPS This parameter is required forio1andio2volume types. The default forgp3volumes is3,000 IOPS. This parameter is not supported forst1,sc1, orstandardvolume types. This parameter maps 1:1 with theIopsparameter of the CreateVolume API in the Amazon EC2 API Reference. - Kms
Key stringId - The Amazon Resource Name (ARN) identifier of the AWS Key Management Service key to use for Amazon EBS encryption. When encryption is turned on and no AWS Key Management Service key is specified, the default AWS managed key for Amazon EBS volumes is used. This parameter maps 1:1 with the
KmsKeyIdparameter of the CreateVolume API in the Amazon EC2 API Reference. AWS authenticates the AWS Key Management Service key asynchronously. Therefore, if you specify an ID, alias, or ARN that is invalid, the action can appear to complete, but eventually fails. - Role
Arn string - The ARN of the IAM role to associate with this volume. This is the Amazon ECS infrastructure IAM role that is used to manage your AWS infrastructure. We recommend using the Amazon ECS-managed
AmazonECSInfrastructureRolePolicyForVolumesIAM policy with this role. For more information, see Amazon ECS infrastructure IAM role in the Amazon ECS Developer Guide. - Size
In intGi B - The size of the volume in GiB. You must specify either a volume size or a snapshot ID. If you specify a snapshot ID, the snapshot size is used for the volume size by default. You can optionally specify a volume size greater than or equal to the snapshot size. This parameter maps 1:1 with the
Sizeparameter of the CreateVolume API in the Amazon EC2 API Reference. The following are the supported volume size values for each volume type. +gp2andgp3: 1-16,384 +io1andio2: 4-16,384 +st1andsc1: 125-16,384 +standard: 1-1,024 - Snapshot
Id string - The snapshot that Amazon ECS uses to create the volume. You must specify either a snapshot ID or a volume size. This parameter maps 1:1 with the
SnapshotIdparameter of the CreateVolume API in the Amazon EC2 API Reference. -
[]EBSTag
Specification Response - The tags to apply to the volume. Amazon ECS applies service-managed tags by default. This parameter maps 1:1 with the
TagSpecifications.Nparameter of the CreateVolume API in the Amazon EC2 API Reference. - Throughput int
- The throughput to provision for a volume, in MiB/s, with a maximum of 1,000 MiB/s. This parameter maps 1:1 with the
Throughputparameter of the CreateVolume API in the Amazon EC2 API Reference. This parameter is only supported for thegp3volume type. - Volume
Type string - The volume type. This parameter maps 1:1 with the
VolumeTypeparameter of the CreateVolume API in the Amazon EC2 API Reference. For more information, see Amazon EBS volume types in the Amazon EC2 User Guide. The following are the supported volume types. + General Purpose SSD:gp2|gp3+ Provisioned IOPS SSD:io1|io2+ Throughput Optimized HDD:st1+ Cold HDD:sc1+ Magnetic:standardThe magnetic volume type is not supported on Fargate.
- encrypted Boolean
- Indicates whether the volume should be encrypted. If no value is specified, encryption is turned on by default. This parameter maps 1:1 with the
Encryptedparameter of the CreateVolume API in the Amazon EC2 API Reference. - filesystem
Type String - The Linux filesystem type for the volume. For volumes created from a snapshot, you must specify the same filesystem type that the volume was using when the snapshot was created. If there is a filesystem type mismatch, the task will fail to start. The available filesystem types are
ext3,ext4, andxfs. If no value is specified, thexfsfilesystem type is used by default. - iops Integer
- The number of I/O operations per second (IOPS). For
gp3,io1, andio2volumes, this represents the number of IOPS that are provisioned for the volume. Forgp2volumes, this represents the baseline performance of the volume and the rate at which the volume accumulates I/O credits for bursting. The following are the supported values for each volume type. +gp3: 3,000 - 16,000 IOPS +io1: 100 - 64,000 IOPS +io2: 100 - 256,000 IOPS This parameter is required forio1andio2volume types. The default forgp3volumes is3,000 IOPS. This parameter is not supported forst1,sc1, orstandardvolume types. This parameter maps 1:1 with theIopsparameter of the CreateVolume API in the Amazon EC2 API Reference. - kms
Key StringId - The Amazon Resource Name (ARN) identifier of the AWS Key Management Service key to use for Amazon EBS encryption. When encryption is turned on and no AWS Key Management Service key is specified, the default AWS managed key for Amazon EBS volumes is used. This parameter maps 1:1 with the
KmsKeyIdparameter of the CreateVolume API in the Amazon EC2 API Reference. AWS authenticates the AWS Key Management Service key asynchronously. Therefore, if you specify an ID, alias, or ARN that is invalid, the action can appear to complete, but eventually fails. - role
Arn String - The ARN of the IAM role to associate with this volume. This is the Amazon ECS infrastructure IAM role that is used to manage your AWS infrastructure. We recommend using the Amazon ECS-managed
AmazonECSInfrastructureRolePolicyForVolumesIAM policy with this role. For more information, see Amazon ECS infrastructure IAM role in the Amazon ECS Developer Guide. - size
In IntegerGi B - The size of the volume in GiB. You must specify either a volume size or a snapshot ID. If you specify a snapshot ID, the snapshot size is used for the volume size by default. You can optionally specify a volume size greater than or equal to the snapshot size. This parameter maps 1:1 with the
Sizeparameter of the CreateVolume API in the Amazon EC2 API Reference. The following are the supported volume size values for each volume type. +gp2andgp3: 1-16,384 +io1andio2: 4-16,384 +st1andsc1: 125-16,384 +standard: 1-1,024 - snapshot
Id String - The snapshot that Amazon ECS uses to create the volume. You must specify either a snapshot ID or a volume size. This parameter maps 1:1 with the
SnapshotIdparameter of the CreateVolume API in the Amazon EC2 API Reference. -
List<EBSTag
Specification Response> - The tags to apply to the volume. Amazon ECS applies service-managed tags by default. This parameter maps 1:1 with the
TagSpecifications.Nparameter of the CreateVolume API in the Amazon EC2 API Reference. - throughput Integer
- The throughput to provision for a volume, in MiB/s, with a maximum of 1,000 MiB/s. This parameter maps 1:1 with the
Throughputparameter of the CreateVolume API in the Amazon EC2 API Reference. This parameter is only supported for thegp3volume type. - volume
Type String - The volume type. This parameter maps 1:1 with the
VolumeTypeparameter of the CreateVolume API in the Amazon EC2 API Reference. For more information, see Amazon EBS volume types in the Amazon EC2 User Guide. The following are the supported volume types. + General Purpose SSD:gp2|gp3+ Provisioned IOPS SSD:io1|io2+ Throughput Optimized HDD:st1+ Cold HDD:sc1+ Magnetic:standardThe magnetic volume type is not supported on Fargate.
- encrypted boolean
- Indicates whether the volume should be encrypted. If no value is specified, encryption is turned on by default. This parameter maps 1:1 with the
Encryptedparameter of the CreateVolume API in the Amazon EC2 API Reference. - filesystem
Type string - The Linux filesystem type for the volume. For volumes created from a snapshot, you must specify the same filesystem type that the volume was using when the snapshot was created. If there is a filesystem type mismatch, the task will fail to start. The available filesystem types are
ext3,ext4, andxfs. If no value is specified, thexfsfilesystem type is used by default. - iops number
- The number of I/O operations per second (IOPS). For
gp3,io1, andio2volumes, this represents the number of IOPS that are provisioned for the volume. Forgp2volumes, this represents the baseline performance of the volume and the rate at which the volume accumulates I/O credits for bursting. The following are the supported values for each volume type. +gp3: 3,000 - 16,000 IOPS +io1: 100 - 64,000 IOPS +io2: 100 - 256,000 IOPS This parameter is required forio1andio2volume types. The default forgp3volumes is3,000 IOPS. This parameter is not supported forst1,sc1, orstandardvolume types. This parameter maps 1:1 with theIopsparameter of the CreateVolume API in the Amazon EC2 API Reference. - kms
Key stringId - The Amazon Resource Name (ARN) identifier of the AWS Key Management Service key to use for Amazon EBS encryption. When encryption is turned on and no AWS Key Management Service key is specified, the default AWS managed key for Amazon EBS volumes is used. This parameter maps 1:1 with the
KmsKeyIdparameter of the CreateVolume API in the Amazon EC2 API Reference. AWS authenticates the AWS Key Management Service key asynchronously. Therefore, if you specify an ID, alias, or ARN that is invalid, the action can appear to complete, but eventually fails. - role
Arn string - The ARN of the IAM role to associate with this volume. This is the Amazon ECS infrastructure IAM role that is used to manage your AWS infrastructure. We recommend using the Amazon ECS-managed
AmazonECSInfrastructureRolePolicyForVolumesIAM policy with this role. For more information, see Amazon ECS infrastructure IAM role in the Amazon ECS Developer Guide. - size
In numberGi B - The size of the volume in GiB. You must specify either a volume size or a snapshot ID. If you specify a snapshot ID, the snapshot size is used for the volume size by default. You can optionally specify a volume size greater than or equal to the snapshot size. This parameter maps 1:1 with the
Sizeparameter of the CreateVolume API in the Amazon EC2 API Reference. The following are the supported volume size values for each volume type. +gp2andgp3: 1-16,384 +io1andio2: 4-16,384 +st1andsc1: 125-16,384 +standard: 1-1,024 - snapshot
Id string - The snapshot that Amazon ECS uses to create the volume. You must specify either a snapshot ID or a volume size. This parameter maps 1:1 with the
SnapshotIdparameter of the CreateVolume API in the Amazon EC2 API Reference. -
EBSTag
Specification Response[] - The tags to apply to the volume. Amazon ECS applies service-managed tags by default. This parameter maps 1:1 with the
TagSpecifications.Nparameter of the CreateVolume API in the Amazon EC2 API Reference. - throughput number
- The throughput to provision for a volume, in MiB/s, with a maximum of 1,000 MiB/s. This parameter maps 1:1 with the
Throughputparameter of the CreateVolume API in the Amazon EC2 API Reference. This parameter is only supported for thegp3volume type. - volume
Type string - The volume type. This parameter maps 1:1 with the
VolumeTypeparameter of the CreateVolume API in the Amazon EC2 API Reference. For more information, see Amazon EBS volume types in the Amazon EC2 User Guide. The following are the supported volume types. + General Purpose SSD:gp2|gp3+ Provisioned IOPS SSD:io1|io2+ Throughput Optimized HDD:st1+ Cold HDD:sc1+ Magnetic:standardThe magnetic volume type is not supported on Fargate.
- encrypted bool
- Indicates whether the volume should be encrypted. If no value is specified, encryption is turned on by default. This parameter maps 1:1 with the
Encryptedparameter of the CreateVolume API in the Amazon EC2 API Reference. - filesystem_
type str - The Linux filesystem type for the volume. For volumes created from a snapshot, you must specify the same filesystem type that the volume was using when the snapshot was created. If there is a filesystem type mismatch, the task will fail to start. The available filesystem types are
ext3,ext4, andxfs. If no value is specified, thexfsfilesystem type is used by default. - iops int
- The number of I/O operations per second (IOPS). For
gp3,io1, andio2volumes, this represents the number of IOPS that are provisioned for the volume. Forgp2volumes, this represents the baseline performance of the volume and the rate at which the volume accumulates I/O credits for bursting. The following are the supported values for each volume type. +gp3: 3,000 - 16,000 IOPS +io1: 100 - 64,000 IOPS +io2: 100 - 256,000 IOPS This parameter is required forio1andio2volume types. The default forgp3volumes is3,000 IOPS. This parameter is not supported forst1,sc1, orstandardvolume types. This parameter maps 1:1 with theIopsparameter of the CreateVolume API in the Amazon EC2 API Reference. - kms_
key_ strid - The Amazon Resource Name (ARN) identifier of the AWS Key Management Service key to use for Amazon EBS encryption. When encryption is turned on and no AWS Key Management Service key is specified, the default AWS managed key for Amazon EBS volumes is used. This parameter maps 1:1 with the
KmsKeyIdparameter of the CreateVolume API in the Amazon EC2 API Reference. AWS authenticates the AWS Key Management Service key asynchronously. Therefore, if you specify an ID, alias, or ARN that is invalid, the action can appear to complete, but eventually fails. - role_
arn str - The ARN of the IAM role to associate with this volume. This is the Amazon ECS infrastructure IAM role that is used to manage your AWS infrastructure. We recommend using the Amazon ECS-managed
AmazonECSInfrastructureRolePolicyForVolumesIAM policy with this role. For more information, see Amazon ECS infrastructure IAM role in the Amazon ECS Developer Guide. - size_
in_ intgi_ b - The size of the volume in GiB. You must specify either a volume size or a snapshot ID. If you specify a snapshot ID, the snapshot size is used for the volume size by default. You can optionally specify a volume size greater than or equal to the snapshot size. This parameter maps 1:1 with the
Sizeparameter of the CreateVolume API in the Amazon EC2 API Reference. The following are the supported volume size values for each volume type. +gp2andgp3: 1-16,384 +io1andio2: 4-16,384 +st1andsc1: 125-16,384 +standard: 1-1,024 - snapshot_
id str - The snapshot that Amazon ECS uses to create the volume. You must specify either a snapshot ID or a volume size. This parameter maps 1:1 with the
SnapshotIdparameter of the CreateVolume API in the Amazon EC2 API Reference. - tag_
specifications Sequence[EBSTagSpecification Response] - The tags to apply to the volume. Amazon ECS applies service-managed tags by default. This parameter maps 1:1 with the
TagSpecifications.Nparameter of the CreateVolume API in the Amazon EC2 API Reference. - throughput int
- The throughput to provision for a volume, in MiB/s, with a maximum of 1,000 MiB/s. This parameter maps 1:1 with the
Throughputparameter of the CreateVolume API in the Amazon EC2 API Reference. This parameter is only supported for thegp3volume type. - volume_
type str - The volume type. This parameter maps 1:1 with the
VolumeTypeparameter of the CreateVolume API in the Amazon EC2 API Reference. For more information, see Amazon EBS volume types in the Amazon EC2 User Guide. The following are the supported volume types. + General Purpose SSD:gp2|gp3+ Provisioned IOPS SSD:io1|io2+ Throughput Optimized HDD:st1+ Cold HDD:sc1+ Magnetic:standardThe magnetic volume type is not supported on Fargate.
- encrypted Boolean
- Indicates whether the volume should be encrypted. If no value is specified, encryption is turned on by default. This parameter maps 1:1 with the
Encryptedparameter of the CreateVolume API in the Amazon EC2 API Reference. - filesystem
Type String - The Linux filesystem type for the volume. For volumes created from a snapshot, you must specify the same filesystem type that the volume was using when the snapshot was created. If there is a filesystem type mismatch, the task will fail to start. The available filesystem types are
ext3,ext4, andxfs. If no value is specified, thexfsfilesystem type is used by default. - iops Number
- The number of I/O operations per second (IOPS). For
gp3,io1, andio2volumes, this represents the number of IOPS that are provisioned for the volume. Forgp2volumes, this represents the baseline performance of the volume and the rate at which the volume accumulates I/O credits for bursting. The following are the supported values for each volume type. +gp3: 3,000 - 16,000 IOPS +io1: 100 - 64,000 IOPS +io2: 100 - 256,000 IOPS This parameter is required forio1andio2volume types. The default forgp3volumes is3,000 IOPS. This parameter is not supported forst1,sc1, orstandardvolume types. This parameter maps 1:1 with theIopsparameter of the CreateVolume API in the Amazon EC2 API Reference. - kms
Key StringId - The Amazon Resource Name (ARN) identifier of the AWS Key Management Service key to use for Amazon EBS encryption. When encryption is turned on and no AWS Key Management Service key is specified, the default AWS managed key for Amazon EBS volumes is used. This parameter maps 1:1 with the
KmsKeyIdparameter of the CreateVolume API in the Amazon EC2 API Reference. AWS authenticates the AWS Key Management Service key asynchronously. Therefore, if you specify an ID, alias, or ARN that is invalid, the action can appear to complete, but eventually fails. - role
Arn String - The ARN of the IAM role to associate with this volume. This is the Amazon ECS infrastructure IAM role that is used to manage your AWS infrastructure. We recommend using the Amazon ECS-managed
AmazonECSInfrastructureRolePolicyForVolumesIAM policy with this role. For more information, see Amazon ECS infrastructure IAM role in the Amazon ECS Developer Guide. - size
In NumberGi B - The size of the volume in GiB. You must specify either a volume size or a snapshot ID. If you specify a snapshot ID, the snapshot size is used for the volume size by default. You can optionally specify a volume size greater than or equal to the snapshot size. This parameter maps 1:1 with the
Sizeparameter of the CreateVolume API in the Amazon EC2 API Reference. The following are the supported volume size values for each volume type. +gp2andgp3: 1-16,384 +io1andio2: 4-16,384 +st1andsc1: 125-16,384 +standard: 1-1,024 - snapshot
Id String - The snapshot that Amazon ECS uses to create the volume. You must specify either a snapshot ID or a volume size. This parameter maps 1:1 with the
SnapshotIdparameter of the CreateVolume API in the Amazon EC2 API Reference. - List<Property Map>
- The tags to apply to the volume. Amazon ECS applies service-managed tags by default. This parameter maps 1:1 with the
TagSpecifications.Nparameter of the CreateVolume API in the Amazon EC2 API Reference. - throughput Number
- The throughput to provision for a volume, in MiB/s, with a maximum of 1,000 MiB/s. This parameter maps 1:1 with the
Throughputparameter of the CreateVolume API in the Amazon EC2 API Reference. This parameter is only supported for thegp3volume type. - volume
Type String - The volume type. This parameter maps 1:1 with the
VolumeTypeparameter of the CreateVolume API in the Amazon EC2 API Reference. For more information, see Amazon EBS volume types in the Amazon EC2 User Guide. The following are the supported volume types. + General Purpose SSD:gp2|gp3+ Provisioned IOPS SSD:io1|io2+ Throughput Optimized HDD:st1+ Cold HDD:sc1+ Magnetic:standardThe magnetic volume type is not supported on Fargate.
ServiceRegistry, ServiceRegistryArgs
, ServiceRegistryArgs
- Container
Name string - The container name value to be used for your service discovery service. It's already specified in the task definition. If the task definition that your service task specifies uses the
bridgeorhostnetwork mode, you must specify acontainerNameandcontainerPortcombination from the task definition. If the task definition that your service task specifies uses theawsvpcnetwork mode and a type SRV DNS record is used, you must specify either acontainerNameandcontainerPortcombination or aportvalue. However, you can't specify both. - Container
Port int - The port value to be used for your service discovery service. It's already specified in the task definition. If the task definition your service task specifies uses the
bridgeorhostnetwork mode, you must specify acontainerNameandcontainerPortcombination from the task definition. If the task definition your service task specifies uses theawsvpcnetwork mode and a type SRV DNS record is used, you must specify either acontainerNameandcontainerPortcombination or aportvalue. However, you can't specify both. - Port int
- The port value used if your service discovery service specified an SRV record. This field might be used if both the
awsvpcnetwork mode and SRV records are used. - Registry
Arn string - The Amazon Resource Name (ARN) of the service registry. The currently supported service registry is CMAP. For more information, see CreateService.
- Container
Name string - The container name value to be used for your service discovery service. It's already specified in the task definition. If the task definition that your service task specifies uses the
bridgeorhostnetwork mode, you must specify acontainerNameandcontainerPortcombination from the task definition. If the task definition that your service task specifies uses theawsvpcnetwork mode and a type SRV DNS record is used, you must specify either acontainerNameandcontainerPortcombination or aportvalue. However, you can't specify both. - Container
Port int - The port value to be used for your service discovery service. It's already specified in the task definition. If the task definition your service task specifies uses the
bridgeorhostnetwork mode, you must specify acontainerNameandcontainerPortcombination from the task definition. If the task definition your service task specifies uses theawsvpcnetwork mode and a type SRV DNS record is used, you must specify either acontainerNameandcontainerPortcombination or aportvalue. However, you can't specify both. - Port int
- The port value used if your service discovery service specified an SRV record. This field might be used if both the
awsvpcnetwork mode and SRV records are used. - Registry
Arn string - The Amazon Resource Name (ARN) of the service registry. The currently supported service registry is CMAP. For more information, see CreateService.
- container
Name String - The container name value to be used for your service discovery service. It's already specified in the task definition. If the task definition that your service task specifies uses the
bridgeorhostnetwork mode, you must specify acontainerNameandcontainerPortcombination from the task definition. If the task definition that your service task specifies uses theawsvpcnetwork mode and a type SRV DNS record is used, you must specify either acontainerNameandcontainerPortcombination or aportvalue. However, you can't specify both. - container
Port Integer - The port value to be used for your service discovery service. It's already specified in the task definition. If the task definition your service task specifies uses the
bridgeorhostnetwork mode, you must specify acontainerNameandcontainerPortcombination from the task definition. If the task definition your service task specifies uses theawsvpcnetwork mode and a type SRV DNS record is used, you must specify either acontainerNameandcontainerPortcombination or aportvalue. However, you can't specify both. - port Integer
- The port value used if your service discovery service specified an SRV record. This field might be used if both the
awsvpcnetwork mode and SRV records are used. - registry
Arn String - The Amazon Resource Name (ARN) of the service registry. The currently supported service registry is CMAP. For more information, see CreateService.
- container
Name string - The container name value to be used for your service discovery service. It's already specified in the task definition. If the task definition that your service task specifies uses the
bridgeorhostnetwork mode, you must specify acontainerNameandcontainerPortcombination from the task definition. If the task definition that your service task specifies uses theawsvpcnetwork mode and a type SRV DNS record is used, you must specify either acontainerNameandcontainerPortcombination or aportvalue. However, you can't specify both. - container
Port number - The port value to be used for your service discovery service. It's already specified in the task definition. If the task definition your service task specifies uses the
bridgeorhostnetwork mode, you must specify acontainerNameandcontainerPortcombination from the task definition. If the task definition your service task specifies uses theawsvpcnetwork mode and a type SRV DNS record is used, you must specify either acontainerNameandcontainerPortcombination or aportvalue. However, you can't specify both. - port number
- The port value used if your service discovery service specified an SRV record. This field might be used if both the
awsvpcnetwork mode and SRV records are used. - registry
Arn string - The Amazon Resource Name (ARN) of the service registry. The currently supported service registry is CMAP. For more information, see CreateService.
- container_
name str - The container name value to be used for your service discovery service. It's already specified in the task definition. If the task definition that your service task specifies uses the
bridgeorhostnetwork mode, you must specify acontainerNameandcontainerPortcombination from the task definition. If the task definition that your service task specifies uses theawsvpcnetwork mode and a type SRV DNS record is used, you must specify either acontainerNameandcontainerPortcombination or aportvalue. However, you can't specify both. - container_
port int - The port value to be used for your service discovery service. It's already specified in the task definition. If the task definition your service task specifies uses the
bridgeorhostnetwork mode, you must specify acontainerNameandcontainerPortcombination from the task definition. If the task definition your service task specifies uses theawsvpcnetwork mode and a type SRV DNS record is used, you must specify either acontainerNameandcontainerPortcombination or aportvalue. However, you can't specify both. - port int
- The port value used if your service discovery service specified an SRV record. This field might be used if both the
awsvpcnetwork mode and SRV records are used. - registry_
arn str - The Amazon Resource Name (ARN) of the service registry. The currently supported service registry is CMAP. For more information, see CreateService.
- container
Name String - The container name value to be used for your service discovery service. It's already specified in the task definition. If the task definition that your service task specifies uses the
bridgeorhostnetwork mode, you must specify acontainerNameandcontainerPortcombination from the task definition. If the task definition that your service task specifies uses theawsvpcnetwork mode and a type SRV DNS record is used, you must specify either acontainerNameandcontainerPortcombination or aportvalue. However, you can't specify both. - container
Port Number - The port value to be used for your service discovery service. It's already specified in the task definition. If the task definition your service task specifies uses the
bridgeorhostnetwork mode, you must specify acontainerNameandcontainerPortcombination from the task definition. If the task definition your service task specifies uses theawsvpcnetwork mode and a type SRV DNS record is used, you must specify either acontainerNameandcontainerPortcombination or aportvalue. However, you can't specify both. - port Number
- The port value used if your service discovery service specified an SRV record. This field might be used if both the
awsvpcnetwork mode and SRV records are used. - registry
Arn String - The Amazon Resource Name (ARN) of the service registry. The currently supported service registry is CMAP. For more information, see CreateService.
ServiceRegistryResponse, ServiceRegistryResponseArgs
, ServiceRegistryResponseArgs
- Container
Name string - The container name value to be used for your service discovery service. It's already specified in the task definition. If the task definition that your service task specifies uses the
bridgeorhostnetwork mode, you must specify acontainerNameandcontainerPortcombination from the task definition. If the task definition that your service task specifies uses theawsvpcnetwork mode and a type SRV DNS record is used, you must specify either acontainerNameandcontainerPortcombination or aportvalue. However, you can't specify both. - Container
Port int - The port value to be used for your service discovery service. It's already specified in the task definition. If the task definition your service task specifies uses the
bridgeorhostnetwork mode, you must specify acontainerNameandcontainerPortcombination from the task definition. If the task definition your service task specifies uses theawsvpcnetwork mode and a type SRV DNS record is used, you must specify either acontainerNameandcontainerPortcombination or aportvalue. However, you can't specify both. - Port int
- The port value used if your service discovery service specified an SRV record. This field might be used if both the
awsvpcnetwork mode and SRV records are used. - Registry
Arn string - The Amazon Resource Name (ARN) of the service registry. The currently supported service registry is CMAP. For more information, see CreateService.
- Container
Name string - The container name value to be used for your service discovery service. It's already specified in the task definition. If the task definition that your service task specifies uses the
bridgeorhostnetwork mode, you must specify acontainerNameandcontainerPortcombination from the task definition. If the task definition that your service task specifies uses theawsvpcnetwork mode and a type SRV DNS record is used, you must specify either acontainerNameandcontainerPortcombination or aportvalue. However, you can't specify both. - Container
Port int - The port value to be used for your service discovery service. It's already specified in the task definition. If the task definition your service task specifies uses the
bridgeorhostnetwork mode, you must specify acontainerNameandcontainerPortcombination from the task definition. If the task definition your service task specifies uses theawsvpcnetwork mode and a type SRV DNS record is used, you must specify either acontainerNameandcontainerPortcombination or aportvalue. However, you can't specify both. - Port int
- The port value used if your service discovery service specified an SRV record. This field might be used if both the
awsvpcnetwork mode and SRV records are used. - Registry
Arn string - The Amazon Resource Name (ARN) of the service registry. The currently supported service registry is CMAP. For more information, see CreateService.
- container
Name String - The container name value to be used for your service discovery service. It's already specified in the task definition. If the task definition that your service task specifies uses the
bridgeorhostnetwork mode, you must specify acontainerNameandcontainerPortcombination from the task definition. If the task definition that your service task specifies uses theawsvpcnetwork mode and a type SRV DNS record is used, you must specify either acontainerNameandcontainerPortcombination or aportvalue. However, you can't specify both. - container
Port Integer - The port value to be used for your service discovery service. It's already specified in the task definition. If the task definition your service task specifies uses the
bridgeorhostnetwork mode, you must specify acontainerNameandcontainerPortcombination from the task definition. If the task definition your service task specifies uses theawsvpcnetwork mode and a type SRV DNS record is used, you must specify either acontainerNameandcontainerPortcombination or aportvalue. However, you can't specify both. - port Integer
- The port value used if your service discovery service specified an SRV record. This field might be used if both the
awsvpcnetwork mode and SRV records are used. - registry
Arn String - The Amazon Resource Name (ARN) of the service registry. The currently supported service registry is CMAP. For more information, see CreateService.
- container
Name string - The container name value to be used for your service discovery service. It's already specified in the task definition. If the task definition that your service task specifies uses the
bridgeorhostnetwork mode, you must specify acontainerNameandcontainerPortcombination from the task definition. If the task definition that your service task specifies uses theawsvpcnetwork mode and a type SRV DNS record is used, you must specify either acontainerNameandcontainerPortcombination or aportvalue. However, you can't specify both. - container
Port number - The port value to be used for your service discovery service. It's already specified in the task definition. If the task definition your service task specifies uses the
bridgeorhostnetwork mode, you must specify acontainerNameandcontainerPortcombination from the task definition. If the task definition your service task specifies uses theawsvpcnetwork mode and a type SRV DNS record is used, you must specify either acontainerNameandcontainerPortcombination or aportvalue. However, you can't specify both. - port number
- The port value used if your service discovery service specified an SRV record. This field might be used if both the
awsvpcnetwork mode and SRV records are used. - registry
Arn string - The Amazon Resource Name (ARN) of the service registry. The currently supported service registry is CMAP. For more information, see CreateService.
- container_
name str - The container name value to be used for your service discovery service. It's already specified in the task definition. If the task definition that your service task specifies uses the
bridgeorhostnetwork mode, you must specify acontainerNameandcontainerPortcombination from the task definition. If the task definition that your service task specifies uses theawsvpcnetwork mode and a type SRV DNS record is used, you must specify either acontainerNameandcontainerPortcombination or aportvalue. However, you can't specify both. - container_
port int - The port value to be used for your service discovery service. It's already specified in the task definition. If the task definition your service task specifies uses the
bridgeorhostnetwork mode, you must specify acontainerNameandcontainerPortcombination from the task definition. If the task definition your service task specifies uses theawsvpcnetwork mode and a type SRV DNS record is used, you must specify either acontainerNameandcontainerPortcombination or aportvalue. However, you can't specify both. - port int
- The port value used if your service discovery service specified an SRV record. This field might be used if both the
awsvpcnetwork mode and SRV records are used. - registry_
arn str - The Amazon Resource Name (ARN) of the service registry. The currently supported service registry is CMAP. For more information, see CreateService.
- container
Name String - The container name value to be used for your service discovery service. It's already specified in the task definition. If the task definition that your service task specifies uses the
bridgeorhostnetwork mode, you must specify acontainerNameandcontainerPortcombination from the task definition. If the task definition that your service task specifies uses theawsvpcnetwork mode and a type SRV DNS record is used, you must specify either acontainerNameandcontainerPortcombination or aportvalue. However, you can't specify both. - container
Port Number - The port value to be used for your service discovery service. It's already specified in the task definition. If the task definition your service task specifies uses the
bridgeorhostnetwork mode, you must specify acontainerNameandcontainerPortcombination from the task definition. If the task definition your service task specifies uses theawsvpcnetwork mode and a type SRV DNS record is used, you must specify either acontainerNameandcontainerPortcombination or aportvalue. However, you can't specify both. - port Number
- The port value used if your service discovery service specified an SRV record. This field might be used if both the
awsvpcnetwork mode and SRV records are used. - registry
Arn String - The Amazon Resource Name (ARN) of the service registry. The currently supported service registry is CMAP. For more information, see CreateService.
ServiceVolumeConfiguration, ServiceVolumeConfigurationArgs
, ServiceVolumeConfigurationArgs
- Managed
EBSVolume Pulumi.Azure Native. Aws Connector. Inputs. Service Managed EBSVolume Configuration - The configuration for the Amazon EBS volume that Amazon ECS creates and manages on your behalf. These settings are used to create each Amazon EBS volume, with one volume created for each task in the service. The Amazon EBS volumes are visible in your account in the Amazon EC2 console once they are created. The configuration for the Amazon EBS volume that Amazon ECS creates and manages on your behalf. These settings are used to create each Amazon EBS volume, with one volume created for each task in the service. Many of these parameters map 1:1 with the Amazon EBS
CreateVolumeAPI request parameters. - Name string
- The name of the volume. This value must match the volume name from the
Volumeobject in the task definition.
- Managed
EBSVolume ServiceManaged EBSVolume Configuration - The configuration for the Amazon EBS volume that Amazon ECS creates and manages on your behalf. These settings are used to create each Amazon EBS volume, with one volume created for each task in the service. The Amazon EBS volumes are visible in your account in the Amazon EC2 console once they are created. The configuration for the Amazon EBS volume that Amazon ECS creates and manages on your behalf. These settings are used to create each Amazon EBS volume, with one volume created for each task in the service. Many of these parameters map 1:1 with the Amazon EBS
CreateVolumeAPI request parameters. - Name string
- The name of the volume. This value must match the volume name from the
Volumeobject in the task definition.
- managed
EBSVolume ServiceManaged EBSVolume Configuration - The configuration for the Amazon EBS volume that Amazon ECS creates and manages on your behalf. These settings are used to create each Amazon EBS volume, with one volume created for each task in the service. The Amazon EBS volumes are visible in your account in the Amazon EC2 console once they are created. The configuration for the Amazon EBS volume that Amazon ECS creates and manages on your behalf. These settings are used to create each Amazon EBS volume, with one volume created for each task in the service. Many of these parameters map 1:1 with the Amazon EBS
CreateVolumeAPI request parameters. - name String
- The name of the volume. This value must match the volume name from the
Volumeobject in the task definition.
- managed
EBSVolume ServiceManaged EBSVolume Configuration - The configuration for the Amazon EBS volume that Amazon ECS creates and manages on your behalf. These settings are used to create each Amazon EBS volume, with one volume created for each task in the service. The Amazon EBS volumes are visible in your account in the Amazon EC2 console once they are created. The configuration for the Amazon EBS volume that Amazon ECS creates and manages on your behalf. These settings are used to create each Amazon EBS volume, with one volume created for each task in the service. Many of these parameters map 1:1 with the Amazon EBS
CreateVolumeAPI request parameters. - name string
- The name of the volume. This value must match the volume name from the
Volumeobject in the task definition.
- managed_
ebs_ Servicevolume Managed EBSVolume Configuration - The configuration for the Amazon EBS volume that Amazon ECS creates and manages on your behalf. These settings are used to create each Amazon EBS volume, with one volume created for each task in the service. The Amazon EBS volumes are visible in your account in the Amazon EC2 console once they are created. The configuration for the Amazon EBS volume that Amazon ECS creates and manages on your behalf. These settings are used to create each Amazon EBS volume, with one volume created for each task in the service. Many of these parameters map 1:1 with the Amazon EBS
CreateVolumeAPI request parameters. - name str
- The name of the volume. This value must match the volume name from the
Volumeobject in the task definition.
- managed
EBSVolume Property Map - The configuration for the Amazon EBS volume that Amazon ECS creates and manages on your behalf. These settings are used to create each Amazon EBS volume, with one volume created for each task in the service. The Amazon EBS volumes are visible in your account in the Amazon EC2 console once they are created. The configuration for the Amazon EBS volume that Amazon ECS creates and manages on your behalf. These settings are used to create each Amazon EBS volume, with one volume created for each task in the service. Many of these parameters map 1:1 with the Amazon EBS
CreateVolumeAPI request parameters. - name String
- The name of the volume. This value must match the volume name from the
Volumeobject in the task definition.
ServiceVolumeConfigurationResponse, ServiceVolumeConfigurationResponseArgs
, ServiceVolumeConfigurationResponseArgs
- Managed
EBSVolume Pulumi.Azure Native. Aws Connector. Inputs. Service Managed EBSVolume Configuration Response - The configuration for the Amazon EBS volume that Amazon ECS creates and manages on your behalf. These settings are used to create each Amazon EBS volume, with one volume created for each task in the service. The Amazon EBS volumes are visible in your account in the Amazon EC2 console once they are created. The configuration for the Amazon EBS volume that Amazon ECS creates and manages on your behalf. These settings are used to create each Amazon EBS volume, with one volume created for each task in the service. Many of these parameters map 1:1 with the Amazon EBS
CreateVolumeAPI request parameters. - Name string
- The name of the volume. This value must match the volume name from the
Volumeobject in the task definition.
- Managed
EBSVolume ServiceManaged EBSVolume Configuration Response - The configuration for the Amazon EBS volume that Amazon ECS creates and manages on your behalf. These settings are used to create each Amazon EBS volume, with one volume created for each task in the service. The Amazon EBS volumes are visible in your account in the Amazon EC2 console once they are created. The configuration for the Amazon EBS volume that Amazon ECS creates and manages on your behalf. These settings are used to create each Amazon EBS volume, with one volume created for each task in the service. Many of these parameters map 1:1 with the Amazon EBS
CreateVolumeAPI request parameters. - Name string
- The name of the volume. This value must match the volume name from the
Volumeobject in the task definition.
- managed
EBSVolume ServiceManaged EBSVolume Configuration Response - The configuration for the Amazon EBS volume that Amazon ECS creates and manages on your behalf. These settings are used to create each Amazon EBS volume, with one volume created for each task in the service. The Amazon EBS volumes are visible in your account in the Amazon EC2 console once they are created. The configuration for the Amazon EBS volume that Amazon ECS creates and manages on your behalf. These settings are used to create each Amazon EBS volume, with one volume created for each task in the service. Many of these parameters map 1:1 with the Amazon EBS
CreateVolumeAPI request parameters. - name String
- The name of the volume. This value must match the volume name from the
Volumeobject in the task definition.
- managed
EBSVolume ServiceManaged EBSVolume Configuration Response - The configuration for the Amazon EBS volume that Amazon ECS creates and manages on your behalf. These settings are used to create each Amazon EBS volume, with one volume created for each task in the service. The Amazon EBS volumes are visible in your account in the Amazon EC2 console once they are created. The configuration for the Amazon EBS volume that Amazon ECS creates and manages on your behalf. These settings are used to create each Amazon EBS volume, with one volume created for each task in the service. Many of these parameters map 1:1 with the Amazon EBS
CreateVolumeAPI request parameters. - name string
- The name of the volume. This value must match the volume name from the
Volumeobject in the task definition.
- managed_
ebs_ Servicevolume Managed EBSVolume Configuration Response - The configuration for the Amazon EBS volume that Amazon ECS creates and manages on your behalf. These settings are used to create each Amazon EBS volume, with one volume created for each task in the service. The Amazon EBS volumes are visible in your account in the Amazon EC2 console once they are created. The configuration for the Amazon EBS volume that Amazon ECS creates and manages on your behalf. These settings are used to create each Amazon EBS volume, with one volume created for each task in the service. Many of these parameters map 1:1 with the Amazon EBS
CreateVolumeAPI request parameters. - name str
- The name of the volume. This value must match the volume name from the
Volumeobject in the task definition.
- managed
EBSVolume Property Map - The configuration for the Amazon EBS volume that Amazon ECS creates and manages on your behalf. These settings are used to create each Amazon EBS volume, with one volume created for each task in the service. The Amazon EBS volumes are visible in your account in the Amazon EC2 console once they are created. The configuration for the Amazon EBS volume that Amazon ECS creates and manages on your behalf. These settings are used to create each Amazon EBS volume, with one volume created for each task in the service. Many of these parameters map 1:1 with the Amazon EBS
CreateVolumeAPI request parameters. - name String
- The name of the volume. This value must match the volume name from the
Volumeobject in the task definition.
SystemDataResponse, SystemDataResponseArgs
, SystemDataResponseArgs
- Created
At string - The timestamp of resource creation (UTC).
- Created
By string - The identity that created the resource.
- Created
By stringType - The type of identity that created the resource.
- Last
Modified stringAt - The timestamp of resource last modification (UTC)
- Last
Modified stringBy - The identity that last modified the resource.
- Last
Modified stringBy Type - The type of identity that last modified the resource.
- Created
At string - The timestamp of resource creation (UTC).
- Created
By string - The identity that created the resource.
- Created
By stringType - The type of identity that created the resource.
- Last
Modified stringAt - The timestamp of resource last modification (UTC)
- Last
Modified stringBy - The identity that last modified the resource.
- Last
Modified stringBy Type - The type of identity that last modified the resource.
- created
At String - The timestamp of resource creation (UTC).
- created
By String - The identity that created the resource.
- created
By StringType - The type of identity that created the resource.
- last
Modified StringAt - The timestamp of resource last modification (UTC)
- last
Modified StringBy - The identity that last modified the resource.
- last
Modified StringBy Type - The type of identity that last modified the resource.
- created
At string - The timestamp of resource creation (UTC).
- created
By string - The identity that created the resource.
- created
By stringType - The type of identity that created the resource.
- last
Modified stringAt - The timestamp of resource last modification (UTC)
- last
Modified stringBy - The identity that last modified the resource.
- last
Modified stringBy Type - The type of identity that last modified the resource.
- created_
at str - The timestamp of resource creation (UTC).
- created_
by str - The identity that created the resource.
- created_
by_ strtype - The type of identity that created the resource.
- last_
modified_ strat - The timestamp of resource last modification (UTC)
- last_
modified_ strby - The identity that last modified the resource.
- last_
modified_ strby_ type - The type of identity that last modified the resource.
- created
At String - The timestamp of resource creation (UTC).
- created
By String - The identity that created the resource.
- created
By StringType - The type of identity that created the resource.
- last
Modified StringAt - The timestamp of resource last modification (UTC)
- last
Modified StringBy - The identity that last modified the resource.
- last
Modified StringBy Type - The type of identity that last modified the resource.
Tag, TagArgs
, TagArgs
- Key string
- The key name of the tag. You can specify a value that is 1 to 128 Unicode characters in length and cannot be prefixed with aws:. You can use any of the following characters: the set of Unicode letters, digits, whitespace, _, ., /, =, +, and -.
- Value string
- The value for the tag. You can specify a value that is 0 to 256 Unicode characters in length and cannot be prefixed with aws:. You can use any of the following characters: the set of Unicode letters, digits, whitespace, _, ., /, =, +, and -.
- Key string
- The key name of the tag. You can specify a value that is 1 to 128 Unicode characters in length and cannot be prefixed with aws:. You can use any of the following characters: the set of Unicode letters, digits, whitespace, _, ., /, =, +, and -.
- Value string
- The value for the tag. You can specify a value that is 0 to 256 Unicode characters in length and cannot be prefixed with aws:. You can use any of the following characters: the set of Unicode letters, digits, whitespace, _, ., /, =, +, and -.
- key String
- The key name of the tag. You can specify a value that is 1 to 128 Unicode characters in length and cannot be prefixed with aws:. You can use any of the following characters: the set of Unicode letters, digits, whitespace, _, ., /, =, +, and -.
- value String
- The value for the tag. You can specify a value that is 0 to 256 Unicode characters in length and cannot be prefixed with aws:. You can use any of the following characters: the set of Unicode letters, digits, whitespace, _, ., /, =, +, and -.
- key string
- The key name of the tag. You can specify a value that is 1 to 128 Unicode characters in length and cannot be prefixed with aws:. You can use any of the following characters: the set of Unicode letters, digits, whitespace, _, ., /, =, +, and -.
- value string
- The value for the tag. You can specify a value that is 0 to 256 Unicode characters in length and cannot be prefixed with aws:. You can use any of the following characters: the set of Unicode letters, digits, whitespace, _, ., /, =, +, and -.
- key str
- The key name of the tag. You can specify a value that is 1 to 128 Unicode characters in length and cannot be prefixed with aws:. You can use any of the following characters: the set of Unicode letters, digits, whitespace, _, ., /, =, +, and -.
- value str
- The value for the tag. You can specify a value that is 0 to 256 Unicode characters in length and cannot be prefixed with aws:. You can use any of the following characters: the set of Unicode letters, digits, whitespace, _, ., /, =, +, and -.
- key String
- The key name of the tag. You can specify a value that is 1 to 128 Unicode characters in length and cannot be prefixed with aws:. You can use any of the following characters: the set of Unicode letters, digits, whitespace, _, ., /, =, +, and -.
- value String
- The value for the tag. You can specify a value that is 0 to 256 Unicode characters in length and cannot be prefixed with aws:. You can use any of the following characters: the set of Unicode letters, digits, whitespace, _, ., /, =, +, and -.
TagResponse, TagResponseArgs
, TagResponseArgs
- Key string
- The key name of the tag. You can specify a value that is 1 to 128 Unicode characters in length and cannot be prefixed with aws:. You can use any of the following characters: the set of Unicode letters, digits, whitespace, _, ., /, =, +, and -.
- Value string
- The value for the tag. You can specify a value that is 0 to 256 Unicode characters in length and cannot be prefixed with aws:. You can use any of the following characters: the set of Unicode letters, digits, whitespace, _, ., /, =, +, and -.
- Key string
- The key name of the tag. You can specify a value that is 1 to 128 Unicode characters in length and cannot be prefixed with aws:. You can use any of the following characters: the set of Unicode letters, digits, whitespace, _, ., /, =, +, and -.
- Value string
- The value for the tag. You can specify a value that is 0 to 256 Unicode characters in length and cannot be prefixed with aws:. You can use any of the following characters: the set of Unicode letters, digits, whitespace, _, ., /, =, +, and -.
- key String
- The key name of the tag. You can specify a value that is 1 to 128 Unicode characters in length and cannot be prefixed with aws:. You can use any of the following characters: the set of Unicode letters, digits, whitespace, _, ., /, =, +, and -.
- value String
- The value for the tag. You can specify a value that is 0 to 256 Unicode characters in length and cannot be prefixed with aws:. You can use any of the following characters: the set of Unicode letters, digits, whitespace, _, ., /, =, +, and -.
- key string
- The key name of the tag. You can specify a value that is 1 to 128 Unicode characters in length and cannot be prefixed with aws:. You can use any of the following characters: the set of Unicode letters, digits, whitespace, _, ., /, =, +, and -.
- value string
- The value for the tag. You can specify a value that is 0 to 256 Unicode characters in length and cannot be prefixed with aws:. You can use any of the following characters: the set of Unicode letters, digits, whitespace, _, ., /, =, +, and -.
- key str
- The key name of the tag. You can specify a value that is 1 to 128 Unicode characters in length and cannot be prefixed with aws:. You can use any of the following characters: the set of Unicode letters, digits, whitespace, _, ., /, =, +, and -.
- value str
- The value for the tag. You can specify a value that is 0 to 256 Unicode characters in length and cannot be prefixed with aws:. You can use any of the following characters: the set of Unicode letters, digits, whitespace, _, ., /, =, +, and -.
- key String
- The key name of the tag. You can specify a value that is 1 to 128 Unicode characters in length and cannot be prefixed with aws:. You can use any of the following characters: the set of Unicode letters, digits, whitespace, _, ., /, =, +, and -.
- value String
- The value for the tag. You can specify a value that is 0 to 256 Unicode characters in length and cannot be prefixed with aws:. You can use any of the following characters: the set of Unicode letters, digits, whitespace, _, ., /, =, +, and -.
TimeoutConfiguration, TimeoutConfigurationArgs
, TimeoutConfigurationArgs
- Idle
Timeout intSeconds - The amount of time in seconds a connection will stay active while idle. A value of
0can be set to disableidleTimeout. TheidleTimeoutdefault forHTTP/HTTP2/GRPCis 5 minutes. TheidleTimeoutdefault forTCPis 1 hour. - Per
Request intTimeout Seconds - The amount of time waiting for the upstream to respond with a complete response per request. A value of
0can be set to disableperRequestTimeout.perRequestTimeoutcan only be set if Service ConnectappProtocolisn'tTCP. OnlyidleTimeoutis allowed forTCPappProtocol.
- Idle
Timeout intSeconds - The amount of time in seconds a connection will stay active while idle. A value of
0can be set to disableidleTimeout. TheidleTimeoutdefault forHTTP/HTTP2/GRPCis 5 minutes. TheidleTimeoutdefault forTCPis 1 hour. - Per
Request intTimeout Seconds - The amount of time waiting for the upstream to respond with a complete response per request. A value of
0can be set to disableperRequestTimeout.perRequestTimeoutcan only be set if Service ConnectappProtocolisn'tTCP. OnlyidleTimeoutis allowed forTCPappProtocol.
- idle
Timeout IntegerSeconds - The amount of time in seconds a connection will stay active while idle. A value of
0can be set to disableidleTimeout. TheidleTimeoutdefault forHTTP/HTTP2/GRPCis 5 minutes. TheidleTimeoutdefault forTCPis 1 hour. - per
Request IntegerTimeout Seconds - The amount of time waiting for the upstream to respond with a complete response per request. A value of
0can be set to disableperRequestTimeout.perRequestTimeoutcan only be set if Service ConnectappProtocolisn'tTCP. OnlyidleTimeoutis allowed forTCPappProtocol.
- idle
Timeout numberSeconds - The amount of time in seconds a connection will stay active while idle. A value of
0can be set to disableidleTimeout. TheidleTimeoutdefault forHTTP/HTTP2/GRPCis 5 minutes. TheidleTimeoutdefault forTCPis 1 hour. - per
Request numberTimeout Seconds - The amount of time waiting for the upstream to respond with a complete response per request. A value of
0can be set to disableperRequestTimeout.perRequestTimeoutcan only be set if Service ConnectappProtocolisn'tTCP. OnlyidleTimeoutis allowed forTCPappProtocol.
- idle_
timeout_ intseconds - The amount of time in seconds a connection will stay active while idle. A value of
0can be set to disableidleTimeout. TheidleTimeoutdefault forHTTP/HTTP2/GRPCis 5 minutes. TheidleTimeoutdefault forTCPis 1 hour. - per_
request_ inttimeout_ seconds - The amount of time waiting for the upstream to respond with a complete response per request. A value of
0can be set to disableperRequestTimeout.perRequestTimeoutcan only be set if Service ConnectappProtocolisn'tTCP. OnlyidleTimeoutis allowed forTCPappProtocol.
- idle
Timeout NumberSeconds - The amount of time in seconds a connection will stay active while idle. A value of
0can be set to disableidleTimeout. TheidleTimeoutdefault forHTTP/HTTP2/GRPCis 5 minutes. TheidleTimeoutdefault forTCPis 1 hour. - per
Request NumberTimeout Seconds - The amount of time waiting for the upstream to respond with a complete response per request. A value of
0can be set to disableperRequestTimeout.perRequestTimeoutcan only be set if Service ConnectappProtocolisn'tTCP. OnlyidleTimeoutis allowed forTCPappProtocol.
TimeoutConfigurationResponse, TimeoutConfigurationResponseArgs
, TimeoutConfigurationResponseArgs
- Idle
Timeout intSeconds - The amount of time in seconds a connection will stay active while idle. A value of
0can be set to disableidleTimeout. TheidleTimeoutdefault forHTTP/HTTP2/GRPCis 5 minutes. TheidleTimeoutdefault forTCPis 1 hour. - Per
Request intTimeout Seconds - The amount of time waiting for the upstream to respond with a complete response per request. A value of
0can be set to disableperRequestTimeout.perRequestTimeoutcan only be set if Service ConnectappProtocolisn'tTCP. OnlyidleTimeoutis allowed forTCPappProtocol.
- Idle
Timeout intSeconds - The amount of time in seconds a connection will stay active while idle. A value of
0can be set to disableidleTimeout. TheidleTimeoutdefault forHTTP/HTTP2/GRPCis 5 minutes. TheidleTimeoutdefault forTCPis 1 hour. - Per
Request intTimeout Seconds - The amount of time waiting for the upstream to respond with a complete response per request. A value of
0can be set to disableperRequestTimeout.perRequestTimeoutcan only be set if Service ConnectappProtocolisn'tTCP. OnlyidleTimeoutis allowed forTCPappProtocol.
- idle
Timeout IntegerSeconds - The amount of time in seconds a connection will stay active while idle. A value of
0can be set to disableidleTimeout. TheidleTimeoutdefault forHTTP/HTTP2/GRPCis 5 minutes. TheidleTimeoutdefault forTCPis 1 hour. - per
Request IntegerTimeout Seconds - The amount of time waiting for the upstream to respond with a complete response per request. A value of
0can be set to disableperRequestTimeout.perRequestTimeoutcan only be set if Service ConnectappProtocolisn'tTCP. OnlyidleTimeoutis allowed forTCPappProtocol.
- idle
Timeout numberSeconds - The amount of time in seconds a connection will stay active while idle. A value of
0can be set to disableidleTimeout. TheidleTimeoutdefault forHTTP/HTTP2/GRPCis 5 minutes. TheidleTimeoutdefault forTCPis 1 hour. - per
Request numberTimeout Seconds - The amount of time waiting for the upstream to respond with a complete response per request. A value of
0can be set to disableperRequestTimeout.perRequestTimeoutcan only be set if Service ConnectappProtocolisn'tTCP. OnlyidleTimeoutis allowed forTCPappProtocol.
- idle_
timeout_ intseconds - The amount of time in seconds a connection will stay active while idle. A value of
0can be set to disableidleTimeout. TheidleTimeoutdefault forHTTP/HTTP2/GRPCis 5 minutes. TheidleTimeoutdefault forTCPis 1 hour. - per_
request_ inttimeout_ seconds - The amount of time waiting for the upstream to respond with a complete response per request. A value of
0can be set to disableperRequestTimeout.perRequestTimeoutcan only be set if Service ConnectappProtocolisn'tTCP. OnlyidleTimeoutis allowed forTCPappProtocol.
- idle
Timeout NumberSeconds - The amount of time in seconds a connection will stay active while idle. A value of
0can be set to disableidleTimeout. TheidleTimeoutdefault forHTTP/HTTP2/GRPCis 5 minutes. TheidleTimeoutdefault forTCPis 1 hour. - per
Request NumberTimeout Seconds - The amount of time waiting for the upstream to respond with a complete response per request. A value of
0can be set to disableperRequestTimeout.perRequestTimeoutcan only be set if Service ConnectappProtocolisn'tTCP. OnlyidleTimeoutis allowed forTCPappProtocol.
Import
An existing resource can be imported using its type token, name, and identifier, e.g.
$ pulumi import azure-native:awsconnector:EcsService meuyovtzgqj /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AwsConnector/ecsServices/{name}
To learn more about importing existing cloud resources, see Importing resources.
Package Details
- Repository
- Azure Native pulumi/pulumi-azure-native
- License
- Apache-2.0
This is the latest version of Azure Native. Use the Azure Native v2 docs if using the v2 version of this package.
Azure Native v3.2.0 published on Monday, Apr 14, 2025 by Pulumi