How Tipico democratized information transformations utilizing Amazon Managed Workflows for Apache Airflow and AWS Batch

This can be a visitor put up by Jake J. Dalli, Knowledge Platform Workforce Lead at Tipico, in partnership with AWS.

Tipico is the primary title in sports activities betting in Germany. Day by day, we join thousands and thousands of followers to the fun of sport, combining expertise, ardour, and belief to ship quick, safe, and thrilling betting, each on-line and in additional than a thousand retail retailers throughout Germany. We additionally deliver this expertise to Austria, the place we proudly function a powerful sports activities betting enterprise.

On this put up, we present how Tipico constructed a unified information transformation platform utilizing Amazon Managed Workflows for Apache Airflow (Amazon MWAA) and AWS Batch.

Resolution overview

To help vital wants akin to product monitoring, buyer insights, and income assurance, our central information operate wanted to offer the instruments for a number of cross-functional analytics and information science groups to run scalable batch workloads on the present information warehouse, powered by Amazon Redshift. The workloads of Tipico’s information neighborhood included extract, remodel, and cargo (ELT), statistical modeling, machine studying (ML) coaching, and reporting throughout numerous frameworks and languages.

Prior to now, analytics groups operated in isolation, distinct from one another and the central information operate. Completely different groups maintained their very own set of instruments, typically performing the identical operate and creating information silos. Lack of visibility meant an absence of standardization. This siloed method slowed down the supply of insights and prevented the corporate from reaching a unified information technique that ensured availability and scalability.

The necessity to introduce a single, unified platform that promoted visibility and collaboration turned clear. Nonetheless, the variety of workloads introduced one other layer of complexity. Groups wanted to sort out various kinds of issues and introduced distinct skillsets and preferences in tooling. Analysts would possibly rely closely on SQL and enterprise intelligence (BI) platforms, whereas information scientists most popular Python or R, and engineers leaned on containerized workflows or orchestration frameworks.

Our aim was to architect a brand new system that helps range whereas sustaining operational management, delivering an open orchestration platform with built-in safety isolation, scheduling, retry mechanisms, fine-grained role-based entry management (RBAC), and governance options akin to two-person approval for manufacturing workflows. We achieved this by designing a system with the next rules:

1. Convey Your Personal Container (BYOC) – Groups are given the pliability to package deal their workloads as containers and are free to decide on dependencies, libraries, or runtime environments. For groups with extremely specialised workloads, this meant that they might work in a setup tailor-made to their wants whereas additionally working inside a harmonized platform. However, groups that didn’t require totally personalized environments might redesign their workloads to align with present workloads.
2. Centralized orchestration for full transparency – All groups can see all workflows and construct interdependencies between them
3. Shared orchestration, remoted compute – Workloads run in team-specific Docker containers inside a unified compute surroundings, offering scalability whereas maintaining execution traceable to every staff.
4. Standardized interfaces, versatile execution – Widespread patterns (operators, hooks, logging, or monitoring) cut back complexity, and groups retain freedom to innovate inside their containers.
5. Cross-team approvals for vital workflows saved inside model management – Adjustments observe a four-eye precept, requiring assessment and approval from one other staff earlier than execution, offering accountability and lowering threat. This allowed our core information operate to observe and contribute recommendations to work throughout completely different analytics groups.

We devised a system whereby orchestration and execution of duties function on shared infrastructure, which groups work together with by means of domain-specific infrastructure. In Tipico’s case, every staff pushes pictures to team-owned container cases. Such containers present code for workflows, together with execution of ELT pipelines or transformations on prime of domain-specific information lakes.

The next diagram reveals the answer structure.

The technical problem was to architect a versatile and high-performance orchestration layer that might scale reliably whereas additionally remaining framework-agnostic, integrating seamlessly with present infrastructure.

When designing our system, we have been conscious of the a number of container orchestration options supplied by Amazon Net Providers (AWS), together with Amazon Elastic Kubernetes Service (Amazon EKS), Amazon Elastic Container Service (Amazon ECS), and AWS Batch, amongst others. Ultimately, the staff chosen AWS Batch as a result of it abstracts away cluster administration, gives elastic scaling, and inherently helps batch workloads as a design function.

Resolution particulars

Earlier than adopting the present answer, Tipico experimented with working a self-managed Apache Airflow setup. Though it was purposeful, it turned more and more burdensome to take care of. The shift towards a managed and scalable answer was pushed by the necessity to focus extra on empowering groups to ship somewhat than sustaining the infrastructure. Tipico replatformed the central orchestration answer utilizing Amazon MWAA and AWS Batch.

Amazon MWAA is a completely managed service that simplifies working open supply Apache Airflow on AWS. Customers can construct and execute information processing workflows whereas integrating seamlessly with varied AWS providers, which suggests builders and information engineers can consider constructing workflows somewhat than managing infrastructure.

AWS Batch is a completely managed service that simplifies batch computing within the cloud so customers can run batch jobs with no need to provision, handle, or keep clusters. It automates useful resource provisioning and workload distribution, with customers solely paying for the underlying AWS sources consumed.

The brand new design gives a unified framework the place analytics workloads are containerized, orchestrated, and executed on scalable compute and built-in with persistent storage:

1. Containerization – Analytics workloads are packaged into Docker containers, with dependencies bundled to offer reproducibility. These pictures are versioned and saved in Amazon Elastic Container Registry (Amazon ECR). This method decouples execution from infrastructure and allows constant habits throughout environments.
2. Workflow orchestration – Airflow Directed Acyclic Graphs (DAGs) are version-controlled in Git and deployed to Amazon MWAA utilizing a steady integration and steady supply (CI/CD) pipeline. Amazon MWAA schedules and orchestrates duties, triggering AWS Batch jobs utilizing customized operators. Logs and metrics are streamed to Amazon CloudWatch, enabling real-time observability and alerting.
3. Knowledge persistence – Workflows work together with Amazon Easy Storage Service (Amazon S3) for sturdy storage of inputs, outputs, and intermediate artifacts. Amazon Elastic File System (Amazon EFS) is mounted to Amazon MWAA for quick entry to shared code and configuration information, synchronized repeatedly from the Git repository.
4. Scalable compute – Amazon MWAA triggers AWS Batch jobs utilizing standardized job definitions. These jobs run in elastic compute environments akin to Amazon Elastic Compute Cloud (Amazon EC2) or AWS Fargate, with secrets and techniques securely injected utilizing AWS Secrets and techniques Supervisor. AWS Batch environments auto scale primarily based on workload demand, optimizing value and efficiency.
5. Safety and governance – AWS Id and Entry Administration (IAM) roles are scoped per staff and workload, offering least-privilege entry. Job executions are logged and auditable, with fine-grained entry management enforced throughout Amazon S3, Amazon ECR, and AWS Batch.

Widespread operators

To streamline the execution of batch jobs throughout groups, we developed a shared operator that wraps the built-in Airflow AWS Batch operator. This abstraction simplifies the execution of containerized workloads by encapsulating widespread logic akin to:

1. Job definition choice
2. Job queue focusing on
3. Setting variable injection
4. Secrets and techniques decision
5. Retry insurance policies and logging configuration

Parameterization is dealt with utilizing Airflow Variables and XComs, enabling dynamic habits throughout DAG runs. The operator is maintained in a shared Git repository, versioned and centrally ruled, however accessible to all groups.

To additional speed up growth, some groups use a DAG Manufacturing facility sample, which programmatically generates DAGs from configuration information. This reduces boilerplate and enforces consistency so groups can outline new workflows declaratively.

By standardizing this operator and supporting patterns, Tipico reduces onboarding friction, promotes reuse, and gives constant observability and error dealing with throughout the analytics ecosystem.

Governance

Governance is enforced by means of a mix of fine-grained IAM roles, AWS IAM Id Heart and automatic position mapping. Every staff is assigned a devoted IAM position, which governs entry to AWS providers akin to Amazon S3, Amazon ECR, AWS Batch and Secrets and techniques Supervisor. These roles are tightly scoped to reduce the extent of harm and supply traceability.

On condition that the airflow surroundings runs model 2.9.2, which doesn’t help multi-tenant entry, Tipico developed a customized element that dynamically maps AWS IAM roles to Airflow roles. The element, which executes periodically utilizing Airflow itself, dynamically syncs IAM position assignments with Airflow’s inner RBAC mannequin. Airflow tags are used to control entry to completely different DAGs, governing which groups have entry to execute or modify the settings on the DAG. This aligns entry permissions stay with organizational construction and staff tasks.

Adoption

The shift towards a managed, scalable answer was pushed by the necessity for higher staff autonomy, standardization, and scalability. The journey started with a single analytics staff validating the brand new method. When it was profitable, the platform staff generalized the answer and rolled it out incrementally to different groups, refining it with every iteration.One of many greatest challenges was migrating legacy code, which frequently included outdated logic and undocumented dependencies. To help adoption, Tipico launched a structured onboarding course of with hands-on coaching, actual use instances, and inner champions. In some instances, groups additionally needed to undertake Git for the primary time—marking a broader shift towards fashionable engineering practices throughout the analytics group.

Key advantages

Probably the most helpful outcomes of our new structure that’s primarily constructed round Amazon MWAA and AWS Batch is to speed up analytics groups’ time to worth. Analysts can now deal with constructing transformation logic and workloads with out worrying concerning the underlying infrastructure. With this method, analysts can depend on preprepared integrations and analytics patterns used throughout completely different groups, supported by customary interfaces developed by the core information staff.

Except for constructing analytics on Amazon Redshift, the orchestration answer additionally interfaces with a number of different analytics providers akin to Amazon Athena and AWS Glue ETL, offering most flexibility on the kind of workloads being delivered. Groups throughout the group have additionally shared practices in utilizing completely different frameworks, akin to dbt Labs, to reuse customized developments to hold out customary processes.

One other helpful final result is the flexibility to obviously segregate prices throughout groups. Throughout the structure, Airflow delegates heavy lifting to AWS Batch, offering activity isolation that spans past Airflow’s built-in employees. By way of this, we achieve granular visibility into useful resource utilization and correct value attribution, selling monetary accountability throughout the group.

Lastly, the platform additionally gives embedded governance and safety, with RBAC and standardized secrets and techniques administration offering an operationalized mannequin for securing and governing working flows throughout completely different groups.

Groups can now deal with constructing and iterating rapidly, figuring out that the encompassing buildings present full transparency and are coherent with the group’s governance, structure, and FinOps objectives. On the identical time, centralized orchestration fosters a collaborative surroundings the place groups can uncover, reuse, and construct upon one another’s workflows, driving innovation and lowering duplication throughout the information panorama.

Conclusion

By reimagining our orchestration layer with Amazon MWAA and AWS Batch, Tipico has unlocked a brand new stage of agility and transparency throughout its information workflows.

Beforehand, analytics groups confronted lengthy lead instances, typically stretching into weeks, to implement new reporting use instances. A lot of this time was spent figuring out datasets, aligning transformation logic, discovering integration choices, and navigating inconsistent high quality assurance processes. In the present day, that has modified. Analysts can now develop and deploy a use case inside a single enterprise day, shifting their focus from groundwork to motion.

The fashionable structure empowers groups to maneuver quicker and extra independently inside a safe, ruled, and scalable framework. The result’s a collaborative information ecosystem the place experimentation is inspired, operational overhead is lowered, and insights are delivered at pace.

To begin constructing your individual orchestrated information platform, discover the Get began with Amazon Managed Workflows for Apache Airflow and AWS Batch Consumer Information. These providers might help you obtain related leads to democratizing information transformations throughout your group. For hands-on expertise with these options, strive our Amazon MWAA for Analytics Workshop or contact your AWS account staff to be taught extra.

In regards to the authors