- Newest
- Most votes
- Most comments
-
using IoT Core
You can use IoT Core rules to work with Kinesis. In this case, you need a device certificate.
https://docs.aws.amazon.com/iot/latest/developerguide/kinesis-rule-action.html -
use device certificate to get STS
https://docs.aws.amazon.com/iot/latest/developerguide/authorizing-direct-aws.html This also uses a device certificate, but you can get an STS token to access Kinesis directly. -
use Lambda function URLs
https://docs.aws.amazon.com/lambda/latest/dg/urls-auth.html
Lambda function URLs can be made without authentication, so it is possible to call Kinesis from Lambda. We do not know if it can withstand high loads or how much it will cost. -
Using AWS SigV4 Proxy
https://github.com/awslabs/aws-sigv4-proxy No authentication information is required for the application, but authentication information is required for the Proxy.
Sorry, I couldn't come up with a good idea. 😥😥.
Using AWS Lambda to process Kinesis Data Streams is a way to do this. You can specify the permissions in the IAM Role assigned to the Lambda function. See: https://docs.aws.amazon.com/lambda/latest/dg/with-kinesis.html
Relevant content
- Accepted Answerasked 3 years ago
- asked a year ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated a year ago