Gig
4
20
Oct 24, 2026
The simplest way to prove the remaining limitation is to run a controlled test using one camera-connected laptop for all three source-side functions.
Simplest test
On one laptop:
1. Connect or activate the laptop’s camera.
2. Run OBS and push the captured stream to an AWS MediaLive RTMP input.
3. From that same laptop, use the AWS CLI to submit:
- Three MediaLive destinations for YouTube,
- One BatchUpdateSchedule request containing an image URI or motion-graphics URL.
4. Start the MediaLive channel.
5. Confirm that:
- MediaLive receives the camera stream.
- The overlay appears.
- MediaLive sends outputs to the three destinations.
The key is using the AWS CLI on the same laptop because the commands, request files, timestamps, and CloudTrail events are easier to preserve than browser activity.
Minimum evidence needed
You need only four coordinated evidence categories:
1. Continuous screen recording
Record the entire operation showing:
- The laptop’s identity and clock.
- The connected camera.
- OBS sending the stream.
- The AWS CLI submitting the destination configuration.
- The AWS CLI submitting the overlay schedule action.
- The resulting overlay and social-platform outputs.
2. OBS log
The OBS log should establish:
- The camera source.
- The MediaLive RTMP endpoint.
- The stream start time.
- The originating computer.
3. CloudTrail records
Preserve the events showing:
- The destination configuration.
- The BatchUpdateSchedule request.
- The overlay URI or URL.
- The IAM principal.
- The source IP address.
- The user agent.
- The channel ID.
- The event timestamps.
4. MediaLive configuration and logs
Export:
- describe-input
- describe-channel
- the channel schedule
- MediaLive encoder logs
- MediaLive as-run logs
These records connect the stream, destinations, and overlay action to the same MediaLive channel.
Strongest simple correlation
The proof chain would be:
1) One identified laptop
2) OBS sends captured content
+ AWS CLI submits three destinations
+ AWS CLI submits overlay URL
3) Same MediaLive channel processes all three inputs
Use the same:
- laptop;
- IAM identity;
- public IP address;
- MediaLive channel ID;
- test name; and
- narrow timestamp window.
A dedicated /32 input-security rule for the laptop’s public IP adds corroboration, although it should not be the only proof.
What this proves
This controlled test would prove that:
> One qualifying source user device can supply the captured digital content, supplemental-content identifier, and plural target identifiers to one MediaLive configuration.
That closes the missing technical limitation for the tested configuration.
Important limitation
The test proves technical operation and capability in the tested configuration. It does not, by itself, prove that Amazon or a particular AWS customer historically operated that configuration. Historical use would require customer logs, AWS records, testimony, source code, or discovery.
Confidence: High that this is the simplest technically reliable method. The best minimal package is a continuous screen recording, OBS log, CloudTrail events, and MediaLive configuration and logs.