AWS Marketplace Reviewer Guide

Obtain the Marketplace product/version, regional AMI, release manifest, launch instructions, supported sizing and supplier contact. Record the actual test account, Region and permitted data privately. The current candidate targets Debian 13 x86_64; confirm the submitted version rather than choosing a similarly named community image.

Confirm a valid purchased entitlement or an explicitly supplied test entitlement and its quantity. Use the review release's EC2 instance-profile instructions with temporary credentials through IMDSv2. The current adapter uses CheckoutLicense, ExtendLicenseConsumption and CheckInLicense. Keep DNS, accurate time and HTTPS access to the specified licensing Region. Use the approved administrative route and exact ports; SSM availability is not assumed.

Launch only the identified VibePackr AMI using the supplied version's settings. Allow its existing first-boot process to complete. Record instance identity and inspect the installed release. Do not rerun install.sh, use image-builder mode, reset identity or capture an initialized customer VM as a reusable product image.

Use the read-only command examples below from the permitted administrative account. Follow the release_manifest, bootstrap and skills paths returned by setup paths. Inspect service results, customer_binding_state and aws_marketplace_license.state separately. The health script's exit code does not by itself certify ACTIVE licensing or customer Work authority.

Read-only command examples

uname -m
cat /etc/os-release
/opt/vibepackr/setup paths
sudo -n systemctl show vibepackr-first-boot.service -p ActiveState -p SubState -p Result
sudo -n systemctl show vibepackr-control-plane.service -p ActiveState -p SubState -p Result
sudo -n /opt/vibepackr/health

Run only on the intended supplied VM through its permitted administrative account. These examples do not install software, grant access or submit a Work. Compare the actual returned fields and service Result; first-boot is a oneshot service, so its state must be interpreted with the result.

With the supplier's agreed test entitlement, verify acquisition and continued renewal. Test single-unit exhaustion using two disposable VMs only when that cost and operation are authorized. Confirm that license loss prevents new Work. Stop the old VM before replacement; the current candidate may hold its unit until lease expiry, up to one hour after its last successful renewal. It does not promise immediate automatic return on shutdown.

Follow the supplied bootstrap and client/runtime instructions. Select a runtime supported by that release; access to an AWS AI service does not establish a VibePackr adapter or runtime binding. Agree one synthetic or approved input and operation, then trace its Work ID, result, validation, human decision and closure. Keep licensing separate from customer identity and Work authorization.

Retain the original Work ID and first error. Review a consistent backup of the required state, configuration and evidence using the supplied version's recovery procedure. Re-evaluate installation identity, customer binding and licensing on a changed host. A snapshot can contain secrets and instance-specific lease data; it is not a portable activation method. Treat restore and upgrade checks as pending until actually tested.

Review the checklist and worksheet, assign owners to unresolved items and record the reviewer conclusion separately from AWS's decision. Account for every disposable instance, volume and snapshot. Terminating an instance does not always delete its EBS volumes. Remove only resources covered by the agreed cleanup scope and retain the approved evidence privately.