AWS Elasticsearch Service failover and fault tolerance

julialeague commented 3 years ago

Elasticsearch Service isn't fault tolerant right now - if the cluster has availability issues, we don't currently support failover. We should determine the failover strategy for AWS Elasticsearch Service and then implement the configuration for the same.

Pre-Conditions

Acceptance Criteria

Determine failover strategy for AWS Elasticsearch Service
Implement the failover strategy or log another issue for the implementation

Mobile Design/Considerations

Security Considerations

[ ] Does this work make you nervous about privacy or security?
[ ] Does this work make major changes to the system?
[ ] Does this work implement new authentication or security controls?
[ ] Does this work create new methods of authentication, modify existing security controls, or explicitly implement any security or privacy features?

Notes

Some references that I found while working on #247 : https://aws.amazon.com/premiumsupport/knowledge-center/elasticsearch-fault-tolerance/ https://aws.amazon.com/blogs/database/increase-availability-for-amazon-elasticsearch-service-by-deploying-in-three-availability-zones-2/

Tasks

Definition of Done (Updated 10-26-20)

Product Owner

[ ] Acceptance criteria have been met and validated on the Flexion Prod env

UX

[ ] Business test scenarios to meet all acceptance criteria have been written
[ ] Usability has been validated
[ ] Wiki has been updated (if applicable)
[ ] Story has been tested on a mobile device (for external users only)

Engineering

[ ] Automated test scripts have been written
[ ] Field level and page level validation errors (front-end and server-side) integrated and functioning
[ ] Paired w/Mark on data migration work (if applicable)
[ ] Verify that language for docket record for internal users and external users is identical
[ ] New screens have been added to pa11y scripts
[ ] All new functionality verified to work with keyboard and macOS voiceover https://www.apple.com/voiceover/info/guide/_1124.html
[ ] READMEs, other appropriate docs, JSDocs and swagger/APIs fully updated
[ ] UI should be touch optimized and responsive for external only (functions on supported mobile devices and optimized for screen sizes as required)
[ ] Module dependencies are up-to-date and are at the latest resolvable version (npm update)
[ ] Errors in Sonarcloud are fixed https://sonarcloud.io/organizations/flexion-github/projects
[ ] Lambdas include CloudWatch logging of users, inputs and outputs
[ ] Interactors should validate entities before calling persistence methods
[ ] Code refactored for clarity and to remove any known technical debt
[ ] Rebuild entity documentation
[ ] Acceptance criteria for the story has been met
[ ] Deployed to the dev environment
[ ] Deployed to the prod environment

adunkman commented 3 years ago

Duplicate of #638, @julialeague let me know if I’m incorrect!