Hybrid Network and Identity
The data centre and the cloud working as one: a private circuit with a VPN behind it, names that resolve both ways, and one sign-in.
While the migration runs, and often long after it, the data centre and the cloud must behave as one network: servers on either side reach each other, find each other by name and recognise the same people. A private circuit carries the traffic into one hub, with a VPN behind it if the circuit fails; DNS forwards names both ways; and people sign in once, with the accounts they already have.
Point at a component to light its links; select it for what it does here and the practice that makes it right on AWS.
When to use it
- Any migration that runs in waves: until the last one, moved servers still talk to servers that have not moved
- Estates where people and servers sign in with Active Directory and find each other by DNS name
- A carve-out, where the new estate keeps a temporary, filtered link and trust to the parent until the transition ends
Where FleziLift fits
The AS-IS assessment finds the domain controllers and every server that depends on the domain, each fact graded by evidence (L0–L3), and the 7R rule tree decides each domain controller: rehost as VMs, replatform to the managed directory, or retain. The Wave Plan puts the link, name resolution and identity in Wave 0 · Foundation, before a pilot of at most five non-production servers, and keeps move groups whole; if a foundation server is on Hold, the project's Go / No-Go is No-Go. The playbook lists each task with the cloud's own tool, which does the work.
Cloud TransformationThe same pattern, the way each provider builds it
Each cloud's own framework and guidance.
