secrets.json). Secrets are created/updated in the selected broker account using broker creds from the API.
redis_rds_user and Loggin IAM users in the selected broker account (SSM bastion access + logging policies). New access keys are returned once — store them securely.
BASTION-<account>. Requires pg_dump/pg_restore on bastion and SCRIPTS_DUMP_S3_BUCKET on the Lambda (or S3 bucket below). May take several minutes.
redis_rds_user + Loggin keys. Sheet IDs are configured in Lambda. Run Redis / RDS IAM users first — keys are loaded from browser storage for this broker.
ecs-services.tf / locals.tf), secrets, and changes vs main. Excludes proton and bajaj-trial.
file:// — S3 browser calls may fail. For auto-detect and reports, serve this file over HTTP (e.g. python -m http.server 8080 → http://localhost:8080/deployment-dashboard_18.html) and add S3 CORS for that origin. You can still type a version prefix manually below.
Type the version folder (e.g. v12 or v12/). Your last value is remembered per broker. Use Detect latest when the dashboard is served over HTTP with CORS.
@sha256:...), skipping latest-tag-only versions.
Start scales the non‑T4G private ASG to 3/3/5 and the public ASG to 1/1/3, waits until InService EC2 counts match, then invokes apt-vpc-ecs-service-scheduler with {"action":"start"} and confirms success via the Lambda response and CloudWatch logs.
Stop invokes {"action":"stop"}, waits for success in logs, then sets both ASGs to 0/0/0. Requires IAM: autoscaling:UpdateAutoScalingGroup, lambda:InvokeFunction, and on /aws/lambda/apt-vpc-ecs-service-scheduler: logs:DescribeLogStreams, logs:GetLogEvents, logs:FilterLogEvents.
Primary container on the task definition currently attached to each ECS service (EC2). Values are ECS units — CPU (e.g. 1024) and memory in MiB (e.g. 2048). Update registers a new revision and redeploys the service.
Compare deployed commits between two brokers using dashboard deployment data (same source as the main services table).
cfg on each refresh (or baked into HTML until API responds).cfg.scriptsApiUrl.GitHub repo to workflow file and ECS service name → workflow key. Used when you click Deploy.| GitHub repo | Workflow file | Orchestrator input key | ECS service → workflow key |
|---|
environment in DynamoDB.ecs:ListServices, ecs:DescribeServices, ecs:ListTaskDefinitions, ecs:DescribeTaskDefinition, ecr:DescribeImages, and autoscaling:DescribeAutoScalingGroups. To change ASG min / desired / max from the monitor tab, add autoscaling:UpdateAutoScalingGroup. For rollback and CPU/memory updates from dashboard, add ecs:UpdateService and ecs:RegisterTaskDefinition; for Lambda rollback add lambda:ListAliases, lambda:ListVersionsByFunction, lambda:GetFunction, lambda:UpdateAlias. Cluster name is apt-vpc-ecs-cluster in all accounts.
For Report (E2E): ecs:RunTask, logs:DescribeLogStreams, logs:GetLogEvents, s3:ListBucket, s3:GetObject on bucket apt-vpc-atoms-frontend-e2e-reports-<account-id>. Set each broker’s AWS account ID below so the dashboard can resolve the reports bucket.
For Cluster start/stop (Monitor → Auto scaling groups): lambda:InvokeFunction on apt-vpc-ecs-service-scheduler and on log group /aws/lambda/apt-vpc-ecs-service-scheduler: logs:DescribeLogStreams, logs:GetLogEvents, logs:FilterLogEvents (in addition to ASG update permissions above).
localStorage on this browser. Share credentials with your team manually.
| Service | Branch | Commit | Deployed at | Age | Status | Actions |
|---|