Paws::ECS::Service
This class represents one of two things:
Use the attributes of this class as arguments to methods. You shouldn't make instances of this class. Each attribute should be used as a named argument in the calls that expect this type of object.
As an example, if Att1 is expected to be a Paws::ECS::Service object:
$service_obj->Method(Att1 => { ClusterArn => $value, ..., TaskSets => $value });
Use accessors for each attribute. If Att1 is expected to be an Paws::ECS::Service object:
$result = $service_obj->Method(...); $result->Att1->ClusterArn
Details on a service within a cluster
The Amazon Resource Name (ARN) of the cluster that hosts the service.
The Unix timestamp for when the service was created.
The principal that created the service.
Optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks.
The deployment controller type the service is using.
The current state of deployments for the service.
The desired number of instantiations of the task definition to keep running on the service. This value is specified when the service is created with CreateService, and it can be modified with UpdateService.
Specifies whether to enable Amazon ECS managed tags for the tasks in the service. For more information, see Tagging Your Amazon ECS Resources (http://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-using-tags.html) in the I<Amazon Elastic Container Service Developer Guide>.
The event stream for your service. A maximum of 100 of the latest events are displayed.
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.
The launch type on which your service is running. For more information, see Amazon ECS Launch Types (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/launch_types.html) in the I<Amazon Elastic Container Service Developer Guide>.
A list of Elastic Load Balancing load balancer objects, containing the load balancer name, the container name (as it appears in a container definition), and the container port to access from the load balancer.
Services with tasks that use the awsvpc network mode (for example, those with the Fargate launch type) only support Application Load Balancers and Network Load Balancers. Classic Load Balancers are not supported. Also, when you create any target groups for these services, you must choose ip as the target type, not instance. Tasks that use the awsvpc network mode are associated with an elastic network interface, not an Amazon EC2 instance.
awsvpc
ip
instance
The VPC subnet and security group configuration for tasks that receive their own elastic network interface by using the C<awsvpc> networking mode.
The number of tasks in the cluster that are in the C<PENDING> state.
The placement constraints for the tasks in the service.
The placement strategy that determines how tasks for the service are placed.
The platform version on which your tasks in the service are running. A platform version is only specified for tasks using the Fargate launch type. If one is not specified, the C<LATEST> platform version is used by default. For more information, see AWS Fargate Platform Versions (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/platform_versions.html) in the I<Amazon Elastic Container Service Developer Guide>.
Specifies whether to propagate the tags from the task definition or the service to the task. If no value is specified, the tags are not propagated.
The ARN of the IAM role associated with the service that allows the Amazon ECS container agent to register container instances with an Elastic Load Balancing load balancer.
The number of tasks in the cluster that are in the C<RUNNING> state.
The scheduling strategy to use for the service. For more information, see Services (http://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs_services.html).
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.
REPLICA
DAEMON-The daemon scheduling strategy deploys exactly one task on each container instance in your cluster. When you are using this strategy, do not specify a desired number of tasks or any task placement strategies.
DAEMON
Fargate tasks do not support the DAEMON scheduling strategy.
The ARN that identifies the service. The ARN contains the C<arn:aws:ecs> namespace, followed by the Region of the service, the AWS account ID of the service owner, the C<service> namespace, and then the service name. For example, C<arn:aws:ecs:I<region>:I<012345678910>:service/I<my-service> >.
The name of your service. Up to 255 letters (uppercase and lowercase), numbers, hyphens, and underscores 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 status of the service. The valid values are C<ACTIVE>, C<DRAINING>, or C<INACTIVE>.
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. Tag keys can have a maximum character length of 128 characters, and tag values can have a maximum length of 256 characters.
The task definition to use for tasks in the service. This value is specified when the service is created with CreateService, and it can be modified with UpdateService.
Information about a set of Amazon ECS tasks in an AWS CodeDeploy deployment. An Amazon ECS task set includes details such as the desired number of tasks, how many tasks are running, and whether the task set serves production traffic.
This class forms part of Paws, describing an object used in Paws::ECS
The source code is located here: https://github.com/pplu/aws-sdk-perl
Please report bugs to: https://github.com/pplu/aws-sdk-perl/issues
To install Paws::SDK::Config, copy and paste the appropriate command in to your terminal.
cpanm
cpanm Paws::SDK::Config
CPAN shell
perl -MCPAN -e shell install Paws::SDK::Config
For more information on module installation, please visit the detailed CPAN module installation guide.