AWS Cloud Infrastructure

How AWS Fleet Hub end-of-life would influence its users?

End of AWS Fleet Hub: Impact on IoT Device Management

 

On October 18, 2025, Amazon Web Services (AWS) will officially discontinue Fleet Hub, a tool within AWS IoT Device Management designed to simplify monitoring and alerting for IoT device fleets. Fleet Hub has allowed organizations to create accessible, web-based applications for real-time monitoring without requiring users to have AWS accounts. With this service’s end-of-life (EOL) approaching, AWS has outlined a phased shutdown process that will impact existing users but leave other IoT Device Management capabilities intact. In this article, we’ll explore what the Fleet Hub discontinuation means, key dates to know, and options for organizations planning their transition.

 

Before discussing the details of Fleet Hub’s end-of-life, let’s clarify what Fleet Hub actually is. AWS Fleet Hub enables the creation of standalone web applications to monitor the health of device fleets. These applications are accessible to users in your organization without requiring them to have AWS accounts. Fleet Hub offers capabilities for near-real-time monitoring of device fleets, setting alerts to notify technicians of unusual behavior, and running jobs.

 

Phased Shutdown of AWS Fleet Hub: What to Expect

 

Fleet Hub will transition into its EOL in a three-phased manner.
The first phase started on October 17th, 2024. AWS stopped onboarding new customers to Fleet Hub. An important thing to notice is that AWS considers new customers to be those who didn’t have any Fleet Hub applications before October 17th.


Until October 17, 2025 existing Fleet Hub customers can continue to use the service. AWS will not introduce new features during this time but will support critical bug fixes.
The third phase will begin on October 18, 2025. On this date, AWS will stop support for  Fleet Hub for AWS IoT Device Management. The discontinuation of Fleet Hub doesn’t impact any other AWS IoT Device Management capabilities. However, existing Fleet Hub applications will be deleted.

 

This does not apply to underlying AWS resources associated with Fleet Hub such as AWS IoT Device Management jobs, Fleet Hub alarm components such as AWS IoT Device Management fleet metrics, CloudWatch alarms, and Amazon SNS topics. These resources can be accessed independently from the AWS Management Console, AWS CLI, or AWS SDK. 

 

Managing AWS Resources After Fleet Hub End-of-Life

 

An important thing to notice is that deleting Fleet Hub applications won’t delete the underlying AWS resources associated with Fleet Hub. Functionalities such as fleet connectivity state summary, Fleet Hub alarms, device search, job execution, and device details view are directly within the AWS IoT Device Management console and will be accessible to support your business needs.

 

If You struggle with deleting underlying AWS resources or would like to know how to access the resources independently from the AWS Management Console, AWS CLI, or AWS SDK, do not hesitate to contact us!

 

Check our previous articles on AWS tool shutdowns:

https://wizzdev.com/blog/aws-codecommit-codestar-and-cloud9-eol-and-how-you-can-migrate/

https://wizzdev.com/blog/aws-opsworks-eol-and-how-you-can-migrate/

 

Recent entries

We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you are happy with it.