AWS MediaLive Engineer Needed for Simple One Laptop Test

Please login or register as jobseeker to apply for this job.

TYPE OF WORK

Gig

SALARY

4

HOURS PER WEEK

20

DATE UPDATED

Oct 24, 2026

JOB OVERVIEW

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, Facebook, and Twitch.
- 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.

SKILL REQUIREMENT
AWS
VIEW OTHER JOB POSTS FROM:
SHARE THIS POST
facebook linkedin
  BENCHMARKS  
Loading Time: Base Classes  0.0008
Controller Execution Time ( Jobseekers / Job )  0.0126
Total Execution Time  0.0139
  GET DATA  
No GET data exists
  MEMORY USAGE  
1,498,800 bytes
  POST DATA  
No POST data exists
  URI STRING  
jobseekers/job/AWS-MediaLive-Engineer-Needed-for-Simple-One-Laptop-Test-1754893
  CLASS/METHOD  
jobseekers/job
  DATABASE:  onlinejobs (Jobseekers:$db)   QUERIES: 13 (0.0065 seconds)  (Hide)
0.0004   SELECT *
                                
FROM exrates
                                WHERE rate_name 
= 'USD-PHP' 
0.0004   SELECT *
FROM `employer_jobs`
WHERE `job_id` = 1754893
 LIMIT 1 
0.0004   SELECT *
FROM `employers`
WHERE `employer_id` = 1012570
 LIMIT 1 
0.0008   SELECT COUNT(*) AS `numrows`
FROM `t_thread` `t`
LEFT JOIN `t_thread_misc` `misc` ON `t`.`id` = `misc`.`thread_id`
WHERE `t`.`job_id` = 1754893
AND `misc`.`id` IS NULL 
0.0005   SELECT e.business_name, e.logo, e.website, e.rebill_date, e.date_added member_date, hits, DATEDIFF('2026-10-26',ej.date_added) duration_days, DATEDIFF('2026-10-26',e.rebill_date) duration_rebill, ej.*, e.deactivate FROM employers e, employer_jobs ej WHERE e.employer_id = ej.employer_id AND
                                   ((
e.user_level >= '500' AND ej.date_added <= e.rebill_date)
                                   OR 
e.employer_id = '' OR (ej.date_approved <> '2000-01-01' and DATEDIFF('2026-10-26',ej.date_added) <= 14 ))
                                   AND 
e.deactivate != 1 AND ej.deleted = 0 AND job_id = '1754893' 
0.0003   SELECT *
FROM `employer_jobs_skills` `ejs`
LEFT JOIN `skills_categories` `sc` ON `ejs`.`skill_id` = `sc`.`id`
WHERE `job_id` = 1754893 
0.0007   UPDATE employer_jobs SET hit_counts = '***Oct-23-2026=8***Oct-24-2026=80***Oct-25-2026=51***Oct-26-2026=3' WHERE job_id= '1754893'  
0.0006   UPDATE employer_jobs SET monthly_hits = '***Oct-2026=142' WHERE job_id= '1754893'  
0.0008   SELECT date_sent FROM jobseeker_sent_emails WHERE jobseeker_id = '' AND job_id = '1754893' AND status LIKE 'sent%' ORDER BY id DESC  
0.0004   SELECT *
FROM `employer_jobs_skills` `ejs`
LEFT JOIN `skills_categories` `sc` ON `ejs`.`skill_id` = `sc`.`id`
WHERE `job_id` = 1754893 
0.0004   SELECT COUNT(*) AS `numrows`
FROM `employer_jobs`
WHERE `employer_id` = '1012570'
AND `date_added` >= '2022-06-08' 
0.0004   select * from teasers 
0.0004   SELECT * FROM skill_categories WHERE skill_cat_id='' 
  HTTP HEADERS  (Show)
  SESSION DATA  (Show)
  CONFIG VARIABLES  (Show)