Cloud Solutions

Plan and set up the cloud environment that fits your systems, with secure office connectivity.

Enquire about this service
Server racks in a data centre

Choose where each system belongs.

Cloud planning starts with your applications and the people who use them. Some systems may remain on dedicated infrastructure, some may use public cloud services, and others may need connections between the two environments.

EDISON covers private, public and hybrid cloud set-ups, including secure connections to office networks. The aim of an initial review is to identify the appropriate environment for each workload and the dependencies that need to be addressed before a change.

  • Private cloud on HPE servers and VMware
  • Public cloud on AWS, Microsoft Azure, Alibaba Cloud and Google Cloud
  • Hybrid set-ups that link on-premises systems to public cloud
  • Secure connections between cloud services and office networks
  • TGT Private Cloud
  • AWS
  • Microsoft Azure
  • Alibaba Cloud
  • Google Cloud

Public, private and hybrid cloud.

These models differ in where resources run and how they are managed. The choice can vary between applications within the same business.

Cloud deployment models and what to review
ModelUse and considerations
Private cloudDedicated infrastructure for your organisation, with EDISON’s scope covering HPE servers and VMware. Review equipment capacity, storage, hosting location and who will operate the environment. This model also requires a plan for hardware upkeep and backup.
Public cloudResources provided through platforms such as AWS, Microsoft Azure, Alibaba Cloud and Google Cloud. Review the services each application needs, access controls and expected usage. Compute, storage and data transfer can affect the ongoing cost, so budget assumptions matter alongside the initial set-up.
Hybrid cloudAn arrangement connecting public cloud with on-premises systems or private cloud. Plan the applications and data that need to communicate across environments, the office connection and the responsibility for managing each part. Connectivity becomes part of the application design.

Plan the move and ongoing operation.

Before moving a workload, identify its users, dependencies, licences, data volume and acceptable interruption. Agree the checks for application access and data after the change, together with the backup and recovery arrangement.

Cloud hosting and ongoing management are separate decisions. Establish who controls the accounts, reviews usage and maintains the systems. For an initial discussion, a workload list and a description of your current environment are more useful than a preferred platform alone.

Considering a move to cloud?

Share your application list, current environment, access needs and ongoing budget requirements.

Discuss your project