iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Amazon ECS GPU auto-repair, EC2 Auto Scaling replacement, and EC2 automatic recovery solve different failures. ECS Managed Instances can use NVIDIA DCGM health checks to detect a critical GPU fault, drain the host, launch replacement capacity, and terminate the impaired instance. EC2 Auto Scaling replaces an instance that its configured health signals mark unhealthy. EC2 automatic instance recovery instead attempts to move the same instance to a healthy host after an AWS infrastructure problem causes a system status-check failure. Choosing the right mechanism depends on what failed, who detects it, and whether your ECS tasks must be drained and rescheduled.
The short answer: three layers of recovery
Think of these features as a stack rather than competing switches:
- ECS GPU auto-repair: GPU-specific detection and replacement for ECS Managed Instances with GPU hardware.
- EC2 Auto Scaling health replacement: group-level capacity management. It replaces an InService instance judged unhealthy by EC2 or other configured health sources.
- EC2 automatic instance recovery and AWS Health: host or infrastructure recovery after an EC2 system status-check failure. The service attempts to restore the existing instance on another host rather than intentionally replacing it because a GPU or application is unhealthy.
These mechanisms can coexist. For a GPU-backed ECS service, GPU auto-repair addresses a failed accelerator, Auto Scaling protects the group’s desired capacity, and EC2 recovery handles an eligible AWS host fault. None of them is a universal application failover system.
Free tools Windows power users keep installed
One-click scans. No signup required.
What each mechanism actually monitors
| Mechanism | Primary failure signal | What it does | ECS task awareness | Outside its scope |
|---|---|---|---|---|
| ECS Managed Instances GPU auto-repair | NVIDIA DCGM GPU-health checks; a critical GPU failure can mark the instance impaired. | Marks the host impaired and draining, provisions replacement capacity, allows a graceful-stop period, then terminates the impaired instance. | Yes, through the documented ECS Managed Instances draining workflow. | Non-GPU guest failures, arbitrary application errors, unsupported providers, and failures that do not trigger the documented GPU signal. |
| EC2 Auto Scaling health replacement | EC2 status checks plus configured signals such as Elastic Load Balancing, VPC Lattice, EBS, or custom health checks. | Terminates and replaces an unhealthy InService instance to maintain the group’s desired capacity. | It can integrate with ECS managed draining when the capacity provider uses an Auto Scaling group, but Auto Scaling itself is not GPU diagnosis. | Failures not reported through configured health inputs, and application resilience beyond replacing a group member. |
| EC2 automatic instance recovery / AWS Health | An underlying AWS host or infrastructure problem that produces an EC2 system-status-check failure. | Attempts to recover the same instance on another host; AWS Health reports a simplified recovery outcome. | The recovery documentation does not describe ECS GPU-aware task replacement. | Guest operating-system, application, GPU, task, and other failures that do not cause an eligible system-status failure. |
Compare them on five questions: what detects the fault, what resource is recovered or replaced, whether ECS drains tasks, how capacity is maintained during the event, and which failure classes are explicitly excluded.
#1 Best Overall
- Powerful Turbo Fan:CAGIWIRU Electric Air Duster have reached speed up to 130000RPM,Can efficient remove dust and debris.With LED light and Three Adjustable Speed to meet with different cleaning tasks.
- With Attached USB C Fasting Charging cable.Charing 3 hours,Enjoy up to 240 minutes of use on the lowest setting, For third speed can use for 25mins.with four charging options to meet with your needs.
- Wide Application: attached 5 different nozzles,making it suitable for a variety of scenes, such as car,pet, pc, keyboards, and other electronic devices. It also serves for office and home clean duster.
- Handy Design & Portable:Cordless air duster electric nozzle is Light weight and small size, design and comfortable to hold and space saving, convenient to carry around. You can put it in your room or inside the car without taking up space.
- Economical &Reusable: Built durable materials with a long-lasting battery,our CAGIWIRU air duster it's a sustainable alternative to disposable air cans.
How Amazon ECS GPU auto-repair works
1. GPU health is checked on the right ECS capacity type
GPU auto-repair is a feature of Amazon ECS Managed Instances using GPU hardware. ECS uses NVIDIA Data Center GPU Manager (DCGM) health monitoring. The feature’s documented default is enabled for this managed-instance GPU scenario; do not generalize that default to every ECS capacity provider or every EC2-backed cluster.
2. A critical GPU failure marks the instance impaired
When DCGM reports a critical GPU condition, ECS can mark the managed instance impaired. This signal is narrower than “the server is unhealthy.” A host can have a functioning GPU while an application, container runtime, disk, network path, or operating system is failing; those conditions require other detection and recovery paths.
3. ECS starts managed draining
The impaired instance is placed into a draining state. ECS stops placing new service tasks there and begins the scheduler’s normal shutdown and rescheduling behavior. Existing service replica tasks can receive their configured stop period so that they finish work or shut down cleanly before the host disappears.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
4. Replacement capacity is provisioned
ECS provisions replacement capacity for the managed-instance capacity provider. The replacement is intended to give the scheduler somewhere to place tasks while the impaired host is being retired. Capacity planning still matters: if the cluster has no spare GPU capacity, a task may remain pending even though repair has begun.
5. The impaired host is terminated
After draining and the supported graceful-stop period, ECS terminates the impaired instance. The sequence is therefore drain, replace, then terminate, not an in-place repair of the failed GPU.
GPU auto-repair settings and related daemon repair
Disabling repair does not disable monitoring
If you disable the ECS GPU auto-repair setting, ECS continues to monitor GPU health but no longer automatically replaces an instance that it marks impaired for that condition. The same setting also disables ECS Managed Daemons auto-repair, so review both effects before changing it.
Rank #2
- Screen Cleaner is Your Screen’s New Bestfriend! - EVEO is proud to present a screen cleaner that’s perfectly suited for your TV. Meet your new screen cleaner, computer screen cleaner, laptop cleaner, iPad cleaner, Macbook,tv cleaner or any other electronic device. Our screen cleaner spray and wipe along with the included plush microfiber cloth, easily removes dust, fingerprints & other smudges on the screen’s surface. Clean effectively for a streak-free screen
- Gentle on your Screens - Our screen cleaner spray and wipes is compatible to be used even for the most sensitive LCD, LED, CRT, and OLED screens in proper use. Be at ease knowing that this product is compatible with all the major brands: LG, SONY, Samsung, Sharp, iPad, iPhone, Android screens, Kindle, PC monitors - we’ve got you covered! Can be used as LCD screen cleaner, tv cleaner, smart tv screen cleaner, and more
- Premium Super Soft Plush Microfiber Cloth - Included in this efficient screen cleaning kit. This screen cleaner spray and wipe has our signature plush microfiber cloth specially designed to comply with screens and monitors and leave them streak-free. Has been shown to effectively absorbs stubborn stains, zero streaks, and no fiber shedding. Always use this together with our screen cleaner for the best results
- Easy-to-Use Screen Cleaner Kit + microfiber cleaning cloth - The EVEO Screen Cleaning Kit will easily be your new favorite tool when it comes to taking care of the things you love most, quick and easy solution for a streak-free screen. Simply screw on the sprayer gun on the screen cleaner bottle. Spray the cleaning liquid onto the microfiber cloth, then wipe the screen until desired cleanliness & shine is achieved.
- Quality Screen Care Kit Worth Purchasing - Enjoy a convenient Screen Cleaner anytime, anywhere you need it. Your satisfaction is our top priority. We stand behind the quality of our products and that’s why, you shouldn’t be worrying at all. We manufacture the Best Screen Cleaner. and can be used for laptop cleaning kit, laptop screen cleaner, tv screen cleaner for smart tv. MacBook screen cleaner, monitor cleaner or screen cleaner spray for electronic devices with microfiber cleaning cloth
Critical-daemon repair is a separate signal
ECS has a related mechanism for critical daemons. If a daemon configured as critical stops or becomes unhealthy, ECS can impair, drain, and replace its host. The daemon documentation states that the critical property defaults to true, but criticality is configurable. A daemon failure is not the same event as a DCGM GPU failure; instrument and alert on both if both matter to your workload.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteConfirm the provider before relying on defaults
- Verify that the capacity provider is ECS Managed Instances, not merely an EC2 Auto Scaling group used by ECS.
- Confirm that the instances have supported NVIDIA GPU hardware and that DCGM health checks are operating.
- Inspect the deployed service and capacity-provider settings rather than assuming a console default survived infrastructure-as-code changes.
- Record whether GPU auto-repair is enabled and whether daemon auto-repair was changed as a side effect.
Will ECS move tasks before replacing an unhealthy instance?
For the documented ECS Managed Instances GPU-repair workflow, yes: ECS drains the instance, gives existing tasks a chance to stop gracefully, provisions replacement capacity, and then terminates the impaired host. “Move” usually means ECS stops and reschedules a service task on another instance; it is not a live migration of a running container or its in-memory state.
Service tasks versus standalone tasks
ECS draining is scheduler-aware for service replica tasks. A standalone task launched with RunTask is not managed like a service replica: it may be allowed to finish, or an operator or automation may need to stop and relaunch it. Design batch and one-off workloads with checkpointing and retry behavior rather than assuming draining will duplicate them automatically.
How long draining can take
A draining operation can remain in progress for up to 48 hours under the ECS managed-instance draining behavior documented by AWS (documentation accessed 2026-10-13). This is an operational upper limit, not a promise that every task receives 48 hours or that recovery completes within that time. Task stop timeouts, stuck processes, insufficient replacement capacity, and deployment constraints can all affect the practical result.
How much capacity can drain at once
AWS documents a limit of no more than 20% of the instances belonging to the capacity provider draining at one time. For a provider with fewer than nine instances, at most one instance drains at a time (AWS documentation accessed 2026-10-13). These are service behavior limits, not measured availability or repair-success statistics. A small GPU fleet can therefore experience serialized repairs, while a larger fleet can lose several hosts concurrently within the percentage limit.
Recommended Free Tools
How EC2 Auto Scaling health replacement differs
It protects desired group capacity
EC2 Auto Scaling considers an instance healthy unless it receives an unhealthy indication from the health sources configured for the group. EC2 status checks are the baseline; integrations can add signals from Elastic Load Balancing, VPC Lattice, EBS, or customer-defined health checks. When an InService instance is judged unhealthy, Auto Scaling terminates it and launches a replacement so the group returns toward its desired capacity.
Rank #3
- 【Large size】：Measuring 800 x 300 mm/ 31. 5×12 inches, which is wider and taller than others. Large mouse pad can perfectly fit your keyboard and mouse of any size, and there is also ample space for peripherals such as phones, tablets, etc.
- 【LED backlight mouse pad】：Blade Hawks RGB mouse pad provides 7 static modes and 7 dynamic modes will give you the options you are looking for. Power-off memory function remembers the last lighting mode you selected. The super glow fiber Chroma will give you a colorful gaming setup that you want.
- 【Anti-slip rubber base】：Made from Natural rubber, this gaming mousepad will firmly grip your desktop, allowing you to enjoy the ultimate precision in the games you are most passionate about. It also comes with a texture that enhances this ability even further.
- 【Smooth and waterproof surface】: Micro-textured cloth surface, for extremely precise mouse control and a smooth movement. When liquid splashes on the gaming mouse pad, it forms water droplets and slides down. Will not delay your work or gameplay.
- 【Plug and play】: This mouse and keyboard pad is powered by USB, plug and play, no driver required. One button control light modes. Press one time to change the lighting mode, press twice to change the brightness, press and hold about 3 seconds turn ON/OFF.
It does not perform GPU-specific diagnosis
An Auto Scaling group does not become GPU-aware merely because its instances contain GPUs. Unless a GPU failure is translated into a health signal that the group consumes, Auto Scaling may continue to regard the instance as healthy. Conversely, a load-balancer failure can make an instance unhealthy even when its GPU is fine. Configure a health-check path that reflects the failure you need the group to act on.
Health-check grace periods affect replacement timing
New instances are commonly given a health-check grace period while the operating system, ECS agent, drivers, and tasks start. A period that is too short can cause healthy-but-not-ready GPU hosts to be replaced repeatedly; one that is too long delays response to a real failure. Set it from measured bootstrap time and alert on replacement loops.
ECS integration through a capacity provider
When an ECS capacity provider uses an Auto Scaling group, ECS managed draining can coordinate with Auto Scaling termination paths, including group health replacement. That coordination is distinct from ECS Managed Instances GPU auto-repair: the group still decides that its member is unhealthy, while ECS handles task draining where supported.
What EC2 automatic instance recovery and AWS Health do
Recovery targets the underlying host
Automatic instance recovery addresses an AWS infrastructure problem that causes an EC2 system status-check failure. AWS attempts to move the instance to a healthy host while preserving the instance identity and attached configuration as supported. This is recovery of the same instance, not a deliberate replacement triggered by a bad GPU, failed process, or unhealthy container.
Simplified recovery and CloudWatch action-based recovery
AWS documentation describes simplified automatic recovery as enabled by default on supported instances, subject to eligibility and instance conditions. A CloudWatch action-based recovery alarm has additional prerequisites: the instance must be running and capacity for that instance type must be available when recovery is attempted. Check current support for the exact instance family, tenancy, storage, and configuration before treating either path as guaranteed.
AWS Health reporting is an outcome signal
AWS Health Dashboard events provide a simplified view of recovery outcomes. They are useful for incident awareness, but they do not turn host recovery into ECS task orchestration or GPU remediation. Use ECS and Auto Scaling events, task health, and application telemetry to determine whether workloads actually recovered.
Rank #4
- 【Softer and More Comfortable】Vaydeer wrist rest has unique diamond pattern, which is the combination of softness and aesthetics. The materials of wrist rest are improved into higher quality memory foam and covered with silky smooth lycra. The computer wrist rest makes you as comfortable and cushiony as like rest your wrists on clouds.
- 【Ergonomic Wrist Saver】The wrist rests for keyboard and mouse comes with a 17.32×3.15×0.83 inch keyboard wrist pad and a 5.94×3.15×0.83 inch mouse wrist support. Based on ergonomic design, the unique concave shape is the perfect fit for your wrist joints. The wrist rest pad fits most computer keyboards and laptops, improve hand and wrist posture, release your wrist and arm stress.
- 【Non-Slip Rubber Bottom】Featuring an anti-skid silicone base on the bottom, this wrist keyboard support stays firmly in place on your desk, preventing the padding from sliding around, ensuring stable and consistent wrist support during extended computer sessions.
- 【Better Experience & Pain Relief】Our keyboard arm rest is beneficial to alleviate the soreness caused by direct contact and friction between your arm and a hard desk surface, reducing the risk of wrist fatigue or carpal tunnel. The soft texture of memory foam can evenly distribute the pressure around your wrists and provide good support with just enough give.
- 【Helpful in Multiple Scenarios】Whether you're working, studying, writing, typing, gaming, this keyboard and mouse rest combo is an essential accessory to add comfort and support to your hands and wrists. It’s also a great gift for men, women, family, friend, coworker, gamer, teacher, etc.
Recovery is not application high availability
A recovered instance can still have a damaged guest operating system, a failed driver, a bad application deployment, or no healthy tasks. AWS recommends designing for traffic failover to healthy instances; instance recovery alone does not establish application-level resilience.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Side-by-side decision table
| Decision axis | ECS GPU auto-repair | EC2 Auto Scaling replacement | EC2 recovery / AWS Health |
|---|---|---|---|
| Best match | Critical NVIDIA GPU failure on an ECS Managed Instance. | An unhealthy member of an Auto Scaling group, based on configured health inputs. | An AWS host or infrastructure fault reported by a system status check. |
| Resource action | Drain and replace the impaired instance. | Terminate the unhealthy member and launch another to restore desired capacity. | Attempt to place the existing instance on a healthy host. |
| GPU diagnosis | Yes, through NVIDIA DCGM. | No, unless a GPU-aware check feeds the group’s health signal. | No; a GPU or guest failure is outside the stated trigger. |
| Task handling | ECS-aware draining and rescheduling for supported service tasks. | Can coordinate with ECS managed draining through an ECS Auto Scaling capacity provider. | No documented ECS GPU-aware task replacement in the recovery mechanism. |
| Capacity behavior | Replacement capacity is provisioned as part of the repair workflow; concurrent draining is limited. | Maintains the group’s desired capacity subject to launch limits, quotas, and available GPU instances. | Restores the instance if eligible capacity is available; it does not maintain a fleet’s spare capacity. |
| Main limitation | Only supported ECS Managed Instances GPU scenarios and detected critical GPU conditions. | Only failures represented by configured health signals; not a general GPU repair service. | Only eligible infrastructure/system-check failures; not an application or task recovery plan. |
Which mechanism should you use?
Choose ECS GPU auto-repair when the accelerator is the failure domain
Use it for GPU workloads where a DCGM-detected critical fault makes the host unsuitable and you want ECS to coordinate draining and replacement. Keep service replicas spread across multiple GPU instances so one impaired host does not exhaust placement options.
Choose Auto Scaling health replacement when fleet capacity is the priority
Use an Auto Scaling group when you need the group to replace members based on EC2, load-balancer, storage, or custom health signals. Add a custom GPU health check only if you can reliably report that signal to the group; otherwise a failed GPU can remain invisible to Auto Scaling.
Use automatic recovery for infrastructure faults
Use EC2 automatic recovery for eligible system-status-check failures caused by the AWS host or infrastructure layer. Keep a separate replacement path for guest, driver, GPU, and application failures.
Combine them for defense in depth
A resilient GPU service may use ECS GPU auto-repair for accelerator faults, an ECS capacity provider backed by Auto Scaling for fleet-level health and desired capacity, and EC2 automatic recovery for eligible host failures. Define precedence and alerts so multiple mechanisms do not replace the same instance simultaneously.
Configuration checklist
- Identify the capacity provider. Record whether the workload uses ECS Managed Instances or an EC2 Auto Scaling capacity provider.
- Verify GPU support. Confirm the instance family, NVIDIA drivers, ECS agent, and DCGM health monitoring meet the current AWS requirements for your deployment.
- Check repair settings. Confirm GPU auto-repair status and understand that disabling it also disables ECS Managed Daemons auto-repair.
- Define task behavior. Set service deployment capacity, task stop timeouts, health checks, and retry policies so tasks can leave a draining host safely.
- Provide replacement headroom. Check GPU quotas, subnet IPs, placement constraints, and instance availability before an incident.
- Configure Auto Scaling health inputs. Select EC2 and integration signals deliberately, set a grace period based on bootstrap measurements, and avoid replacing hosts merely because they are still initializing.
- Enable and verify EC2 recovery. Confirm instance eligibility, running state, available capacity, and the alarms or notifications used to observe recovery attempts.
- Alert on each layer. Monitor DCGM/ECS impairment, instance draining, Auto Scaling replacements, EC2 system-status failures, task placement failures, and application-level health.
Failure scenarios and the correct response
Scenario: DCGM reports a critical GPU fault
ECS GPU auto-repair is the direct mechanism for an ECS Managed Instance. Expect impairment, draining, replacement capacity, and termination. Verify that service tasks reschedule and that standalone jobs have a retry or checkpoint path.
Best Value
- 【No Drill Mounted】Cable management tray can be assembled in as little as 3 minutes or less-simply. Side clips easily clampe the edge of desk, pass through the holes on the sides, and secure excess cables with baskets. Desk cable management supports inward or outward installation to meet your needs in different scenarios, and provides you with great convenience when collecting and organizing wires.
- 【Rubber Pad Protects Desk】Wire organizer under desk built-in soft rubber pads on the clamp protect your desk from scratches, so you will not damage your furniture or office.
- 【Sturdy and Beautiful】Cord management under desk is made of high-quality carbon steel and holds about 15 lbs. The wire basket has 2 holes on each side of the tray to enable your cables to pass freely. Cable baskets are suitable for desk thickness use from 0.4" to 2.4".
- 【Space Saving & Keep Organized】Desk cable management tray holds all your power cords, outlet strips, USB hubs and computer transformers hidden from your feet, and the data cables will not enter the vacuum cleaner to keep your desk clean and tidy. Desk wire organizer is also suitable for use in the kitchen and outdoors.
- 【Reduce Safety Risks】Cable tray under desk keeps all plugs away from your kids, no more worry about tripping. Using 2 holes wire tray saves extra space, helps you easily cabling and wire protection. The mesh design is not easy to accumulate dust, but avoids safety accidents caused by messy wires.
Scenario: The load balancer marks an instance unhealthy
Auto Scaling can replace the instance if the load-balancer health signal is enabled for the group. ECS draining may coordinate termination through the capacity provider. GPU auto-repair is not required unless the underlying problem is also a critical GPU fault.
Scenario: EC2 system status check fails
Investigate automatic instance recovery and AWS Health events. If recovery succeeds, validate ECS agent state, GPU visibility, task health, and traffic before declaring the service recovered. If recovery is unavailable or fails, let the fleet’s replacement and task-rescheduling path take over.
Scenario: A container or standalone task crashes
Neither GPU auto-repair nor host recovery is a substitute for task-level supervision. Configure ECS service deployment and restart behavior, and make standalone tasks idempotent with durable checkpoints or an external job queue.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteScenario: Replacement tasks stay pending
Inspect GPU resource requirements, placement constraints, capacity-provider strategy, subnet capacity, service deployment limits, and account quotas. A repair event can be correct while scheduling still fails because no compatible GPU capacity is available.
Operational pitfalls
- Assuming every ECS provider has the GPU default: the documented enabled-by-default behavior is for ECS Managed Instances with GPU hardware.
- Calling all replacement “recovery”: Auto Scaling replaces a group member; EC2 automatic recovery attempts to restore the same instance.
- Expecting live migration: ECS stops and reschedules tasks; container memory and local ephemeral state do not move live to another host.
- Ignoring standalone tasks: RunTask workloads do not receive the same scheduler treatment as service replicas during draining.
- Relying on one host: replacement cannot provide availability when there is no spare compatible GPU capacity.
- Disabling repair without checking daemon behavior: the setting also disables ECS Managed Daemons auto-repair.
- Treating the 20% and 48-hour figures as uptime guarantees: they are documented operational limits, not measured repair time or availability.
- Using system recovery for a GPU problem: an infrastructure recovery event does not diagnose or replace a failed accelerator or repair a guest driver.
How to validate a recovery design safely
Test each signal independently in a non-production environment and document the observed event order. Confirm that ECS marks the expected instance draining, that replacement capacity joins the provider, that service tasks become healthy elsewhere, and that standalone jobs follow their own retry path. Separately validate Auto Scaling health replacement and EC2 system-status recovery. During every test, record task placement, deployment capacity, stop timeouts, notification delivery, and application traffic—not just whether an instance disappeared.
Before production, establish runbooks for a stuck drain, pending GPU tasks, repeated Auto Scaling replacements, failed EC2 recovery, and quota exhaustion. Include the exact owner for changing repair settings and the rollback action if a new health check causes a replacement loop.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
