Skip to content
JPZERPA

02 · AWS · Disaster recovery · Hybrid identity

Building hybrid cloud resilience on AWS

Extending identity, ERP access, backup and business services into AWS so the company no longer depends on a single physical site.

Client
Multi-brand retail group, South Florida
My role
Cloud Solutions Architect & System Administrator (advisory engagement through Inteligentic Solutions)

Context

With the core ERP and directory services running on-premises, a site-level outage would have left stores and the office without authentication or ERP access. Several business services—telephony, accounting, asset management, digital signage—also lived on separate servers or providers.

Business challenge

  • Identity and ERP access depended on one location.
  • Backups were stored on-site only.
  • Business services were spread across individual servers and different cloud providers.

Architectural approach

  1. 01

    Redundant identity in the cloud

    Deployed a redundant Windows domain controller in AWS and transitioned the domain controller architecture to a cloud-based design.

  2. 02

    Secure connectivity

    Configured VPN connectivity between AWS and the company’s on-premises environment.

  3. 03

    ERP recovery access

    Deployed an AWS-hosted Remote Desktop server for ERP disaster-recovery access, and a cloud-based ERP application server.

  4. 04

    Automated off-site backup

    Automated off-site backup of NAS data to Amazon S3 and integrated Windows Server storage access with AWS Storage Gateway.

  5. 05

    Consolidate business services

    Moved the 3CX phone system from Google Cloud to AWS for operational and cost optimization, and hosted QuickBooks Enterprise, Snipe-IT asset management, network management, a digital signage server and a product-image media server in the cloud.

Results

  • Authentication no longer depends on a single physical site.
  • The ERP has a cloud-based path for disaster-recovery access.
  • Business data is copied off-site automatically.
  • Telephony and several business applications run on one cloud provider instead of being scattered.

Lessons learned

In a hybrid environment, identity is the first thing to make redundant: without it, nothing else can be reached.
Moving a service to the cloud is an opportunity to consolidate providers, not just to change where a server runs.

Let's build what comes next.

Whether you're exploring technology leadership, enterprise architecture or a complex modernization initiative, I'd welcome a conversation.

Let's Connect