http.`healthcheck` String or Map If you specify a string, Copilot interprets it as the path exposed in your container to handle target group health check requests. The default is "/". ```yaml http: healthcheck: '/' ``` You can also specify healthcheck as a map: ```yaml http: healthcheck: path: '/' port: 8080 success_codes: '200' healthy_threshold: 3 unhealthy_threshold: 2 interval: 15s timeout: 10s grace_period: 60s ``` http.healthcheck.`path` String The destination that the health check requests are sent to. http.healthcheck.`port` Integer The port that the health check requests are sent to. The default is [`image.port`](./#image-port), or the port exposed by [`http.target_container`](./#http-target-container), if set. If the port exposed is `443`, then the health check protocol is automatically set to HTTPS. http.healthcheck.`success_codes` String The HTTP status codes that healthy targets must use when responding to an HTTP health check. You can specify values between 200 and 499. You can specify multiple values (for example, "200,202") or a range of values (for example, "200-299"). The default is 200. http.healthcheck.`healthy_threshold` Integer The number of consecutive health check successes required before considering an unhealthy target healthy. The default is 5. Range: 2-10. http.healthcheck.`unhealthy_threshold` Integer The number of consecutive health check failures required before considering a target unhealthy. The default is 2. Range: 2-10. http.healthcheck.`interval` Duration The approximate amount of time, in seconds, between health checks of an individual target. The default is 30s. Range: 5s–300s. http.healthcheck.`timeout` Duration The amount of time, in seconds, during which no response from a target means a failed health check. The default is 5s. Range 5s-300s. http.healthcheck.`grace_period` Duration The amount of time to ignore failing target group healthchecks on container start. The default is 60s. This can be useful to fix deployment issues for containers which take a while to become healthy and begin listening for incoming connections, or to speed up deployment of containers guaranteed to start quickly.