👤 [User Story]: AWS version of Pulumi

[edwardchalstrey1]

Role

Developer

Desired Feature

Pulumi deployment for AWS cloud

Benefit

IAC can be used at CSH where AWS is the preferred provider

Acceptance Criteria

GIVEN An AWS subscription, this repo (and a backup of the Seshat database) WHEN Running pulumi up THEN The Seshat site can be deployed to AWS

Dependencies

• [ ] #13
• [ ] #46

Technical Notes

No response

Definition of Done

• [ ] The feature fulfills all acceptance criteria.
• [ ] The code is reviewed and meets team coding standards.
• [ ] All unit, integration, and end-to-end tests are passed.
• [ ] The feature meets accessibility standards set for the project.
• [ ] The code passes the CI/CD pipeline quality controls (style and linting).
• [ ] The feature is merged into the main branch.
• [ ] The feature is deployed and functional in the QA environment.
• [ ] The feature was demonstrated to the team and accepted by the product owner.

[edwardchalstrey1]

@kallewesterling I've rejigged some issues here and created an IAC label:

1. 46 which I intend to work on soon

2. This one #47 which could be worked on in tandem or afterwards - I'm also happy to work on this but might need your help on how to get a sufficiently credited test AWS subscription

3. 48 which I've put on the backlog for now

[edwardchalstrey1]

@kallewesterling if helpful, the AWS setup that Majid used is documented here: https://seshat-global-history-databank.github.io/seshat/admin/setup/cloud/CSH_manual.html

[edwardchalstrey1]

@kallewesterling Do you still intend to work on this? I'd be happy to move it to Backlog