In the week 3 lab, instances from the AWS autoscaling group keep being detected as unhealthy and respawned (cf log from activity below). Is that an issue with the instances themselves, or maybe specific to the nano size preventing instances from working correctly ?
Log of autoscaling group activity
| Successful | Launching a new EC2 instance: i-08349498c5c2ddc6f | At 2026-03-23T15:19:07Z an instance was launched in response to an unhealthy instance needing to be replaced. | 2026 March 23, 04:19:09 PM +01:00 | 2026 March 23, 04:19:19 PM +01:00 |
|---|---|---|---|---|
| In progress | Terminating EC2 instance: i-09255395032c3d5d4 | At 2026-03-23T15:19:07Z an instance was taken out of service in response to an EC2 health check indicating it has been terminated or stopped. | 2026 March 23, 04:19:07 PM +01:00 | |
| Successful | Launching a new EC2 instance: i-00b14a1d41cc1688b | At 2026-03-23T15:17:06Z an instance was launched in response to an unhealthy instance needing to be replaced. | 2026 March 23, 04:17:08 PM +01:00 | 2026 March 23, 04:17:13 PM +01:00 |
| In progress | Terminating EC2 instance: i-04ecda24a8c4371ec | At 2026-03-23T15:17:06Z an instance was taken out of service in response to an EC2 health check indicating it has been terminated or stopped. | 2026 March 23, 04:17:06 PM +01:00 | |
| Successful | Terminating EC2 instance: i-0f3f6bb221e52b9ec | At 2026-03-23T15:16:03Z a monitor alarm TargetTracking-c62825a3581670l14338996t1w015973937388-AutoScalingGroup-t45BKDp9pUlm-AlarmLow-6914a655-4160-4928-85b6-68099b26b294 in state ALARM triggered policy de-c1w3-scaling-policy changing the desired capacity from 3 to 2. At 2026-03-23T15:16:10Z an instance was taken out of service in response to a difference between desired and actual capacity, shrinking the capacity from 3 to 2. At 2026-03-23T15:16:10Z instance i-0f3f6bb221e52b9ec was selected for termination. | 2026 March 23, 04:16:10 PM +01:00 | 2026 March 23, 04:17:53 PM +01:00 |
| Successful | Launching a new EC2 instance: i-04ecda24a8c4371ec | At 2026-03-23T15:15:04Z an instance was launched in response to an unhealthy instance needing to be replaced. | 2026 March 23, 04:15:06 PM +01:00 | 2026 March 23, 04:15:11 PM +01:00 |
| Successful | Terminating EC2 instance: i-0314b280c6706c54d | At 2026-03-23T15:15:04Z an instance was taken out of service in response to an EC2 health check indicating it has been terminated or stopped. | 2026 March 23, 04:15:04 PM +01:00 | 2026 March 23, 04:15:46 PM +01:00 |
| Successful | Terminating EC2 instance: i-0d362774167fc72fa | At 2026-03-23T15:14:49Z a monitor alarm TargetTracking-c62825a3581670l14338996t1w015973937388-AutoScalingGroup-t45BKDp9pUlm-AlarmLow-6914a655-4160-4928-85b6-68099b26b294 in state ALARM triggered policy de-c1w3-scaling-policy changing the desired capacity from 4 to 3. At 2026-03-23T15:14:54Z an instance was taken out of service in response to a difference between desired and actual capacity, shrinking the capacity from 4 to 3. At 2026-03-23T15:14:54Z instance i-0d362774167fc72fa was selected for termination. | 2026 March 23, 04:14:54 PM +01:00 | 2026 March 23, 04:15:57 PM +01:00 |
| Successful | Launching a new EC2 instance: i-09255395032c3d5d4 | At 2026-03-23T15:13:11Z an instance was launched in response to an unhealthy instance needing to be replaced. | 2026 March 23, 04:13:13 PM +01:00 | 2026 March 23, 04:13:18 PM +01:00 |
| Successful | Terminating EC2 instance: i-0cbb8fe80bf272821 | At 2026-03-23T15:13:11Z an instance was taken out of service in response to an EC2 health check indicating it has been terminated or stopped. | 2026 March 23, 04:13:11 PM +01:00 | 2026 March 23, 04:13:33 PM +01:00 |
| Successful | Launching a new EC2 instance: i-0314b280c6706c54d | At 2026-03-23T15:11:10Z an instance was launched in response to an unhealthy instance needing to be replaced. | 2026 March 23, 04:11:12 PM +01:00 | 2026 March 23, 04:11:20 PM +01:00 |
| Successful | Terminating EC2 instance: i-045de17dfacf2666e | At 2026-03-23T15:11:10Z an instance was taken out of service in response to an EC2 health check indicating it has been terminated or stopped. | 2026 March 23, 04:11:10 PM +01:00 | 2026 March 23, 04:11:33 PM +01:00 |
| Successful | Launching a new EC2 instance: i-0cbb8fe80bf272821 | At 2026-03-23T15:09:09Z an instance was launched in response to an unhealthy instance needing to be replaced. | 2026 March 23, 04:09:11 PM +01:00 | 2026 March 23, 04:09:16 PM +01:00 |
| Successful | Terminating EC2 instance: i-09e3d50678f9a02a2 | At 2026-03-23T15:09:09Z an instance was taken out of service in response to an EC2 health check indicating it has been terminated or stopped. | 2026 March 23, 04:09:09 PM +01:00 | 2026 March 23, 04:11:53 PM +01:00 |
| Successful | Launching a new EC2 instance: i-09e3d50678f9a02a2 | At 2026-03-23T15:07:08Z an instance was launched in response to an unhealthy instance needing to be replaced. | 2026 March 23, 04:07:10 PM +01:00 | 2026 March 23, 04:07:18 PM +01:00 |
| Successful | Terminating EC2 instance: i-072a2bc27ff39dda6 | At 2026-03-23T15:07:08Z an instance was taken out of service in response to an EC2 health check indicating it has been terminated or stopped. | 2026 March 23, 04:07:08 PM +01:00 | 2026 March 23, 04:11:32 PM +01:00 |
| Successful | Launching a new EC2 instance: i-045de17dfacf2666e | At 2026-03-23T15:05:07Z an instance was launched in response to an unhealthy instance needing to be replaced. | 2026 March 23, 04:05:09 PM +01:00 | 2026 March 23, 04:05:15 PM +01:00 |
| Successful | Terminating EC2 instance: i-0af9044391b0b554f | At 2026-03-23T15:05:07Z an instance was taken out of service in response to an EC2 health check indicating it has been terminated or stopped. | 2026 March 23, 04:05:07 PM +01:00 | 2026 March 23, 04:05:30 PM +01:00 |
| Successful | Launching a new EC2 instance: i-072a2bc27ff39dda6 | At 2026-03-23T15:03:06Z an instance was launched in response to an unhealthy instance needing to be replaced. | 2026 March 23, 04:03:08 PM +01:00 | 2026 March 23, 04:03:14 PM +01:00 |
| Successful | Terminating EC2 instance: i-038a592e9ce6c0db4 | At 2026-03-23T15:03:06Z an instance was taken out of service in response to an EC2 health check indicating it has been terminated or stopped. | 2026 March 23, 04:03:06 PM +01:00 | 2026 March 23, 04:05:29 PM +01:00 |
| Successful | Launching a new EC2 instance: i-038a592e9ce6c0db4 | At 2026-03-23T15:01:05Z an instance was launched in response to an unhealthy instance needing to be replaced. | 2026 March 23, 04:01:07 PM +01:00 | 2026 March 23, 04:01:12 PM +01:00 |
| Successful | Terminating EC2 instance: i-0553d738756ac8e6f | At 2026-03-23T15:01:05Z an instance was taken out of service in response to an EC2 health check indicating it has been terminated or stopped. | 2026 March 23, 04:01:05 PM +01:00 | 2026 March 23, 04:01:27 PM +01:00 |
| Successful | Launching a new EC2 instance: i-0553d738756ac8e6f | At 2026-03-23T14:59:07Z a monitor alarm TargetTracking-c62825a3581670l14338996t1w015973937388-AutoScalingGroup-t45BKDp9pUlm-AlarmHigh-277c294a-cb13-477b-9098-a779f9e4e228 in state ALARM triggered policy de-c1w3-scaling-policy changing the desired capacity from 2 to 4. At 2026-03-23T14:59:12Z an instance was started in response to a difference between desired and actual capacity, increasing the capacity from 2 to 4. | 2026 March 23, 03:59:14 PM +01:00 | 2026 March 23, 04:00:22 PM +01:00 |
| Successful | Launching a new EC2 instance: i-0af9044391b0b554f | At 2026-03-23T14:59:07Z a monitor alarm TargetTracking-c62825a3581670l14338996t1w015973937388-AutoScalingGroup-t45BKDp9pUlm-AlarmHigh-277c294a-cb13-477b-9098-a779f9e4e228 in state ALARM triggered policy de-c1w3-scaling-policy changing the desired capacity from 2 to 4. At 2026-03-23T14:59:12Z an instance was started in response to a difference between desired and actual capacity, increasing the capacity from 2 to 4. | 2026 March 23, 03:59:14 PM +01:00 | 2026 March 23, 04:00:19 PM +01:00 |
| Successful | Launching a new EC2 instance: i-0f3f6bb221e52b9ec | At 2026-03-23T14:50:58Z an instance was launched in response to an unhealthy instance needing to be replaced. | 2026 March 23, 03:50:59 PM +01:00 | 2026 March 23, 03:51:05 PM +01:00 |
| Successful | Terminating EC2 instance: i-0716bedf25b194f22 | At 2026-03-23T14:50:57Z an instance was taken out of service in response to an EC2 health check indicating it has been terminated or stopped. | 2026 March 23, 03:50:58 PM +01:00 | 2026 March 23, 03:51:20 PM +01:00 |
| Successful | Launching a new EC2 instance: i-0d362774167fc72fa | At 2026-03-23T14:48:56Z an instance was launched in response to an unhealthy instance needing to be replaced. | 2026 March 23, 03:48:58 PM +01:00 | 2026 March 23, 03:49:04 PM +01:00 |
| Successful | Terminating EC2 instance: i-0d288e70cacce7570 | At 2026-03-23T14:48:56Z an instance was taken out of service in response to an EC2 health check indicating it has been terminated or stopped. | 2026 March 23, 03:48:56 PM +01:00 | 2026 March 23, 03:49:19 PM +01:00 |
| Successful | Launching a new EC2 instance: i-0d288e70cacce7570 | At 2026-03-23T13:30:21Z a user request update of AutoScalingGroup constraints to min: 2, max: 4, desired: 2 changing the desired capacity from 0 to 2. At 2026-03-23T13:30:25Z an instance was started in response to a difference between desired and actual capacity, increasing the capacity from 0 to 2. | 2026 March 23, 02:30:27 PM +01:00 | 2026 March 23, 02:30:37 PM +01:00 |
| Successful | Launching a new EC2 instance: i-0716bedf25b194f22 | At 2026-03-23T13:30:21Z a user request update of AutoScalingGroup constraints to min: 2, max: 4, desired: 2 changing the desired capacity from 0 to 2. At 2026-03-23T13:30:25Z an instance was started in response to a difference between desired and actual capacity, increasing the capacity from 0 to 2. | 2026 March 23, 02:30:27 PM +01:00 | 2026 March 23, 02:30:32 PM +01:00 |