- Newest
- Most votes
- Most comments
Hi,
The property ingress_port_override
matches with the ingressPortOverride attribute of a ServiceConnectService
data type, required by the services
property of a ServiceConnectConfiguration
type [1]. You can use this data type with your service definition (in CreateService [2], for example)
As you can read in the data type description [3], ingress_port_override
is the port number for the Service Connect proxy to listen on. Use the value of this field to bypass the proxy for traffic on the port number specified in the named portMapping in the task definition of this application, and then use it in your VPC security groups to allow traffic into the proxy for this Amazon ECS service.
In awsvpc mode and Fargate, the default value is the container port number. The container port number is in the portMapping in the task definition. In bridge mode, the default value is the ephemeral port of the Service Connect proxy.
In case you want to expose your container on a different port than it is listening on (based on your container image definition), you need to use portMapping
property [4] of your task definition, with the containerPort
and hostPort
set accordingly [5].
References:
[1] https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_ServiceConnectConfiguration.html - ServiceConnectConfiguration data type
[2] https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_CreateService.html
[4] PortMapping - https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_PortMapping.html
[5] https://docs.aws.amazon.com/cdk/api/v2/python/aws_cdk.aws_ecs/PortMapping.html
Relevant content
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated a year ago