Home labs & practical projects
Plan an acquisition into a multi-account estate
A project to do with your own tools, with guidance on what to create and capture.
What you could create
A group acquires a company with its own AWS accounts, overlapping IP ranges and different audit requirements. The acquired business must keep trading during integration.
| Evidence | What to capture |
|---|---|
| Target operating model and account diagram | Show the inputs, scope and decisions behind this record. The plan preserves ownership of existing workloads throughout migration. |
| Migration decision log and rollback matrix | Include the evidence supporting your conclusion. Network overlap has an explicit treatment. |
What you'll need
Document, spreadsheet or diagram tool
Invent two account inventories, one overlapping network range and three workloads with different criticality. Record the group’s identity and logging requirements.
Project record
Keep the working files for target operating model and account diagram and record assumptions as you go.
Current reference material
Use the linked provider resources to verify the features, access terms and version relevant to your project.
Access & cost
No paid platform is needed for the written version. Use a document, spreadsheet or diagram tool you already have.
The organisation and records are fictional. Write down assumptions; do not substitute confidential employer information.
Suggested milestones
- 1
Plan and investigate
Design organisational boundaries, account ownership and central audit collection.
- 2
Develop your approach
Compare network integration options without assuming address ranges can be changed immediately.
- 3
Verify and explain
Sequence migration waves with rollback criteria and a temporary exception process.
Useful resources
Use these resources to deepen your understanding and check key details.
Review the current provider requirements and relevant subject areas.
Check relevance, platform versions and current access terms.
Find relevant providers and check features, access requirements and costs.
A useful starting point
Invent two account inventories, one overlapping network range and three workloads with different criticality. Record the group’s identity and logging requirements.
What a good result looks like
- The plan preserves ownership of existing workloads throughout migration.
- Network overlap has an explicit treatment.
- Security exceptions have owners, expiry dates and review evidence.
Finish the project
Keep the decision record and note unanswered questions. A written design is not evidence that a technical control has been tested.
Independent home-project guidance, not an official vendor lab or a claim of complete exam coverage. Use your own tools and label the work accurately.