Skip to content

Build1 publisher2 min readPublished

Rekognition draws the boxes for the people AWS's diffusion model inserts into real scenes

AWS's synthetic hazard pipeline reports up to 160 percent higher person-detection mAP50 from images one model edited and a second model labeled. How starved the baseline was decides what that multiplier is worth.

The Engineer · Build desk

What happened

  • AWS published a two-stage pipeline in which Qwen-Image-Edit-2509 on SageMaker AI inserts synthetic people into real industrial photos, and reports up to 160 percent improvement in person-detection mAP50.
  • The bounding boxes for those inserted people are produced by Amazon Rekognition's DetectLabels API, so the training labels arrive without any manual annotation step.
  • The post prices the alternative at an estimated $3 to $5 per image for manual collection and annotation, with annotation teams processing on the order of 2,000 images per day.
  • The scenarios AWS targets, such as a worker in a blind spot or a child near a moving implement, are the rarest in collected datasets and the most dangerous to stage for photography.

Compiled by The EngineerSomething wrong?How this is made

Why it matters

  • decision The 160 percent is reported as an upper bound, so any team budgeting a generation pipeline against a saved annotation bill has to measure its own tail-class baseline first.
  • exposure Label quality on the hardest poses now rests on Rekognition, and an insertion it fails to find leaves the training set short of the example that was generated to fill the gap.
  • constraint Because the camera on the tractor or railcar caps model size, teams cannot answer tail scarcity by scaling the detector; the remedy has to come from the dataset.
  • capability Generating hazards on demand puts classes into reach that cannot be photographed at all, including the child-near-machinery case AWS calls unsafe and unethical to stage.

A structured prompt tells Qwen-Image-Edit-2509 where to put the person: on tracks, on top of equipment, hanging from an edge, or standing in a vehicle's path [12]. The generator does not return coordinates. Amazon Rekognition's DetectLabels API reads the finished image and produces the bounding box for the person that was just inserted [4]. Rekognition never saw the prompt.

Label quality on the hardest examples therefore depends on a second detector finding a person in exactly the poses that make detection hard. Those are the poses the dataset exists to cover [10]. An inserted worker that DetectLabels misses drops out of the training set, or comes back with a loose box, and the pipeline has no annotator in the loop to catch either case [4].

Editing real photographs instead of rendering whole scenes is the strongest choice in the design. The insertion preserves background, lighting and scale [3]. AWS's reason is domain gap, which the post defines as the performance drop when a model trained on one distribution, such as fully synthetic scenes, is applied to real-world images [6]. Existing equipment annotations also stay valid, so the machinery in each scene does not have to be relabeled [5].

At the rates the post quotes, a 100,000-image tail set costs $300,000 to $500,000 and takes 50 days of one annotation team [15]. AWS puts the requirement at thousands to millions of images [8]. A million images comes to $3 million to $5 million and 500 team-days [16]. The generation side is one ml.g5.12xlarge instance with four NVIDIA A10G GPUs and 96 GB of VRAM, 24 GB per GPU [11][17].

The insertion spec in the walkthrough randomizes gender for demographic diversity [12]. Age and body size are a different distribution, and randomizing gender does not produce them. The post opens on a child near a moving implement, though, and says that placing vulnerable populations including children near active machinery for photography is unsafe, unethical and often impractical [10][13].

An improvement of 160 percent is a multiplier of 2.6 on whatever the starting mAP50 was [2][14]. For it to transfer, your baseline has to be as starved in the tail classes as theirs, because a low starting number makes a large percentage cheap to earn. The evaluation set has to hold the hazardous scenarios too, or the gain lands where nothing is measuring it. And the detector has to sit in the same weight class as an edge model. That is the post's own reason every training example counts disproportionately: the camera is mounted on the tractor, forklift or railcar, and that caps the size of the model it can run [9].

What to watch

  • Whether AWS publishes the baseline mAP50 and the evaluation split behind the 160 percent figure. Those would show how starved the starting model was.
  • Whether the pipeline reports agreement between Rekognition's boxes and the placements the prompt actually requested.
  • Whether AWS publishes instance-hours and a cost per generated image to set against the $3 to $5 manual rate.
Loading claim ledger
Loading source directory links
Loading share composer
Loading topic controls
Loading related stories