# Ensure that Container Health is Checked at Runtime

- Source: https://support.icompaas.com/support/solutions/articles/62000234352-ensure-that-container-health-is-checked-at-runtime
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [CIS Docker Benchmark v1.7.0](https://support.icompaas.com/support/solutions/62000112687) › [CIS Docker Benchmark](https://support.icompaas.com/support/solutions/folders/62000169241)
- Last updated: 2026-05-29
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

###  Profile Applicability:

-   Level 1
    

Description:

Docker containers should be configured to have their health checked at runtime to ensure the application running inside the container is functioning as expected. Docker provides a HEALTHCHECK instruction in Dockerfiles to define a command that can test the health of the container.

Rationale:

Health checks help monitor the state of the application inside the container. If a container becomes unhealthy, it can be restarted automatically or handled in other ways, reducing downtime and preventing problems from escalating.

Impact:

Pros:

-   Allows automated remediation of failed containers.
    
-   Reduces manual intervention and provides proactive monitoring.
    

Cons:

-   May slightly increase resource usage due to regular health checks.
    
-   Some applications might require specific configurations for proper health check commands.
    

Default Value:

Health checks are not defined by default in Docker images. They need to be manually configured in Dockerfiles or at runtime.

Pre-requisites:

-   Ensure Docker is installed and running on the host system.
    
-   Health check commands must be properly defined in the container's Dockerfile or specified when running the container.
    

Remediation:

Test Plan:

Using AWS Console:

1.  Navigate to the EC2 instance running Docker.
    
2.  Run the following command to inspect the container's health status:
    

docker inspect --format '{{.State.Health.Status}}' <container\_name\_or\_id>

3.  Ensure the container has a valid health check configured.
    

Using AWS CLI:

1.  Connect to the EC2 instance.
    
2.  Run the following command to check the health status of a running container:
    

docker inspect --format '{{.State.Health.Status}}' <container\_name\_or\_id>

Implementation Plan:

Using AWS Console:

1.  Connect to the EC2 instance where Docker is running.
    
    1.  Modify the Dockerfile to include a HEALTHCHECK instruction. Example:
        
        HEALTHCHECK CMD curl --fail http://localhost:8080/health || exit 1
        
2.  Rebuild the container image and redeploy the container with the updated Dockerfile.
    

Using AWS CLI:

1.  Use SSM to update the Dockerfile remotely and redeploy the container:
    

Run the following command to apply the health check:

aws ssm send-command --document-name "AWS-RunShellScript" --targets "Key=instanceIds,Values=instance\_id" --parameters 'commands=\["echo \\"HEALTHCHECK CMD curl --fail http://localhost:8080/health || exit 1\\" >> /path/to/Dockerfile && docker build -t my-image . && docker run -d my-image"\]'

Backout Plan:

Using AWS Console:

1.  Connect to the EC2 instance.
    
2.  Remove or comment out the HEALTHCHECK instruction from the Dockerfile.
    
3.  Rebuild and redeploy the container without the health check.
    

Using AWS CLI:

1.  Use SSM to revert the Dockerfile and redeploy the container:
    

Run the following command to remove the health check:

aws ssm send-command --document-name "AWS-RunShellScript" --targets "Key=instanceIds,Values=instance\_id" --parameters 'commands=\["echo \\"#HEALTHCHECK CMD curl --fail http://localhost:8080/health || exit 1\\" >> /path/to/Dockerfile && docker build -t my-image . && docker run -d my-image"\]'

**References:**

-   CIS Docker Benchmark v1.7
    
-   Docker Health Checks Documentation: [https://docs.docker.com/engine/reference/builder/#healthcheck](https://docs.docker.com/engine/reference/builder/#healthcheck)

## Related compliance guidance

- [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Configuration checks like this one are the technical half of a SOC 2 / ISO 27001 programme — the guide shows where they fit, what else an auditor expects, and how to evidence them.
- [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): ISO 27001 Annex A.8 (technological controls) is where cloud hardening evidence lands; the guide shows how to run the ISMS around it.