{"id":594339,"date":"2025-04-28T10:00:00","date_gmt":"2025-04-28T08:00:00","guid":{"rendered":"https:\/\/www.devoteam.com\/success-story\/filmstro-had-been-working-with-aws-for-several-years-before-approaching-devoteam-consulting\/"},"modified":"2025-04-28T10:00:00","modified_gmt":"2025-04-28T08:00:00","slug":"filmstro-had-been-working-with-aws-for-several-years-before-approaching-devoteam-consulting","status":"publish","type":"success-story","link":"https:\/\/devoteam.info\/me\/success-story\/filmstro-had-been-working-with-aws-for-several-years-before-approaching-devoteam-consulting\/","title":{"rendered":"Filmstro: Filmstro had been working with AWS for several years before approaching Devoteam Consulting."},"content":{"rendered":"\n

About Filmstro<\/h2>\n\n\n\n

Filmstro<\/a>\u00a0is a SaaS and desktop application vendor, offering a unique music editing and digital composition service for multimedia producers. This small company has been in existence for approximately 5 years, and hosts a website, proprietary SaaS and audio processing services on AWS. There is also a proprietary desktop application that loads assets from AWS.<\/p>\n\n\n\n

The Challenge<\/h2>\n\n\n\n

Despite being able to service their own requirements in terms of functionality, such as processing and serving assets to the website and desktop application, they were doing so from just a single environment and VPC (production). Resources were deployed into public subnets too, with little understanding of how to privatise these.<\/p>\n\n\n\n

Another cause for the engagement was a desire to migrate away from EC2 instances and a heavy reliance on large EFS volumes for asset storage (currently 1.2TiB), in a bid to improvement cost optimisation.<\/p>\n\n\n\n

The Solution<\/h2>\n\n\n\n

Devoteam Consulting provisioned two new CloudFormation templated VPCs \u2013 staging and production \u2013 replete with private and public subnets, internet gateway, NAT gateway and baseline security groups. Into each VPC, they deployed a new ECS Fargate (serverless) stack to run containerised versions of Filmstro\u2019s audio processing software. Given the batch-processing nature of this workload, the ECS tasks were configured to run on a poll, which can be adjusted by the client per environment.<\/p>\n\n\n\n

AWS DataSync copies this data into a small EFS volume. When the containers execute, the EFS contents are batch-processed by the containers. There is a second DataSync task that exports processed files to another S3 bucket, which acts as source for AWS CloudFront.<\/strong><\/p>\n\n\n\n

Filmstro will eventually remove the dependency on EFS themselves, at a later date, given the high relative complexity of this refactoring. Each environment has been given its own CloudFront distribution and Web Application Firewall. Rules can therefore be customised on each firewall, in order to keep unsolicited use of CloudFront to a minimum. All deployed resources are private-by-default.<\/p>\n\n\n\n

Finally, a Windows build server was migrated into the same private subnets. This can also only access via the VPN.<\/strong><\/p>\n\n\n\n

The Benefits<\/h2>\n\n\n\n

Filmstro are now in a better position to: begin building release pipelines; audit and categorise their short and long-term storage policies & lifecycles; utilise their new multiple environments in far more secure way than before; enjoy a reduced maintenance overhead and technical debt; leverage AWS managed services and serverless.<\/p>\n\n\n\n

The overall benefits include:<\/h3>\n\n\n\n

Security enhancement<\/strong><\/h4>\n\n\n\n