TAC AWS Workloads extends the capabilities of TAC AWS Foundations. It enables customers to deploy their defined workload packages, consistently and repeatedly across their AWS organisation.

Workloads integrate cleanly with your existing organisation, account structure, and guardrails, using the same settings-driven orchestration engine that powers Foundations. Workloads follow the same principles as Foundations — consistency, repeatability, auditability and explicit customer approval.

What Workloads Provides

Custom-defined, settings-based infrastructure that integrates cleanly with your Foundations environment.

TAC AWS Workloads allow you to specify the outcome you need, and TAC assembles the supporting AWS infrastructure using the tools and patterns established in TAC AWS Foundations. Each workload becomes a reusable, settings-driven unit that can be deployed across multiple accounts and environments without hand-crafted IaC.

Examples Include

Compute Environments

(EC2, Auto Scaling, Load Balancing and supporting networking)

Event-driven Architectures

(Lambda, EventBridge, SNS, SQS and Step Functions)

Data & Analytics Foundations

(S3 data zones, Glue, Athena and Lake Formation integrations)

Security & Monitoring Integrations

(additional controls, pipelines, cross-account integrations)

Shared Platform Services

(common infrastructure used by multiple workload teams)

Custom-defined Workload Packages

(any AWS services required to achieve the desired outcome)

When Workloads Make Sense

Deploy custom infrastructure without designing everything from scratch

Workloads enable consistent, governed infrastructure patterns without bespoke IaC for each team.

Enable consistent patterns across multiple application teams

Standardised infrastructure accelerates delivery while reducing operational risk.

Introduce new AWS services safely and predictably

New services can be introduced in a controlled, governed way using validated patterns.

Expand platform capability without growing your IaC team

TAC provides reusable orchestration units that eliminate snowflake builds.

Maintain Dev/Test/Prod consistency

Workloads enforce environment parity through settings-driven deployments.

Reduce operational risk with repeatable patterns

Reusable units avoid one-off deployments and reduce manual error.

How Workloads Are Delivered

You define the workload outcome: Describe what the workload must achieve, and the settings that will define required resources.
TAC maps the outcome to infrastructure: TAC selects the required modules, integrates additional AWS services as needed and defines the orchestration units that form the workload package.
Settings drive the deployment: Your workload settings are compiled by the logic layer into usable inputs, just like Foundations. All deployment is fully data-driven and aligns with your Foundations settings.
A read-only plan is generated inside your AWS accounts: You review the proposed changes exactly as you do with Foundations.
You approve the change-set for that build: Nothing applies without your explicit AWS-level approval.
The workload becomes reusable: Once defined, the workload can be deployed repeatedly across environments or accounts, using the same settings-driven model.

What's Included, What's Not

Workloads includes:

Settings-driven deployment of additional AWS services and integrated infrastructure
Use of TAC-maintained modules, with the ability to extend beyond them
Integration with your existing accounts, networking, identity and governance boundaries
Full auditability via native AWS plan and approval workflows.

Workloads does not:

Operate or manage your applications once deployed
Replace your application release or deployment processes
Provide ongoing operational support for application-level issues
Override your organisational baselines or governance controls.

TAC AWS Workloads are continuously maintained in the same way as Foundations - module updates, new AWS capabilities and improvements flow through the workload definitions, with all changes visible and approved by you before deployment.