Compute choice
Match the deployment model to the vendor and team skills.
Project scenario
Add capacity without adding unnecessary complexity.
A customer portal needs a supported deployment path, better monitoring and a cost baseline as traffic grows.
The workload question
A portal is outgrowing its first server
The design should solve the observed constraint while remaining manageable for a small team.
EXAMPLE ENGAGEMENT
Related delivery service Example engagement scenario, not a completed customer project. Components and scope are confirmed against the actual workload.
01
Public entry
Amazon CloudFront where appropriate
02
Application
Amazon EC2 or ECS service
03
Private data
Amazon RDS + scoped access
04
Operating controls
CloudWatch + backup + releases
Read alongside the decisions and validation steps below.
Design decisions
Decisions to resolve.
Architecture is a set of trade-offs. These are the questions to resolve before implementation.
Database care
Check connections, query behaviour and restore requirements.
Scaling
Measure a representative peak before setting scaling policies.
Validation before handover
Test the assumptions.
Check the business workflow as well as the individual AWS resources before handing the environment to its operator.
- Validate load and application health.
- Demonstrate rollback after a failed release.
- Compare the cost estimate with the agreed usage assumptions.
From scenario to scope
A workload-specific migration or service scope, cost assumptions, operating responsibilities and agreed handover checks.
Free migration assessmentStart with the workload.
Start with the workload.
We’ll help plan the move.
Share what you run today and what needs to change. We will agree the initial assessment scope; implementation and AWS usage are quoted separately.