---
title: "How BMW Group accelerated connected vehicle workloads on AWS Graviton"
description: "BMW Group’s Connected Vehicle platform, Orbit, powers digital services for more than 24.5 million vehicles worldwide. In 2024, the team began migrating from x86 to AWS Graviton Arm-based compute to advance economic and environmental goals. They adopted Karpenter for flexible node provisioning, extended GitHub Actions runners with Graviton for native arm64 builds, and used multi-architecture container images via manifest lists to support both architectures transparently. The migration achieved approximately $600,000 in annual infrastructure savings, a 40 percent price-performance improvement on the NGINX ingress controller, and a 57 percent reduction in CPU consumption while scaling efficiently during peak loads. Today, over 65 percent of the platform runs on Graviton, with an opt-in scheduling model using taints and tolerations that allows teams to migrate at their own pace without disruption."
---

# How BMW Group accelerated connected vehicle workloads on AWS Graviton

[AWS](https://yomu.fyi/company/aws) · Tomislav Lozančić · Oct 29, 2026

**Type:** Problem & solution

## Summary

BMW Group’s Connected Vehicle platform, Orbit, powers digital services for more than 24.5 million vehicles worldwide. In 2024, the team began migrating from x86 to AWS Graviton Arm-based compute to advance economic and environmental goals. They adopted Karpenter for flexible node provisioning, extended GitHub Actions runners with Graviton for native arm64 builds, and used multi-architecture container images via manifest lists to support both architectures transparently. The migration achieved approximately $600,000 in annual infrastructure savings, a 40 percent price-performance improvement on the NGINX ingress controller, and a 57 percent reduction in CPU consumption while scaling efficiently during peak loads. Today, over 65 percent of the platform runs on Graviton, with an opt-in scheduling model using taints and tolerations that allows teams to migrate at their own pace without disruption.

## Context

BMW Connected Company migrated its Orbit connected vehicle platform from x86 to AWS Graviton Arm-based compute as part of a broader modernization strategy. The platform supports over 24.5 million vehicles, with more than 130,000 daily builds and deployments. The migration aimed to reduce costs, improve performance, and support sustainability goals.

## Approach / What changed

The approach involved five stages: 1) Introducing Graviton-based CI/CD runners for native arm64 builds, 2) Implementing multi-architecture container images via Docker Buildx and OCI manifest lists, 3) Mirroring base images with Crane to preserve multi-arch support, 4) Creating dedicated Graviton node pools in Amazon EKS using Karpenter with taints and tolerations for opt-in scheduling, 5) Phased rollout starting with platform services (Karpenter, Prometheus) before application teams. Dual build pipelines and GitOps-based ArgoCD enabled quick rollback. Both native and emulated builds were supported.

## Takeaways

- Use taints, tolerations, and node selectors for opt-in scheduling so that only workloads explicitly ready for Arm migrate to Graviton nodes, preventing accidental disruption.
- Build multi-architecture container images using OCI manifest lists so a single tag serves both arm64 and amd64 nodes transparently, simplifying deployment and instant rollback.
- Validate the migration on platform services first (Karpenter, Prometheus, operational tooling) before enabling application teams; this identifies compatibility gaps and establishes rollback patterns.

## FAQ

### What cost savings did BMW Group achieve from the migration?

The migration achieved approximately $600,000 in annualized infrastructure savings while maintaining the same workload profile.

### How did BMW ensure a smooth migration without service disruption?

They used dual build pipelines for multi-architecture images, taint-based opt-in scheduling with dedicated Graviton node pools, and GitOps-based ArgoCD for easy rollback. Workloads could fall back to x86 without image rebuilds.

### What was the price-performance improvement on the NGINX ingress controller?

Price-performance improved by roughly 40 percent, with CPU consumption decreasing by about 57 percent while maintaining the same ingress profile and scaling efficiently at peak loads.

**Tags:** [Amazon EKS](https://yomu.fyi/topic/amazon-eks), [ARM](https://yomu.fyi/topic/arm), [AWS Graviton](https://yomu.fyi/topic/aws-graviton), [CI/CD](https://yomu.fyi/topic/ci-cd)

- Source: [AWS](https://aws.amazon.com/blogs/architecture/how-bmw-group-accelerated-connected-vehicle-workloads-on-aws-graviton)
- Source URL: https://aws.amazon.com/blogs/architecture/how-bmw-group-accelerated-connected-vehicle-workloads-on-aws-graviton
- Ingested by Yomu: 2026-10-29T21:00:12.939Z

[Read original post](https://aws.amazon.com/blogs/architecture/how-bmw-group-accelerated-connected-vehicle-workloads-on-aws-graviton)
