1. Packages
  2. Azure Native
  3. API Docs
  4. awsconnector
  5. EcsService
This is the latest version of Azure Native. Use the Azure Native v1 docs if using the v1 version of this package.
Azure Native v2.71.0 published on Friday, Nov 8, 2024 by Pulumi

azure-native.awsconnector.EcsService

Explore with Pulumi AI

azure-native logo
This is the latest version of Azure Native. Use the Azure Native v1 docs if using the v1 version of this package.
Azure Native v2.71.0 published on Friday, Nov 8, 2024 by Pulumi

    A Microsoft.AwsConnector resource Azure REST API version: 2024-12-01.

    Example Usage

    EcsServices_CreateOrReplace

    using System.Collections.Generic;
    using System.Linq;
    using Pulumi;
    using AzureNative = Pulumi.AzureNative;
    
    return await Deployment.RunAsync(() => 
    {
        var ecsService = new AzureNative.AwsConnector.EcsService("ecsService", new()
        {
            Location = "xqpjwxermnqxbnitxykbnjhw",
            Name = "Replace this value with a string matching RegExp ^(z=.{0,259}[^zs.]$)(z!.*[zzzzzzzz])",
            Properties = new AzureNative.AwsConnector.Inputs.EcsServicePropertiesArgs
            {
                Arn = "advapj",
                AwsAccountId = "egkrtzylfud",
                AwsProperties = new AzureNative.AwsConnector.Inputs.AwsEcsServicePropertiesArgs
                {
                    CapacityProviderStrategy = new[]
                    {
                        new AzureNative.AwsConnector.Inputs.CapacityProviderStrategyItemArgs
                        {
                            Base = 4,
                            CapacityProvider = "wlfpynlwozihqvkgynmdqqmojbs",
                            Weight = 28,
                        },
                    },
                    Cluster = "rdbkmvsugiuvbwkuzagsnrx",
                    DeploymentConfiguration = new AzureNative.AwsConnector.Inputs.DeploymentConfigurationArgs
                    {
                        Alarms = new AzureNative.AwsConnector.Inputs.DeploymentAlarmsArgs
                        {
                            AlarmNames = new[]
                            {
                                "cibbvixciizruhpdxhpkifpwsaq",
                            },
                            Enable = true,
                            Rollback = true,
                        },
                        DeploymentCircuitBreaker = new AzureNative.AwsConnector.Inputs.DeploymentCircuitBreakerArgs
                        {
                            Enable = true,
                            Rollback = true,
                        },
                        MaximumPercent = 14,
                        MinimumHealthyPercent = 21,
                    },
                    DeploymentController = new AzureNative.AwsConnector.Inputs.DeploymentControllerArgs
                    {
                        Type = AzureNative.AwsConnector.DeploymentControllerType.CODE_DEPLOY,
                    },
                    DesiredCount = 21,
                    EnableECSManagedTags = true,
                    EnableExecuteCommand = true,
                    HealthCheckGracePeriodSeconds = 1,
                    LaunchType = AzureNative.AwsConnector.LaunchType.EC2,
                    LoadBalancers = new[]
                    {
                        new AzureNative.AwsConnector.Inputs.LoadBalancerArgs
                        {
                            ContainerName = "vjvntpnuzyftbm",
                            ContainerPort = 17,
                            LoadBalancerName = "eryjxwmbfkms",
                            TargetGroupArn = "woxbyyccpmqyiy",
                        },
                    },
                    Name = "vo",
                    NetworkConfiguration = new AzureNative.AwsConnector.Inputs.NetworkConfigurationArgs
                    {
                        AwsvpcConfiguration = new AzureNative.AwsConnector.Inputs.AwsVpcConfigurationArgs
                        {
                            AssignPublicIp = AzureNative.AwsConnector.AwsVpcConfigurationAssignPublicIp.DISABLED,
                            SecurityGroups = new[]
                            {
                                "uoauevqyxylmvje",
                            },
                            Subnets = new[]
                            {
                                "gkqxeakxvyw",
                            },
                        },
                    },
                    PlacementConstraints = new[]
                    {
                        new AzureNative.AwsConnector.Inputs.PlacementConstraintArgs
                        {
                            Expression = "hxzfzxbfmqqiwgbpgn",
                            Type = AzureNative.AwsConnector.PlacementConstraintType.DistinctInstance,
                        },
                    },
                    PlacementStrategies = new[]
                    {
                        new AzureNative.AwsConnector.Inputs.PlacementStrategyArgs
                        {
                            Field = "tyrqdzgjrkwfhzwebvqld",
                            Type = AzureNative.AwsConnector.PlacementStrategyType.Binpack,
                        },
                    },
                    PlatformVersion = "sfsqyvslsustugopfnnzssjli",
                    PropagateTags = AzureNative.AwsConnector.PropagateTags.SERVICE,
                    Role = "te",
                    SchedulingStrategy = AzureNative.AwsConnector.SchedulingStrategy.DAEMON,
                    ServiceArn = "zuuoanjk",
                    ServiceConnectConfiguration = new AzureNative.AwsConnector.Inputs.ServiceConnectConfigurationArgs
                    {
                        Enabled = true,
                        LogConfiguration = new AzureNative.AwsConnector.Inputs.LogConfigurationArgs
                        {
                            LogDriver = "xwshxwanyuqrfzboxwfv",
                            SecretOptions = new[]
                            {
                                new AzureNative.AwsConnector.Inputs.SecretArgs
                                {
                                    Name = "uxsxwquwbafmsmbyyivhsjrjmfpmim",
                                    ValueFrom = "jnygsbiroyjlgrhs",
                                },
                            },
                        },
                        Namespace = "tlewpbulbuguuuvq",
                        Services = new[]
                        {
                            new AzureNative.AwsConnector.Inputs.ServiceConnectServiceArgs
                            {
                                ClientAliases = new[]
                                {
                                    new AzureNative.AwsConnector.Inputs.ServiceConnectClientAliasArgs
                                    {
                                        DnsName = "hnnavbjclqhbdebomjoqzo",
                                        Port = 16,
                                    },
                                },
                                DiscoveryName = "zuhijazofg",
                                IngressPortOverride = 26,
                                PortName = "q",
                                Timeout = new AzureNative.AwsConnector.Inputs.TimeoutConfigurationArgs
                                {
                                    IdleTimeoutSeconds = 11,
                                    PerRequestTimeoutSeconds = 22,
                                },
                                Tls = new AzureNative.AwsConnector.Inputs.ServiceConnectTlsConfigurationArgs
                                {
                                    IssuerCertificateAuthority = new AzureNative.AwsConnector.Inputs.ServiceConnectTlsCertificateAuthorityArgs
                                    {
                                        AwsPcaAuthorityArn = "fqrmk",
                                    },
                                    KmsKey = "jdjym",
                                    RoleArn = "stdhwuiylmutipeonkolqjnbqelds",
                                },
                            },
                        },
                    },
                    ServiceName = "lyblywxxfszkgaaornuxliolfbft",
                    ServiceRegistries = new[]
                    {
                        new AzureNative.AwsConnector.Inputs.ServiceRegistryArgs
                        {
                            ContainerName = "ppbxlxmpdbri",
                            ContainerPort = 7,
                            Port = 6,
                            RegistryArn = "qmfm",
                        },
                    },
                    Tags = new[]
                    {
                        new AzureNative.AwsConnector.Inputs.TagArgs
                        {
                            Key = "dteknaijsygghfdplikegztgz",
                            Value = "qukd",
                        },
                    },
                    TaskDefinition = "fozrumijzejhpjxeqkmthsswwuden",
                    VolumeConfigurations = new[]
                    {
                        new AzureNative.AwsConnector.Inputs.ServiceVolumeConfigurationArgs
                        {
                            ManagedEBSVolume = new AzureNative.AwsConnector.Inputs.ServiceManagedEBSVolumeConfigurationArgs
                            {
                                Encrypted = true,
                                FilesystemType = "ugwxqcjnrqonyao",
                                Iops = 10,
                                KmsKeyId = "oyuobklzhgpvg",
                                RoleArn = "gdudzczxymgopjjzqubzphgdi",
                                SizeInGiB = 15,
                                SnapshotId = "yff",
                                TagSpecifications = new[]
                                {
                                    new AzureNative.AwsConnector.Inputs.EBSTagSpecificationArgs
                                    {
                                        PropagateTags = AzureNative.AwsConnector.EBSTagSpecificationPropagateTags.SERVICE,
                                        ResourceType = "tocxgkuiblcccawaenqv",
                                        Tags = new[]
                                        {
                                            new AzureNative.AwsConnector.Inputs.TagArgs
                                            {
                                                Key = "dteknaijsygghfdplikegztgz",
                                                Value = "qukd",
                                            },
                                        },
                                    },
                                },
                                Throughput = 3,
                                VolumeType = "uwvjfmuzpksfpnfsukbunbuqcwxslx",
                            },
                            Name = "zkqnipaoexthwwot",
                        },
                    },
                },
                AwsRegion = "pwmulwhqhosmbthwzammshywxzaxhi",
                AwsSourceSchema = "woodigpcfntomkursi",
                AwsTags = 
                {
                    { "key3094", "gxbzlhku" },
                },
                PublicCloudConnectorsResourceId = "ghyukpeo",
                PublicCloudResourceName = "jumpzlzalckrkaqg",
            },
            ResourceGroupName = "rgecsService",
            Tags = 
            {
                { "key8484", "nnsyti" },
            },
        });
    
    });
    
    package main
    
    import (
    	awsconnector "github.com/pulumi/pulumi-azure-native-sdk/awsconnector/v2"
    	"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
    )
    
    func main() {
    	pulumi.Run(func(ctx *pulumi.Context) error {
    		_, err := awsconnector.NewEcsService(ctx, "ecsService", &awsconnector.EcsServiceArgs{
    			Location: pulumi.String("xqpjwxermnqxbnitxykbnjhw"),
    			Name:     pulumi.String("Replace this value with a string matching RegExp ^(z=.{0,259}[^zs.]$)(z!.*[zzzzzzzz])"),
    			Properties: &awsconnector.EcsServicePropertiesArgs{
    				Arn:          pulumi.String("advapj"),
    				AwsAccountId: pulumi.String("egkrtzylfud"),
    				AwsProperties: &awsconnector.AwsEcsServicePropertiesArgs{
    					CapacityProviderStrategy: awsconnector.CapacityProviderStrategyItemArray{
    						&awsconnector.CapacityProviderStrategyItemArgs{
    							Base:             pulumi.Int(4),
    							CapacityProvider: pulumi.String("wlfpynlwozihqvkgynmdqqmojbs"),
    							Weight:           pulumi.Int(28),
    						},
    					},
    					Cluster: pulumi.String("rdbkmvsugiuvbwkuzagsnrx"),
    					DeploymentConfiguration: &awsconnector.DeploymentConfigurationArgs{
    						Alarms: &awsconnector.DeploymentAlarmsArgs{
    							AlarmNames: pulumi.StringArray{
    								pulumi.String("cibbvixciizruhpdxhpkifpwsaq"),
    							},
    							Enable:   pulumi.Bool(true),
    							Rollback: pulumi.Bool(true),
    						},
    						DeploymentCircuitBreaker: &awsconnector.DeploymentCircuitBreakerArgs{
    							Enable:   pulumi.Bool(true),
    							Rollback: pulumi.Bool(true),
    						},
    						MaximumPercent:        pulumi.Int(14),
    						MinimumHealthyPercent: pulumi.Int(21),
    					},
    					DeploymentController: &awsconnector.DeploymentControllerArgs{
    						Type: pulumi.String(awsconnector.DeploymentControllerType_CODE_DEPLOY),
    					},
    					DesiredCount:                  pulumi.Int(21),
    					EnableECSManagedTags:          pulumi.Bool(true),
    					EnableExecuteCommand:          pulumi.Bool(true),
    					HealthCheckGracePeriodSeconds: pulumi.Int(1),
    					LaunchType:                    pulumi.String(awsconnector.LaunchTypeEC2),
    					LoadBalancers: awsconnector.LoadBalancerArray{
    						&awsconnector.LoadBalancerArgs{
    							ContainerName:    pulumi.String("vjvntpnuzyftbm"),
    							ContainerPort:    pulumi.Int(17),
    							LoadBalancerName: pulumi.String("eryjxwmbfkms"),
    							TargetGroupArn:   pulumi.String("woxbyyccpmqyiy"),
    						},
    					},
    					Name: pulumi.String("vo"),
    					NetworkConfiguration: &awsconnector.NetworkConfigurationArgs{
    						AwsvpcConfiguration: &awsconnector.AwsVpcConfigurationArgs{
    							AssignPublicIp: pulumi.String(awsconnector.AwsVpcConfigurationAssignPublicIpDISABLED),
    							SecurityGroups: pulumi.StringArray{
    								pulumi.String("uoauevqyxylmvje"),
    							},
    							Subnets: pulumi.StringArray{
    								pulumi.String("gkqxeakxvyw"),
    							},
    						},
    					},
    					PlacementConstraints: awsconnector.PlacementConstraintArray{
    						&awsconnector.PlacementConstraintArgs{
    							Expression: pulumi.String("hxzfzxbfmqqiwgbpgn"),
    							Type:       pulumi.String(awsconnector.PlacementConstraintTypeDistinctInstance),
    						},
    					},
    					PlacementStrategies: awsconnector.PlacementStrategyArray{
    						&awsconnector.PlacementStrategyArgs{
    							Field: pulumi.String("tyrqdzgjrkwfhzwebvqld"),
    							Type:  pulumi.String(awsconnector.PlacementStrategyTypeBinpack),
    						},
    					},
    					PlatformVersion:    pulumi.String("sfsqyvslsustugopfnnzssjli"),
    					PropagateTags:      pulumi.String(awsconnector.PropagateTagsSERVICE),
    					Role:               pulumi.String("te"),
    					SchedulingStrategy: pulumi.String(awsconnector.SchedulingStrategyDAEMON),
    					ServiceArn:         pulumi.String("zuuoanjk"),
    					ServiceConnectConfiguration: &awsconnector.ServiceConnectConfigurationArgs{
    						Enabled: pulumi.Bool(true),
    						LogConfiguration: &awsconnector.LogConfigurationArgs{
    							LogDriver: pulumi.String("xwshxwanyuqrfzboxwfv"),
    							SecretOptions: awsconnector.SecretArray{
    								&awsconnector.SecretArgs{
    									Name:      pulumi.String("uxsxwquwbafmsmbyyivhsjrjmfpmim"),
    									ValueFrom: pulumi.String("jnygsbiroyjlgrhs"),
    								},
    							},
    						},
    						Namespace: pulumi.String("tlewpbulbuguuuvq"),
    						Services: awsconnector.ServiceConnectServiceArray{
    							&awsconnector.ServiceConnectServiceArgs{
    								ClientAliases: awsconnector.ServiceConnectClientAliasArray{
    									&awsconnector.ServiceConnectClientAliasArgs{
    										DnsName: pulumi.String("hnnavbjclqhbdebomjoqzo"),
    										Port:    pulumi.Int(16),
    									},
    								},
    								DiscoveryName:       pulumi.String("zuhijazofg"),
    								IngressPortOverride: pulumi.Int(26),
    								PortName:            pulumi.String("q"),
    								Timeout: &awsconnector.TimeoutConfigurationArgs{
    									IdleTimeoutSeconds:       pulumi.Int(11),
    									PerRequestTimeoutSeconds: pulumi.Int(22),
    								},
    								Tls: &awsconnector.ServiceConnectTlsConfigurationArgs{
    									IssuerCertificateAuthority: &awsconnector.ServiceConnectTlsCertificateAuthorityArgs{
    										AwsPcaAuthorityArn: pulumi.String("fqrmk"),
    									},
    									KmsKey:  pulumi.String("jdjym"),
    									RoleArn: pulumi.String("stdhwuiylmutipeonkolqjnbqelds"),
    								},
    							},
    						},
    					},
    					ServiceName: pulumi.String("lyblywxxfszkgaaornuxliolfbft"),
    					ServiceRegistries: awsconnector.ServiceRegistryArray{
    						&awsconnector.ServiceRegistryArgs{
    							ContainerName: pulumi.String("ppbxlxmpdbri"),
    							ContainerPort: pulumi.Int(7),
    							Port:          pulumi.Int(6),
    							RegistryArn:   pulumi.String("qmfm"),
    						},
    					},
    					Tags: awsconnector.TagArray{
    						&awsconnector.TagArgs{
    							Key:   pulumi.String("dteknaijsygghfdplikegztgz"),
    							Value: pulumi.String("qukd"),
    						},
    					},
    					TaskDefinition: pulumi.String("fozrumijzejhpjxeqkmthsswwuden"),
    					VolumeConfigurations: awsconnector.ServiceVolumeConfigurationArray{
    						&awsconnector.ServiceVolumeConfigurationArgs{
    							ManagedEBSVolume: &awsconnector.ServiceManagedEBSVolumeConfigurationArgs{
    								Encrypted:      pulumi.Bool(true),
    								FilesystemType: pulumi.String("ugwxqcjnrqonyao"),
    								Iops:           pulumi.Int(10),
    								KmsKeyId:       pulumi.String("oyuobklzhgpvg"),
    								RoleArn:        pulumi.String("gdudzczxymgopjjzqubzphgdi"),
    								SizeInGiB:      pulumi.Int(15),
    								SnapshotId:     pulumi.String("yff"),
    								TagSpecifications: awsconnector.EBSTagSpecificationArray{
    									&awsconnector.EBSTagSpecificationArgs{
    										PropagateTags: pulumi.String(awsconnector.EBSTagSpecificationPropagateTagsSERVICE),
    										ResourceType:  pulumi.String("tocxgkuiblcccawaenqv"),
    										Tags: awsconnector.TagArray{
    											&awsconnector.TagArgs{
    												Key:   pulumi.String("dteknaijsygghfdplikegztgz"),
    												Value: pulumi.String("qukd"),
    											},
    										},
    									},
    								},
    								Throughput: pulumi.Int(3),
    								VolumeType: pulumi.String("uwvjfmuzpksfpnfsukbunbuqcwxslx"),
    							},
    							Name: pulumi.String("zkqnipaoexthwwot"),
    						},
    					},
    				},
    				AwsRegion:       pulumi.String("pwmulwhqhosmbthwzammshywxzaxhi"),
    				AwsSourceSchema: pulumi.String("woodigpcfntomkursi"),
    				AwsTags: pulumi.StringMap{
    					"key3094": pulumi.String("gxbzlhku"),
    				},
    				PublicCloudConnectorsResourceId: pulumi.String("ghyukpeo"),
    				PublicCloudResourceName:         pulumi.String("jumpzlzalckrkaqg"),
    			},
    			ResourceGroupName: pulumi.String("rgecsService"),
    			Tags: pulumi.StringMap{
    				"key8484": pulumi.String("nnsyti"),
    			},
    		})
    		if err != nil {
    			return err
    		}
    		return nil
    	})
    }
    
    package generated_program;
    
    import com.pulumi.Context;
    import com.pulumi.Pulumi;
    import com.pulumi.core.Output;
    import com.pulumi.azurenative.awsconnector.EcsService;
    import com.pulumi.azurenative.awsconnector.EcsServiceArgs;
    import com.pulumi.azurenative.awsconnector.inputs.EcsServicePropertiesArgs;
    import com.pulumi.azurenative.awsconnector.inputs.AwsEcsServicePropertiesArgs;
    import com.pulumi.azurenative.awsconnector.inputs.DeploymentConfigurationArgs;
    import com.pulumi.azurenative.awsconnector.inputs.DeploymentAlarmsArgs;
    import com.pulumi.azurenative.awsconnector.inputs.DeploymentCircuitBreakerArgs;
    import com.pulumi.azurenative.awsconnector.inputs.DeploymentControllerArgs;
    import com.pulumi.azurenative.awsconnector.inputs.NetworkConfigurationArgs;
    import com.pulumi.azurenative.awsconnector.inputs.AwsVpcConfigurationArgs;
    import com.pulumi.azurenative.awsconnector.inputs.ServiceConnectConfigurationArgs;
    import com.pulumi.azurenative.awsconnector.inputs.LogConfigurationArgs;
    import java.util.List;
    import java.util.ArrayList;
    import java.util.Map;
    import java.io.File;
    import java.nio.file.Files;
    import java.nio.file.Paths;
    
    public class App {
        public static void main(String[] args) {
            Pulumi.run(App::stack);
        }
    
        public static void stack(Context ctx) {
            var ecsService = new EcsService("ecsService", EcsServiceArgs.builder()
                .location("xqpjwxermnqxbnitxykbnjhw")
                .name("Replace this value with a string matching RegExp ^(z=.{0,259}[^zs.]$)(z!.*[zzzzzzzz])")
                .properties(EcsServicePropertiesArgs.builder()
                    .arn("advapj")
                    .awsAccountId("egkrtzylfud")
                    .awsProperties(AwsEcsServicePropertiesArgs.builder()
                        .capacityProviderStrategy(CapacityProviderStrategyItemArgs.builder()
                            .base(4)
                            .capacityProvider("wlfpynlwozihqvkgynmdqqmojbs")
                            .weight(28)
                            .build())
                        .cluster("rdbkmvsugiuvbwkuzagsnrx")
                        .deploymentConfiguration(DeploymentConfigurationArgs.builder()
                            .alarms(DeploymentAlarmsArgs.builder()
                                .alarmNames("cibbvixciizruhpdxhpkifpwsaq")
                                .enable(true)
                                .rollback(true)
                                .build())
                            .deploymentCircuitBreaker(DeploymentCircuitBreakerArgs.builder()
                                .enable(true)
                                .rollback(true)
                                .build())
                            .maximumPercent(14)
                            .minimumHealthyPercent(21)
                            .build())
                        .deploymentController(DeploymentControllerArgs.builder()
                            .type("CODE_DEPLOY")
                            .build())
                        .desiredCount(21)
                        .enableECSManagedTags(true)
                        .enableExecuteCommand(true)
                        .healthCheckGracePeriodSeconds(1)
                        .launchType("EC2")
                        .loadBalancers(LoadBalancerArgs.builder()
                            .containerName("vjvntpnuzyftbm")
                            .containerPort(17)
                            .loadBalancerName("eryjxwmbfkms")
                            .targetGroupArn("woxbyyccpmqyiy")
                            .build())
                        .name("vo")
                        .networkConfiguration(NetworkConfigurationArgs.builder()
                            .awsvpcConfiguration(AwsVpcConfigurationArgs.builder()
                                .assignPublicIp("DISABLED")
                                .securityGroups("uoauevqyxylmvje")
                                .subnets("gkqxeakxvyw")
                                .build())
                            .build())
                        .placementConstraints(PlacementConstraintArgs.builder()
                            .expression("hxzfzxbfmqqiwgbpgn")
                            .type("distinctInstance")
                            .build())
                        .placementStrategies(PlacementStrategyArgs.builder()
                            .field("tyrqdzgjrkwfhzwebvqld")
                            .type("binpack")
                            .build())
                        .platformVersion("sfsqyvslsustugopfnnzssjli")
                        .propagateTags("SERVICE")
                        .role("te")
                        .schedulingStrategy("DAEMON")
                        .serviceArn("zuuoanjk")
                        .serviceConnectConfiguration(ServiceConnectConfigurationArgs.builder()
                            .enabled(true)
                            .logConfiguration(LogConfigurationArgs.builder()
                                .logDriver("xwshxwanyuqrfzboxwfv")
                                .secretOptions(SecretArgs.builder()
                                    .name("uxsxwquwbafmsmbyyivhsjrjmfpmim")
                                    .valueFrom("jnygsbiroyjlgrhs")
                                    .build())
                                .build())
                            .namespace("tlewpbulbuguuuvq")
                            .services(ServiceConnectServiceArgs.builder()
                                .clientAliases(ServiceConnectClientAliasArgs.builder()
                                    .dnsName("hnnavbjclqhbdebomjoqzo")
                                    .port(16)
                                    .build())
                                .discoveryName("zuhijazofg")
                                .ingressPortOverride(26)
                                .portName("q")
                                .timeout(TimeoutConfigurationArgs.builder()
                                    .idleTimeoutSeconds(11)
                                    .perRequestTimeoutSeconds(22)
                                    .build())
                                .tls(ServiceConnectTlsConfigurationArgs.builder()
                                    .issuerCertificateAuthority(ServiceConnectTlsCertificateAuthorityArgs.builder()
                                        .awsPcaAuthorityArn("fqrmk")
                                        .build())
                                    .kmsKey("jdjym")
                                    .roleArn("stdhwuiylmutipeonkolqjnbqelds")
                                    .build())
                                .build())
                            .build())
                        .serviceName("lyblywxxfszkgaaornuxliolfbft")
                        .serviceRegistries(ServiceRegistryArgs.builder()
                            .containerName("ppbxlxmpdbri")
                            .containerPort(7)
                            .port(6)
                            .registryArn("qmfm")
                            .build())
                        .tags(TagArgs.builder()
                            .key("dteknaijsygghfdplikegztgz")
                            .value("qukd")
                            .build())
                        .taskDefinition("fozrumijzejhpjxeqkmthsswwuden")
                        .volumeConfigurations(ServiceVolumeConfigurationArgs.builder()
                            .managedEBSVolume(ServiceManagedEBSVolumeConfigurationArgs.builder()
                                .encrypted(true)
                                .filesystemType("ugwxqcjnrqonyao")
                                .iops(10)
                                .kmsKeyId("oyuobklzhgpvg")
                                .roleArn("gdudzczxymgopjjzqubzphgdi")
                                .sizeInGiB(15)
                                .snapshotId("yff")
                                .tagSpecifications(EBSTagSpecificationArgs.builder()
                                    .propagateTags("SERVICE")
                                    .resourceType("tocxgkuiblcccawaenqv")
                                    .tags(TagArgs.builder()
                                        .key("dteknaijsygghfdplikegztgz")
                                        .value("qukd")
                                        .build())
                                    .build())
                                .throughput(3)
                                .volumeType("uwvjfmuzpksfpnfsukbunbuqcwxslx")
                                .build())
                            .name("zkqnipaoexthwwot")
                            .build())
                        .build())
                    .awsRegion("pwmulwhqhosmbthwzammshywxzaxhi")
                    .awsSourceSchema("woodigpcfntomkursi")
                    .awsTags(Map.of("key3094", "gxbzlhku"))
                    .publicCloudConnectorsResourceId("ghyukpeo")
                    .publicCloudResourceName("jumpzlzalckrkaqg")
                    .build())
                .resourceGroupName("rgecsService")
                .tags(Map.of("key8484", "nnsyti"))
                .build());
    
        }
    }
    
    import pulumi
    import pulumi_azure_native as azure_native
    
    ecs_service = azure_native.awsconnector.EcsService("ecsService",
        location="xqpjwxermnqxbnitxykbnjhw",
        name="Replace this value with a string matching RegExp ^(z=.{0,259}[^zs.]$)(z!.*[zzzzzzzz])",
        properties={
            "arn": "advapj",
            "aws_account_id": "egkrtzylfud",
            "aws_properties": {
                "capacity_provider_strategy": [{
                    "base": 4,
                    "capacity_provider": "wlfpynlwozihqvkgynmdqqmojbs",
                    "weight": 28,
                }],
                "cluster": "rdbkmvsugiuvbwkuzagsnrx",
                "deployment_configuration": {
                    "alarms": {
                        "alarm_names": ["cibbvixciizruhpdxhpkifpwsaq"],
                        "enable": True,
                        "rollback": True,
                    },
                    "deployment_circuit_breaker": {
                        "enable": True,
                        "rollback": True,
                    },
                    "maximum_percent": 14,
                    "minimum_healthy_percent": 21,
                },
                "deployment_controller": {
                    "type": azure_native.awsconnector.DeploymentControllerType.COD_E_DEPLOY,
                },
                "desired_count": 21,
                "enable_ecs_managed_tags": True,
                "enable_execute_command": True,
                "health_check_grace_period_seconds": 1,
                "launch_type": azure_native.awsconnector.LaunchType.EC2,
                "load_balancers": [{
                    "container_name": "vjvntpnuzyftbm",
                    "container_port": 17,
                    "load_balancer_name": "eryjxwmbfkms",
                    "target_group_arn": "woxbyyccpmqyiy",
                }],
                "name": "vo",
                "network_configuration": {
                    "awsvpc_configuration": {
                        "assign_public_ip": azure_native.awsconnector.AwsVpcConfigurationAssignPublicIp.DISABLED,
                        "security_groups": ["uoauevqyxylmvje"],
                        "subnets": ["gkqxeakxvyw"],
                    },
                },
                "placement_constraints": [{
                    "expression": "hxzfzxbfmqqiwgbpgn",
                    "type": azure_native.awsconnector.PlacementConstraintType.DISTINCT_INSTANCE,
                }],
                "placement_strategies": [{
                    "field": "tyrqdzgjrkwfhzwebvqld",
                    "type": azure_native.awsconnector.PlacementStrategyType.BINPACK,
                }],
                "platform_version": "sfsqyvslsustugopfnnzssjli",
                "propagate_tags": azure_native.awsconnector.PropagateTags.SERVICE,
                "role": "te",
                "scheduling_strategy": azure_native.awsconnector.SchedulingStrategy.DAEMON,
                "service_arn": "zuuoanjk",
                "service_connect_configuration": {
                    "enabled": True,
                    "log_configuration": {
                        "log_driver": "xwshxwanyuqrfzboxwfv",
                        "secret_options": [{
                            "name": "uxsxwquwbafmsmbyyivhsjrjmfpmim",
                            "value_from": "jnygsbiroyjlgrhs",
                        }],
                    },
                    "namespace": "tlewpbulbuguuuvq",
                    "services": [{
                        "client_aliases": [{
                            "dns_name": "hnnavbjclqhbdebomjoqzo",
                            "port": 16,
                        }],
                        "discovery_name": "zuhijazofg",
                        "ingress_port_override": 26,
                        "port_name": "q",
                        "timeout": {
                            "idle_timeout_seconds": 11,
                            "per_request_timeout_seconds": 22,
                        },
                        "tls": {
                            "issuer_certificate_authority": {
                                "aws_pca_authority_arn": "fqrmk",
                            },
                            "kms_key": "jdjym",
                            "role_arn": "stdhwuiylmutipeonkolqjnbqelds",
                        },
                    }],
                },
                "service_name": "lyblywxxfszkgaaornuxliolfbft",
                "service_registries": [{
                    "container_name": "ppbxlxmpdbri",
                    "container_port": 7,
                    "port": 6,
                    "registry_arn": "qmfm",
                }],
                "tags": [{
                    "key": "dteknaijsygghfdplikegztgz",
                    "value": "qukd",
                }],
                "task_definition": "fozrumijzejhpjxeqkmthsswwuden",
                "volume_configurations": [{
                    "managed_ebs_volume": {
                        "encrypted": True,
                        "filesystem_type": "ugwxqcjnrqonyao",
                        "iops": 10,
                        "kms_key_id": "oyuobklzhgpvg",
                        "role_arn": "gdudzczxymgopjjzqubzphgdi",
                        "size_in_gi_b": 15,
                        "snapshot_id": "yff",
                        "tag_specifications": [{
                            "propagate_tags": azure_native.awsconnector.EBSTagSpecificationPropagateTags.SERVICE,
                            "resource_type": "tocxgkuiblcccawaenqv",
                            "tags": [{
                                "key": "dteknaijsygghfdplikegztgz",
                                "value": "qukd",
                            }],
                        }],
                        "throughput": 3,
                        "volume_type": "uwvjfmuzpksfpnfsukbunbuqcwxslx",
                    },
                    "name": "zkqnipaoexthwwot",
                }],
            },
            "aws_region": "pwmulwhqhosmbthwzammshywxzaxhi",
            "aws_source_schema": "woodigpcfntomkursi",
            "aws_tags": {
                "key3094": "gxbzlhku",
            },
            "public_cloud_connectors_resource_id": "ghyukpeo",
            "public_cloud_resource_name": "jumpzlzalckrkaqg",
        },
        resource_group_name="rgecsService",
        tags={
            "key8484": "nnsyti",
        })
    
    import * as pulumi from "@pulumi/pulumi";
    import * as azure_native from "@pulumi/azure-native";
    
    const ecsService = new azure_native.awsconnector.EcsService("ecsService", {
        location: "xqpjwxermnqxbnitxykbnjhw",
        name: "Replace this value with a string matching RegExp ^(z=.{0,259}[^zs.]$)(z!.*[zzzzzzzz])",
        properties: {
            arn: "advapj",
            awsAccountId: "egkrtzylfud",
            awsProperties: {
                capacityProviderStrategy: [{
                    base: 4,
                    capacityProvider: "wlfpynlwozihqvkgynmdqqmojbs",
                    weight: 28,
                }],
                cluster: "rdbkmvsugiuvbwkuzagsnrx",
                deploymentConfiguration: {
                    alarms: {
                        alarmNames: ["cibbvixciizruhpdxhpkifpwsaq"],
                        enable: true,
                        rollback: true,
                    },
                    deploymentCircuitBreaker: {
                        enable: true,
                        rollback: true,
                    },
                    maximumPercent: 14,
                    minimumHealthyPercent: 21,
                },
                deploymentController: {
                    type: azure_native.awsconnector.DeploymentControllerType.CODE_DEPLOY,
                },
                desiredCount: 21,
                enableECSManagedTags: true,
                enableExecuteCommand: true,
                healthCheckGracePeriodSeconds: 1,
                launchType: azure_native.awsconnector.LaunchType.EC2,
                loadBalancers: [{
                    containerName: "vjvntpnuzyftbm",
                    containerPort: 17,
                    loadBalancerName: "eryjxwmbfkms",
                    targetGroupArn: "woxbyyccpmqyiy",
                }],
                name: "vo",
                networkConfiguration: {
                    awsvpcConfiguration: {
                        assignPublicIp: azure_native.awsconnector.AwsVpcConfigurationAssignPublicIp.DISABLED,
                        securityGroups: ["uoauevqyxylmvje"],
                        subnets: ["gkqxeakxvyw"],
                    },
                },
                placementConstraints: [{
                    expression: "hxzfzxbfmqqiwgbpgn",
                    type: azure_native.awsconnector.PlacementConstraintType.DistinctInstance,
                }],
                placementStrategies: [{
                    field: "tyrqdzgjrkwfhzwebvqld",
                    type: azure_native.awsconnector.PlacementStrategyType.Binpack,
                }],
                platformVersion: "sfsqyvslsustugopfnnzssjli",
                propagateTags: azure_native.awsconnector.PropagateTags.SERVICE,
                role: "te",
                schedulingStrategy: azure_native.awsconnector.SchedulingStrategy.DAEMON,
                serviceArn: "zuuoanjk",
                serviceConnectConfiguration: {
                    enabled: true,
                    logConfiguration: {
                        logDriver: "xwshxwanyuqrfzboxwfv",
                        secretOptions: [{
                            name: "uxsxwquwbafmsmbyyivhsjrjmfpmim",
                            valueFrom: "jnygsbiroyjlgrhs",
                        }],
                    },
                    namespace: "tlewpbulbuguuuvq",
                    services: [{
                        clientAliases: [{
                            dnsName: "hnnavbjclqhbdebomjoqzo",
                            port: 16,
                        }],
                        discoveryName: "zuhijazofg",
                        ingressPortOverride: 26,
                        portName: "q",
                        timeout: {
                            idleTimeoutSeconds: 11,
                            perRequestTimeoutSeconds: 22,
                        },
                        tls: {
                            issuerCertificateAuthority: {
                                awsPcaAuthorityArn: "fqrmk",
                            },
                            kmsKey: "jdjym",
                            roleArn: "stdhwuiylmutipeonkolqjnbqelds",
                        },
                    }],
                },
                serviceName: "lyblywxxfszkgaaornuxliolfbft",
                serviceRegistries: [{
                    containerName: "ppbxlxmpdbri",
                    containerPort: 7,
                    port: 6,
                    registryArn: "qmfm",
                }],
                tags: [{
                    key: "dteknaijsygghfdplikegztgz",
                    value: "qukd",
                }],
                taskDefinition: "fozrumijzejhpjxeqkmthsswwuden",
                volumeConfigurations: [{
                    managedEBSVolume: {
                        encrypted: true,
                        filesystemType: "ugwxqcjnrqonyao",
                        iops: 10,
                        kmsKeyId: "oyuobklzhgpvg",
                        roleArn: "gdudzczxymgopjjzqubzphgdi",
                        sizeInGiB: 15,
                        snapshotId: "yff",
                        tagSpecifications: [{
                            propagateTags: azure_native.awsconnector.EBSTagSpecificationPropagateTags.SERVICE,
                            resourceType: "tocxgkuiblcccawaenqv",
                            tags: [{
                                key: "dteknaijsygghfdplikegztgz",
                                value: "qukd",
                            }],
                        }],
                        throughput: 3,
                        volumeType: "uwvjfmuzpksfpnfsukbunbuqcwxslx",
                    },
                    name: "zkqnipaoexthwwot",
                }],
            },
            awsRegion: "pwmulwhqhosmbthwzammshywxzaxhi",
            awsSourceSchema: "woodigpcfntomkursi",
            awsTags: {
                key3094: "gxbzlhku",
            },
            publicCloudConnectorsResourceId: "ghyukpeo",
            publicCloudResourceName: "jumpzlzalckrkaqg",
        },
        resourceGroupName: "rgecsService",
        tags: {
            key8484: "nnsyti",
        },
    });
    
    resources:
      ecsService:
        type: azure-native:awsconnector:EcsService
        properties:
          location: xqpjwxermnqxbnitxykbnjhw
          name: Replace this value with a string matching RegExp ^(z=.{0,259}[^zs.]$)(z!.*[zzzzzzzz])
          properties:
            arn: advapj
            awsAccountId: egkrtzylfud
            awsProperties:
              capacityProviderStrategy:
                - base: 4
                  capacityProvider: wlfpynlwozihqvkgynmdqqmojbs
                  weight: 28
              cluster: rdbkmvsugiuvbwkuzagsnrx
              deploymentConfiguration:
                alarms:
                  alarmNames:
                    - cibbvixciizruhpdxhpkifpwsaq
                  enable: true
                  rollback: true
                deploymentCircuitBreaker:
                  enable: true
                  rollback: true
                maximumPercent: 14
                minimumHealthyPercent: 21
              deploymentController:
                type: CODE_DEPLOY
              desiredCount: 21
              enableECSManagedTags: true
              enableExecuteCommand: true
              healthCheckGracePeriodSeconds: 1
              launchType: EC2
              loadBalancers:
                - containerName: vjvntpnuzyftbm
                  containerPort: 17
                  loadBalancerName: eryjxwmbfkms
                  targetGroupArn: woxbyyccpmqyiy
              name: vo
              networkConfiguration:
                awsvpcConfiguration:
                  assignPublicIp: DISABLED
                  securityGroups:
                    - uoauevqyxylmvje
                  subnets:
                    - gkqxeakxvyw
              placementConstraints:
                - expression: hxzfzxbfmqqiwgbpgn
                  type: distinctInstance
              placementStrategies:
                - field: tyrqdzgjrkwfhzwebvqld
                  type: binpack
              platformVersion: sfsqyvslsustugopfnnzssjli
              propagateTags: SERVICE
              role: te
              schedulingStrategy: DAEMON
              serviceArn: zuuoanjk
              serviceConnectConfiguration:
                enabled: true
                logConfiguration:
                  logDriver: xwshxwanyuqrfzboxwfv
                  secretOptions:
                    - name: uxsxwquwbafmsmbyyivhsjrjmfpmim
                      valueFrom: jnygsbiroyjlgrhs
                namespace: tlewpbulbuguuuvq
                services:
                  - clientAliases:
                      - dnsName: hnnavbjclqhbdebomjoqzo
                        port: 16
                    discoveryName: zuhijazofg
                    ingressPortOverride: 26
                    portName: q
                    timeout:
                      idleTimeoutSeconds: 11
                      perRequestTimeoutSeconds: 22
                    tls:
                      issuerCertificateAuthority:
                        awsPcaAuthorityArn: fqrmk
                      kmsKey: jdjym
                      roleArn: stdhwuiylmutipeonkolqjnbqelds
              serviceName: lyblywxxfszkgaaornuxliolfbft
              serviceRegistries:
                - containerName: ppbxlxmpdbri
                  containerPort: 7
                  port: 6
                  registryArn: qmfm
              tags:
                - key: dteknaijsygghfdplikegztgz
                  value: qukd
              taskDefinition: fozrumijzejhpjxeqkmthsswwuden
              volumeConfigurations:
                - managedEBSVolume:
                    encrypted: true
                    filesystemType: ugwxqcjnrqonyao
                    iops: 10
                    kmsKeyId: oyuobklzhgpvg
                    roleArn: gdudzczxymgopjjzqubzphgdi
                    sizeInGiB: 15
                    snapshotId: yff
                    tagSpecifications:
                      - propagateTags: SERVICE
                        resourceType: tocxgkuiblcccawaenqv
                        tags:
                          - key: dteknaijsygghfdplikegztgz
                            value: qukd
                    throughput: 3
                    volumeType: uwvjfmuzpksfpnfsukbunbuqcwxslx
                  name: zkqnipaoexthwwot
            awsRegion: pwmulwhqhosmbthwzammshywxzaxhi
            awsSourceSchema: woodigpcfntomkursi
            awsTags:
              key3094: gxbzlhku
            publicCloudConnectorsResourceId: ghyukpeo
            publicCloudResourceName: jumpzlzalckrkaqg
          resourceGroupName: rgecsService
          tags:
            key8484: nnsyti
    

    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 string
    The unique name of the resource.
    args EcsServiceArgs
    The arguments to resource properties.
    opts CustomResourceOptions
    Bag of options to control resource's behavior.
    resource_name str
    The unique name of the resource.
    args 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 string
    The unique name of the resource.
    args EcsServiceArgs
    The arguments to resource properties.
    opts ResourceOption
    Bag of options to control resource's behavior.
    name string
    The unique name of the resource.
    args EcsServiceArgs
    The arguments to resource properties.
    opts CustomResourceOptions
    Bag of options to control resource's behavior.
    name String
    The unique name of the resource.
    args 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:

    ResourceGroupName string
    The name of the resource group. The name is case insensitive.
    Location string
    The geo-location where the resource lives
    Name string
    Name of EcsService
    Properties Pulumi.AzureNative.AwsConnector.Inputs.EcsServiceProperties
    The resource-specific properties for this resource.
    Tags Dictionary<string, string>
    Resource tags.
    ResourceGroupName string
    The name of the resource group. The name is case insensitive.
    Location string
    The geo-location where the resource lives
    Name string
    Name of EcsService
    Properties EcsServicePropertiesArgs
    The resource-specific properties for this resource.
    Tags map[string]string
    Resource tags.
    resourceGroupName String
    The name of the resource group. The name is case insensitive.
    location String
    The geo-location where the resource lives
    name String
    Name of EcsService
    properties EcsServiceProperties
    The resource-specific properties for this resource.
    tags Map<String,String>
    Resource tags.
    resourceGroupName string
    The name of the resource group. The name is case insensitive.
    location string
    The geo-location where the resource lives
    name string
    Name of EcsService
    properties EcsServiceProperties
    The resource-specific properties for this resource.
    tags {[key: string]: string}
    Resource tags.
    resource_group_name str
    The name of the resource group. The name is case insensitive.
    location str
    The geo-location where the resource lives
    name str
    Name of EcsService
    properties EcsServicePropertiesArgs
    The resource-specific properties for this resource.
    tags Mapping[str, str]
    Resource tags.
    resourceGroupName String
    The name of the resource group. The name is case insensitive.
    location String
    The geo-location where the resource lives
    name String
    Name of EcsService
    properties Property Map
    The resource-specific properties for this resource.
    tags Map<String>
    Resource tags.

    Outputs

    All input properties are implicitly available as output properties. Additionally, the EcsService resource produces the following output properties:

    Id string
    The provider-assigned unique ID for this managed resource.
    SystemData Pulumi.AzureNative.AwsConnector.Outputs.SystemDataResponse
    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"
    Id string
    The provider-assigned unique ID for this managed resource.
    SystemData SystemDataResponse
    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"
    id String
    The provider-assigned unique ID for this managed resource.
    systemData SystemDataResponse
    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"
    id string
    The provider-assigned unique ID for this managed resource.
    systemData SystemDataResponse
    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"
    id str
    The provider-assigned unique ID for this managed resource.
    system_data SystemDataResponse
    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"
    id String
    The provider-assigned unique ID for this managed resource.
    systemData 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

    CapacityProviderStrategy List<Pulumi.AzureNative.AwsConnector.Inputs.CapacityProviderStrategyItem>
    The capacity provider strategy to use for the service. If a capacityProviderStrategy is specified, the launchType parameter must be omitted. If no capacityProviderStrategy or launchType is specified, the defaultCapacityProviderStrategy for 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.
    DeploymentConfiguration Pulumi.AzureNative.AwsConnector.Inputs.DeploymentConfiguration
    Optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks. The DeploymentConfiguration property specifies optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks.
    DeploymentController Pulumi.AzureNative.AwsConnector.Inputs.DeploymentController
    The deployment controller to use for the service. If no deployment controller is specified, the default value of ECS is 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.
    DesiredCount 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 1 is used. When using the DAEMON scheduling strategy, the desired count is not required. For existing services, if a desired count is not specified, it is omitted from the operation.
    EnableECSManagedTags 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 propagateTags request parameter.
    EnableExecuteCommand bool
    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.
    HealthCheckGracePeriodSeconds int
    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 0 is used. If you do not use an Elastic Load Balancing, we recommend that you use the startPeriod in 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.
    LaunchType string | Pulumi.AzureNative.AwsConnector.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.
    LoadBalancers List<Pulumi.AzureNative.AwsConnector.Inputs.LoadBalancer>
    A list of load balancer objects to associate with the service. If you specify the Role property, LoadBalancers must 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
    NetworkConfiguration Pulumi.AzureNative.AwsConnector.Inputs.NetworkConfiguration
    The network configuration for the service. This parameter is required for task definitions that use the awsvpc network 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. The NetworkConfiguration property specifies an object representing the network configuration for a task or service.
    PlacementConstraints List<Pulumi.AzureNative.AwsConnector.Inputs.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.
    PlacementStrategies List<Pulumi.AzureNative.AwsConnector.Inputs.PlacementStrategy>
    The placement strategy objects to use for tasks in your service. You can specify a maximum of 5 strategy rules for each service.
    PlatformVersion 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 LATEST platform version is used. For more information, see platform versions in the Amazon Elastic Container Service Developer Guide.
    PropagateTags string | Pulumi.AzureNative.AwsConnector.PropagateTags
    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 awsvpc network mode. If you specify the role parameter, you must also specify a load balancer object with the loadBalancers parameter. 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 the awsvpc network 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 name bar has a path of /foo/ then you would specify /foo/bar as the role name. For more information, see Friendly names and paths in the IAM User Guide.
    SchedulingStrategy string | Pulumi.AzureNative.AwsConnector.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 the CODE_DEPLOY or EXTERNAL deployment 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 the CODE_DEPLOY or EXTERNAL deployment controller types don't support the DAEMON scheduling strategy.
    ServiceArn string
    Property serviceArn
    ServiceConnectConfiguration Pulumi.AzureNative.AwsConnector.Inputs.ServiceConnectConfiguration
    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.
    ServiceName 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 ServiceName is configured. This is because AWS CloudFormation creates the replacement service first, but each ServiceName must be unique in the cluster.
    ServiceRegistries List<Pulumi.AzureNative.AwsConnector.Inputs.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.
    Tags List<Pulumi.AzureNative.AwsConnector.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.
    TaskDefinition string
    The family and revision (family:revision) or full ARN of the task definition to run in your service. If a revision isn't specified, the latest ACTIVE revision is used. A task definition must be specified if the service uses either the ECS or CODE_DEPLOY deployment controllers. For more information about deployment types, see Amazon ECS deployment types.
    VolumeConfigurations List<Pulumi.AzureNative.AwsConnector.Inputs.ServiceVolumeConfiguration>
    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.
    CapacityProviderStrategy []CapacityProviderStrategyItem
    The capacity provider strategy to use for the service. If a capacityProviderStrategy is specified, the launchType parameter must be omitted. If no capacityProviderStrategy or launchType is specified, the defaultCapacityProviderStrategy for 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.
    DeploymentConfiguration DeploymentConfiguration
    Optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks. The DeploymentConfiguration property specifies optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks.
    DeploymentController DeploymentController
    The deployment controller to use for the service. If no deployment controller is specified, the default value of ECS is 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.
    DesiredCount 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 1 is used. When using the DAEMON scheduling strategy, the desired count is not required. For existing services, if a desired count is not specified, it is omitted from the operation.
    EnableECSManagedTags 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 propagateTags request parameter.
    EnableExecuteCommand bool
    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.
    HealthCheckGracePeriodSeconds int
    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 0 is used. If you do not use an Elastic Load Balancing, we recommend that you use the startPeriod in 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.
    LaunchType 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.
    LoadBalancers []LoadBalancer
    A list of load balancer objects to associate with the service. If you specify the Role property, LoadBalancers must 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
    NetworkConfiguration NetworkConfiguration
    The network configuration for the service. This parameter is required for task definitions that use the awsvpc network 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. The NetworkConfiguration property specifies an object representing the network configuration for a task or service.
    PlacementConstraints []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.
    PlacementStrategies []PlacementStrategy
    The placement strategy objects to use for tasks in your service. You can specify a maximum of 5 strategy rules for each service.
    PlatformVersion 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 LATEST platform version is used. For more information, see platform versions in the Amazon Elastic Container Service Developer Guide.
    PropagateTags string | PropagateTags
    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 awsvpc network mode. If you specify the role parameter, you must also specify a load balancer object with the loadBalancers parameter. 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 the awsvpc network 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 name bar has a path of /foo/ then you would specify /foo/bar as the role name. For more information, see Friendly names and paths in the IAM User Guide.
    SchedulingStrategy 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 the CODE_DEPLOY or EXTERNAL deployment 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 the CODE_DEPLOY or EXTERNAL deployment controller types don't support the DAEMON scheduling strategy.
    ServiceArn string
    Property serviceArn
    ServiceConnectConfiguration ServiceConnectConfiguration
    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.
    ServiceName 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 ServiceName is configured. This is because AWS CloudFormation creates the replacement service first, but each ServiceName must be unique in the cluster.
    ServiceRegistries []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.
    Tags []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.
    TaskDefinition string
    The family and revision (family:revision) or full ARN of the task definition to run in your service. If a revision isn't specified, the latest ACTIVE revision is used. A task definition must be specified if the service uses either the ECS or CODE_DEPLOY deployment controllers. For more information about deployment types, see Amazon ECS deployment types.
    VolumeConfigurations []ServiceVolumeConfiguration
    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.
    capacityProviderStrategy List<CapacityProviderStrategyItem>
    The capacity provider strategy to use for the service. If a capacityProviderStrategy is specified, the launchType parameter must be omitted. If no capacityProviderStrategy or launchType is specified, the defaultCapacityProviderStrategy for 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.
    deploymentConfiguration DeploymentConfiguration
    Optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks. The DeploymentConfiguration property specifies optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks.
    deploymentController DeploymentController
    The deployment controller to use for the service. If no deployment controller is specified, the default value of ECS is 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.
    desiredCount 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 1 is used. When using the DAEMON scheduling strategy, the desired count is not required. For existing services, if a desired count is not specified, it is omitted from the operation.
    enableECSManagedTags 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 propagateTags request parameter.
    enableExecuteCommand Boolean
    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.
    healthCheckGracePeriodSeconds Integer
    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 0 is used. If you do not use an Elastic Load Balancing, we recommend that you use the startPeriod in 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.
    launchType 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.
    loadBalancers List<LoadBalancer>
    A list of load balancer objects to associate with the service. If you specify the Role property, LoadBalancers must 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
    networkConfiguration NetworkConfiguration
    The network configuration for the service. This parameter is required for task definitions that use the awsvpc network 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. The NetworkConfiguration property specifies an object representing the network configuration for a task or service.
    placementConstraints 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.
    placementStrategies 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.
    platformVersion 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 LATEST platform version is used. For more information, see platform versions in the Amazon Elastic Container Service Developer Guide.
    propagateTags String | PropagateTags
    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 awsvpc network mode. If you specify the role parameter, you must also specify a load balancer object with the loadBalancers parameter. 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 the awsvpc network 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 name bar has a path of /foo/ then you would specify /foo/bar as the role name. For more information, see Friendly names and paths in the IAM User Guide.
    schedulingStrategy 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 the CODE_DEPLOY or EXTERNAL deployment 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 the CODE_DEPLOY or EXTERNAL deployment controller types don't support the DAEMON scheduling strategy.
    serviceArn String
    Property serviceArn
    serviceConnectConfiguration ServiceConnectConfiguration
    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.
    serviceName 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 ServiceName is configured. This is because AWS CloudFormation creates the replacement service first, but each ServiceName must be unique in the cluster.
    serviceRegistries 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.
    tags 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.
    taskDefinition String
    The family and revision (family:revision) or full ARN of the task definition to run in your service. If a revision isn't specified, the latest ACTIVE revision is used. A task definition must be specified if the service uses either the ECS or CODE_DEPLOY deployment controllers. For more information about deployment types, see Amazon ECS deployment types.
    volumeConfigurations List<ServiceVolumeConfiguration>
    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.
    capacityProviderStrategy CapacityProviderStrategyItem[]
    The capacity provider strategy to use for the service. If a capacityProviderStrategy is specified, the launchType parameter must be omitted. If no capacityProviderStrategy or launchType is specified, the defaultCapacityProviderStrategy for 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.
    deploymentConfiguration DeploymentConfiguration
    Optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks. The DeploymentConfiguration property specifies optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks.
    deploymentController DeploymentController
    The deployment controller to use for the service. If no deployment controller is specified, the default value of ECS is 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.
    desiredCount 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 1 is used. When using the DAEMON scheduling strategy, the desired count is not required. For existing services, if a desired count is not specified, it is omitted from the operation.
    enableECSManagedTags 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 propagateTags request parameter.
    enableExecuteCommand boolean
    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.
    healthCheckGracePeriodSeconds number
    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 0 is used. If you do not use an Elastic Load Balancing, we recommend that you use the startPeriod in 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.
    launchType 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.
    loadBalancers LoadBalancer[]
    A list of load balancer objects to associate with the service. If you specify the Role property, LoadBalancers must 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
    networkConfiguration NetworkConfiguration
    The network configuration for the service. This parameter is required for task definitions that use the awsvpc network 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. The NetworkConfiguration property specifies an object representing the network configuration for a task or service.
    placementConstraints 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.
    placementStrategies PlacementStrategy[]
    The placement strategy objects to use for tasks in your service. You can specify a maximum of 5 strategy rules for each service.
    platformVersion 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 LATEST platform version is used. For more information, see platform versions in the Amazon Elastic Container Service Developer Guide.
    propagateTags string | PropagateTags
    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 awsvpc network mode. If you specify the role parameter, you must also specify a load balancer object with the loadBalancers parameter. 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 the awsvpc network 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 name bar has a path of /foo/ then you would specify /foo/bar as the role name. For more information, see Friendly names and paths in the IAM User Guide.
    schedulingStrategy 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 the CODE_DEPLOY or EXTERNAL deployment 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 the CODE_DEPLOY or EXTERNAL deployment controller types don't support the DAEMON scheduling strategy.
    serviceArn string
    Property serviceArn
    serviceConnectConfiguration ServiceConnectConfiguration
    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.
    serviceName 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 ServiceName is configured. This is because AWS CloudFormation creates the replacement service first, but each ServiceName must be unique in the cluster.
    serviceRegistries 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.
    tags 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.
    taskDefinition string
    The family and revision (family:revision) or full ARN of the task definition to run in your service. If a revision isn't specified, the latest ACTIVE revision is used. A task definition must be specified if the service uses either the ECS or CODE_DEPLOY deployment controllers. For more information about deployment types, see Amazon ECS deployment types.
    volumeConfigurations ServiceVolumeConfiguration[]
    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_strategy Sequence[CapacityProviderStrategyItem]
    The capacity provider strategy to use for the service. If a capacityProviderStrategy is specified, the launchType parameter must be omitted. If no capacityProviderStrategy or launchType is specified, the defaultCapacityProviderStrategy for 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 DeploymentConfiguration property 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 ECS is 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 1 is used. When using the DAEMON scheduling strategy, the desired count is not required. For existing services, if a desired count is not specified, it is omitted from the operation.
    enable_ecs_managed_tags 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 propagateTags request parameter.
    enable_execute_command bool
    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_grace_period_seconds int
    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 0 is used. If you do not use an Elastic Load Balancing, we recommend that you use the startPeriod in 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 Role property, LoadBalancers must 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 awsvpc network 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. The NetworkConfiguration property 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 LATEST platform version is used. For more information, see platform versions in the Amazon Elastic Container Service Developer Guide.
    propagate_tags str | PropagateTags
    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 awsvpc network mode. If you specify the role parameter, you must also specify a load balancer object with the loadBalancers parameter. 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 the awsvpc network 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 name bar has a path of /foo/ then you would specify /foo/bar as 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 the CODE_DEPLOY or EXTERNAL deployment 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 the CODE_DEPLOY or EXTERNAL deployment controller types don't support the DAEMON scheduling strategy.
    service_arn str
    Property serviceArn
    service_connect_configuration ServiceConnectConfiguration
    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 ServiceName is configured. This is because AWS CloudFormation creates the replacement service first, but each ServiceName must 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.
    tags 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 family and revision (family:revision) or full ARN of the task definition to run in your service. If a revision isn't specified, the latest ACTIVE revision is used. A task definition must be specified if the service uses either the ECS or CODE_DEPLOY deployment controllers. For more information about deployment types, see Amazon ECS deployment types.
    volume_configurations Sequence[ServiceVolumeConfiguration]
    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.
    capacityProviderStrategy List<Property Map>
    The capacity provider strategy to use for the service. If a capacityProviderStrategy is specified, the launchType parameter must be omitted. If no capacityProviderStrategy or launchType is specified, the defaultCapacityProviderStrategy for 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.
    deploymentConfiguration Property Map
    Optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks. The DeploymentConfiguration property specifies optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks.
    deploymentController Property Map
    The deployment controller to use for the service. If no deployment controller is specified, the default value of ECS is 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.
    desiredCount 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 1 is used. When using the DAEMON scheduling strategy, the desired count is not required. For existing services, if a desired count is not specified, it is omitted from the operation.
    enableECSManagedTags 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 propagateTags request parameter.
    enableExecuteCommand Boolean
    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.
    healthCheckGracePeriodSeconds Number
    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 0 is used. If you do not use an Elastic Load Balancing, we recommend that you use the startPeriod in 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.
    launchType 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.
    loadBalancers List<Property Map>
    A list of load balancer objects to associate with the service. If you specify the Role property, LoadBalancers must 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
    networkConfiguration Property Map
    The network configuration for the service. This parameter is required for task definitions that use the awsvpc network 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. The NetworkConfiguration property specifies an object representing the network configuration for a task or service.
    placementConstraints 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.
    placementStrategies 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.
    platformVersion 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 LATEST platform version is used. For more information, see platform versions in the Amazon Elastic Container Service Developer Guide.
    propagateTags 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 awsvpc network mode. If you specify the role parameter, you must also specify a load balancer object with the loadBalancers parameter. 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 the awsvpc network 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 name bar has a path of /foo/ then you would specify /foo/bar as the role name. For more information, see Friendly names and paths in the IAM User Guide.
    schedulingStrategy 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 the CODE_DEPLOY or EXTERNAL deployment 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 the CODE_DEPLOY or EXTERNAL deployment controller types don't support the DAEMON scheduling strategy.
    serviceArn String
    Property serviceArn
    serviceConnectConfiguration Property Map
    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.
    serviceName 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 ServiceName is configured. This is because AWS CloudFormation creates the replacement service first, but each ServiceName must be unique in the cluster.
    serviceRegistries 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.
    tags 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.
    taskDefinition String
    The family and revision (family:revision) or full ARN of the task definition to run in your service. If a revision isn't specified, the latest ACTIVE revision is used. A task definition must be specified if the service uses either the ECS or CODE_DEPLOY deployment controllers. For more information about deployment types, see Amazon ECS deployment types.
    volumeConfigurations 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

    CapacityProviderStrategy List<Pulumi.AzureNative.AwsConnector.Inputs.CapacityProviderStrategyItemResponse>
    The capacity provider strategy to use for the service. If a capacityProviderStrategy is specified, the launchType parameter must be omitted. If no capacityProviderStrategy or launchType is specified, the defaultCapacityProviderStrategy for 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.
    DeploymentConfiguration Pulumi.AzureNative.AwsConnector.Inputs.DeploymentConfigurationResponse
    Optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks. The DeploymentConfiguration property specifies optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks.
    DeploymentController Pulumi.AzureNative.AwsConnector.Inputs.DeploymentControllerResponse
    The deployment controller to use for the service. If no deployment controller is specified, the default value of ECS is 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.
    DesiredCount 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 1 is used. When using the DAEMON scheduling strategy, the desired count is not required. For existing services, if a desired count is not specified, it is omitted from the operation.
    EnableECSManagedTags 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 propagateTags request parameter.
    EnableExecuteCommand bool
    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.
    HealthCheckGracePeriodSeconds int
    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 0 is used. If you do not use an Elastic Load Balancing, we recommend that you use the startPeriod in 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.
    LaunchType 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.
    LoadBalancers List<Pulumi.AzureNative.AwsConnector.Inputs.LoadBalancerResponse>
    A list of load balancer objects to associate with the service. If you specify the Role property, LoadBalancers must 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
    NetworkConfiguration Pulumi.AzureNative.AwsConnector.Inputs.NetworkConfigurationResponse
    The network configuration for the service. This parameter is required for task definitions that use the awsvpc network 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. The NetworkConfiguration property specifies an object representing the network configuration for a task or service.
    PlacementConstraints List<Pulumi.AzureNative.AwsConnector.Inputs.PlacementConstraintResponse>
    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.
    PlacementStrategies List<Pulumi.AzureNative.AwsConnector.Inputs.PlacementStrategyResponse>
    The placement strategy objects to use for tasks in your service. You can specify a maximum of 5 strategy rules for each service.
    PlatformVersion 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 LATEST platform version is used. For more information, see platform versions in the Amazon Elastic Container Service Developer Guide.
    PropagateTags 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 awsvpc network mode. If you specify the role parameter, you must also specify a load balancer object with the loadBalancers parameter. 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 the awsvpc network 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 name bar has a path of /foo/ then you would specify /foo/bar as the role name. For more information, see Friendly names and paths in the IAM User Guide.
    SchedulingStrategy 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 the CODE_DEPLOY or EXTERNAL deployment 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 the CODE_DEPLOY or EXTERNAL deployment controller types don't support the DAEMON scheduling strategy.
    ServiceArn string
    Property serviceArn
    ServiceConnectConfiguration Pulumi.AzureNative.AwsConnector.Inputs.ServiceConnectConfigurationResponse
    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.
    ServiceName 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 ServiceName is configured. This is because AWS CloudFormation creates the replacement service first, but each ServiceName must be unique in the cluster.
    ServiceRegistries List<Pulumi.AzureNative.AwsConnector.Inputs.ServiceRegistryResponse>
    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.
    Tags List<Pulumi.AzureNative.AwsConnector.Inputs.TagResponse>
    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.
    TaskDefinition string
    The family and revision (family:revision) or full ARN of the task definition to run in your service. If a revision isn't specified, the latest ACTIVE revision is used. A task definition must be specified if the service uses either the ECS or CODE_DEPLOY deployment controllers. For more information about deployment types, see Amazon ECS deployment types.
    VolumeConfigurations List<Pulumi.AzureNative.AwsConnector.Inputs.ServiceVolumeConfigurationResponse>
    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.
    CapacityProviderStrategy []CapacityProviderStrategyItemResponse
    The capacity provider strategy to use for the service. If a capacityProviderStrategy is specified, the launchType parameter must be omitted. If no capacityProviderStrategy or launchType is specified, the defaultCapacityProviderStrategy for 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.
    DeploymentConfiguration DeploymentConfigurationResponse
    Optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks. The DeploymentConfiguration property specifies optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks.
    DeploymentController DeploymentControllerResponse
    The deployment controller to use for the service. If no deployment controller is specified, the default value of ECS is 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.
    DesiredCount 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 1 is used. When using the DAEMON scheduling strategy, the desired count is not required. For existing services, if a desired count is not specified, it is omitted from the operation.
    EnableECSManagedTags 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 propagateTags request parameter.
    EnableExecuteCommand bool
    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.
    HealthCheckGracePeriodSeconds int
    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 0 is used. If you do not use an Elastic Load Balancing, we recommend that you use the startPeriod in 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.
    LaunchType 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.
    LoadBalancers []LoadBalancerResponse
    A list of load balancer objects to associate with the service. If you specify the Role property, LoadBalancers must 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
    NetworkConfiguration NetworkConfigurationResponse
    The network configuration for the service. This parameter is required for task definitions that use the awsvpc network 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. The NetworkConfiguration property specifies an object representing the network configuration for a task or service.
    PlacementConstraints []PlacementConstraintResponse
    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.
    PlacementStrategies []PlacementStrategyResponse
    The placement strategy objects to use for tasks in your service. You can specify a maximum of 5 strategy rules for each service.
    PlatformVersion 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 LATEST platform version is used. For more information, see platform versions in the Amazon Elastic Container Service Developer Guide.
    PropagateTags 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 awsvpc network mode. If you specify the role parameter, you must also specify a load balancer object with the loadBalancers parameter. 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 the awsvpc network 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 name bar has a path of /foo/ then you would specify /foo/bar as the role name. For more information, see Friendly names and paths in the IAM User Guide.
    SchedulingStrategy 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 the CODE_DEPLOY or EXTERNAL deployment 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 the CODE_DEPLOY or EXTERNAL deployment controller types don't support the DAEMON scheduling strategy.
    ServiceArn string
    Property serviceArn
    ServiceConnectConfiguration ServiceConnectConfigurationResponse
    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.
    ServiceName 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 ServiceName is configured. This is because AWS CloudFormation creates the replacement service first, but each ServiceName must be unique in the cluster.
    ServiceRegistries []ServiceRegistryResponse
    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.
    Tags []TagResponse
    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.
    TaskDefinition string
    The family and revision (family:revision) or full ARN of the task definition to run in your service. If a revision isn't specified, the latest ACTIVE revision is used. A task definition must be specified if the service uses either the ECS or CODE_DEPLOY deployment controllers. For more information about deployment types, see Amazon ECS deployment types.
    VolumeConfigurations []ServiceVolumeConfigurationResponse
    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.
    capacityProviderStrategy List<CapacityProviderStrategyItemResponse>
    The capacity provider strategy to use for the service. If a capacityProviderStrategy is specified, the launchType parameter must be omitted. If no capacityProviderStrategy or launchType is specified, the defaultCapacityProviderStrategy for 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.
    deploymentConfiguration DeploymentConfigurationResponse
    Optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks. The DeploymentConfiguration property specifies optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks.
    deploymentController DeploymentControllerResponse
    The deployment controller to use for the service. If no deployment controller is specified, the default value of ECS is 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.
    desiredCount 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 1 is used. When using the DAEMON scheduling strategy, the desired count is not required. For existing services, if a desired count is not specified, it is omitted from the operation.
    enableECSManagedTags 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 propagateTags request parameter.
    enableExecuteCommand Boolean
    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.
    healthCheckGracePeriodSeconds Integer
    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 0 is used. If you do not use an Elastic Load Balancing, we recommend that you use the startPeriod in 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.
    launchType 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.
    loadBalancers List<LoadBalancerResponse>
    A list of load balancer objects to associate with the service. If you specify the Role property, LoadBalancers must 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
    networkConfiguration NetworkConfigurationResponse
    The network configuration for the service. This parameter is required for task definitions that use the awsvpc network 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. The NetworkConfiguration property specifies an object representing the network configuration for a task or service.
    placementConstraints List<PlacementConstraintResponse>
    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.
    placementStrategies List<PlacementStrategyResponse>
    The placement strategy objects to use for tasks in your service. You can specify a maximum of 5 strategy rules for each service.
    platformVersion 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 LATEST platform version is used. For more information, see platform versions in the Amazon Elastic Container Service Developer Guide.
    propagateTags 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 awsvpc network mode. If you specify the role parameter, you must also specify a load balancer object with the loadBalancers parameter. 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 the awsvpc network 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 name bar has a path of /foo/ then you would specify /foo/bar as the role name. For more information, see Friendly names and paths in the IAM User Guide.
    schedulingStrategy 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 the CODE_DEPLOY or EXTERNAL deployment 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 the CODE_DEPLOY or EXTERNAL deployment controller types don't support the DAEMON scheduling strategy.
    serviceArn String
    Property serviceArn
    serviceConnectConfiguration ServiceConnectConfigurationResponse
    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.
    serviceName 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 ServiceName is configured. This is because AWS CloudFormation creates the replacement service first, but each ServiceName must be unique in the cluster.
    serviceRegistries List<ServiceRegistryResponse>
    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.
    tags List<TagResponse>
    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.
    taskDefinition String
    The family and revision (family:revision) or full ARN of the task definition to run in your service. If a revision isn't specified, the latest ACTIVE revision is used. A task definition must be specified if the service uses either the ECS or CODE_DEPLOY deployment controllers. For more information about deployment types, see Amazon ECS deployment types.
    volumeConfigurations List<ServiceVolumeConfigurationResponse>
    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.
    capacityProviderStrategy CapacityProviderStrategyItemResponse[]
    The capacity provider strategy to use for the service. If a capacityProviderStrategy is specified, the launchType parameter must be omitted. If no capacityProviderStrategy or launchType is specified, the defaultCapacityProviderStrategy for 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.
    deploymentConfiguration DeploymentConfigurationResponse
    Optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks. The DeploymentConfiguration property specifies optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks.
    deploymentController DeploymentControllerResponse
    The deployment controller to use for the service. If no deployment controller is specified, the default value of ECS is 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.
    desiredCount 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 1 is used. When using the DAEMON scheduling strategy, the desired count is not required. For existing services, if a desired count is not specified, it is omitted from the operation.
    enableECSManagedTags 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 propagateTags request parameter.
    enableExecuteCommand boolean
    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.
    healthCheckGracePeriodSeconds number
    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 0 is used. If you do not use an Elastic Load Balancing, we recommend that you use the startPeriod in 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.
    launchType 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.
    loadBalancers LoadBalancerResponse[]
    A list of load balancer objects to associate with the service. If you specify the Role property, LoadBalancers must 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
    networkConfiguration NetworkConfigurationResponse
    The network configuration for the service. This parameter is required for task definitions that use the awsvpc network 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. The NetworkConfiguration property specifies an object representing the network configuration for a task or service.
    placementConstraints PlacementConstraintResponse[]
    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.
    placementStrategies PlacementStrategyResponse[]
    The placement strategy objects to use for tasks in your service. You can specify a maximum of 5 strategy rules for each service.
    platformVersion 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 LATEST platform version is used. For more information, see platform versions in the Amazon Elastic Container Service Developer Guide.
    propagateTags 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 awsvpc network mode. If you specify the role parameter, you must also specify a load balancer object with the loadBalancers parameter. 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 the awsvpc network 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 name bar has a path of /foo/ then you would specify /foo/bar as the role name. For more information, see Friendly names and paths in the IAM User Guide.
    schedulingStrategy 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 the CODE_DEPLOY or EXTERNAL deployment 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 the CODE_DEPLOY or EXTERNAL deployment controller types don't support the DAEMON scheduling strategy.
    serviceArn string
    Property serviceArn
    serviceConnectConfiguration ServiceConnectConfigurationResponse
    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.
    serviceName 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 ServiceName is configured. This is because AWS CloudFormation creates the replacement service first, but each ServiceName must be unique in the cluster.
    serviceRegistries ServiceRegistryResponse[]
    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.
    tags TagResponse[]
    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.
    taskDefinition string
    The family and revision (family:revision) or full ARN of the task definition to run in your service. If a revision isn't specified, the latest ACTIVE revision is used. A task definition must be specified if the service uses either the ECS or CODE_DEPLOY deployment controllers. For more information about deployment types, see Amazon ECS deployment types.
    volumeConfigurations ServiceVolumeConfigurationResponse[]
    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_strategy Sequence[CapacityProviderStrategyItemResponse]
    The capacity provider strategy to use for the service. If a capacityProviderStrategy is specified, the launchType parameter must be omitted. If no capacityProviderStrategy or launchType is specified, the defaultCapacityProviderStrategy for 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 DeploymentConfigurationResponse
    Optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks. The DeploymentConfiguration property specifies optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks.
    deployment_controller DeploymentControllerResponse
    The deployment controller to use for the service. If no deployment controller is specified, the default value of ECS is 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 1 is used. When using the DAEMON scheduling strategy, the desired count is not required. For existing services, if a desired count is not specified, it is omitted from the operation.
    enable_ecs_managed_tags 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 propagateTags request parameter.
    enable_execute_command bool
    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_grace_period_seconds int
    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 0 is used. If you do not use an Elastic Load Balancing, we recommend that you use the startPeriod in 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[LoadBalancerResponse]
    A list of load balancer objects to associate with the service. If you specify the Role property, LoadBalancers must 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 NetworkConfigurationResponse
    The network configuration for the service. This parameter is required for task definitions that use the awsvpc network 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. The NetworkConfiguration property specifies an object representing the network configuration for a task or service.
    placement_constraints Sequence[PlacementConstraintResponse]
    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[PlacementStrategyResponse]
    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 LATEST platform version is used. For more information, see platform versions in the Amazon Elastic Container Service Developer Guide.
    propagate_tags 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 awsvpc network mode. If you specify the role parameter, you must also specify a load balancer object with the loadBalancers parameter. 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 the awsvpc network 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 name bar has a path of /foo/ then you would specify /foo/bar as 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 the CODE_DEPLOY or EXTERNAL deployment 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 the CODE_DEPLOY or EXTERNAL deployment controller types don't support the DAEMON scheduling strategy.
    service_arn str
    Property serviceArn
    service_connect_configuration ServiceConnectConfigurationResponse
    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 ServiceName is configured. This is because AWS CloudFormation creates the replacement service first, but each ServiceName must be unique in the cluster.
    service_registries Sequence[ServiceRegistryResponse]
    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.
    tags Sequence[TagResponse]
    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 family and revision (family:revision) or full ARN of the task definition to run in your service. If a revision isn't specified, the latest ACTIVE revision is used. A task definition must be specified if the service uses either the ECS or CODE_DEPLOY deployment controllers. For more information about deployment types, see Amazon ECS deployment types.
    volume_configurations Sequence[ServiceVolumeConfigurationResponse]
    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.
    capacityProviderStrategy List<Property Map>
    The capacity provider strategy to use for the service. If a capacityProviderStrategy is specified, the launchType parameter must be omitted. If no capacityProviderStrategy or launchType is specified, the defaultCapacityProviderStrategy for 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.
    deploymentConfiguration Property Map
    Optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks. The DeploymentConfiguration property specifies optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks.
    deploymentController Property Map
    The deployment controller to use for the service. If no deployment controller is specified, the default value of ECS is 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.
    desiredCount 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 1 is used. When using the DAEMON scheduling strategy, the desired count is not required. For existing services, if a desired count is not specified, it is omitted from the operation.
    enableECSManagedTags 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 propagateTags request parameter.
    enableExecuteCommand Boolean
    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.
    healthCheckGracePeriodSeconds Number
    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 0 is used. If you do not use an Elastic Load Balancing, we recommend that you use the startPeriod in 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.
    launchType 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.
    loadBalancers List<Property Map>
    A list of load balancer objects to associate with the service. If you specify the Role property, LoadBalancers must 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
    networkConfiguration Property Map
    The network configuration for the service. This parameter is required for task definitions that use the awsvpc network 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. The NetworkConfiguration property specifies an object representing the network configuration for a task or service.
    placementConstraints 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.
    placementStrategies 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.
    platformVersion 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 LATEST platform version is used. For more information, see platform versions in the Amazon Elastic Container Service Developer Guide.
    propagateTags 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 awsvpc network mode. If you specify the role parameter, you must also specify a load balancer object with the loadBalancers parameter. 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 the awsvpc network 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 name bar has a path of /foo/ then you would specify /foo/bar as the role name. For more information, see Friendly names and paths in the IAM User Guide.
    schedulingStrategy 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 the CODE_DEPLOY or EXTERNAL deployment 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 the CODE_DEPLOY or EXTERNAL deployment controller types don't support the DAEMON scheduling strategy.
    serviceArn String
    Property serviceArn
    serviceConnectConfiguration Property Map
    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.
    serviceName 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 ServiceName is configured. This is because AWS CloudFormation creates the replacement service first, but each ServiceName must be unique in the cluster.
    serviceRegistries 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.
    tags 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.
    taskDefinition String
    The family and revision (family:revision) or full ARN of the task definition to run in your service. If a revision isn't specified, the latest ACTIVE revision is used. A task definition must be specified if the service uses either the ECS or CODE_DEPLOY deployment controllers. For more information about deployment types, see Amazon ECS deployment types.
    volumeConfigurations 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

    AssignPublicIp string | Pulumi.AzureNative.AwsConnector.AwsVpcConfigurationAssignPublicIp
    Whether the task's elastic network interface receives a public IP address. The default value is DISABLED.
    SecurityGroups 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.
    AssignPublicIp string | AwsVpcConfigurationAssignPublicIp
    Whether the task's elastic network interface receives a public IP address. The default value is DISABLED.
    SecurityGroups []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.
    assignPublicIp String | AwsVpcConfigurationAssignPublicIp
    Whether the task's elastic network interface receives a public IP address. The default value is DISABLED.
    securityGroups 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.
    assignPublicIp string | AwsVpcConfigurationAssignPublicIp
    Whether the task's elastic network interface receives a public IP address. The default value is DISABLED.
    securityGroups 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_ip str | AwsVpcConfigurationAssignPublicIp
    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.
    assignPublicIp String | "DISABLED" | "ENABLED"
    Whether the task's elastic network interface receives a public IP address. The default value is DISABLED.
    securityGroups 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

    DISABLED
    DISABLEDAwsVpcConfigurationAssignPublicIp enum DISABLED
    ENABLED
    ENABLEDAwsVpcConfigurationAssignPublicIp enum ENABLED
    AwsVpcConfigurationAssignPublicIpDISABLED
    DISABLEDAwsVpcConfigurationAssignPublicIp enum DISABLED
    AwsVpcConfigurationAssignPublicIpENABLED
    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

    AssignPublicIp string
    Whether the task's elastic network interface receives a public IP address. The default value is DISABLED.
    SecurityGroups 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.
    AssignPublicIp string
    Whether the task's elastic network interface receives a public IP address. The default value is DISABLED.
    SecurityGroups []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.
    assignPublicIp String
    Whether the task's elastic network interface receives a public IP address. The default value is DISABLED.
    securityGroups 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.
    assignPublicIp string
    Whether the task's elastic network interface receives a public IP address. The default value is DISABLED.
    securityGroups 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_ip str
    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.
    assignPublicIp String
    Whether the task's elastic network interface receives a public IP address. The default value is DISABLED.
    securityGroups 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

    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 0 is used.
    CapacityProvider 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 weight value is taken into consideration after the base value, if defined, is satisfied. If no weight value is specified, the default value of 0 is 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 of 0 can't be used to place tasks. If you specify multiple capacity providers in a strategy that all have a weight of 0, any RunTask or CreateService actions 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 of 1, then when the base is satisfied, the tasks will be split evenly across the two capacity providers. Using that same logic, if you specify a weight of 1 for capacityProviderA and a weight of 4 for 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 0 is used.
    CapacityProvider 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 weight value is taken into consideration after the base value, if defined, is satisfied. If no weight value is specified, the default value of 0 is 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 of 0 can't be used to place tasks. If you specify multiple capacity providers in a strategy that all have a weight of 0, any RunTask or CreateService actions 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 of 1, then when the base is satisfied, the tasks will be split evenly across the two capacity providers. Using that same logic, if you specify a weight of 1 for capacityProviderA and a weight of 4 for 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 0 is used.
    capacityProvider 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 weight value is taken into consideration after the base value, if defined, is satisfied. If no weight value is specified, the default value of 0 is 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 of 0 can't be used to place tasks. If you specify multiple capacity providers in a strategy that all have a weight of 0, any RunTask or CreateService actions 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 of 1, then when the base is satisfied, the tasks will be split evenly across the two capacity providers. Using that same logic, if you specify a weight of 1 for capacityProviderA and a weight of 4 for 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 0 is used.
    capacityProvider 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 weight value is taken into consideration after the base value, if defined, is satisfied. If no weight value is specified, the default value of 0 is 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 of 0 can't be used to place tasks. If you specify multiple capacity providers in a strategy that all have a weight of 0, any RunTask or CreateService actions 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 of 1, then when the base is satisfied, the tasks will be split evenly across the two capacity providers. Using that same logic, if you specify a weight of 1 for capacityProviderA and a weight of 4 for 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 0 is 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 weight value is taken into consideration after the base value, if defined, is satisfied. If no weight value is specified, the default value of 0 is 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 of 0 can't be used to place tasks. If you specify multiple capacity providers in a strategy that all have a weight of 0, any RunTask or CreateService actions 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 of 1, then when the base is satisfied, the tasks will be split evenly across the two capacity providers. Using that same logic, if you specify a weight of 1 for capacityProviderA and a weight of 4 for 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 0 is used.
    capacityProvider 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 weight value is taken into consideration after the base value, if defined, is satisfied. If no weight value is specified, the default value of 0 is 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 of 0 can't be used to place tasks. If you specify multiple capacity providers in a strategy that all have a weight of 0, any RunTask or CreateService actions 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 of 1, then when the base is satisfied, the tasks will be split evenly across the two capacity providers. Using that same logic, if you specify a weight of 1 for capacityProviderA and a weight of 4 for capacityProviderB, then for every one task that's run using capacityProviderA, four tasks would use capacityProviderB.

    CapacityProviderStrategyItemResponse, 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 0 is used.
    CapacityProvider 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 weight value is taken into consideration after the base value, if defined, is satisfied. If no weight value is specified, the default value of 0 is 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 of 0 can't be used to place tasks. If you specify multiple capacity providers in a strategy that all have a weight of 0, any RunTask or CreateService actions 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 of 1, then when the base is satisfied, the tasks will be split evenly across the two capacity providers. Using that same logic, if you specify a weight of 1 for capacityProviderA and a weight of 4 for 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 0 is used.
    CapacityProvider 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 weight value is taken into consideration after the base value, if defined, is satisfied. If no weight value is specified, the default value of 0 is 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 of 0 can't be used to place tasks. If you specify multiple capacity providers in a strategy that all have a weight of 0, any RunTask or CreateService actions 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 of 1, then when the base is satisfied, the tasks will be split evenly across the two capacity providers. Using that same logic, if you specify a weight of 1 for capacityProviderA and a weight of 4 for 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 0 is used.
    capacityProvider 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 weight value is taken into consideration after the base value, if defined, is satisfied. If no weight value is specified, the default value of 0 is 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 of 0 can't be used to place tasks. If you specify multiple capacity providers in a strategy that all have a weight of 0, any RunTask or CreateService actions 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 of 1, then when the base is satisfied, the tasks will be split evenly across the two capacity providers. Using that same logic, if you specify a weight of 1 for capacityProviderA and a weight of 4 for 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 0 is used.
    capacityProvider 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 weight value is taken into consideration after the base value, if defined, is satisfied. If no weight value is specified, the default value of 0 is 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 of 0 can't be used to place tasks. If you specify multiple capacity providers in a strategy that all have a weight of 0, any RunTask or CreateService actions 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 of 1, then when the base is satisfied, the tasks will be split evenly across the two capacity providers. Using that same logic, if you specify a weight of 1 for capacityProviderA and a weight of 4 for 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 0 is 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 weight value is taken into consideration after the base value, if defined, is satisfied. If no weight value is specified, the default value of 0 is 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 of 0 can't be used to place tasks. If you specify multiple capacity providers in a strategy that all have a weight of 0, any RunTask or CreateService actions 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 of 1, then when the base is satisfied, the tasks will be split evenly across the two capacity providers. Using that same logic, if you specify a weight of 1 for capacityProviderA and a weight of 4 for 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 0 is used.
    capacityProvider 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 weight value is taken into consideration after the base value, if defined, is satisfied. If no weight value is specified, the default value of 0 is 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 of 0 can't be used to place tasks. If you specify multiple capacity providers in a strategy that all have a weight of 0, any RunTask or CreateService actions 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 of 1, then when the base is satisfied, the tasks will be split evenly across the two capacity providers. Using that same logic, if you specify a weight of 1 for capacityProviderA and a weight of 4 for capacityProviderB, then for every one task that's run using capacityProviderA, four tasks would use capacityProviderB.

    DeploymentAlarms, DeploymentAlarmsArgs

    AlarmNames 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.
    AlarmNames []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.
    alarmNames 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.
    alarmNames 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.
    alarmNames 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

    AlarmNames 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.
    AlarmNames []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.
    alarmNames 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.
    alarmNames 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.
    alarmNames 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

    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

    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

    Alarms Pulumi.AzureNative.AwsConnector.Inputs.DeploymentAlarms
    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 DeploymentAlarms method to detect failures when the DeploymentController is set to ECS (rolling update). For more information, see Rolling update in the Amazon Elastic Container Service Developer Guide.
    DeploymentCircuitBreaker Pulumi.AzureNative.AwsConnector.Inputs.DeploymentCircuitBreaker
    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.
    MaximumPercent int
    If a service is using the rolling update (ECS) deployment type, the maximumPercent parameter represents an upper limit on the number of your service's tasks that are allowed in the RUNNING or PENDING state during a deployment, as a percentage of the desiredCount (rounded down to the nearest integer). This parameter enables you to define the deployment batch size. For example, if your service is using the REPLICA service scheduler and has a desiredCount of four tasks and a maximumPercent value 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 default maximumPercent value for a service using the REPLICA service scheduler is 200%. If a service is using either the blue/green (CODE_DEPLOY) or EXTERNAL deployment 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 the RUNNING state while the container instances are in the DRAINING state. 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.
    MinimumHealthyPercent int
    If a service is using the rolling update (ECS) deployment type, the minimumHealthyPercent represents a lower limit on the number of your service's tasks that must remain in the RUNNING state during a deployment, as a percentage of the desiredCount (rounded up to the nearest integer). This parameter enables you to deploy without using additional cluster capacity. For example, if your service has a desiredCount of four tasks and a minimumHealthyPercent of 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 a RUNNING state 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) or EXTERNAL deployment 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 the RUNNING state while the container instances are in the DRAINING state. If a service is using either the blue/green (CODE_DEPLOY) or EXTERNAL deployment 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 DeploymentAlarms
    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 DeploymentAlarms method to detect failures when the DeploymentController is set to ECS (rolling update). For more information, see Rolling update in the Amazon Elastic Container Service Developer Guide.
    DeploymentCircuitBreaker DeploymentCircuitBreaker
    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.
    MaximumPercent int
    If a service is using the rolling update (ECS) deployment type, the maximumPercent parameter represents an upper limit on the number of your service's tasks that are allowed in the RUNNING or PENDING state during a deployment, as a percentage of the desiredCount (rounded down to the nearest integer). This parameter enables you to define the deployment batch size. For example, if your service is using the REPLICA service scheduler and has a desiredCount of four tasks and a maximumPercent value 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 default maximumPercent value for a service using the REPLICA service scheduler is 200%. If a service is using either the blue/green (CODE_DEPLOY) or EXTERNAL deployment 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 the RUNNING state while the container instances are in the DRAINING state. 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.
    MinimumHealthyPercent int
    If a service is using the rolling update (ECS) deployment type, the minimumHealthyPercent represents a lower limit on the number of your service's tasks that must remain in the RUNNING state during a deployment, as a percentage of the desiredCount (rounded up to the nearest integer). This parameter enables you to deploy without using additional cluster capacity. For example, if your service has a desiredCount of four tasks and a minimumHealthyPercent of 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 a RUNNING state 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) or EXTERNAL deployment 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 the RUNNING state while the container instances are in the DRAINING state. If a service is using either the blue/green (CODE_DEPLOY) or EXTERNAL deployment 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 DeploymentAlarms
    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 DeploymentAlarms method to detect failures when the DeploymentController is set to ECS (rolling update). For more information, see Rolling update in the Amazon Elastic Container Service Developer Guide.
    deploymentCircuitBreaker DeploymentCircuitBreaker
    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.
    maximumPercent Integer
    If a service is using the rolling update (ECS) deployment type, the maximumPercent parameter represents an upper limit on the number of your service's tasks that are allowed in the RUNNING or PENDING state during a deployment, as a percentage of the desiredCount (rounded down to the nearest integer). This parameter enables you to define the deployment batch size. For example, if your service is using the REPLICA service scheduler and has a desiredCount of four tasks and a maximumPercent value 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 default maximumPercent value for a service using the REPLICA service scheduler is 200%. If a service is using either the blue/green (CODE_DEPLOY) or EXTERNAL deployment 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 the RUNNING state while the container instances are in the DRAINING state. 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.
    minimumHealthyPercent Integer
    If a service is using the rolling update (ECS) deployment type, the minimumHealthyPercent represents a lower limit on the number of your service's tasks that must remain in the RUNNING state during a deployment, as a percentage of the desiredCount (rounded up to the nearest integer). This parameter enables you to deploy without using additional cluster capacity. For example, if your service has a desiredCount of four tasks and a minimumHealthyPercent of 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 a RUNNING state 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) or EXTERNAL deployment 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 the RUNNING state while the container instances are in the DRAINING state. If a service is using either the blue/green (CODE_DEPLOY) or EXTERNAL deployment 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 DeploymentAlarms
    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 DeploymentAlarms method to detect failures when the DeploymentController is set to ECS (rolling update). For more information, see Rolling update in the Amazon Elastic Container Service Developer Guide.
    deploymentCircuitBreaker DeploymentCircuitBreaker
    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.
    maximumPercent number
    If a service is using the rolling update (ECS) deployment type, the maximumPercent parameter represents an upper limit on the number of your service's tasks that are allowed in the RUNNING or PENDING state during a deployment, as a percentage of the desiredCount (rounded down to the nearest integer). This parameter enables you to define the deployment batch size. For example, if your service is using the REPLICA service scheduler and has a desiredCount of four tasks and a maximumPercent value 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 default maximumPercent value for a service using the REPLICA service scheduler is 200%. If a service is using either the blue/green (CODE_DEPLOY) or EXTERNAL deployment 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 the RUNNING state while the container instances are in the DRAINING state. 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.
    minimumHealthyPercent number
    If a service is using the rolling update (ECS) deployment type, the minimumHealthyPercent represents a lower limit on the number of your service's tasks that must remain in the RUNNING state during a deployment, as a percentage of the desiredCount (rounded up to the nearest integer). This parameter enables you to deploy without using additional cluster capacity. For example, if your service has a desiredCount of four tasks and a minimumHealthyPercent of 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 a RUNNING state 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) or EXTERNAL deployment 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 the RUNNING state while the container instances are in the DRAINING state. If a service is using either the blue/green (CODE_DEPLOY) or EXTERNAL deployment 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 DeploymentAlarms
    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 DeploymentAlarms method to detect failures when the DeploymentController is set to ECS (rolling update). For more information, see Rolling update in the Amazon Elastic Container Service Developer Guide.
    deployment_circuit_breaker DeploymentCircuitBreaker
    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, the maximumPercent parameter represents an upper limit on the number of your service's tasks that are allowed in the RUNNING or PENDING state during a deployment, as a percentage of the desiredCount (rounded down to the nearest integer). This parameter enables you to define the deployment batch size. For example, if your service is using the REPLICA service scheduler and has a desiredCount of four tasks and a maximumPercent value 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 default maximumPercent value for a service using the REPLICA service scheduler is 200%. If a service is using either the blue/green (CODE_DEPLOY) or EXTERNAL deployment 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 the RUNNING state while the container instances are in the DRAINING state. 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_percent int
    If a service is using the rolling update (ECS) deployment type, the minimumHealthyPercent represents a lower limit on the number of your service's tasks that must remain in the RUNNING state during a deployment, as a percentage of the desiredCount (rounded up to the nearest integer). This parameter enables you to deploy without using additional cluster capacity. For example, if your service has a desiredCount of four tasks and a minimumHealthyPercent of 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 a RUNNING state 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) or EXTERNAL deployment 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 the RUNNING state while the container instances are in the DRAINING state. If a service is using either the blue/green (CODE_DEPLOY) or EXTERNAL deployment 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 DeploymentAlarms method to detect failures when the DeploymentController is set to ECS (rolling update). For more information, see Rolling update in the Amazon Elastic Container Service Developer Guide.
    deploymentCircuitBreaker Property Map
    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.
    maximumPercent Number
    If a service is using the rolling update (ECS) deployment type, the maximumPercent parameter represents an upper limit on the number of your service's tasks that are allowed in the RUNNING or PENDING state during a deployment, as a percentage of the desiredCount (rounded down to the nearest integer). This parameter enables you to define the deployment batch size. For example, if your service is using the REPLICA service scheduler and has a desiredCount of four tasks and a maximumPercent value 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 default maximumPercent value for a service using the REPLICA service scheduler is 200%. If a service is using either the blue/green (CODE_DEPLOY) or EXTERNAL deployment 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 the RUNNING state while the container instances are in the DRAINING state. 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.
    minimumHealthyPercent Number
    If a service is using the rolling update (ECS) deployment type, the minimumHealthyPercent represents a lower limit on the number of your service's tasks that must remain in the RUNNING state during a deployment, as a percentage of the desiredCount (rounded up to the nearest integer). This parameter enables you to deploy without using additional cluster capacity. For example, if your service has a desiredCount of four tasks and a minimumHealthyPercent of 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 a RUNNING state 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) or EXTERNAL deployment 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 the RUNNING state while the container instances are in the DRAINING state. If a service is using either the blue/green (CODE_DEPLOY) or EXTERNAL deployment 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

    Alarms Pulumi.AzureNative.AwsConnector.Inputs.DeploymentAlarmsResponse
    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 DeploymentAlarms method to detect failures when the DeploymentController is set to ECS (rolling update). For more information, see Rolling update in the Amazon Elastic Container Service Developer Guide.
    DeploymentCircuitBreaker Pulumi.AzureNative.AwsConnector.Inputs.DeploymentCircuitBreakerResponse
    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.
    MaximumPercent int
    If a service is using the rolling update (ECS) deployment type, the maximumPercent parameter represents an upper limit on the number of your service's tasks that are allowed in the RUNNING or PENDING state during a deployment, as a percentage of the desiredCount (rounded down to the nearest integer). This parameter enables you to define the deployment batch size. For example, if your service is using the REPLICA service scheduler and has a desiredCount of four tasks and a maximumPercent value 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 default maximumPercent value for a service using the REPLICA service scheduler is 200%. If a service is using either the blue/green (CODE_DEPLOY) or EXTERNAL deployment 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 the RUNNING state while the container instances are in the DRAINING state. 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.
    MinimumHealthyPercent int
    If a service is using the rolling update (ECS) deployment type, the minimumHealthyPercent represents a lower limit on the number of your service's tasks that must remain in the RUNNING state during a deployment, as a percentage of the desiredCount (rounded up to the nearest integer). This parameter enables you to deploy without using additional cluster capacity. For example, if your service has a desiredCount of four tasks and a minimumHealthyPercent of 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 a RUNNING state 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) or EXTERNAL deployment 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 the RUNNING state while the container instances are in the DRAINING state. If a service is using either the blue/green (CODE_DEPLOY) or EXTERNAL deployment 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 DeploymentAlarmsResponse
    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 DeploymentAlarms method to detect failures when the DeploymentController is set to ECS (rolling update). For more information, see Rolling update in the Amazon Elastic Container Service Developer Guide.
    DeploymentCircuitBreaker DeploymentCircuitBreakerResponse
    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.
    MaximumPercent int
    If a service is using the rolling update (ECS) deployment type, the maximumPercent parameter represents an upper limit on the number of your service's tasks that are allowed in the RUNNING or PENDING state during a deployment, as a percentage of the desiredCount (rounded down to the nearest integer). This parameter enables you to define the deployment batch size. For example, if your service is using the REPLICA service scheduler and has a desiredCount of four tasks and a maximumPercent value 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 default maximumPercent value for a service using the REPLICA service scheduler is 200%. If a service is using either the blue/green (CODE_DEPLOY) or EXTERNAL deployment 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 the RUNNING state while the container instances are in the DRAINING state. 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.
    MinimumHealthyPercent int
    If a service is using the rolling update (ECS) deployment type, the minimumHealthyPercent represents a lower limit on the number of your service's tasks that must remain in the RUNNING state during a deployment, as a percentage of the desiredCount (rounded up to the nearest integer). This parameter enables you to deploy without using additional cluster capacity. For example, if your service has a desiredCount of four tasks and a minimumHealthyPercent of 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 a RUNNING state 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) or EXTERNAL deployment 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 the RUNNING state while the container instances are in the DRAINING state. If a service is using either the blue/green (CODE_DEPLOY) or EXTERNAL deployment 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 DeploymentAlarmsResponse
    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 DeploymentAlarms method to detect failures when the DeploymentController is set to ECS (rolling update). For more information, see Rolling update in the Amazon Elastic Container Service Developer Guide.
    deploymentCircuitBreaker DeploymentCircuitBreakerResponse
    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.
    maximumPercent Integer
    If a service is using the rolling update (ECS) deployment type, the maximumPercent parameter represents an upper limit on the number of your service's tasks that are allowed in the RUNNING or PENDING state during a deployment, as a percentage of the desiredCount (rounded down to the nearest integer). This parameter enables you to define the deployment batch size. For example, if your service is using the REPLICA service scheduler and has a desiredCount of four tasks and a maximumPercent value 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 default maximumPercent value for a service using the REPLICA service scheduler is 200%. If a service is using either the blue/green (CODE_DEPLOY) or EXTERNAL deployment 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 the RUNNING state while the container instances are in the DRAINING state. 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.
    minimumHealthyPercent Integer
    If a service is using the rolling update (ECS) deployment type, the minimumHealthyPercent represents a lower limit on the number of your service's tasks that must remain in the RUNNING state during a deployment, as a percentage of the desiredCount (rounded up to the nearest integer). This parameter enables you to deploy without using additional cluster capacity. For example, if your service has a desiredCount of four tasks and a minimumHealthyPercent of 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 a RUNNING state 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) or EXTERNAL deployment 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 the RUNNING state while the container instances are in the DRAINING state. If a service is using either the blue/green (CODE_DEPLOY) or EXTERNAL deployment 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 DeploymentAlarmsResponse
    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 DeploymentAlarms method to detect failures when the DeploymentController is set to ECS (rolling update). For more information, see Rolling update in the Amazon Elastic Container Service Developer Guide.
    deploymentCircuitBreaker DeploymentCircuitBreakerResponse
    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.
    maximumPercent number
    If a service is using the rolling update (ECS) deployment type, the maximumPercent parameter represents an upper limit on the number of your service's tasks that are allowed in the RUNNING or PENDING state during a deployment, as a percentage of the desiredCount (rounded down to the nearest integer). This parameter enables you to define the deployment batch size. For example, if your service is using the REPLICA service scheduler and has a desiredCount of four tasks and a maximumPercent value 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 default maximumPercent value for a service using the REPLICA service scheduler is 200%. If a service is using either the blue/green (CODE_DEPLOY) or EXTERNAL deployment 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 the RUNNING state while the container instances are in the DRAINING state. 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.
    minimumHealthyPercent number
    If a service is using the rolling update (ECS) deployment type, the minimumHealthyPercent represents a lower limit on the number of your service's tasks that must remain in the RUNNING state during a deployment, as a percentage of the desiredCount (rounded up to the nearest integer). This parameter enables you to deploy without using additional cluster capacity. For example, if your service has a desiredCount of four tasks and a minimumHealthyPercent of 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 a RUNNING state 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) or EXTERNAL deployment 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 the RUNNING state while the container instances are in the DRAINING state. If a service is using either the blue/green (CODE_DEPLOY) or EXTERNAL deployment 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 DeploymentAlarmsResponse
    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 DeploymentAlarms method to detect failures when the DeploymentController is set to ECS (rolling update). For more information, see Rolling update in the Amazon Elastic Container Service Developer Guide.
    deployment_circuit_breaker DeploymentCircuitBreakerResponse
    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, the maximumPercent parameter represents an upper limit on the number of your service's tasks that are allowed in the RUNNING or PENDING state during a deployment, as a percentage of the desiredCount (rounded down to the nearest integer). This parameter enables you to define the deployment batch size. For example, if your service is using the REPLICA service scheduler and has a desiredCount of four tasks and a maximumPercent value 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 default maximumPercent value for a service using the REPLICA service scheduler is 200%. If a service is using either the blue/green (CODE_DEPLOY) or EXTERNAL deployment 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 the RUNNING state while the container instances are in the DRAINING state. 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_percent int
    If a service is using the rolling update (ECS) deployment type, the minimumHealthyPercent represents a lower limit on the number of your service's tasks that must remain in the RUNNING state during a deployment, as a percentage of the desiredCount (rounded up to the nearest integer). This parameter enables you to deploy without using additional cluster capacity. For example, if your service has a desiredCount of four tasks and a minimumHealthyPercent of 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 a RUNNING state 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) or EXTERNAL deployment 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 the RUNNING state while the container instances are in the DRAINING state. If a service is using either the blue/green (CODE_DEPLOY) or EXTERNAL deployment 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 DeploymentAlarms method to detect failures when the DeploymentController is set to ECS (rolling update). For more information, see Rolling update in the Amazon Elastic Container Service Developer Guide.
    deploymentCircuitBreaker Property Map
    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.
    maximumPercent Number
    If a service is using the rolling update (ECS) deployment type, the maximumPercent parameter represents an upper limit on the number of your service's tasks that are allowed in the RUNNING or PENDING state during a deployment, as a percentage of the desiredCount (rounded down to the nearest integer). This parameter enables you to define the deployment batch size. For example, if your service is using the REPLICA service scheduler and has a desiredCount of four tasks and a maximumPercent value 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 default maximumPercent value for a service using the REPLICA service scheduler is 200%. If a service is using either the blue/green (CODE_DEPLOY) or EXTERNAL deployment 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 the RUNNING state while the container instances are in the DRAINING state. 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.
    minimumHealthyPercent Number
    If a service is using the rolling update (ECS) deployment type, the minimumHealthyPercent represents a lower limit on the number of your service's tasks that must remain in the RUNNING state during a deployment, as a percentage of the desiredCount (rounded up to the nearest integer). This parameter enables you to deploy without using additional cluster capacity. For example, if your service has a desiredCount of four tasks and a minimumHealthyPercent of 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 a RUNNING state 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) or EXTERNAL deployment 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 the RUNNING state while the container instances are in the DRAINING state. If a service is using either the blue/green (CODE_DEPLOY) or EXTERNAL deployment 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

    Type string | Pulumi.AzureNative.AwsConnector.DeploymentControllerType
    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 | DeploymentControllerType
    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 | DeploymentControllerType
    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 | DeploymentControllerType
    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 | DeploymentControllerType
    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

    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

    CODE_DEPLOY
    CODE_DEPLOYDeploymentControllerType enum CODE_DEPLOY
    ECS
    ECSDeploymentControllerType enum ECS
    EXTERNAL
    EXTERNALDeploymentControllerType enum EXTERNAL
    DeploymentControllerType_CODE_DEPLOY
    CODE_DEPLOYDeploymentControllerType enum CODE_DEPLOY
    DeploymentControllerTypeECS
    ECSDeploymentControllerType enum ECS
    DeploymentControllerTypeEXTERNAL
    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

    PropagateTags string | Pulumi.AzureNative.AwsConnector.EBSTagSpecificationPropagateTags
    Determines whether to propagate the tags from the task definition to the Amazon EBS volume. Tags can only propagate to a SERVICE specified in ServiceVolumeConfiguration. If no value is specified, the tags aren't propagated.
    ResourceType string
    The type of volume resource.
    Tags List<Pulumi.AzureNative.AwsConnector.Inputs.Tag>
    The tags applied to this Amazon EBS volume. AmazonECSCreated and AmazonECSManaged are reserved tags that can't be used.
    PropagateTags string | EBSTagSpecificationPropagateTags
    Determines whether to propagate the tags from the task definition to the Amazon EBS volume. Tags can only propagate to a SERVICE specified in ServiceVolumeConfiguration. If no value is specified, the tags aren't propagated.
    ResourceType string
    The type of volume resource.
    Tags []Tag
    The tags applied to this Amazon EBS volume. AmazonECSCreated and AmazonECSManaged are reserved tags that can't be used.
    propagateTags String | EBSTagSpecificationPropagateTags
    Determines whether to propagate the tags from the task definition to the Amazon EBS volume. Tags can only propagate to a SERVICE specified in ServiceVolumeConfiguration. If no value is specified, the tags aren't propagated.
    resourceType String
    The type of volume resource.
    tags List<Tag>
    The tags applied to this Amazon EBS volume. AmazonECSCreated and AmazonECSManaged are reserved tags that can't be used.
    propagateTags string | EBSTagSpecificationPropagateTags
    Determines whether to propagate the tags from the task definition to the Amazon EBS volume. Tags can only propagate to a SERVICE specified in ServiceVolumeConfiguration. If no value is specified, the tags aren't propagated.
    resourceType string
    The type of volume resource.
    tags Tag[]
    The tags applied to this Amazon EBS volume. AmazonECSCreated and AmazonECSManaged are reserved tags that can't be used.
    propagate_tags str | EBSTagSpecificationPropagateTags
    Determines whether to propagate the tags from the task definition to the Amazon EBS volume. Tags can only propagate to a SERVICE specified in ServiceVolumeConfiguration. If no value is specified, the tags aren't propagated.
    resource_type str
    The type of volume resource.
    tags Sequence[Tag]
    The tags applied to this Amazon EBS volume. AmazonECSCreated and AmazonECSManaged are reserved tags that can't be used.
    propagateTags 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 SERVICE specified in ServiceVolumeConfiguration. If no value is specified, the tags aren't propagated.
    resourceType String
    The type of volume resource.
    tags List<Property Map>
    The tags applied to this Amazon EBS volume. AmazonECSCreated and AmazonECSManaged are reserved tags that can't be used.

    EBSTagSpecificationPropagateTags, EBSTagSpecificationPropagateTagsArgs

    SERVICE
    SERVICEEBSTagSpecificationPropagateTags enum SERVICE
    TASK_DEFINITION
    TASK_DEFINITIONEBSTagSpecificationPropagateTags enum TASK_DEFINITION
    EBSTagSpecificationPropagateTagsSERVICE
    SERVICEEBSTagSpecificationPropagateTags enum SERVICE
    EBSTagSpecificationPropagateTags_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

    PropagateTags string
    Determines whether to propagate the tags from the task definition to the Amazon EBS volume. Tags can only propagate to a SERVICE specified in ServiceVolumeConfiguration. If no value is specified, the tags aren't propagated.
    ResourceType string
    The type of volume resource.
    Tags List<Pulumi.AzureNative.AwsConnector.Inputs.TagResponse>
    The tags applied to this Amazon EBS volume. AmazonECSCreated and AmazonECSManaged are reserved tags that can't be used.
    PropagateTags string
    Determines whether to propagate the tags from the task definition to the Amazon EBS volume. Tags can only propagate to a SERVICE specified in ServiceVolumeConfiguration. If no value is specified, the tags aren't propagated.
    ResourceType string
    The type of volume resource.
    Tags []TagResponse
    The tags applied to this Amazon EBS volume. AmazonECSCreated and AmazonECSManaged are reserved tags that can't be used.
    propagateTags String
    Determines whether to propagate the tags from the task definition to the Amazon EBS volume. Tags can only propagate to a SERVICE specified in ServiceVolumeConfiguration. If no value is specified, the tags aren't propagated.
    resourceType String
    The type of volume resource.
    tags List<TagResponse>
    The tags applied to this Amazon EBS volume. AmazonECSCreated and AmazonECSManaged are reserved tags that can't be used.
    propagateTags string
    Determines whether to propagate the tags from the task definition to the Amazon EBS volume. Tags can only propagate to a SERVICE specified in ServiceVolumeConfiguration. If no value is specified, the tags aren't propagated.
    resourceType string
    The type of volume resource.
    tags TagResponse[]
    The tags applied to this Amazon EBS volume. AmazonECSCreated and AmazonECSManaged are reserved tags that can't be used.
    propagate_tags str
    Determines whether to propagate the tags from the task definition to the Amazon EBS volume. Tags can only propagate to a SERVICE specified in ServiceVolumeConfiguration. If no value is specified, the tags aren't propagated.
    resource_type str
    The type of volume resource.
    tags Sequence[TagResponse]
    The tags applied to this Amazon EBS volume. AmazonECSCreated and AmazonECSManaged are reserved tags that can't be used.
    propagateTags String
    Determines whether to propagate the tags from the task definition to the Amazon EBS volume. Tags can only propagate to a SERVICE specified in ServiceVolumeConfiguration. If no value is specified, the tags aren't propagated.
    resourceType String
    The type of volume resource.
    tags List<Property Map>
    The tags applied to this Amazon EBS volume. AmazonECSCreated and AmazonECSManaged are reserved tags that can't be used.

    EcsServiceProperties, EcsServicePropertiesArgs

    Arn string
    Amazon Resource Name (ARN)
    AwsAccountId string
    AWS Account ID
    AwsProperties Pulumi.AzureNative.AwsConnector.Inputs.AwsEcsServiceProperties
    AWS Properties
    AwsRegion string
    AWS Region
    AwsSourceSchema string
    AWS Source Schema
    AwsTags Dictionary<string, string>
    AWS Tags
    PublicCloudConnectorsResourceId string
    Public Cloud Connectors Resource ID
    PublicCloudResourceName string
    Public Cloud Resource Name
    Arn string
    Amazon Resource Name (ARN)
    AwsAccountId string
    AWS Account ID
    AwsProperties AwsEcsServiceProperties
    AWS Properties
    AwsRegion string
    AWS Region
    AwsSourceSchema string
    AWS Source Schema
    AwsTags map[string]string
    AWS Tags
    PublicCloudConnectorsResourceId string
    Public Cloud Connectors Resource ID
    PublicCloudResourceName string
    Public Cloud Resource Name
    arn String
    Amazon Resource Name (ARN)
    awsAccountId String
    AWS Account ID
    awsProperties AwsEcsServiceProperties
    AWS Properties
    awsRegion String
    AWS Region
    awsSourceSchema String
    AWS Source Schema
    awsTags Map<String,String>
    AWS Tags
    publicCloudConnectorsResourceId String
    Public Cloud Connectors Resource ID
    publicCloudResourceName String
    Public Cloud Resource Name
    arn string
    Amazon Resource Name (ARN)
    awsAccountId string
    AWS Account ID
    awsProperties AwsEcsServiceProperties
    AWS Properties
    awsRegion string
    AWS Region
    awsSourceSchema string
    AWS Source Schema
    awsTags {[key: string]: string}
    AWS Tags
    publicCloudConnectorsResourceId string
    Public Cloud Connectors Resource ID
    publicCloudResourceName string
    Public Cloud Resource Name
    arn str
    Amazon Resource Name (ARN)
    aws_account_id str
    AWS Account ID
    aws_properties AwsEcsServiceProperties
    AWS Properties
    aws_region str
    AWS Region
    aws_source_schema str
    AWS Source Schema
    aws_tags Mapping[str, str]
    AWS Tags
    public_cloud_connectors_resource_id str
    Public Cloud Connectors Resource ID
    public_cloud_resource_name str
    Public Cloud Resource Name
    arn String
    Amazon Resource Name (ARN)
    awsAccountId String
    AWS Account ID
    awsProperties Property Map
    AWS Properties
    awsRegion String
    AWS Region
    awsSourceSchema String
    AWS Source Schema
    awsTags Map<String>
    AWS Tags
    publicCloudConnectorsResourceId String
    Public Cloud Connectors Resource ID
    publicCloudResourceName String
    Public Cloud Resource Name

    EcsServicePropertiesResponse, EcsServicePropertiesResponseArgs

    ProvisioningState string
    The status of the last operation.
    Arn string
    Amazon Resource Name (ARN)
    AwsAccountId string
    AWS Account ID
    AwsProperties Pulumi.AzureNative.AwsConnector.Inputs.AwsEcsServicePropertiesResponse
    AWS Properties
    AwsRegion string
    AWS Region
    AwsSourceSchema string
    AWS Source Schema
    AwsTags Dictionary<string, string>
    AWS Tags
    PublicCloudConnectorsResourceId string
    Public Cloud Connectors Resource ID
    PublicCloudResourceName string
    Public Cloud Resource Name
    ProvisioningState string
    The status of the last operation.
    Arn string
    Amazon Resource Name (ARN)
    AwsAccountId string
    AWS Account ID
    AwsProperties AwsEcsServicePropertiesResponse
    AWS Properties
    AwsRegion string
    AWS Region
    AwsSourceSchema string
    AWS Source Schema
    AwsTags map[string]string
    AWS Tags
    PublicCloudConnectorsResourceId string
    Public Cloud Connectors Resource ID
    PublicCloudResourceName string
    Public Cloud Resource Name
    provisioningState String
    The status of the last operation.
    arn String
    Amazon Resource Name (ARN)
    awsAccountId String
    AWS Account ID
    awsProperties AwsEcsServicePropertiesResponse
    AWS Properties
    awsRegion String
    AWS Region
    awsSourceSchema String
    AWS Source Schema
    awsTags Map<String,String>
    AWS Tags
    publicCloudConnectorsResourceId String
    Public Cloud Connectors Resource ID
    publicCloudResourceName String
    Public Cloud Resource Name
    provisioningState string
    The status of the last operation.
    arn string
    Amazon Resource Name (ARN)
    awsAccountId string
    AWS Account ID
    awsProperties AwsEcsServicePropertiesResponse
    AWS Properties
    awsRegion string
    AWS Region
    awsSourceSchema string
    AWS Source Schema
    awsTags {[key: string]: string}
    AWS Tags
    publicCloudConnectorsResourceId string
    Public Cloud Connectors Resource ID
    publicCloudResourceName string
    Public Cloud Resource Name
    provisioning_state str
    The status of the last operation.
    arn str
    Amazon Resource Name (ARN)
    aws_account_id str
    AWS Account ID
    aws_properties AwsEcsServicePropertiesResponse
    AWS Properties
    aws_region str
    AWS Region
    aws_source_schema str
    AWS Source Schema
    aws_tags Mapping[str, str]
    AWS Tags
    public_cloud_connectors_resource_id str
    Public Cloud Connectors Resource ID
    public_cloud_resource_name str
    Public Cloud Resource Name
    provisioningState String
    The status of the last operation.
    arn String
    Amazon Resource Name (ARN)
    awsAccountId String
    AWS Account ID
    awsProperties Property Map
    AWS Properties
    awsRegion String
    AWS Region
    awsSourceSchema String
    AWS Source Schema
    awsTags Map<String>
    AWS Tags
    publicCloudConnectorsResourceId String
    Public Cloud Connectors Resource ID
    publicCloudResourceName String
    Public Cloud Resource Name

    LaunchType, LaunchTypeArgs

    EC2
    EC2LaunchType enum EC2
    EXTERNAL
    EXTERNALLaunchType enum EXTERNAL
    FARGATE
    FARGATELaunchType enum FARGATE
    LaunchTypeEC2
    EC2LaunchType enum EC2
    LaunchTypeEXTERNAL
    EXTERNALLaunchType enum EXTERNAL
    LaunchTypeFARGATE
    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

    ContainerName 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.
    ContainerPort int
    The port on the container to associate with the load balancer. This port must correspond to a containerPort in 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 the hostPort of the port mapping.
    LoadBalancerName string
    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.
    TargetGroupArn string
    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 ECS deployment 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 the CODE_DEPLOY deployment 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 the awsvpc network mode, you must choose ip as the target type, not instance. Do this when creating your target groups because tasks that use the awsvpc network mode are associated with an elastic network interface, not an Amazon EC2 instance. This network mode is required for the Fargate launch type.
    ContainerName 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.
    ContainerPort int
    The port on the container to associate with the load balancer. This port must correspond to a containerPort in 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 the hostPort of the port mapping.
    LoadBalancerName string
    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.
    TargetGroupArn string
    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 ECS deployment 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 the CODE_DEPLOY deployment 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 the awsvpc network mode, you must choose ip as the target type, not instance. Do this when creating your target groups because tasks that use the awsvpc network mode are associated with an elastic network interface, not an Amazon EC2 instance. This network mode is required for the Fargate launch type.
    containerName 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.
    containerPort Integer
    The port on the container to associate with the load balancer. This port must correspond to a containerPort in 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 the hostPort of the port mapping.
    loadBalancerName String
    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.
    targetGroupArn String
    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 ECS deployment 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 the CODE_DEPLOY deployment 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 the awsvpc network mode, you must choose ip as the target type, not instance. Do this when creating your target groups because tasks that use the awsvpc network mode are associated with an elastic network interface, not an Amazon EC2 instance. This network mode is required for the Fargate launch type.
    containerName 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.
    containerPort number
    The port on the container to associate with the load balancer. This port must correspond to a containerPort in 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 the hostPort of the port mapping.
    loadBalancerName string
    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.
    targetGroupArn string
    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 ECS deployment 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 the CODE_DEPLOY deployment 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 the awsvpc network mode, you must choose ip as the target type, not instance. Do this when creating your target groups because tasks that use the awsvpc network 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 containerPort in 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 the hostPort of the port mapping.
    load_balancer_name str
    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_arn str
    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 ECS deployment 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 the CODE_DEPLOY deployment 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 the awsvpc network mode, you must choose ip as the target type, not instance. Do this when creating your target groups because tasks that use the awsvpc network mode are associated with an elastic network interface, not an Amazon EC2 instance. This network mode is required for the Fargate launch type.
    containerName 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.
    containerPort Number
    The port on the container to associate with the load balancer. This port must correspond to a containerPort in 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 the hostPort of the port mapping.
    loadBalancerName String
    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.
    targetGroupArn String
    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 ECS deployment 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 the CODE_DEPLOY deployment 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 the awsvpc network mode, you must choose ip as the target type, not instance. Do this when creating your target groups because tasks that use the awsvpc network 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

    ContainerName 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.
    ContainerPort int
    The port on the container to associate with the load balancer. This port must correspond to a containerPort in 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 the hostPort of the port mapping.
    LoadBalancerName string
    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.
    TargetGroupArn string
    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 ECS deployment 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 the CODE_DEPLOY deployment 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 the awsvpc network mode, you must choose ip as the target type, not instance. Do this when creating your target groups because tasks that use the awsvpc network mode are associated with an elastic network interface, not an Amazon EC2 instance. This network mode is required for the Fargate launch type.
    ContainerName 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.
    ContainerPort int
    The port on the container to associate with the load balancer. This port must correspond to a containerPort in 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 the hostPort of the port mapping.
    LoadBalancerName string
    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.
    TargetGroupArn string
    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 ECS deployment 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 the CODE_DEPLOY deployment 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 the awsvpc network mode, you must choose ip as the target type, not instance. Do this when creating your target groups because tasks that use the awsvpc network mode are associated with an elastic network interface, not an Amazon EC2 instance. This network mode is required for the Fargate launch type.
    containerName 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.
    containerPort Integer
    The port on the container to associate with the load balancer. This port must correspond to a containerPort in 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 the hostPort of the port mapping.
    loadBalancerName String
    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.
    targetGroupArn String
    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 ECS deployment 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 the CODE_DEPLOY deployment 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 the awsvpc network mode, you must choose ip as the target type, not instance. Do this when creating your target groups because tasks that use the awsvpc network mode are associated with an elastic network interface, not an Amazon EC2 instance. This network mode is required for the Fargate launch type.
    containerName 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.
    containerPort number
    The port on the container to associate with the load balancer. This port must correspond to a containerPort in 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 the hostPort of the port mapping.
    loadBalancerName string
    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.
    targetGroupArn string
    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 ECS deployment 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 the CODE_DEPLOY deployment 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 the awsvpc network mode, you must choose ip as the target type, not instance. Do this when creating your target groups because tasks that use the awsvpc network 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 containerPort in 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 the hostPort of the port mapping.
    load_balancer_name str
    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_arn str
    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 ECS deployment 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 the CODE_DEPLOY deployment 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 the awsvpc network mode, you must choose ip as the target type, not instance. Do this when creating your target groups because tasks that use the awsvpc network mode are associated with an elastic network interface, not an Amazon EC2 instance. This network mode is required for the Fargate launch type.
    containerName 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.
    containerPort Number
    The port on the container to associate with the load balancer. This port must correspond to a containerPort in 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 the hostPort of the port mapping.
    loadBalancerName String
    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.
    targetGroupArn String
    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 ECS deployment 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 the CODE_DEPLOY deployment 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 the awsvpc network mode, you must choose ip as the target type, not instance. Do this when creating your target groups because tasks that use the awsvpc network 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

    LogDriver string
    The log driver to use for the container. For tasks on FARGATElong, the supported log drivers are awslogs, splunk, and awsfirelens. For tasks hosted on Amazon EC2 instances, the supported log drivers are awslogs, fluentd, gelf, json-file, journald, logentries,syslog, splunk, and awsfirelens. For more information about using the awslogs log driver, see Using the awslogs log driver in the Amazon Elastic Container Service Developer Guide. For more information about using the awsfirelens log 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}}'
    SecretOptions List<Pulumi.AzureNative.AwsConnector.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.
    LogDriver string
    The log driver to use for the container. For tasks on FARGATElong, the supported log drivers are awslogs, splunk, and awsfirelens. For tasks hosted on Amazon EC2 instances, the supported log drivers are awslogs, fluentd, gelf, json-file, journald, logentries,syslog, splunk, and awsfirelens. For more information about using the awslogs log driver, see Using the awslogs log driver in the Amazon Elastic Container Service Developer Guide. For more information about using the awsfirelens log 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}}'
    SecretOptions []Secret
    The secrets to pass to the log configuration. For more information, see Specifying sensitive data in the Amazon Elastic Container Service Developer Guide.
    logDriver String
    The log driver to use for the container. For tasks on FARGATElong, the supported log drivers are awslogs, splunk, and awsfirelens. For tasks hosted on Amazon EC2 instances, the supported log drivers are awslogs, fluentd, gelf, json-file, journald, logentries,syslog, splunk, and awsfirelens. For more information about using the awslogs log driver, see Using the awslogs log driver in the Amazon Elastic Container Service Developer Guide. For more information about using the awsfirelens log 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}}'
    secretOptions 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.
    logDriver string
    The log driver to use for the container. For tasks on FARGATElong, the supported log drivers are awslogs, splunk, and awsfirelens. For tasks hosted on Amazon EC2 instances, the supported log drivers are awslogs, fluentd, gelf, json-file, journald, logentries,syslog, splunk, and awsfirelens. For more information about using the awslogs log driver, see Using the awslogs log driver in the Amazon Elastic Container Service Developer Guide. For more information about using the awsfirelens log 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}}'
    secretOptions 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, and awsfirelens. For tasks hosted on Amazon EC2 instances, the supported log drivers are awslogs, fluentd, gelf, json-file, journald, logentries,syslog, splunk, and awsfirelens. For more information about using the awslogs log driver, see Using the awslogs log driver in the Amazon Elastic Container Service Developer Guide. For more information about using the awsfirelens log 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.
    logDriver String
    The log driver to use for the container. For tasks on FARGATElong, the supported log drivers are awslogs, splunk, and awsfirelens. For tasks hosted on Amazon EC2 instances, the supported log drivers are awslogs, fluentd, gelf, json-file, journald, logentries,syslog, splunk, and awsfirelens. For more information about using the awslogs log driver, see Using the awslogs log driver in the Amazon Elastic Container Service Developer Guide. For more information about using the awsfirelens log 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}}'
    secretOptions 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

    LogDriver string
    The log driver to use for the container. For tasks on FARGATElong, the supported log drivers are awslogs, splunk, and awsfirelens. For tasks hosted on Amazon EC2 instances, the supported log drivers are awslogs, fluentd, gelf, json-file, journald, logentries,syslog, splunk, and awsfirelens. For more information about using the awslogs log driver, see Using the awslogs log driver in the Amazon Elastic Container Service Developer Guide. For more information about using the awsfirelens log 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}}'
    SecretOptions List<Pulumi.AzureNative.AwsConnector.Inputs.SecretResponse>
    The secrets to pass to the log configuration. For more information, see Specifying sensitive data in the Amazon Elastic Container Service Developer Guide.
    LogDriver string
    The log driver to use for the container. For tasks on FARGATElong, the supported log drivers are awslogs, splunk, and awsfirelens. For tasks hosted on Amazon EC2 instances, the supported log drivers are awslogs, fluentd, gelf, json-file, journald, logentries,syslog, splunk, and awsfirelens. For more information about using the awslogs log driver, see Using the awslogs log driver in the Amazon Elastic Container Service Developer Guide. For more information about using the awsfirelens log 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}}'
    SecretOptions []SecretResponse
    The secrets to pass to the log configuration. For more information, see Specifying sensitive data in the Amazon Elastic Container Service Developer Guide.
    logDriver String
    The log driver to use for the container. For tasks on FARGATElong, the supported log drivers are awslogs, splunk, and awsfirelens. For tasks hosted on Amazon EC2 instances, the supported log drivers are awslogs, fluentd, gelf, json-file, journald, logentries,syslog, splunk, and awsfirelens. For more information about using the awslogs log driver, see Using the awslogs log driver in the Amazon Elastic Container Service Developer Guide. For more information about using the awsfirelens log 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}}'
    secretOptions 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.
    logDriver string
    The log driver to use for the container. For tasks on FARGATElong, the supported log drivers are awslogs, splunk, and awsfirelens. For tasks hosted on Amazon EC2 instances, the supported log drivers are awslogs, fluentd, gelf, json-file, journald, logentries,syslog, splunk, and awsfirelens. For more information about using the awslogs log driver, see Using the awslogs log driver in the Amazon Elastic Container Service Developer Guide. For more information about using the awsfirelens log 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}}'
    secretOptions 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, and awsfirelens. For tasks hosted on Amazon EC2 instances, the supported log drivers are awslogs, fluentd, gelf, json-file, journald, logentries,syslog, splunk, and awsfirelens. For more information about using the awslogs log driver, see Using the awslogs log driver in the Amazon Elastic Container Service Developer Guide. For more information about using the awsfirelens log 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.
    logDriver String
    The log driver to use for the container. For tasks on FARGATElong, the supported log drivers are awslogs, splunk, and awsfirelens. For tasks hosted on Amazon EC2 instances, the supported log drivers are awslogs, fluentd, gelf, json-file, journald, logentries,syslog, splunk, and awsfirelens. For more information about using the awslogs log driver, see Using the awslogs log driver in the Amazon Elastic Container Service Developer Guide. For more information about using the awsfirelens log 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}}'
    secretOptions 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

    AwsvpcConfiguration Pulumi.AzureNative.AwsConnector.Inputs.AwsVpcConfiguration
    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']}
    AwsvpcConfiguration AwsVpcConfiguration
    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']}
    awsvpcConfiguration AwsVpcConfiguration
    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']}
    awsvpcConfiguration AwsVpcConfiguration
    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 AwsVpcConfiguration
    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']}
    awsvpcConfiguration 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

    AwsvpcConfiguration Pulumi.AzureNative.AwsConnector.Inputs.AwsVpcConfigurationResponse
    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']}
    AwsvpcConfiguration AwsVpcConfigurationResponse
    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']}
    awsvpcConfiguration AwsVpcConfigurationResponse
    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']}
    awsvpcConfiguration AwsVpcConfigurationResponse
    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 AwsVpcConfigurationResponse
    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']}
    awsvpcConfiguration 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

    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.AzureNative.AwsConnector.PlacementConstraintType
    The type of constraint. Use distinctInstance to ensure that each task in a particular group is running on a different container instance. Use memberOf to 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 | PlacementConstraintType
    The type of constraint. Use distinctInstance to ensure that each task in a particular group is running on a different container instance. Use memberOf to 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 | PlacementConstraintType
    The type of constraint. Use distinctInstance to ensure that each task in a particular group is running on a different container instance. Use memberOf to 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 | PlacementConstraintType
    The type of constraint. Use distinctInstance to ensure that each task in a particular group is running on a different container instance. Use memberOf to 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 | PlacementConstraintType
    The type of constraint. Use distinctInstance to ensure that each task in a particular group is running on a different container instance. Use memberOf to 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 | "distinctInstance" | "memberOf"
    The type of constraint. Use distinctInstance to ensure that each task in a particular group is running on a different container instance. Use memberOf to restrict the selection to a group of valid candidates.

    PlacementConstraintResponse, 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 distinctInstance to ensure that each task in a particular group is running on a different container instance. Use memberOf to 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 distinctInstance to ensure that each task in a particular group is running on a different container instance. Use memberOf to 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 distinctInstance to ensure that each task in a particular group is running on a different contain