Huawei Cloud for applications that need region, connectivity, identity and operations defined before migration
Computing, data, networking, identity and continuity organised around verifiable criteria.
Huawei Cloud is addressed separately from the Huawei Enterprise portfolio of enterprise networking products.
Huawei Cloud to evolve your company’s infrastructure
Dependencies between applications, identity, data, connectivity, licences and recovery determine whether a workload should be migrated, modernised or kept outside Huawei Cloud. ADD starts with this map and the acceptance criteria before proposing services and a sequence of changes. Operating since 2011 in São José do Rio Preto, ADD Solution works in infrastructure engineering, deployment and operations. The starting point is to understand your applications, dependencies and priorities to determine what makes sense to migrate, modernise or keep in the current environment. This page covers Huawei Cloud services. Huawei Enterprise equipment and enterprise networking solutions, such as switches and campus infrastructure, belong to a different project scope.
Resources chosen around the application
A useful architecture combines services according to the workload. Elastic Cloud Server, or ECS, provides virtual machines for applications that need control over the operating system. Cloud Container Engine, CCE, provides managed Kubernetes clusters for containerised applications. Adopting it requires assessing team maturity, the update lifecycle and application dependencies. For storage, EVS provides block volumes, while OBS organises data as objects. SFS provides file sharing. The choice depends on the required protocol, access frequency and read/write characteristics. Managed databases, such as RDS for MySQL, can reduce infrastructure administration tasks. Versions, extensions, queries, integrations and maintenance requirements still need validation. The catalogue guides the assessment; the final service mix must be confirmed for the intended region and configuration.
An organised foundation for growth
Before creating resources, we recommend defining the structure of accounts, projects, environments and responsibilities. Production, staging and development should have clear criteria for separation, access and budget. Naming conventions, identified owners and documentation make long-term maintenance easier. The architecture must also record external dependencies, certificates, name resolution, data flows and change procedures. Where appropriate, infrastructure-as-code templates help reproduce configurations and review changes. Resource Formation Service provides this type of provisioning in Huawei Cloud, including documented availability in LA-Sao Paulo1. The expected outcome is a manageable foundation: every resource has a purpose, every access has an accountable owner and every change can be assessed before it reaches production.
Networks that connect applications and sites
Virtual Private Cloud, VPC, enables the organisation of subnets, addressing and traffic controls. Security groups and network ACLs have specific roles in protecting communications. The design should limit public exposure and document which systems may communicate with each other. For hybrid environments, VPN and Direct Connect are options for connecting on-premises infrastructure to the cloud. Selection requires consideration of bandwidth, latency, redundancy, carriers, costs and operational capacity. Direct Connect also depends on available connection points and procurement of the corresponding circuit. Services compatible with VPC Endpoint can be accessed over private channels without a public IP address. Each integration must be checked in the chosen region. Connectivity testing needs to include link failures, alternative routes and administrative access.
Identity and security with defined responsibilities
IAM enables permissions to be assigned to people, applications and services. A deployment should apply least privilege, multifactor authentication and periodic access reviews. Federation with the corporate identity provider can centralise user onboarding and offboarding, within the supported protocols and features. In day-to-day operations, we recommend avoiding shared accounts and documenting emergency access. Application credentials need appropriate storage, rotation and a restricted scope. Available capabilities vary between IAM editions and should be checked before controls are standardised. Security follows a shared responsibility model. Huawei Cloud manages the protection of the infrastructure it provides; the customer remains responsible for its data, identities and configurations. For virtual machines, this includes components such as the operating system and applications. The exact division depends on the service used and must be recorded in the operating plan.
Protecting data throughout its lifecycle
Classifying information before migration helps determine location, encryption, retention and access controls. In OBS, access and lifecycle policies need to reflect the purpose of the data. Storage classes have different retrieval and minimum-storage-duration conditions that must be included in technical and financial planning. Encryption requires attention to key management and usage permissions. In EVS, integration with Key Management Service enables disk encryption. For web applications, WAF can add inspection and protection policies, depending on the purchased edition and how the application is published. These capabilities must be accompanied by patching, configuration reviews and incident response. Compliance analysis should involve those responsible for privacy and industry-specific requirements, considering actual data processing and applicable contracts.
Operations with visibility and usage control
Cloud Eye tracks resource metrics and allows alarms to be configured. Log Tank Service collects and analyses logs; Cloud Trace Service records supported operations for queries and auditing. This information must reach people with clear procedures for investigation and response. We recommend defining indicators for perceived availability, response time, capacity and backup success. Alarms should have priorities, owners and routing appropriate to their business impact. Usage reviews need to examine idle resources, storage growth, traffic and log retention. The budget must include support, connectivity, licences and operations. Contractual commitments only make sense after usage patterns and cancellation terms are understood.
Migration with acceptance and recovery criteria
The initial inventory should identify operating systems, applications, databases, integrations, data volumes and available windows. It can then be used to organise migration waves and select a representative pilot. Server Migration Service, SMS, provides replication and synchronisation capabilities for supported scenarios. Important restrictions apply: identifier changes may invalidate licences, and destination disks are formatted during the process. The destination must therefore be prepared specifically for migration, with any existing content protected beforehand. Validation should cover authentication, data integrity, scheduled jobs, performance and integration functionality. Before cutover, we recommend defining who approves the result, how conflicting writes will be stopped and how to return to the previous environment. The scope and duration of assisted operations should be agreed.
Continuity proven through testing
The continuity strategy starts with tolerable data loss and acceptable recovery time, expressed as RPO and RTO. These objectives guide redundancy, replication, backup and failback procedures. Cloud Backup and Recovery, CBR, uses vaults and policies to protect supported resources. Frequency, retention and replication must be configured for each application. Distributing components across zones can reduce exposure to localised failures, but the application, database and connectivity must support that design. Restore tests should verify both data and service functionality. The ECS SLA distinguishes between deployment modes and includes exclusions and credit rules. Application availability also depends on the layers the company configures and operates.
Region and contracting must align with the project
Huawei Cloud documents the Brazilian region LA-Sao Paulo1. Its existence must be considered alongside the availability of each service, edition, capacity and integration. Globally announced features may have different regional coverage. The applicable contractual instrument must also be checked. The international Customer Agreement distinguishes direct contracting from contracting through Solution Partners, referring the latter to the EULA. Prepayments may involve cancellation charges. Expired resources or those with overdue payments are subject to grace and retention conditions, with data deletion provided for after the applicable period. Support, taxes, renewal and data export need to be assessed in the actual proposal. Choosing a Brazilian region determines where resources will be deployed. A data residency requirement must also examine backups, replication and support-related processing. Third-party licences need to be validated with their respective suppliers.
Key decisions about Huawei Cloud
Do Huawei Cloud and Huawei Enterprise have the same scope?
They are distinct areas. Here, the focus is on cloud services such as compute, storage and managed platforms. Huawei Enterprise corporate networks, switches and campus solutions should be sized within their own project, even when integrated with the cloud.
Can I use a region in Brazil?
Yes. LA-Sao Paulo1 is listed in the official documentation. Confirm the availability of the service, deployment option, capacity and required features before contracting. The location must also meet latency and data processing requirements.
Can I keep part of my infrastructure on premises?
Yes. VPN and Direct Connect can connect on-premises and cloud resources. The hybrid architecture must address addressing, routing, authentication and communication failures. The choice depends on application requirements and available connectivity.
What is the difference between ECS and CCE?
ECS provides virtual machines. CCE provides Kubernetes cluster management for containers, integrating compute, network and storage resources. The decision depends on the application architecture and the team’s ability to manage its dependencies and updates.
Who handles security after deployment?
Responsibilities should be allocated among the provider, customer and team contracted to operate the environment. Data, access and configurations still require management. The scope varies by service and must be documented, with owners assigned for patching and incidents.
Will my current licences remain valid in the cloud?
This depends on the supplier and the contract for each software product. SMS documentation warns that identifier changes may affect licences after migration. Validation should take place before the pilot, including costs and terms for any replacement.
Is backup enough to keep the application available?
Backup enables recovery to protected points within the configured policy. Continuity also requires consideration of redundancy, dependencies and restore time. Tests must demonstrate whether the selected combination meets the business’s defined recovery objectives.
How do I start a project with ADD Solution?
Describe the applications involved, current challenges and continuity priorities. The initial discussion can guide a technical assessment, followed by a proposal covering architecture, deployment stages, responsibilities and operating terms. The scope will be defined according to the company’s needs.
Cloud conectada à operação.
Plan your cloud around applications and data
Structure infrastructure, identity, connectivity, protection and operations with verifiable assumptions.