Skip to content

[Draft] Bootstrap initial AWS service baseline #57

@BASIC-BIT

Description

@BASIC-BIT

Problem

VRDex has a locked supporting-infrastructure direction (AWS), but there is not yet a concrete first-pass setup for the initial AWS-backed services the product expects to rely on.

Scope

  • define and bootstrap the narrowest initial AWS service baseline needed by the locked stack direction
  • focus the first pass on the most likely early needs:
    • transactional/verification email
    • asset storage direction
  • document the minimum local/dev and hosted environment expectations for those services
  • keep the setup compatible with later self-hosting and infrastructure-as-code direction

Non-goals

  • full production AWS architecture
  • complete IaC rollout for every environment
  • exhaustive security/compliance hardening
  • every future AWS service VRDex might eventually use
  • billing/webhook implementation
  • full self-hosting automation

Acceptance criteria

  • the repo has a clear first-pass AWS service baseline defined and bootstrapped for early product needs
  • the initial direction for email delivery is explicit
  • the initial direction for asset storage is explicit
  • the required environment/config expectations are documented
  • the setup stays narrow and does not overbuild AWS infrastructure before the product needs it

Likely docs to update

  • README.md
  • docs/planning/engineering-strategy.md
  • docs/README.md
  • #42 self-hosting and infrastructure-as-code direction if that issue remains separate
  • any AWS/bootstrap doc created during implementation

Soft dependencies

  • #54 Bootstrap initial Convex backend, if we want service expectations grounded in the backend runtime early
  • should stay aligned with #42 and the locked stack direction in docs/planning/engineering-strategy.md

Soft dependents

  • #18 Implement multi-provider account login for v0.5 (Discord, Google, email/password), especially email verification needs
  • #22 Add profile presentation assets and owner-authored content sections
  • hosted deployment environment setup
  • later infrastructure-as-code work

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions