Skip to content

Latest commit

 

History

History
53 lines (37 loc) · 2.19 KB

Design-Considerations.md

File metadata and controls

53 lines (37 loc) · 2.19 KB
Raw

Design Considerations

Below are the key design considerations for TREEHOOSE

Maintenance

  • All the core infrastructure is deployed using IaC (Infrastructure as Code).
  • The solution is based on Serverless Architecture for ease of operability and scalability.

Audit

  • AWS CloudTrail is enabled in all AWS accounts and the logs centralised for Auditing.
  • AWS Config is enabled in all AWS accounts and the config records centralised for Auditing.
  • Amazon CloudWatch is used for log aggregation and metrics for each TRE project/AWS account.

Security

  • Use AWS KMS for encryption at-rest.
  • Encryption in-transit is enabled for all AWS services where applicable and also enabled for all API calls.
  • For all AWS IAM policies the principle of least privilege has been followed.
  • AWS Accounts provide well-defined billing and security boundaries. Hence each research project should be hosted in a separate AWS account.

Considerations for End Users

These are some additional decisions that the end user of TREEHOOSE should make based on their functional and non-functional requirements.