- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
If you want true isolation between your lower environments (Staging, QA, etc) and production, you need to use separate accounts. This is true, even outside of the AWS IoT services.
For your rule example, you can specify the source in your Rule query statement to restrict what topic filter gets sent to SQS.
Thanks. What about using different Regions to separate them? I notice that the Rules and Things I create are region-specific, I assume the endpoint would be different in a different region as well.
Yes the endpoint is different in different regions. Nonetheless, multiple accounts is generally considered best practice. This whitepaper is well worth a read: https://docs.aws.amazon.com/whitepapers/latest/organizing-your-aws-environment/organizing-your-aws-environment.html
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 10 Monaten
- Wie veröffentliche ich MQTT-Nachrichten von meinem Gerät auf AWS IoT Core, wenn ich Python verwende?AWS OFFICIALAktualisiert vor 3 Jahren
As an example, I have a rule that forwards messages from topics to SQS under certain conditions. I'd want to make sure that a rule intended for one project doesn't process things from a different project. I'm not seeing any obvious way to restrict the scope of rules this way.