Amazon IoT Events end of support - Amazon IoT Events
Considerations when migrating away from Amazon IoT Events
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

End of support notice: On May 20, 2026, Amazon end support for Amazon IoT Events. After May 20, 2026, you will no longer be able to access the Amazon IoT Events console or Amazon IoT Events resources. For more information, visit this Amazon IoT Events end of support.

Amazon IoT Events end of support

After careful consideration, we decided to end support for the Amazon IoT Events service, effective May 20, 2026. Amazon IoT Events will no longer accept new customers beginning May 20, 2025. As an existing customer with an account signed up for the service before May 20, 2025, you can continue to use Amazon IoT Events features. After May 20, 2026, you will no longer be able to use Amazon IoT Events.

This page provides instructions and considerations for Amazon IoT Events customers to transition to an alternate solution to meet your business needs.

Note

The solutions presented in these guides are meant to serve as an illustrative examples, not as a production-ready replacements for Amazon IoT Events functionality. Customize the code, workflow, and related Amazon resources to your business needs.

Topics

Considerations when migrating away from Amazon IoT Events

  • Implement security best practices, including using IAM roles with least privilege for each component and encrypting data at rest and in transit. For more information, see Security best practices in IAM in the IAM User Guide.

  • Consider the number of shards for the Kinesis stream based on your data ingestion requirements. For more information on Kinesis shards, see Amazon Kinesis Data Streams terminology and concepts in the Amazon Kinesis Data Streams Developer Guide.

  • Set up comprehensive monitoring and debugging using CloudWatch for metrics and logs. For more information, see What is CloudWatch? in the Amazon CloudWatch User Guide.

  • Consider the structure of your error handling, including how to manage messages that fail processing repeatedly, implementing retry policies, and setting up a process to isolate and analyze problematic messages.

  • Use the Amazon Pricing Calculator to estimate costs for your specific use case.