Create Service
| ecs_create_service | R Documentation |
Runs and maintains your desired number of tasks from a specified task definition¶
Description¶
Runs and maintains your desired number of tasks from a specified task
definition. If the number of tasks running in a service drops below the
desiredCount, Amazon ECS runs another copy of the task in the
specified cluster. To update an existing service, use update_service.
On March 21, 2024, a change was made to resolve the task definition revision before authorization. When a task definition revision is not specified, authorization will occur using the latest revision of a task definition.
Amazon Elastic Inference (EI) is no longer available to customers.
In addition to maintaining the desired count of tasks in your service, you can optionally run your service behind one or more load balancers. The load balancers distribute traffic across the tasks that are associated with the service. For more information, see Service load balancing in the Amazon Elastic Container Service Developer Guide.
You can attach Amazon EBS volumes to Amazon ECS tasks by configuring the
volume when creating or updating a service. volumeConfigurations is
only supported for REPLICA service and not DAEMON service. For more
information, see Amazon EBS
volumes
in the Amazon Elastic Container Service Developer Guide.
Tasks for services that don't use a load balancer are considered healthy
if they're in the RUNNING state. Tasks for services that use a load
balancer are considered healthy if they're in the RUNNING state and
are reported as healthy by the load balancer.
There are two service scheduler strategies available:
-
REPLICA- The replica scheduling strategy places and maintains your 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. For more information, see Service scheduler concepts in the Amazon Elastic Container Service Developer Guide. -
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. It also stops tasks that don't meet the placement constraints. When using this strategy, you don't need to specify a desired number of tasks, a task placement strategy, or use Service Auto Scaling policies. For more information, see Amazon ECS services in the Amazon Elastic Container Service Developer Guide.
The deployment controller is the mechanism that determines how tasks are deployed for your service. The valid options are:
- ECS
When you create a service which uses the ECS deployment controller,
you can choose between the following deployment strategies (which you
can set in the “strategy” field in “deploymentConfiguration”): :
-
ROLLING: When you create a service which uses the rolling update (ROLLING) deployment strategy, the Amazon ECS service scheduler replaces the currently running tasks with new tasks. The number of tasks that Amazon ECS adds or removes from the service during a rolling update is controlled by the service deployment configuration. For more information, see Deploy Amazon ECS services by replacing tasks in the Amazon Elastic Container Service Developer Guide.Rolling update deployments are best suited for the following scenarios:
-
Gradual service updates: You need to update your service incrementally without taking the entire service offline at once.
-
Limited resource requirements: You want to avoid the additional resource costs of running two complete environments simultaneously (as required by blue/green deployments).
-
Acceptable deployment time: Your application can tolerate a longer deployment process, as rolling updates replace tasks one by one.
-
No need for instant roll back: Your service can tolerate a rollback process that takes minutes rather than seconds.
-
Simple deployment process: You prefer a straightforward deployment approach without the complexity of managing multiple environments, target groups, and listeners.
-
No load balancer requirement: Your service doesn't use or require a load balancer, Application Load Balancer, Network Load Balancer, or Service Connect (which are required for blue/green deployments).
-
Stateful applications: Your application maintains state that makes it difficult to run two parallel environments.
-
Cost sensitivity: You want to minimize deployment costs by not running duplicate environments during deployment.
Rolling updates are the default deployment strategy for services and provide a balance between deployment safety and resource efficiency for many common application scenarios.
-
-
BLUE_GREEN: A blue/green deployment strategy (BLUE_GREEN) is a release methodology that reduces downtime and risk by running two identical production environments called blue and green. With Amazon ECS blue/green deployments, you can validate new service revisions before directing production traffic to them. This approach provides a safer way to deploy changes with the ability to quickly roll back if needed. For more information, see Amazon ECS blue/green deployments in the Amazon Elastic Container Service Developer Guide.Amazon ECS blue/green deployments are best suited for the following scenarios:
-
Service validation: When you need to validate new service revisions before directing production traffic to them
-
Zero downtime: When your service requires zero-downtime deployments
-
Instant roll back: When you need the ability to quickly roll back if issues are detected
-
Load balancer requirement: When your service uses Application Load Balancer, Network Load Balancer, or Service Connect
-
-
LINEAR: A linear deployment strategy (LINEAR) gradually shifts traffic from the current production environment to a new environment in equal percentage increments. With Amazon ECS linear deployments, you can control the pace of traffic shifting and validate new service revisions with increasing amounts of production traffic.Linear deployments are best suited for the following scenarios:
-
Gradual validation: When you want to gradually validate your new service version with increasing traffic
-
Performance monitoring: When you need time to monitor metrics and performance during the deployment
-
Risk minimization: When you want to minimize risk by exposing the new version to production traffic incrementally
-
Load balancer requirement: When your service uses Application Load Balancer or Service Connect
-
-
CANARY: A canary deployment strategy (CANARY) shifts a small percentage of traffic to the new service revision first, then shifts the remaining traffic all at once after a specified time period. This allows you to test the new version with a subset of users before full deployment.Canary deployments are best suited for the following scenarios:
-
Feature testing: When you want to test new features with a small subset of users before full rollout
-
Production validation: When you need to validate performance and functionality with real production traffic
-
Blast radius control: When you want to minimize blast radius if issues are discovered in the new version
-
Load balancer requirement: When your service uses Application Load Balancer or Service Connect
-
-
External
Use a third-party deployment controller.
- Blue/green deployment (powered by CodeDeploy)
CodeDeploy installs an updated version of the application as a new replacement task set and reroutes production traffic from the original application task set to the replacement task set. The original task set is terminated after a successful deployment. Use this deployment controller to verify a new deployment of a service before sending production traffic to it.
When creating a service that uses the EXTERNAL deployment controller,
you can specify only parameters that aren't controlled at the task set
level. The only required parameter is the service name. You control your
services using the create_task_set. For more information, see Amazon
ECS deployment
types in
the Amazon Elastic Container Service Developer Guide.
When the service scheduler launches new tasks, it determines task placement. For information about task placement and task placement strategies, see Amazon ECS task placement in the Amazon Elastic Container Service Developer Guide
Usage¶
ecs_create_service(cluster, serviceName, taskDefinition,
availabilityZoneRebalancing, loadBalancers, serviceRegistries,
desiredCount, clientToken, launchType, capacityProviderStrategy,
platformVersion, role, deploymentConfiguration, placementConstraints,
placementStrategy, networkConfiguration, healthCheckGracePeriodSeconds,
schedulingStrategy, deploymentController, tags, enableECSManagedTags,
propagateTags, enableExecuteCommand, serviceConnectConfiguration,
volumeConfigurations, vpcLatticeConfigurations)
Arguments¶
cluster |
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. |
serviceName |
[required] 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. |
taskDefinition |
The A task definition must be specified if the service uses either the
For more information about deployment types, see Amazon ECS deployment types. |
availabilityZoneRebalancing |
Indicates whether to use Availability Zone rebalancing for the service. For more information, see Balancing an Amazon ECS service across Availability Zones in the Amazon Elastic Container Service Developer Guide . The default behavior of
|
loadBalancers |
A load balancer object representing the load balancers to use with your service. For more information, see Service load balancing in the Amazon Elastic Container Service Developer Guide. If the service uses the If the service uses the If you use the For Application Load Balancers and Network Load Balancers, this object must contain the load balancer target group ARN, the container name, and the container port to access from the load balancer. The container name must be as it appears in a container definition. The load balancer name parameter must be omitted. When a task from this service is placed on a container instance, the container instance and port combination is registered as a target in the target group that's specified here. For Classic Load Balancers, this object must contain the load balancer name, the container name , and the container port to access from the load balancer. The container name must be as it appears in a container definition. The target group ARN parameter must be omitted. When a task from this service is placed on a container instance, the container instance is registered with the load balancer that's specified here. Services with tasks that use the |
serviceRegistries |
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. |
desiredCount |
The number of instantiations of the specified task definition to place and keep running in your service. This is required if |
clientToken |
An identifier that you provide to ensure the idempotency of the request. It must be unique and is case sensitive. Up to 36 ASCII characters in the range of 33-126 (inclusive) are allowed. |
launchType |
The infrastructure that you run your service on. For more information, see Amazon ECS launch types in the Amazon Elastic Container Service Developer Guide. If you want to use Amazon ECS Managed Instances, you must use the
The Fargate Spot infrastructure is available for use but a capacity provider strategy must be used. For more information, see Fargate capacity providers in the Amazon ECS Developer Guide. The The A service can use either a launch type or a capacity provider
strategy. If a |
capacityProviderStrategy |
The capacity provider strategy to use for the service. If you want to use Amazon ECS Managed Instances, you must use the
If a A capacity provider strategy can contain a maximum of 20 capacity providers. |
platformVersion |
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 |
role |
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
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
If your specified role has a path other than |
deploymentConfiguration |
Optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks. |
placementConstraints |
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. |
placementStrategy |
The placement strategy objects to use for tasks in your service. You can specify a maximum of 5 strategy rules for each service. |
networkConfiguration |
The network configuration for the service. This parameter is
required for task definitions that use the |
healthCheckGracePeriodSeconds |
The period of time, in seconds, that the Amazon ECS service
scheduler ignores unhealthy Elastic Load Balancing, VPC Lattice, and
container health checks after a task has first started. If you do not
specify a health check grace period value, the default value of 0 is
used. If you do not use any of the health checks, then
If your service has more running tasks than desired, unhealthy tasks in the grace period might be stopped to reach the desired count. |
schedulingStrategy |
The scheduling strategy to use for the service. For more information, see Services. There are two service scheduler strategies available:
|
deploymentController |
The deployment controller to use for the service. If no
deployment controller is specified, the default value of
|
tags |
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:
|
enableECSManagedTags |
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 must set the
|
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 You must set this to a value other than The default is |
enableExecuteCommand |
Determines whether the execute command functionality is turned on
for the service. If |
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. |
volumeConfigurations |
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. |
vpcLatticeConfigurations |
The VPC Lattice configuration for the service being created. |
Value¶
A list with the following syntax:
list(
service = list(
serviceArn = "string",
serviceName = "string",
clusterArn = "string",
loadBalancers = list(
list(
targetGroupArn = "string",
loadBalancerName = "string",
containerName = "string",
containerPort = 123,
advancedConfiguration = list(
alternateTargetGroupArn = "string",
productionListenerRule = "string",
testListenerRule = "string",
roleArn = "string"
)
)
),
serviceRegistries = list(
list(
registryArn = "string",
port = 123,
containerName = "string",
containerPort = 123
)
),
status = "string",
desiredCount = 123,
runningCount = 123,
pendingCount = 123,
launchType = "EC2"|"FARGATE"|"EXTERNAL"|"MANAGED_INSTANCES",
capacityProviderStrategy = list(
list(
capacityProvider = "string",
weight = 123,
base = 123
)
),
platformVersion = "string",
platformFamily = "string",
taskDefinition = "string",
deploymentConfiguration = list(
deploymentCircuitBreaker = list(
enable = TRUE|FALSE,
rollback = TRUE|FALSE
),
maximumPercent = 123,
minimumHealthyPercent = 123,
alarms = list(
alarmNames = list(
"string"
),
rollback = TRUE|FALSE,
enable = TRUE|FALSE
),
strategy = "ROLLING"|"BLUE_GREEN"|"LINEAR"|"CANARY",
bakeTimeInMinutes = 123,
lifecycleHooks = list(
list(
targetType = "AWS_LAMBDA"|"PAUSE",
hookTargetArn = "string",
roleArn = "string",
lifecycleStages = list(
"RECONCILE_SERVICE"|"PRE_SCALE_UP"|"POST_SCALE_UP"|"TEST_TRAFFIC_SHIFT"|"POST_TEST_TRAFFIC_SHIFT"|"PRE_PRODUCTION_TRAFFIC_SHIFT"|"PRODUCTION_TRAFFIC_SHIFT"|"POST_PRODUCTION_TRAFFIC_SHIFT"
),
hookDetails = list(),
timeoutConfiguration = list(
timeoutInMinutes = 123,
action = "ROLLBACK"|"CONTINUE"
)
)
),
linearConfiguration = list(
stepPercent = 123.0,
stepBakeTimeInMinutes = 123
),
canaryConfiguration = list(
canaryPercent = 123.0,
canaryBakeTimeInMinutes = 123
)
),
taskSets = list(
list(
id = "string",
taskSetArn = "string",
serviceArn = "string",
clusterArn = "string",
startedBy = "string",
externalId = "string",
status = "string",
taskDefinition = "string",
computedDesiredCount = 123,
pendingCount = 123,
runningCount = 123,
createdAt = as.POSIXct(
"2015-01-01"
),
updatedAt = as.POSIXct(
"2015-01-01"
),
launchType = "EC2"|"FARGATE"|"EXTERNAL"|"MANAGED_INSTANCES",
capacityProviderStrategy = list(
list(
capacityProvider = "string",
weight = 123,
base = 123
)
),
platformVersion = "string",
platformFamily = "string",
networkConfiguration = list(
awsvpcConfiguration = list(
subnets = list(
"string"
),
securityGroups = list(
"string"
),
assignPublicIp = "ENABLED"|"DISABLED"
)
),
loadBalancers = list(
list(
targetGroupArn = "string",
loadBalancerName = "string",
containerName = "string",
containerPort = 123,
advancedConfiguration = list(
alternateTargetGroupArn = "string",
productionListenerRule = "string",
testListenerRule = "string",
roleArn = "string"
)
)
),
serviceRegistries = list(
list(
registryArn = "string",
port = 123,
containerName = "string",
containerPort = 123
)
),
scale = list(
value = 123.0,
unit = "PERCENT"
),
stabilityStatus = "STEADY_STATE"|"STABILIZING",
stabilityStatusAt = as.POSIXct(
"2015-01-01"
),
tags = list(
list(
key = "string",
value = "string"
)
),
fargateEphemeralStorage = list(
kmsKeyId = "string"
)
)
),
deployments = list(
list(
id = "string",
status = "string",
taskDefinition = "string",
desiredCount = 123,
pendingCount = 123,
runningCount = 123,
failedTasks = 123,
createdAt = as.POSIXct(
"2015-01-01"
),
updatedAt = as.POSIXct(
"2015-01-01"
),
capacityProviderStrategy = list(
list(
capacityProvider = "string",
weight = 123,
base = 123
)
),
launchType = "EC2"|"FARGATE"|"EXTERNAL"|"MANAGED_INSTANCES",
platformVersion = "string",
platformFamily = "string",
networkConfiguration = list(
awsvpcConfiguration = list(
subnets = list(
"string"
),
securityGroups = list(
"string"
),
assignPublicIp = "ENABLED"|"DISABLED"
)
),
rolloutState = "COMPLETED"|"FAILED"|"IN_PROGRESS",
rolloutStateReason = "string",
serviceConnectConfiguration = list(
enabled = TRUE|FALSE,
namespace = "string",
services = list(
list(
portName = "string",
discoveryName = "string",
clientAliases = list(
list(
port = 123,
dnsName = "string",
testTrafficRules = list(
header = list(
name = "string",
value = list(
exact = "string"
)
)
)
)
),
ingressPortOverride = 123,
timeout = list(
idleTimeoutSeconds = 123,
perRequestTimeoutSeconds = 123
),
tls = list(
issuerCertificateAuthority = list(
awsPcaAuthorityArn = "string"
),
kmsKey = "string",
roleArn = "string"
)
)
),
logConfiguration = list(
logDriver = "json-file"|"syslog"|"journald"|"gelf"|"fluentd"|"awslogs"|"splunk"|"awsfirelens",
options = list(
"string"
),
secretOptions = list(
list(
name = "string",
valueFrom = "string"
)
)
),
accessLogConfiguration = list(
format = "TEXT"|"JSON",
includeQueryParameters = "DISABLED"|"ENABLED"
)
),
serviceConnectResources = list(
list(
discoveryName = "string",
discoveryArn = "string"
)
),
volumeConfigurations = list(
list(
name = "string",
managedEBSVolume = list(
encrypted = TRUE|FALSE,
kmsKeyId = "string",
volumeType = "string",
sizeInGiB = 123,
snapshotId = "string",
volumeInitializationRate = 123,
iops = 123,
throughput = 123,
tagSpecifications = list(
list(
resourceType = "volume",
tags = list(
list(
key = "string",
value = "string"
)
),
propagateTags = "TASK_DEFINITION"|"SERVICE"|"NONE"
)
),
roleArn = "string",
filesystemType = "ext3"|"ext4"|"xfs"|"ntfs"
)
)
),
fargateEphemeralStorage = list(
kmsKeyId = "string"
),
vpcLatticeConfigurations = list(
list(
roleArn = "string",
targetGroupArn = "string",
portName = "string"
)
)
)
),
roleArn = "string",
events = list(
list(
id = "string",
createdAt = as.POSIXct(
"2015-01-01"
),
message = "string"
)
),
createdAt = as.POSIXct(
"2015-01-01"
),
currentServiceDeployment = "string",
currentServiceRevisions = list(
list(
arn = "string",
requestedTaskCount = 123,
runningTaskCount = 123,
pendingTaskCount = 123
)
),
placementConstraints = list(
list(
type = "distinctInstance"|"memberOf",
expression = "string"
)
),
placementStrategy = list(
list(
type = "random"|"spread"|"binpack",
field = "string"
)
),
networkConfiguration = list(
awsvpcConfiguration = list(
subnets = list(
"string"
),
securityGroups = list(
"string"
),
assignPublicIp = "ENABLED"|"DISABLED"
)
),
healthCheckGracePeriodSeconds = 123,
schedulingStrategy = "REPLICA"|"DAEMON",
deploymentController = list(
type = "ECS"|"CODE_DEPLOY"|"EXTERNAL"
),
tags = list(
list(
key = "string",
value = "string"
)
),
createdBy = "string",
enableECSManagedTags = TRUE|FALSE,
propagateTags = "TASK_DEFINITION"|"SERVICE"|"NONE",
enableExecuteCommand = TRUE|FALSE,
availabilityZoneRebalancing = "ENABLED"|"DISABLED",
resourceManagementType = "CUSTOMER"|"ECS"
)
)
Request syntax¶
svc$create_service(
cluster = "string",
serviceName = "string",
taskDefinition = "string",
availabilityZoneRebalancing = "ENABLED"|"DISABLED",
loadBalancers = list(
list(
targetGroupArn = "string",
loadBalancerName = "string",
containerName = "string",
containerPort = 123,
advancedConfiguration = list(
alternateTargetGroupArn = "string",
productionListenerRule = "string",
testListenerRule = "string",
roleArn = "string"
)
)
),
serviceRegistries = list(
list(
registryArn = "string",
port = 123,
containerName = "string",
containerPort = 123
)
),
desiredCount = 123,
clientToken = "string",
launchType = "EC2"|"FARGATE"|"EXTERNAL"|"MANAGED_INSTANCES",
capacityProviderStrategy = list(
list(
capacityProvider = "string",
weight = 123,
base = 123
)
),
platformVersion = "string",
role = "string",
deploymentConfiguration = list(
deploymentCircuitBreaker = list(
enable = TRUE|FALSE,
rollback = TRUE|FALSE
),
maximumPercent = 123,
minimumHealthyPercent = 123,
alarms = list(
alarmNames = list(
"string"
),
rollback = TRUE|FALSE,
enable = TRUE|FALSE
),
strategy = "ROLLING"|"BLUE_GREEN"|"LINEAR"|"CANARY",
bakeTimeInMinutes = 123,
lifecycleHooks = list(
list(
targetType = "AWS_LAMBDA"|"PAUSE",
hookTargetArn = "string",
roleArn = "string",
lifecycleStages = list(
"RECONCILE_SERVICE"|"PRE_SCALE_UP"|"POST_SCALE_UP"|"TEST_TRAFFIC_SHIFT"|"POST_TEST_TRAFFIC_SHIFT"|"PRE_PRODUCTION_TRAFFIC_SHIFT"|"PRODUCTION_TRAFFIC_SHIFT"|"POST_PRODUCTION_TRAFFIC_SHIFT"
),
hookDetails = list(),
timeoutConfiguration = list(
timeoutInMinutes = 123,
action = "ROLLBACK"|"CONTINUE"
)
)
),
linearConfiguration = list(
stepPercent = 123.0,
stepBakeTimeInMinutes = 123
),
canaryConfiguration = list(
canaryPercent = 123.0,
canaryBakeTimeInMinutes = 123
)
),
placementConstraints = list(
list(
type = "distinctInstance"|"memberOf",
expression = "string"
)
),
placementStrategy = list(
list(
type = "random"|"spread"|"binpack",
field = "string"
)
),
networkConfiguration = list(
awsvpcConfiguration = list(
subnets = list(
"string"
),
securityGroups = list(
"string"
),
assignPublicIp = "ENABLED"|"DISABLED"
)
),
healthCheckGracePeriodSeconds = 123,
schedulingStrategy = "REPLICA"|"DAEMON",
deploymentController = list(
type = "ECS"|"CODE_DEPLOY"|"EXTERNAL"
),
tags = list(
list(
key = "string",
value = "string"
)
),
enableECSManagedTags = TRUE|FALSE,
propagateTags = "TASK_DEFINITION"|"SERVICE"|"NONE",
enableExecuteCommand = TRUE|FALSE,
serviceConnectConfiguration = list(
enabled = TRUE|FALSE,
namespace = "string",
services = list(
list(
portName = "string",
discoveryName = "string",
clientAliases = list(
list(
port = 123,
dnsName = "string",
testTrafficRules = list(
header = list(
name = "string",
value = list(
exact = "string"
)
)
)
)
),
ingressPortOverride = 123,
timeout = list(
idleTimeoutSeconds = 123,
perRequestTimeoutSeconds = 123
),
tls = list(
issuerCertificateAuthority = list(
awsPcaAuthorityArn = "string"
),
kmsKey = "string",
roleArn = "string"
)
)
),
logConfiguration = list(
logDriver = "json-file"|"syslog"|"journald"|"gelf"|"fluentd"|"awslogs"|"splunk"|"awsfirelens",
options = list(
"string"
),
secretOptions = list(
list(
name = "string",
valueFrom = "string"
)
)
),
accessLogConfiguration = list(
format = "TEXT"|"JSON",
includeQueryParameters = "DISABLED"|"ENABLED"
)
),
volumeConfigurations = list(
list(
name = "string",
managedEBSVolume = list(
encrypted = TRUE|FALSE,
kmsKeyId = "string",
volumeType = "string",
sizeInGiB = 123,
snapshotId = "string",
volumeInitializationRate = 123,
iops = 123,
throughput = 123,
tagSpecifications = list(
list(
resourceType = "volume",
tags = list(
list(
key = "string",
value = "string"
)
),
propagateTags = "TASK_DEFINITION"|"SERVICE"|"NONE"
)
),
roleArn = "string",
filesystemType = "ext3"|"ext4"|"xfs"|"ntfs"
)
)
),
vpcLatticeConfigurations = list(
list(
roleArn = "string",
targetGroupArn = "string",
portName = "string"
)
)
)
Examples¶
## Not run:
# This example creates a service in your default region called
# `ecs-simple-service`. The service uses the `hello_world` task
# definition and it maintains 10 copies of that task.
svc$create_service(
desiredCount = 10L,
serviceName = "ecs-simple-service",
taskDefinition = "hello_world"
)
# This example creates a service in your default region called
# `ecs-simple-service-elb`. The service uses the `ecs-demo` task
# definition and it maintains 10 copies of that task. You must reference
# an existing load balancer in the same region by its name.
svc$create_service(
desiredCount = 10L,
loadBalancers = list(
list(
containerName = "simple-app",
containerPort = 80L,
loadBalancerName = "EC2Contai-EcsElast-15DCDAURT3ZO2"
)
),
role = "ecsServiceRole",
serviceName = "ecs-simple-service-elb",
taskDefinition = "console-sample-app-static"
)
## End(Not run)