When Wirebox met Playrcart for AWS Best Practices

who are playrcart?

Playrcart allows customers to complete transactions whilst engaging in video content.

Imagine: you’re scrolling through a webpage, and there’s a video advertisement for donuts.

Instead of just watching and thinking ‘mmmm. I could do with one of those,’ Playrcart allows customers to complete a checkout STRAIGHT from inside the video’s borders. Easy peasy.

why playrcart approached wirebox_

After their initial product launch, Playrcart approached Wirebox to bring their hosting environment in line with best industry practices.

Wirebox AREN’T strangers when it comes to AWS’ Well Architected Framework, so this one was a no-brainer.

the wirebox approach_

Wirebox scheduled a number of workshops with the team (who are a group of super talented developers and engineers by the way), to share details and diagrams. Wirebox developed the implementation plan, which was signed off at each stage. The Playrcart team had input at each stage, to see how the environment was being set up.

the focus was to:

• Separate Playrcart’s environments into discrete AWS accounts, managed within an AWS organisation. This meant that access to each environment could easily be granted, and that maintaining Least Privileged Access for users and services would be much easier. Another benefit was that deploying to one environment could be done completely independently of another.
• Set up and maintain user accounts, groups, and roles. Wirebox helped Playrcart to set up and maintain user accounts, groups, and roles, allowing the team to have a single place to manage access control for the entire organisation, including multi-factor authentication controls, with one place to log in. Who needs more passwords? Not us. And not you, either.
• Configuration of the entire Playrcart environment together, with Terraform Infrastructure as Code.

the outcome_

Wirebox rebuilt everything from the ground up, capturing every requirement and document as it was built. Here’s what Wirebox had to say about the process:

“We committed all of the Terraform code into branches of an Infrastructure as Code repository, and in our final workshop, we had some cool demonstrations of changes being promoted through the environments, all the way to production. This gave them the peace of mind to know that uncontrolled changes were a thing of the past.”

“We loved working with the Playrcart team. Their enthusiasm to learn from our experience really underlined why we work in this space. Cloud is cool, and when you do cloud hosting and delivery properly, it’s even better!”