2 Respuestas
- Más nuevo
- Más votos
- Más comentarios
0
In the link you shared it says that HealthCheckPath is not required so I'm not sure why you think it is required.
It also doesn't make sense in the context of TCP health check because the path is related to the HTTP(S) request.
respondido hace un mes
0
I ended up just switching the the health check to HTTPS on port 443, which removed the original problem. If anyone has the answer to the original problem and why that was happening though I'd still love to know.
respondido hace un mes
Contenido relevante
- ¿Cómo puedo solucionar una advertencia de estado amarillo o rojo en mi entorno de Elastic Beanstalk?OFICIAL DE AWSActualizada hace un año
- OFICIAL DE AWSActualizada hace 3 años
- OFICIAL DE AWSActualizada hace 2 años
It says in the docs, the default is / and the minimum is 1, so if you don't set it I assume it's set as 1, and if you try to set it empty, it wont work because it must be at least of length 1.