Class: Aws::ECS::Types::ServiceConnectConfiguration

Inherits:
Struct
  • Object
show all
Includes:
Structure
Defined in:
lib/aws-sdk-ecs/types.rb

Overview

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*.

[1]: docs.aws.amazon.com/AmazonECS/latest/developerguide/service-connect.html

Constant Summary collapse

SENSITIVE =
[]

Instance Attribute Summary collapse

Instance Attribute Details

#enabledBoolean

Specifies whether to use Service Connect with this service.

Returns:

  • (Boolean)


9286
9287
9288
9289
9290
9291
9292
9293
# File 'lib/aws-sdk-ecs/types.rb', line 9286

class ServiceConnectConfiguration < Struct.new(
  :enabled,
  :namespace,
  :services,
  :log_configuration)
  SENSITIVE = []
  include Aws::Structure
end

#log_configurationTypes::LogConfiguration

The log configuration for the container. This parameter maps to ‘LogConfig` in the [Create a container] section of the [Docker Remote API] and the `–log-driver` option to [ `docker run` ][3].

By default, containers use the same logging driver that the Docker daemon uses. However, the container might use a different logging driver than the Docker daemon by specifying a log driver configuration in the container definition. For more information about the options for different supported log drivers, see

Configure logging drivers][4

in the Docker documentation.

Understand the following when specifying a log configuration for your containers.

  • Amazon ECS currently supports a subset of the logging drivers available to the Docker daemon. Additional log drivers may be available in future releases of the Amazon ECS container agent.

    For tasks on Fargate, 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`.

  • This parameter requires version 1.18 of the Docker Remote API or greater on your container instance.

  • For tasks that are hosted on Amazon EC2 instances, the Amazon ECS container agent must register the available logging drivers with the ‘ECS_AVAILABLE_LOGGING_DRIVERS` environment variable before containers placed on that instance can use these log configuration options. For more information, see [Amazon ECS container agent configuration] in the *Amazon Elastic Container Service Developer Guide*.

  • For tasks that are on Fargate, because you don’t have access to the underlying infrastructure your tasks are hosted on, any additional software needed must be installed outside of the task. For example, the Fluentd output aggregators or a remote host running Logstash to send Gelf logs to.

[1]: docs.docker.com/engine/api/v1.35/#operation/ContainerCreate [2]: docs.docker.com/engine/api/v1.35/ [3]: docs.docker.com/engine/reference/commandline/run/ [4]: docs.docker.com/engine/admin/logging/overview/ [5]: docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-agent-config.html



9286
9287
9288
9289
9290
9291
9292
9293
# File 'lib/aws-sdk-ecs/types.rb', line 9286

class ServiceConnectConfiguration < Struct.new(
  :enabled,
  :namespace,
  :services,
  :log_configuration)
  SENSITIVE = []
  include Aws::Structure
end

#namespaceString

The namespace name or full Amazon Resource Name (ARN) of the Cloud Map namespace for use with Service Connect. The namespace must be in the same Amazon Web Services Region as the Amazon ECS service and cluster. The type of namespace doesn’t affect Service Connect. For more information about Cloud Map, see [Working with Services] in the *Cloud Map Developer Guide*.

[1]: docs.aws.amazon.com/cloud-map/latest/dg/working-with-services.html

Returns:

  • (String)


9286
9287
9288
9289
9290
9291
9292
9293
# File 'lib/aws-sdk-ecs/types.rb', line 9286

class ServiceConnectConfiguration < Struct.new(
  :enabled,
  :namespace,
  :services,
  :log_configuration)
  SENSITIVE = []
  include Aws::Structure
end

#servicesArray<Types::ServiceConnectService>

The list of Service Connect service objects. These are names and aliases (also known as endpoints) that are used by other Amazon ECS services to connect to this service.

This field is not required for a “client” Amazon ECS service that’s a member of a namespace only to connect to other services within the namespace. An example of this would be a frontend application that accepts incoming requests from either a load balancer that’s attached to the service or by other means.

An object selects a port from the task definition, assigns a name for the Cloud Map service, and a list of aliases (endpoints) and ports for client applications to refer to this service.

Returns:



9286
9287
9288
9289
9290
9291
9292
9293
# File 'lib/aws-sdk-ecs/types.rb', line 9286

class ServiceConnectConfiguration < Struct.new(
  :enabled,
  :namespace,
  :services,
  :log_configuration)
  SENSITIVE = []
  include Aws::Structure
end