Skip to content

IoT Core devices shadow amount limit

0

Hi, I have a question, is there a specific limit to the number of named device shadows in one IoT Core Thing? I can't find anything in the documentation, Amazon Developer Q says there isn't, but I wanted to confirm this before I start implementing my solution with this assumption.

3 Answers
0

Hello @Grzegorz,

From my basic attempts, it seems as if there are no limits to named shadow. I just tried creating 200 named shadows and was successful in doing so. I am not sure what the limit is. I am trying to find official documentation for it.

Thank you for your patience.

Thanks, Aniruddha

AWS

answered 2 years ago

0

I just created 10,000 named device shadows in one thing, that's enough for me at that moment but still will be good if limit information is added to the documentation.

answered a year ago

-1

Yes, there is a specific limit to the number of named device shadows in one IoT Core Thing. According to AWS documentation, you can have a maximum of 25 named shadows per thing. This limit is important to consider when designing your IoT solution.

It's worth noting that while you can have up to 25 named shadows per thing, there are some additional considerations:

  1. For dynamic groups, only a maximum of 25 named shadows per thing are processed for query terms that are not data source specific. If this limit is exceeded for a thing, an event called "NamedShadowCountForDynamicGroupQueryLimitExceeded" will be emitted.

  2. By default, you can add up to 10 shadow names per AWS account for indexing purposes. However, this limit can be increased by contacting AWS support.

  3. There's no limit on the number of things you can create in IoT Core, but there are limits on the number of attributes per thing. A thing with a thing type can have up to 50 attributes, while a thing without a thing type can have up to three attributes.

  4. The Device Shadow service supports up to 10 in-flight unacknowledged messages per thing on a single connection. When this quota is reached, all new shadow requests are rejected with a 429 error code until the number of in-flight requests drops below the limit.

When implementing your solution, keep these limits in mind to ensure optimal performance and avoid potential issues with your IoT Core setup.
Sources
CloudWatch Logs AWS IoT log entries - AWS IoT Core
AWS IoT Device Shadow service - AWS IoT Core
AWS IoT Core endpoints and quotas - AWS General Reference
Managing fleet indexing - AWS IoT Core

answered 2 years ago

  • 25 limit is regarding dynamic query, not applied to my case. I just created 27 named shadows in one Thing. Question is where is limit

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.