AWS Well-Architected design considerations
This Guidance uses the best practices from the
AWS Well-Architected Framework
This section describes how the design principles and best practices of the Well-Architected Framework benefit this Guidance.
Operational excellence
This section describes how we architected this Guidance using the principles and best practices of the operational excellence pillar.
-
This Guidance pushes metrics to CloudWatch at various stages to provide visibility into archive transfer progress.
Security
This section describes how we architected this Guidance using the principles and best practices of the security pillar.
-
All interservice communications use applicable AWS Identity and Access Management
(IAM) roles. -
All roles used by the Guidance follow least privilege access. They only contain the minimum permissions required to accomplish the transfer.
-
All data storage, including the S3 buckets, encrypts the data at rest.
Reliability
This section describes how we architected this Guidance using the principles and best practices of the reliability pillar.
-
The Guidance uses a serverless architecture to achieve high availability and recovery from failure.
-
The Guidance protects against state machine definition errors through a suite of automated tests.
-
Data processing uses Lambda functions. Data is stored in DynamoDB and Amazon S3, which persist in multiple Availability Zones by default.
Performance efficiency
This section describes how we architected this Guidance using the principles and best practices of the performance efficiency pillar.
-
The Guidance uses a serverless architecture with the ability to scale horizontally as needed.
-
The Guidance is tested and deployed daily to achieve consistency as AWS services change.
Cost optimization
This section describes how we architected this Guidance using the principles and best practices of the cost optimization pillar.
-
The Guidance uses a serverless architecture that only charges customers for what they use.
-
DynamoDB global secondary indexes are selected to reduce the pricing for queries.
Sustainability
This section describes how we architected this Guidance using the principles and best practices of the sustainability pillar.
-
The Guidance uses managed serverless services to minimize the environmental impact of the backend services compared to continually operating on-premises services.
