Integrate AMI's into EKS

jbrown-xentity commented 2 years ago

User Story

In order to keep our compliance up to date, the Data.gov SSB team wants the latest secure AMI tested and integrated into SSB.

[ACs should be clearly demoable/verifiable whenever possible. Try specifying them using BDD.]

[ ] GIVEN a new AMI is released \ AND the AMI is copied into the correct space WHEN the EKS brokerpak is applied \ THEN the secure AMI's are in use \ AND our workload is stable

Related to #3770. External dependency

[Any security concerns that might be implicated in the change. "None" is OK, just be explicit here!]

[ ] Document process for copying AMI from GSA ISE Team to GSA Data.gov Team to EKS-accessible location
- [ ] Document in EKS Brokerpak
- [ ] Update documentation references at https://github.com/GSA/data.gov/wiki/Operation-and-Maintenance-Responsibilities#apply-new-amis
[ ] Perform documented process
[ ] Spin up EKS Cluster with the agreed-upon AMI (TBD from meeting)
[ ] Deploy Solr
[ ] Reindex and Start Harvesting on catalog cloud.gov (dev/staging/prod TBD)
[ ] Ensure workload is stable for at least one week

nickumia-reisys commented 2 years ago

See instructions here on how to copy/share AMIs.

hkdctol commented 2 years ago

Waiting for test to complete.