DevSecOps

Ephemeral Azure Pipelines Agents on AWS Fargate

Azure DevOps builds and deploys to AWS with a fresh Fargate agent per job and no long-lived keys.

A pipeline job starts a Fargate task from the agent image in ECR. The agent registers to a self-hosted pool, runs the queued job with a scoped task role, deploys the serverless app and stops when the job ends.

pushstart agentlaunchregister, run jobimagetokenstatetask definitiondeploypackageAzure DevOps · organisationAWS CloudCI agents · built with TerraformServerless applicationDevelopersAzure Reposapp and IaC codeAzure Pipelinesbuild and releaseAgent poolself-hosted, on FargateTerraformCI infrastructureAmazon ECSRunTask, StopTaskFargate agent taskone per jobTerraform stateS3 backendAWS IAMa role per purposeAmazon ECRagent imageSSM Parameter Storepool token, encryptedAWS CloudFormationServerless FrameworkAmazon API GatewayAWS LambdaDeployment packageS3Amazon SQSAmazon DynamoDB

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

  • Azure DevOps teams deploying to AWS from an old shared build server
  • Deployments that use long-lived AWS access keys with broad rights
  • Builds that fail on dirty agents: leftover files, version conflicts

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