2 Respuestas
- Más nuevo
- Más votos
- Más comentarios
1
Well, it looks like this is WAD (working as designed). According to this Stackoverflow post, this is a know problem with ECS Service Connect.
Oh well. I guess I'll just re-deploy my "web" service. ☹️
respondido hace un mes
0
Ah, I did discover something interesting. It looks as though the ECS Service Connect agent updates the /etc/hosts
file on the "web" service (somehow). Before I rebooted my "web" service the /etc/hosts
file only contained entries for the App-A service. After rebooting my "web" service, the /etc/hosts
file contains entries for both the App-A and App-B service.
Is there a way to force the "web" service to update it's /etc/hosts
file?
respondido hace un mes
Contenido relevante
- OFICIAL DE AWSActualizada hace 2 años
- OFICIAL DE AWSActualizada hace 3 años
- OFICIAL DE AWSActualizada hace 5 meses