Which caused the service to exit. I believe that RequestError could be caught and handled so the service does not close when AWS ECS is temporarily unavailable
This should be doable with perpetual retries, but the last connection success timestamp should be posted as a metric so the user can query and alert on whether the discovery data is stale.
I've encountered a problem
Which caused the service to exit. I believe that
RequestError
could be caught and handled so the service does not close when AWS ECS is temporarily unavailable