PlayCloudLabs
Sign in
  1. Learn AWS
  2. Architecture
  3. Media processing pipeline

Architecture pattern

AWS Media processing pipeline architecture

when uploads need heavy work that nobody is waiting on

Upload and processing are separate problems. The upload lands in S3 and returns immediately; the event queues the work; workers scale on queue depth and take minutes if they need to. A failed job retries without blocking the next one, and the finished asset is served from the edge.

What it runs through

In the order a request or a record moves through it. Each one links to the page that explains it.

  1. S3Amazon S3
  2. EventBridgeAmazon EventBridge
  3. SQSAmazon SQS
  4. ECS on FargateAmazon ECS on AWS Fargate
  5. S3Amazon S3
  6. CloudFrontAmazon CloudFront

Signals in a brief that point here

Phrases that, when you meet them in a scenario, mean this shape rather than another. They are the tell, and they are what an exam question is built around.

  • “transcode”
  • “thumbnails”
  • “takes several minutes”
  • “does not need to be immediate”
  • “one failure must not block others”

What it costs you

The user needs somewhere to see progress, because "done" now arrives long after "uploaded".

Every shape has one. A design decision with no stated downside is usually a decision nobody has finished making.

Learn the services in it

Shapes it is easily confused with

These run through some of the same services, which is exactly why a brief that fits one can look like it fits another.

Now build it from a brief

Reading a shape and producing one from a scenario that never names a service are different skills, and the exam asks for the second. The scenarios give you the brief; you draw the architecture and it is scored against what the brief requires.

Still there?

You have been away for a while. We have saved what you were working on in this browser. In 60 seconds you will be signed out to keep your account safe.