1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
Aha! Turns out we were overloading the IAM role 'device-dynamodb' with too many policies (max 10 per role).
We've gotten a better understanding of roles and policies, and editing the "Resource" JSON in policies to organise everything.
We've created new tables and better naming conventions for everything and all seems to be working (6 hours run so far and all good).
I'll update this thread with results when possible (if all goes well over the weekend, I'll consider it all a success).
répondu il y a 5 mois
Contenus pertinents
- demandé il y a un an
- demandé il y a 7 mois
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a 4 mois
Can you share more information? The DynamoDB table schema, the rule etc??
Did you enabled logging for AWS IoT Core? When the rule execution fails, you should be able to find the reason in the CloudWatch logs.