Karan Vasnani

Thanks for opening this bug @abespalko. SC Agent becoming unhealthy here as indicated by the logs is due to failure to reach another component on the instance called as Relay...

Our local testing suggests that this is a regression introduced in our `v1.26.4.0` image version and are currently narrowing down the root cause. Once we have identified the root cause,...

Just to provide an update, we've found that this only impacts the EKS + Fargate use case and is not a problem on the EC2 platform. Lately, there have been...

@axot thanks for following up on this, that change would explain the behavior we're observing. We were still on `go1.20.6` in Envoy image `v.1.26.4.0` so, I'll perhaps need to test...

I have built a custom image with the change being introduced in this PR (https://github.com/aws/amazon-ecs-service-connect-agent/pull/73) for testing: `354290006986.dkr.ecr.us-west-2.amazonaws.com/aws-appmesh-envoy:v1.27.3.0-raise-nofile-soft-limit`, and will be validating if that worked this week.

Hi @nitinkapur, does the connection to RDS MS SQL has TLS enabled or not? Additionally, is it possible for you to provide logs from Envoy as that would help us...

Thanks for the update. Closing this issue then.

> This is fine for all other services that call SVC B but not for SVC A. So, for SVC A we wanted to override this settings with x-envoy-* headers....

Hi @robinvdvleuten, is it possible for you to share your mesh configurations specifically the Route spec for your backend virtual node? My current guess is that your setup is experiencing...

@robinvdvleuten thanks for the update. Since you mentioned that it's a persistent TCP connection and that there's no Routes configured, I would suspect the issue here could be the connection...