ServiceConnect

class aws_cdk.aws_ecs.ServiceConnect(networkmode, *, container_port, app_protocol=None, container_port_range=None, host_port=None, name=None, protocol=None)

Bases: object

ServiceConnect ValueObjectClass having by ContainerDefinition.

ExampleMetadata:: fixture=_generated

Example:

# The code below shows an example of how to instantiate this type.
# The values are placeholders you should change.
from aws_cdk import aws_ecs as ecs

# app_protocol: ecs.AppProtocol

service_connect = ecs.ServiceConnect(ecs.NetworkMode.NONE,
    container_port=123,

    # the properties below are optional
    app_protocol=app_protocol,
    container_port_range="containerPortRange",
    host_port=123,
    name="name",
    protocol=ecs.Protocol.TCP
)

Parameters:

networkmode (NetworkMode) –
container_port (Union[int, float]) – The port number on the container that is bound to the user-specified or automatically assigned host port. If you are using containers in a task with the awsvpc or host network mode, exposed ports should be specified using containerPort. If you are using containers in a task with the bridge network mode and you specify a container port and not a host port, your container automatically receives a host port in the ephemeral port range. For more information, see hostPort. Port mappings that are automatically assigned in this way do not count toward the 100 reserved ports limit of a container instance. If you want to expose a port range, you must specify CONTAINER_PORT_USE_RANGE as container port.
app_protocol (Optional[AppProtocol]) – The protocol used by Service Connect. Valid values are AppProtocol.http, AppProtocol.http2, and AppProtocol.grpc. The protocol determines what telemetry will be shown in the ECS Console for Service Connect services using this port mapping. This field may only be set when the task definition uses Bridge or Awsvpc network modes. Default: - no app protocol
container_port_range (Optional[str]) – The port number range on the container that’s bound to the dynamically mapped host port range. The following rules apply when you specify a containerPortRange: - You must specify CONTAINER_PORT_USE_RANGE as containerPort - You must use either the bridge network mode or the awsvpc network mode. - The container instance must have at least version 1.67.0 of the container agent and at least version 1.67.0-1 of the ecs-init package - You can specify a maximum of 100 port ranges per container. - A port can only be included in one port mapping per container. - You cannot specify overlapping port ranges. - The first port in the range must be less than last port in the range. If you want to expose a single port, you must not set a range.
host_port (Union[int, float, None]) – The port number on the container instance to reserve for your container. If you are using containers in a task with the awsvpc or host network mode, the hostPort can either be left blank or set to the same value as the containerPort. If you are using containers in a task with the bridge network mode, you can specify a non-reserved host port for your container port mapping, or you can omit the hostPort (or set it to 0) while specifying a containerPort and your container automatically receives a port in the ephemeral port range for your container instance operating system and Docker version.
name (Optional[str]) – The name to give the port mapping. Name is required in order to use the port mapping with ECS Service Connect. This field may only be set when the task definition uses Bridge or Awsvpc network modes. Default: - no port mapping name
protocol (Optional[Protocol]) – The protocol used for the port mapping. Valid values are Protocol.TCP and Protocol.UDP. Default: TCP

Methods

is_service_connect()

Judge parameters can be serviceconnect logick.

If parameters can be serviceConnect return true.

Return type:: bool

validate()

Judge serviceconnect parametes are valid.

If invalid, throw Error.

Return type:: None

Attributes

networkmode: The networking mode to use for the containers in the task.

portmapping: Port mappings allow containers to access ports on the host container instance to send or receive traffic.