Architecture Decision Records (ADR)
Documents here are intended to record and describe particular architectural decisions.
An ADR records a a particular decision and contains the key information to understand how the mechanism it describes work.
An ADR is not an RFC. An RFC is speculative and provides a place to discuss multiple options with pros and cons, which may or may not be implemented. An ADR relates only to the current implementation and will be replaced as new decisions are made.
Table of contents
A description of the purpose of ADRs and how they differ from RFCs.
Guidelines for implementing faceting in APIs, including expectations for performance and usability.
Best practices for using GitHub Actions with AWS, including authentication and permissions.
An overview of GitHub groups and permissions, including how to manage access to repositories.
Guidelines for securing GitHub repositories, including best practices for managing secrets and access.
Best practices for logging in applications, including log levels and structured logging.
Guidelines for managing secrets in applications, including best practices for storing and accessing sensitive information.
A process for updating base AMIs in Wellcome Collection AWS accounts.
Last updated