Skip to content

[AWS] Define the capability matrix and select MVP component mappings #51

Open

Description

@gnanirahulnutakki

Outcome

Choose the first AWS surface with explicit region, identity, network, lifecycle, and cost trade-offs.

Scope

  • Select supported partitions/regions, first compute and managed-service mappings, ownership, import/reference behavior, and exclusions.

Acceptance criteria

  • Every choice maps to public resource and provider contracts.
  • Unsupported features and deletion consequences are listed.
  • IAM, networking, data retention, quota, and monthly cost implications are documented.

Test and evidence

  • Accepted AWS mapping ADR, capability matrix, and cost comparison.

Dependencies

  • Blocked by #38.
  • Blocked by #18.
  • Blocked by #19.
  • Blocked by #11.

References

Activity

  1. added
    priority:p1Required for the first operable alpha
    decision-requiredRequires an explicit architecture or governance decision
    area:awsAWS provider implementation
    on Sep 1, 2026
  2. gnanirahulnutakki commented on Sep 9, 2026

    @gnanirahulnutakki
    MemberAuthor

    Input for the AWS capability matrix: DuploCloud's provider covers 52 aws_* Terraform resources plus RDS, S3, ElastiCache, ECS, ASG, hosts, load balancers, CloudFront, API Gateway, Lambda, Batch, EMR, Glue, MWAA, Kinesis, IoT, and Timestream. The parity epics #102, #104, #105 enumerate them so the MVP selection here can record what is chosen and what is deferred.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:awsAWS provider implementationdecision-requiredRequires an explicit architecture or governance decisionpriority:p1Required for the first operable alpha

    Type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions