2개 답변
- 최신
- 최다 투표
- 가장 많은 댓글
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. ☹️
답변함 한 달 전
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?
답변함 한 달 전
관련 콘텐츠
- AWS 공식업데이트됨 2년 전