Reach Uses Amazon CloudFront to Deliver News to Millions of Customers

To address its challenges, Reach chose to migrate its core websites to Amazon CloudFront, a CDN service that securely delivers data and applications to global customers. “We selected Amazon Web Services (AWS) because it has built a reputation for speed of innovation and constantly delivering new services and features,” Smith says. The organization also chose to use Lambda@Edge, an Amazon CloudFront feature that runs code closer to application users in order to reduce latency and boost performance.

Following an initial discovery phase, Reach conducted a trial phase where it ran several smaller websites on Amazon CloudFront. “The majority of our migration time was spent getting the core configuration right,” says Smith. “Our code that holds our deployment pipeline together is very complex, and it’s technically difficult to roll out changes to 55 websites. We were concerned about making a change and doing something wrong, which could bring down all the sites at once.” To solve its migration challenges, Reach engaged AWS Professional Services for technical assistance. “The help we received from AWS solutions architects was invaluable,” says Smith. “After working with the architects, we changed our approach and that helped us ultimately pull off the migration.”

Running its websites on Amazon CloudFront, Reach can ensure scalability and strong performance for the customers visiting its 55 sites. “Using Amazon CloudFront, we can deliver low latency to millions of customers every day,” says Smith. “We also know we can scale our environment on AWS to support increasing traffic whenever necessary.”

Reach has also reduced its network transfer costs by migrating to Amazon CloudFront, and the company as a whole has recently closed its two data centers by moving production workloads to AWS.

By using AWS to automate its pipeline, developers can make configuration changes on their own without manual processes and approvals. “Previously, we made manual changes many times when we wanted to make a configuration change,” says Smith. “Moving to Amazon CloudFront solved that problem, because we were able to build fully automated pipelines. Now our developers can submit pull requests, review the changes, and push them into production on their own without asking our platform operations team to do it. This means we can move faster when we make any configuration changes at the CDN layer of our websites.”

Using AWS, Reach has the agility to create and deploy features faster than before. For example, the company quickly created and implemented service-side A/B testing using Lambda@Edge. “We’ve been able to move more quickly because a broader range of people have been able to work on the problems that fit at the CDN layer,” says Smith. “Relying on Amazon CloudFront, we can iterate faster on features at the CDN layer and we have more flexibility with Lambda@Edge.”

In addition, Reach is gaining new insights by using Amazon Athena to query Amazon CloudFront access log data. “Because we have insight into access logs, we can more easily analyze how people use our websites,” says Smith. “This is particularly useful for search engine optimization and troubleshooting website problems. Moving forward, we expect to introduce more features to help us better understand our customers and optimize our websites.”