ecs_service_facts - list or describe services in ecs

New in version 2.1.


  • Lists or describes services in ecs.

Requirements (on host that executes module)

  • boto
  • boto3
  • botocore
  • json
  • python >= 2.6


parameter required default choices comments
AWS access key. If not set then the value of the AWS_ACCESS_KEY_ID, AWS_ACCESS_KEY or EC2_ACCESS_KEY environment variable is used.

aliases: ec2_access_key, access_key
AWS secret key. If not set then the value of the AWS_SECRET_ACCESS_KEY, AWS_SECRET_KEY, or EC2_SECRET_KEY environment variable is used.

aliases: ec2_secret_key, secret_key
no default
The cluster ARNS in which to list the services.
no false
  • true
  • false
Set this to true if you want detailed information about the services.
Url to use to connect to EC2 or your Eucalyptus cloud (by default the module will use EC2 endpoints). Ignored for modules where region is required. Must be specified for all other modules if region is not used. If not set then the value of the EC2_URL environment variable, if any, is used.
(added in 1.6)
Uses a boto profile. Only works with boto >= 2.24.0.
The AWS region to use. If not specified then the value of the AWS_REGION or EC2_REGION environment variable, if any, is used. See

aliases: aws_region, ec2_region
(added in 1.6)
AWS STS security token. If not set then the value of the AWS_SECURITY_TOKEN or EC2_SECURITY_TOKEN environment variable is used.

aliases: access_token
The service to get details for (required if details is true)
(added in 1.5)
no yes
  • yes
  • no
When set to "no", SSL certificates will not be validated for boto versions >= 2.6.0.


# Note: These examples do not set authentication details, see the AWS Guide for details.

# Basic listing example
- ecs_service_facts:
    cluster: test-cluster
    service: console-test-service
    details: true

# Basic listing example
- ecs_service_facts:
    cluster: test-cluster

Return Values

Common return values are documented here Return Values, the following are the fields unique to this module:

name description returned type sample
services When details is false, returns an array of service ARNs, otherwise an array of complex objects as described below. success complex
name description returned type sample
status The valid values are ACTIVE, DRAINING, or INACTIVE. always string
pendingCount The number of tasks in the cluster that are in the PENDING state. always int
loadBalancers A list of load balancer objects always complex
desiredCount The desired number of instantiations of the task definition to keep running on the service. always int
runningCount The number of tasks in the cluster that are in the RUNNING state. always int
serviceName A user-generated string used to identify the service always string
clusterArn The Amazon Resource Name (ARN) of the of the cluster that hosts the service. always string
serviceArn The Amazon Resource Name (ARN) that identifies the service. The ARN contains the arn:aws:ecs namespace, followed by the region of the service, the AWS account ID of the service owner, the service namespace, and then the service name. For example, arn:aws:ecs:region :012345678910 :service/my-service . always string
deployments list of service deployments always list of complex
events lost of service events always list of complex
taskDefinition The ARN of a task definition to use for tasks in the service. always string



  • for details of the parameters and returns see
  • If parameters are not set within the module, the following environment variables can be used in decreasing order of precedence AWS_URL or EC2_URL, AWS_ACCESS_KEY_ID or AWS_ACCESS_KEY or EC2_ACCESS_KEY, AWS_SECRET_ACCESS_KEY or AWS_SECRET_KEY or EC2_SECRET_KEY, AWS_SECURITY_TOKEN or EC2_SECURITY_TOKEN, AWS_REGION or EC2_REGION
  • Ansible uses the boto configuration file (typically ~/.boto) if no credentials are provided. See
  • AWS_REGION or EC2_REGION can be typically be used to specify the AWS region, when required, but this can also be configured in the boto config file


This module is flagged as preview which means that it is not guaranteed to have a backwards compatible interface.


This module is community maintained without core committer oversight.

For more information on what this means please read Module Support

For help in developing on modules, should you be so inclined, please read Community Information & Contributing, Testing Ansible and Developing Modules.