Values.ServiceConnectConfigurationSourceThe 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.
type nonrec t = {enabled : Boolean.t;Specifies whether to use Service Connect with this service.
*)namespace : String_.t option;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.
*)services : ServiceConnectServiceList.t option;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.
*)logConfiguration : LogConfiguration.t option;accessLogConfiguration : ServiceConnectAccessLogConfiguration.t option;The configuration for Service Connect access logging. Access logs capture detailed information about requests made to your service, including request patterns, response codes, and timing data. They can be useful for debugging connectivity issues, monitoring service performance, and auditing service-to-service communication for security and compliance purposes. To enable access logs, you must also specify a logConfiguration in the serviceConnectConfiguration.
*)}val to_value :
t ->
[> `Structure of
(string
* [> `Boolean of Boolean.t
| `List of
[> `Structure of
(string
* [> `Integer of PortNumber.t
| `List of
[> `Structure of
(string
* [> `Integer of PortNumber.t
| `String of String_.t
| `Structure of
(string
* [> `Structure of
(string
* [> `String of String_.t
| `Structure of
(string
* [> `String of String_.t ])
list ])
list ])
list ])
list ]
list
| `String of String_.t
| `Structure of
(string
* [> `Integer of Duration.t
| `String of String_.t
| `Structure of
(string * [> `String of String_.t ]) list ])
list ])
list ]
list
| `String of String_.t
| `Structure of
(string
* [> `Enum of string
| `List of
[> `Structure of (string * [> `String of String_.t ]) list ]
list
| `Map of
([> `String of String_.t ] * [> `String of String_.t ]) list ])
list ])
list ]