DevSecOps

Huawei Cloud Next to AWS and Azure: One DevSecOps Toolchain

One set of pipelines, Terraform modules and access automation that deploys to Huawei Cloud as it does to AWS and Azure.

When Huawei Cloud is added as a second public cloud, NGT keeps one way of delivering. Development teams order resources from a self-service catalogue built on Terraform modules; applications pass the same security gates; joiners, leavers, database users and permissions are handled by automation instead of tickets.

requestapplydeploygrant, revokeRequestsOne DevSecOps toolchainInfrastructure self-serviceApplication pipelineAccess automationAWSHuawei CloudMicrosoft AzureDevelopment teamsresource requestsCode changesJoiners and leaversSelf-servicecatalogueapproved templatesTerraform modulesone set, a provider per cloudPlan reviewpolicy checksGitLab CIshared stagesSonarQubequality gateTrivyimage scan gateOnboarding andoffboardingas a pipelineVaultsecrets and credentialsPermissions anddatabase usersHuawei CloudaccountsIAM per teamCloud ContainerEngine (CCE)RDSAWS accountsIAM roles per teamAmazon EKSAmazon RDSAzure subscriptionsEntra ID groupsAzure KubernetesServiceAzure Database

Point at a component to light its links; select it for what it does here and the practice that makes it right.

When to use it

  • Huawei Cloud added beside AWS or Azure
  • Development teams waiting on a platform team for every resource
  • Access granted and removed by hand on several clouds

How NGT delivers it

Built from code, reviewed at a gate by an NGT architect, and handed over with runbooks your team can run.

DevSecOps