AWS IoT Core（使用 IoT 规则）到不同 AWS 账户中的 Kinesis Steam/Firehose
AWS IoT Core (using IoT Rule) to Kinesis Steam/Firehose in Different AWS Account
我想将数据从 IoT 规则发送到 AWS Kinesis Stream/Firehose。
IoT Core 和 Kinesis Steam 都在不同的帐户中。
有什么办法吗？
执行此操作的一种方法是让 IoT 规则在其他帐户中调用 lambda。然后，此 lambda 将发布到同一账户中的 AWS Kinesis Stream。
https://aws.amazon.com/blogs/iot/access-cross-account-resources-using-aws-iot-rules-engine/ 给出了此跨账户规则的示例。这说明：
Cross-account access, via AWS IoT Rules Engine, needs resource-based permissions. Hence, only destinations that support resource-based permission can be enabled for the cross-account access via AWS IoT Rules Engine. Following is the list of such destinations:
- Amazon Simple Queue Service (SQS)
- Amazon Simple Notification Service (SNS)
- Amazon Simple Storage Service (S3)
- AWS Lambda
我想将数据从 IoT 规则发送到 AWS Kinesis Stream/Firehose。 IoT Core 和 Kinesis Steam 都在不同的帐户中。
有什么办法吗？
执行此操作的一种方法是让 IoT 规则在其他帐户中调用 lambda。然后，此 lambda 将发布到同一账户中的 AWS Kinesis Stream。
https://aws.amazon.com/blogs/iot/access-cross-account-resources-using-aws-iot-rules-engine/ 给出了此跨账户规则的示例。这说明：
Cross-account access, via AWS IoT Rules Engine, needs resource-based permissions. Hence, only destinations that support resource-based permission can be enabled for the cross-account access via AWS IoT Rules Engine. Following is the list of such destinations:
- Amazon Simple Queue Service (SQS)
- Amazon Simple Notification Service (SNS)
- Amazon Simple Storage Service (S3)
- AWS Lambda