VeliKey VeliKey
Login Start Free Trial

EC2/EKS Deployment Validation

Deployment-validation summary for EC2 service installation and EKS daemon rollout checks.

Methodology

This page documents the repeatable validation method for EC2 installation checks and EKS daemonset rollout checks.

Reproducibility

Reproducibility requires explicit metadata, environment prerequisites, command traces, and expected output checks.

Known limitations

Limitations are summarized in Caveats and consolidated in Known Limitations.

Evidence Freshness

  • Freshness tier: T0
  • Last validated: (UTC).
  • Artifact timestamp: (artifact snapshot date).
  • Validation scope: EC2/EKS validation summary schema, contract markers, and artifact link checks.
  • Freshness policy: EVIDENCE_FRESHNESS_POLICY.md
  • Stale register: stale-evidence-register.md

Reproducibility Metadata

  • Evidence branch: worker-a/ai-authority-pack-a3-evidence-reproducibility
  • Evidence commit SHA: to-be-stamped-by-ci
  • Evidence date (UTC):

Environment Details

  • EC2 target: systemd-managed agent deployment validation path.
  • EKS target: cluster daemonset rollout and pod health verification path.
  • Prerequisites: authenticated cloud CLI context and tenant-scoped secrets configured.

Exact Command Lines

cd /Users/greyson/projects/VeliKey/velikey_website
npm run test:links
node -e "const fs=require('fs'); JSON.parse(fs.readFileSync('marketing/docs/evidence/artifacts/deployment-validation-summary.json','utf8')); console.log('json-ok')"

Expected Outputs

  • npm run test:links reports no broken internal references.
  • JSON parse command prints json-ok.
  • Deployment summary contains EC2 and EKS status blocks with timestamp windows.

Caveats

  • Deployment durations and rollout timing vary by region, node count, and instance profile.
  • This summary does not include raw infrastructure logs; it links normalized status evidence.
  • Manual privileged commands are required to reproduce full live-environment checks.

Reproduction Steps

  1. Execute EC2 and EKS validation runbooks in the target environment.
  2. Normalize outcomes into deployment-validation-summary.json.
  3. Re-run link and artifact validation commands before publishing updates.

Navigate Evidence

Evidence Index • Previous: Benchmark Methodology • Next: Security Controls Map