1 Respuesta
- Más nuevo
- Más votos
- Más comentarios
1
Found out the problem, the port mapping protocol was on "None" which is assumed as TCP, changing it to HTTP seems like resolved the issue. Unfortunately changing the port mapping protocol requires you to delete the service and create with the new task definition.
respondido hace 8 meses
Good day Gustavo,
This is Zubair from the AWS Premium Support Team regarding the post that you've create on the errors that you were getting due to the port mapping protocol.
You're correct in saying that changing this to HTTP would resolve the issue and your concern regarding the port mapping protocol will create a new revision of the task definition.
Kindest regards,
Zubair S.
Contenido relevante
- OFICIAL DE AWSActualizada hace 3 años
- OFICIAL DE AWSActualizada hace 2 años
- OFICIAL DE AWSActualizada hace 2 años
- OFICIAL DE AWSActualizada hace un año
AWS/ECS namespace should have Service Connect specific metrics such as:
ActiveConnectionCount
,NewConnectionCount
,RequestCount
,ProcessedBytes
,HTTPCode_Target_5XX_Count
,HTTPCode_Target_4XX_Count
, and so on. From the screenshot shared, I'm not sure if you are checking this namespace. Could you please confirm that?Went to Cloudwatch metrics to be sure, but when I set ECS, ClusterName, DiscoveryName, ServiceName and chose this service, there is only ProcessedBytes, NewConnectionCount and ActiveConnectionCount
Also found out that my react (next.js) applications are collecting that metrics, just the .net apis aren't
I'm glad that you were able to solve the issue. Thank you for sharing the solution!