Service Registries and Service Connect configuration in AWS ECS Service deployment
C
Correct Lungfish
We tried to configure serviceRegistries and serviceConnectConfiguration in service definition and tried the ECS deployment.
But deploying is failing with "Cannot deserialize value of type". Requesting a feature support for Service Registries and Service Connect configuration in AWS ECS Service deployment
Log In
R
Rural Gopher
Our setup uses Harness Filestore as the manifest source for the ECS service definition.
During the initial deployment, the ECS service is successfully created and runs as expected.
However, when we update the service definition in the Harness Filestore to include Service Connect or Service Discovery configuration, the changes do not propagate to AWS ECS during subsequent rolling deploys.
Observed Behavior:
ECS service is already running in the cluster.
We update the service definition YAML (in Harness Filestore) to add:
serviceConnectConfiguration, or
serviceRegistries / service discovery config.
Running ECS Rolling Deploy does not update these fields in AWS ECS.
The updated configuration only reflects if we manually delete the ECS service in AWS and then rerun the ECS rolling deploy from Harness.
In that case, the new service is created with Service Connect + Service Discovery successfully.
Expected Behavior:
Updating the service definition manifest and running ECS Rolling Deploy should update the existing service in AWS to include Service Connect / Service Discovery without requiring manual deletion of the service.