This document outlines the key differences between utilizing CloudM Migrate as a hosted deployment (SaaS) or a self-hosted deployment. A self-hosted deployment refers to resources that you own and manage, whether they are on-premises or within a cloud tenant like Google Cloud Platform (GCP) or Microsoft Azure.
Security Considerations
CloudM prioritizes security. While this document covers some security aspects of CloudM Migrate deployments, it's not exhaustive. If you have specific security questions or require a security review, please contact your sales representative for assistance.
CloudM Migrate Hosted
CloudM Migrate Hosted offers a fully managed infrastructure where CloudM provides and handles all the necessary infrastructure for your migration projects.
Pros of the Hosted Deployment
- Dedicated Resources: Every customer instance is deployed on its own dedicated migration infrastructure, ensuring isolation and performance.
- Automatic Scalability: The CloudM Migrate deployment automatically provisions additional resources as needed, adapting to your migration demands.
- Enhanced Security: Migration servers are protected by advanced security measures that align with industry-leading cloud security best practices recommended by providers like Google and Microsoft. This ensures the servers remain inaccessible from the open internet.
- Automated Deletion: Servers are automatically deleted after 30 days of project inactivity, significantly reducing potential security risks and ensuring data hygiene.
- Comprehensive Auditing: All CloudM Migrate Hosted logins and actions are meticulously recorded for auditing purposes, providing transparency and accountability.
- User Administration: Easily add co-workers, enabling secure and collaborative contribution to your migration projects.
- Microsoft Migration Infrastructure Location Flexibility: You can choose the geographical location of your migration VMs from a selection of available Azure datacenters, helping with potential data residency requirements.
- Effortless Setup: Getting started is a breeze. With just a one-time login, you can have your CloudM Migrate Hosted deployment up and running with minimal fuss.
- Automated Updates: CloudM Migrate's hosted deployment takes care of itself. Both the software and underlying infrastructure are automatically updated, but only when no migrations are actively processing, ensuring a seamless and uninterrupted experience.
Cons of Hosted Deployment
- Limited Infrastructure Access: You will not have direct access to the underlying backend migration infrastructure, including migration logs and trace files.
- Scalability Limit: Hosted deployments are currently scalable up to a maximum of 155 concurrent threads. For higher concurrency needs, a self-hosted deployment may be more suitable.
CloudM Migrate Self-Hosted
CloudM Migrate Self-Hosted puts you in control, allowing you to manage and run the migration within your own infrastructure, GCP or Azure.
Pros of Self-Hosted Deployment
- Custom Scaling: Configure as many instances of the CloudM Migrate application as needed, with no additional licensing charges from CloudM, giving you ultimate control over your migration capacity.
- Network Containment: With a self-hosted deployment, all data entering (ingress) and leaving (egress) your migration environment remains strictly within your existing private network infrastructure. This design provides you with enhanced control over data flow, security policies, and compliance requirements, as your sensitive data does not traverse external networks or the public internet during the migration process.
- Minimal Data Reporting: In a self-hosted deployment, only essential CloudM license portal metadata is transmitted to CloudM. Your actual migration content, user data, or any other sensitive information being processed remains entirely within your self-hosted environment and is never sent to or stored by CloudM.
- Effortless Setup: The CloudM Migrate deployment is designed as a self-contained package, offering a simple and rapid installation process within your environment. You can get it up and running with minimal fuss.
Cons of Self-Hosted Deployment
- Increased Management Overhead: You are responsible for provisioning, maintaining, patching, and securing the underlying infrastructure (servers, OS, networking) and implementing and maintaining security controls. This requires dedicated internal resources and expertise.
- Cloud Infrastructure Costs: Though the CloudM Migrate application has no instance charges, you pay for your infrastructure (e.g., VMs, storage, networking, power, cooling) and IT operational costs.
- Manual Scalability Management: Unlike the automatic resource provisioning in a hosted deployment, you must manually monitor and scale your infrastructure to meet changing migration demands. This requires careful planning and active management.
- Infrastructure Support Responsibility: CloudM provides support for the CloudM Migrate application itself. However, troubleshooting and resolving issues related to your self-hosted infrastructure are your team's responsibility.