Our first deliverable in AWS projects is usually the invisible layer: account and organisation structure, the VPC network plan, the IAM role model, budget alarms. Build that foundation right and every workload that follows lands in the same order; build it wrong and every project invents its own exception.
Workload sizing starts from on-premises measurements — right type and right size rather than a one-to-one copy. Roles instead of access keys, a locked root account and a tag on every resource: that is the standard.