Platform Engineering

Self-Service Infrastructure Engine

A portal request becomes a Terraform run in the right account: no tickets, no keys on laptops, every run logged.

The engine behind the self-service catalogue of an internal developer platform we built inside FPT Software. The portal calls an API gateway; the backend records the request and creates a cloud-application resource; a Terraform controller starts a job that applies the template in the project's target account, with credentials fetched from a separate management account.

requesttoken checkwatchednew jobcredentialsapply · destroyPlatform services · main Kubernetes clusterExecution cluster · one job per runManagement accountProject's target accountDeveloperCorporate directoryDeveloper portalcatalogue · formsKeycloaksingle sign-onAPI gatewayKongCloud-servicebackendPostgreSQLprojects · requestsKubeVelacloud-app resourcesTerraform controllercustomTerraform jobplan · apply · destroyAWS Secrets Managerproject credentialsAmazon CloudFrontstatic webAmazon S3site · logsAmazon EC2VM packages

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

When to use it

  • Teams need cloud resources from vetted templates without cloud console access
  • Credentials must stay out of developers' hands
  • Every provisioning run must leave a log the portal can show

How NGT delivers it

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

Platform Engineering