The Kinesis stream names weren't having the LAUNCH_ID appended to them. Also, the region in which the stream is created in could not be set via the ROS_AWS_REGION environment variable, like how it could be done for CloudWatchLogs and CloudWatchMetrics, and had to be set in kvs_config.yaml.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
I have added more changes. Now Rekognition works in simulation ("I see ..." messages will show up in the logs) if both the robot and simulation applications are launched in RoboMaker.
Description of changes:
(Depends on https://github.com/aws-robotics/kinesisvideo-ros2/pull/20)
The Kinesis stream names weren't having the
LAUNCH_ID
appended to them. Also, the region in which the stream is created in could not be set via theROS_AWS_REGION
environment variable, like how it could be done for CloudWatchLogs and CloudWatchMetrics, and had to be set inkvs_config.yaml
.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.