AWS Activate Approves $1,000 in Infrastructure Credits for Abba Baba

AWS Activate has approved $1,000 in infrastructure credits for Abba Baba. We are publishing this because we said we would be transparent about infrastructure funding, and $1,000 qualifies as infrastructure funding.

We are also publishing it because the number is modest, and there is a version of this announcement that would make $1,000 sound impressive by omitting context. That version is not useful to anyone trying to understand what pre-launch infrastructure for a solo-built A2A protocol actually looks like.

What AWS Activate is

AWS Activate is a program providing AWS credits to early-stage startups. Credit amounts vary by cohort, partner referrals, and application. It is one of several startup credit programs alongside Google Cloud for Startups, Azure for Startups, and similar initiatives.

Abba Baba applied. The application was approved.

The production AWS stack in detail

ECS (Elastic Container Service) — three services run as containers in the abbababa-prod-cluster:

• abbababa-web — the Next.js web application (1 task)
• abbababa-docs — the documentation site (1 task)
• abbababa-ambassador — the autonomous social posting agent (1 task, isolated with its own Postgres, no shared database access with the main platform)

RDS (PostgreSQL) — in February 2026, the platform migrated from Supabase to AWS RDS for the production database. The instance is a db.t3.medium running PostgreSQL 16, Multi-AZ, in a private subnet. 73 Prisma models moved in the migration. Supabase Auth is retained for human developer authentication; the database itself moved to RDS. The ECS-to-RDS connection is same-VPC IPv4 — this matters because Supabase's host was IPv6-only, which caused authentication failures from ECS before the migration.

ALB (Application Load Balancer) — HTTPS termination on port 443 (web service) and port 8080 (docs). HTTP port 80 redirects to HTTPS. Fronted by an ACM certificate issued for abbababa.com and *.abbababa.com.

ECR (Elastic Container Registry) — three repositories: abbababa/web, abbababa/docs, abbababa/ambassador. GitHub Actions pushes new images on merge to the main branch.

VPC and networking — production VPC vpc-041be70d8775b6ed7. Public subnets for the ALB, private subnets for ECS tasks and RDS.

Route53 — DNS for abbababa.com.

CloudWatch — logs from all three ECS services, RDS performance insights, ALB access logs, and container-level metrics.

Secrets Manager — environment variables stored in abbababa/prod/env, injected at container startup via ECS task execution role.

What $1,000 covers

At current scale — three ECS tasks, one t3.medium RDS instance, one ALB — monthly AWS spend runs in the range of several hundred dollars. $1,000 in credits covers roughly 2–3 months of baseline infrastructure.

After March 1st, transaction volume will determine whether that baseline holds or needs to scale. If adoption is faster than expected, the credits run out sooner. If the first 30 days are quiet, they carry further.

The startup credits playbook

AWS Activate is one program. Google Cloud for Startups and Microsoft for Startups have comparable programs. Abba Baba is actively pursuing multiple programs.

The total from all startup credit programs, if approved, represents a meaningful portion of the pre-revenue infrastructure budget. These programs exist to reduce capital requirements for launching technical infrastructure before there is revenue to cover it. They are doing exactly that here.

The $1,000 from AWS does not change the launch date, fee model, or contract architecture. It extends runway by 2–3 months.

Transparency commitment

Operation Bootstrap contributions, AWS credits, and all other infrastructure funding will be summarized in a public spending breakdown at the March 1st mainnet launch. The campaign at abbababa.com/operation-bootstrap remains open through launch.