Learn how we stored 3D scenes for Addictive Pixel

At a glance

Addictive Pixel provides a proven partnering model that supports creative content and digital production needs, guaranteeing a smooth and cost-efficient experience. 

Addictive Pixel now has a scalable application that allowed for scene creation within a visual 3D editor as well as a user-friendly UAM. This saves the client time as well as centralises assets, user access and storage.

Challenge

Addictive Pixel needed a solution to store, manage, and design 3D scenes for their industry-leading client, with different user levels and future adaptability.

Solution

Firemind’s solution used a suite of AWS services to create a scalable application that allowed for 3D scene creation, user and asset management, and reduced costs.

Services used
  • AWS Lambda
  • Amazon S3
  • Amazon API Gateway
  • Amazon CloudFront
Outcomes
  • 40% monthly cost reduction
  • Scalable 3D scene creation and user/asset management
Business challenges

Enabling scalable 3D scene management for Addictive Pixel's clients

Addictive Pixel had an industry leading client that needed a solution to store, manage and design 3D scenes.

The solution had to include different user levels such as admin, user admin and singular user. It also needed to have future adaptability so that it could be used for other customers with similar needs.

What our customers say

Hear directly from those who’ve experienced our services. Discover how we’ve made a difference for our clients.

Solution

Architecting a comprehensive AWS-based 3D scene management platform

Firemind’s solution used a suite of different AWS services such as AWS LambdaAmazon API GatewayAmazon S3 and AWS Batch.

In order to serve the content for this application, Amazon CloudFront was used as it allows Amazon API gateway to connect to most of the AWS Lambda resources necessary. Amazon CloudFront also used Amazon S3 to display static content. The Amazon API gateway was configured to use rest APIs which have edge optimised endpoints.

As part of the solution, we needed thorough authentication for all users. To do this we used AWS Lambda to authenticate the user and then set the user’s sessions. We stored these sessions in Amazon DynamoDB due to the importance of the ‘time to live’ feature.

For the UAM section of the application we used AWS Lambda, Amazon Relational Database Service and Amazon API Gateway. Amazon Relational Database Manager was used to store user, scene and asset information. The scene and asset information also correlated to Amazon S3 objects. AWS Lambda was used to query the database in order to save new information and display this data on the frontend.

In terms of the 3D visual studio, we used ThreeJS to create most components, with assets and background images pulling from S3 using signed URLs. The render section of the editor incorporated multiple AWS components. This allowed it to run a python script on a container.

Finally, we incorporated CloudWatch logs to monitor AWS Batch and AWS Lambda. This enhanced any future troubleshooting if an error occurred within a render.

Virtual 3D studio

Creation of an environment where the user can add assets, backgrounds and cameras, as well as alter lighting to create different variations of shadow.

User & asset management

Crafting a UAM interface that allowed appropriate access and authentication to multiple user types.

Reduced costs

Crafting a replacement cloud process to lower costs of designs, renders, storage and access – from the ground up.

Get in touch

Want to learn more?

Seen a specific case study or insight and want to learn more? Or thinking about your next project? Drop us a message!