feat(aws): add AWS Marketplace target to s3-cloud

[pcfreak30]

Summary

Adds a complete AWS Marketplace target for s3-cloud, mirroring the existing DigitalOcean and Vultr targets.

What's included

• deploy/aws/ — Packer AMI template (HVM/EBS-backed, x86-64, us-east-1), CloudFormation deployment template, Makefile, submit helper, README, AGENTS.md.
• deploy/aws/scripts/ — per-instance cloud-init provisioning, AMI cleanup/validation, EC2/AMI pruning helpers.
• deploy/aws/marketplace/ — AMMP submission assets: usage instructions, security group recommendations, submission checklist.
• CI wiring — packer-ci-aws.yml, packer-release-aws.yml, and dispatch entries in packer-ci.yml / packer-release.yml.
• Local validation — new scripts/validate-aws.sh that checks Packer formatting, CloudFormation JSON, shell/Python syntax, and marketplace docs without needing AWS credentials.
• Bug fix — corrects the auto-update disable instructions in packer/scripts/install-s3-server.sh from a docker exec ... rm command to the documented touch /state/autoupdate.disabled flag-file API.
• Docs — updates docs/platform-support.md with AWS row/feature parity.

Verification

Ran ./scripts/validate-aws.sh locally:

• CloudFormation JSON parses ✅
• Shell scripts pass bash -n ✅
• Python files compile ✅
• Makefile syntax check ✅
• Marketplace docs present and non-empty ✅

Out of scope

• AWS Marketplace seller onboarding and AMMP submission.
• Paid/BYOL pricing decision.
• End-to-end AWS build cost approval.

[kody-ai]

Code Review Completed! 🔥

The code review was successfully completed based on your current configurations.

Kody Guide: Usage and Configuration

Interacting with Kody

• Request a Review: Ask Kody to review your PR manually by adding a comment with the @kody start-review command at the root of your PR.

• Validate Business Logic: Ask Kody to validate your code against business rules by adding a comment with the @kody -v business-logic command.

• Provide Feedback: Help Kody learn and improve by reacting to its comments with a 👍 for helpful suggestions or a 👎 if improvements are needed.

Current Kody Configuration

Review Options

The following review options are enabled or disabled:

Options	Enabled
Bug	✅
Performance	✅
Security	✅
Business Logic	✅

Access your configuration settings here.

​

[kody-ai]

The github.event.inputs.rescue-password context is empty for workflow_call triggers, silently dropping the operator-supplied rescue password and making the cleanup-on-failure guard always true, which deregisters a failed AMI even when the operator intended to keep it for debugging. Replace github.event.inputs.rescue-password with inputs.rescue-password on both lines.

          RESCUE_PASSWORD: ${{ inputs.rescue-password }}
...
        if: failure() && inputs.rescue-password == ''

Prompt for LLM

File .github/workflows/packer-ci-aws.yml:

Line 156:

The `github.event.inputs.rescue-password` context is empty for `workflow_call` triggers, silently dropping the operator-supplied rescue password and making the `cleanup-on-failure` guard always true, which deregisters a failed AMI even when the operator intended to keep it for debugging. Replace `github.event.inputs.rescue-password` with `inputs.rescue-password` on both lines.

Suggested Code:

          RESCUE_PASSWORD: ${{ inputs.rescue-password }}
...
        if: failure() && inputs.rescue-password == ''

_{Talk to Kody by mentioning @kody}

_{Was this suggestion helpful? React with 👍 or 👎 to help Kody learn from this interaction.}

​

​

[kody-ai]

The github.event.inputs.rescue-password context is not populated under workflow_call triggers, leaving RESCUE_PASSWORD empty and causing the cleanup-on-failure guard to always deregister the instance even when a rescue password was supplied. Use inputs.rescue-password instead of github.event.inputs.rescue-password on both lines, matching the job's existing use of inputs.cleanup-mode and inputs.pr-number.

          RESCUE_PASSWORD: ${{ inputs.rescue-password }}
...
        if: failure() && inputs.rescue-password == ''

Prompt for LLM

File .github/workflows/packer-ci-aws.yml:

Line 156:

The `github.event.inputs.rescue-password` context is not populated under `workflow_call` triggers, leaving `RESCUE_PASSWORD` empty and causing the `cleanup-on-failure` guard to always deregister the instance even when a rescue password was supplied. Use `inputs.rescue-password` instead of `github.event.inputs.rescue-password` on both lines, matching the job's existing use of `inputs.cleanup-mode` and `inputs.pr-number`.

Suggested Code:

          RESCUE_PASSWORD: ${{ inputs.rescue-password }}
...
        if: failure() && inputs.rescue-password == ''

_{Talk to Kody by mentioning @kody}

_{Was this suggestion helpful? React with 👍 or 👎 to help Kody learn from this interaction.}

​

​