One or two sentences explaining what the sample accomplishes and when a user should choose it.
Describe the Deadline Cloud capability or OpenJD pattern, the important delivery or lifecycle choice, and the expected result. Omit or combine this section if the introduction already makes that clear.
Document required AWS resources and permissions, local tools and versions, and any application, plugin, or license access users must provide.
Explain the components and data flow needed to operate the sample safely. Link detailed architecture to canonical documentation or a focused design document rather than repeating it here.
Provide deterministic setup instructions and identify configuration values users must replace.
Show the shortest working command first, followed by meaningful variants when useful.
# commandDescribe important inputs, defaults, output locations, and artifacts or resources the sample creates. A compact table is often useful, but use whichever format fits the sample.
Call out permission boundaries, secret handling, network exposure, billable resources, licensing, and cleanup steps that apply. Do not embed credentials or private data.
List likely, diagnosable failures and where users can find relevant worker, job, or service logs.
Link canonical AWS Deadline Cloud documentation and closely related samples when those links help the reader choose a next step.