Signals AWS Marketplace reach expansion (umbrella)

[fheikens]

Umbrella tracking the reach-expansion options for the Signals AWS Marketplace
listing. Signals currently ships one delivery path: a Helm chart for
Amazon EKS (ContainerProduct@1.0, live). This issue owns the cross-cutting
decisions; the child issues carry per-lever detail and reference back here.

Cross-cutting decisions (owned here — children must not restate)

1. Correctness before reach. Land the accurate EKS/Helm listing first —
   i.e. finish the align-down (strip the ECS / Container-image over-claim from
   the storefront so the listing matches what we actually ship). Reach is a
   deliberate per-lever decision, not a drive-by. See the ECS storefront
   fix context in the pgAgroal/Signals region work.
   Status: CLEARED (2026-07-02) — see decision log.
2. Container-image delivery is the first candidate. Lowest incremental
   effort: the signed multi-arch image is already built and re-hosted to the
   Marketplace ECR. It is the cheapest reach and the natural next lever if we
   pursue any.
3. Each lever is a separate review round. Adding a delivery method or a new
   product type triggers an AWS review; do not bundle.

Levers (child issues)

#	Lever	Rough effort	Reach
a	Container-image delivery option (ECS / Fargate / docker pull)	M	Non-Helm / ECS / Fargate buyers
b	AMI product + EC2 Image Builder component	L	EC2 golden-AMI bakers
c	EKS add-on delivery	M	Native EKS-console discovery

Reference (lever b): https://aws.amazon.com/blogs/awsmarketplace/boost-your-softwares-reach-with-aws-marketplace-and-ec2-image-builder-integration/ (AMI-only; requires a separate AmiProduct@1.0 listing).

Decision log

• 2026-07-01: Levers captured. No lever selected yet; gated on decision (1)
  above. Filed so the reach options are not forgotten.

• 2026-07-02: Align-down gate (decision 1) CLEARED. Verified main: the
  live storefront already claims EKS/Helm only (CompatibleServices: ["EKS"],
  no ECS/Fargate over-claim in LongDescription or Highlights). Reach levers
  unblocked.

• 2026-07-02: All three levers greenlit. Execution order by
  reach-per-effort: Reach: add container-image delivery option (ECS / Fargate / docker pull) #234 container-image delivery (cheapest; reuses the
  already-re-hosted MP-ECR image) -> Reach: EKS add-on delivery for the Signals Helm chart #236 EKS add-on (same chart+image) ->
  Reach: AMI product + EC2 Image Builder component #235 AMI product (effort:L; separate AmiProduct@1.0, not a delivery
  option). Each is its own AWS review round; do not bundle (decision 3). Each
  child starts spec-first under STDD on its own issue/branch.

• 2026-07-02: Levers executed. Reach: add container-image delivery option (ECS / Fargate / docker pull) #234 container-image delivery (PR marketplace: container-image (ECS/Fargate) delivery option template #237, merged) and
  Reach: EKS add-on delivery for the Signals Helm chart #236 EKS add-on delivery (PR marketplace: EKS add-on delivery option template #238, merged) shipped as committed change-set
  templates + specs + preflight guards, each additive and reusing the re-hosted
  MP-ECR artifact. Reach: AMI product + EC2 Image Builder component #235 AMI: groundwork only (PR marketplace: AMI / EC2 Image Builder groundwork (demand-gated) #239) - EC2 Image Builder
  component + spec committed; the live AmiProduct@1.0 standup stays deferred and
  demand-gated per this issue. Each live submission remains a gated operator step
  (one AWS review round; do not bundle).