VeUP
← All case studies
Production Engagement · Anonymized
Multi-region digital-signage content delivery on Amazon CloudFront, FinOps-optimized
Media & Entertainment (interactive digital-signage SaaS)
Amazon CloudFrontAmazon OpenSearchAmazon RDSAmazon CloudWatch
Media & Entertainment Competency · Digital Signage + FinOps

A multi-region digital-signage SaaS platform

AWS-validated reference — full details available to AWS Partner Validation or on request. (Customer name held on file with VeUP.)

For the customer (formerly Raydiant), a digital-signage SaaS, VeUP ran a multi-region FinOps optimization on its ~$402K/yr AWS estate: the CloudFront Savings Bundle on delivery, long-lived instances moved off 30-day GRIs onto 1-year commitments, CloudWatch log-cost cuts, and RDS extended-support fix.

The challenge

the customer (formerly Raydiant) runs an interactive digital-signage SaaS that turns in-venue TVs into connected media experiences for customers from SMB to global enterprise. Its product economics depend on efficient multi-region content delivery and storage, but spend was spread across us-west-2 (Oregon), us-east-1 (N. Virginia), and an EU/Canada footprint with no clear per-region/per-service picture: CloudFront delivery costs were uncommitted, modernized long-lived instances sat on 30-day GRIs, CloudWatch logging cost was high (custom/3rd-party dashboard metrics in Oregon), and RDS carried EU extended-support charges. The Raydiant-> the customer entity change also had to be handled mid-contract.

The solution

A multi-region digital-signage content-delivery platform on AWS with a documented FinOps optimization across its delivery, search, data, and observability tiers: Amazon CloudFront for global edge delivery of media to in-venue signage screens (CloudFront Savings Bundle applied), Amazon OpenSearch Service (concentrated in us-west-2) for search/indexing, Amazon RDS as the relational data tier, and Amazon CloudWatch for observability. The flagship deliverable established centralized multi-region cost visibility (Oregon + N. Virginia as the primary cost regions), applied the CloudFront Savings Bundle, recommended CloudWatch log-retention/volume reduction in Oregon, addressed RDS EU extended-support, analyzed OpenSearch workload locality, and moved modernized long-lived instances off 30-day GRIs (Archera) onto 1-year commitments.

Architecture

AWS Well-Architected view of the multi-region digital-signage estate — from the pre-FinOps baseline (uncommitted CloudFront delivery, 30-day GRIs, fragmented cost visibility) through to the production CloudFront edge, per-region OpenSearch/RDS/CloudWatch estate, and the Archera-managed cost-governance plane.

A multi-region digital-signage SaaS platform — AWS Well-Architected architecture diagram. Previous state: uncommitted CloudFront delivery costs, 30-day GRI compute commitments, unclear OpenSearch workload locality, RDS EU extended-support charges, high CloudWatch log cost, and fragmented multi-region cost visibility. Target state: AWS Cloud with Amazon CloudFront (Savings Bundle applied), a centralized multi-region cost-visibility dashboard, us-west-2 (Oregon) with Amazon OpenSearch Service, Amazon RDS, and Amazon CloudWatch, us-east-1 (N. Virginia) signage application compute, a minor EU/Canada RDS footprint, and an Archera-managed cost-governance rail. Includes a Well-Architected pillar-by-pillar alignment strip.
VeUP-rendered Well-Architected diagram from the VeUP engagement record and AWS competency case-study evidence (Media & Entertainment, CloudFront SD, OpenSearch SD).

Production outcomes

KPIResult
Production outcomesCentralized multi-region cost visibility established across the ~$402K/yr estate (Oregon + N. Virginia identified as the primary cost regions); the CloudFront Savings Bundle applied directly to the core content-delivery cost driver; modernized long-lived instances recommended off 30-day GRIs onto 1-year commitments; CloudWatch log-retention/volume reduction recommended in Oregon; RDS EU extended-support charges flagged and addressed; OpenSearch workload locality analyzed. Realized cost data held in the customer's Cost Explorer and provided via the customer-reference channel.
Engagement windowIgnite engagement; FinOps Intro — Raydiant/the customer review → AWS ACE opportunity Closed Won; ongoing
Cost / TCO postureThe engagement's flagship deliverable was the FinOps review: per-region/per-service spend mapping against the ~$402K/yr estate, CloudFront Savings Bundle on delivery, commitment-coverage modernization (30-day GRI -> 1-year), CloudWatch log-source cost analysis, and RDS extended-support review — each tied to protecting the multi-region content-delivery economics of a digital-signage media platform.
Lessons & continuationFor a multi-region signage media platform, establishing centralized per-region/per-service cost visibility is the precondition for every other lever; the CloudFront Savings Bundle is the direct reduction on the core delivery cost driver; modernized long-lived instances belong on 1-year commitments not 30-day GRIs; and high-cost custom/3rd-party dashboard log metrics are a recurring CloudWatch cost driver worth tuning.
AWS services in production

Amazon CloudFront · Amazon OpenSearch Service · Amazon RDS · Amazon CloudWatch