🔥(project) remove lambdas and Cloudfront configs from the project #2730
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
As Cloudfront is not used anymore on project Marsha, removing it totally.
Cloudfront signed URLs have been removed from Marsha project. Removing it from the tray.
There was a problem hiding this comment.
Pull Request Overview
This PR removes all AWS Lambda functions and CloudFront configurations from the Marsha project as media files are now hosted and delivered via Scaleway instead of AWS.
Key changes:
- Removed CloudFront configuration variables and credentials from deployment templates
- Deleted entire AWS Lambda codebase (convert, medialive, mediapackage, elemental-routing, migrate)
- Removed AWS infrastructure provisioning (VPC, S3 buckets, IAM roles, security groups)
- Updated code references from CloudFront to generic storage terminology
Reviewed Changes
Copilot reviewed 138 out of 157 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| src/tray/vars/vault/main.yml.j2 | Removed CloudFront credentials template section |
| src/tray/vars/all/main.yml | Removed CloudFront-related configuration variables |
| src/tray/templates/services/app/* | Removed CloudFront private key secrets and volume mounts from Kubernetes templates |
| src/backend/marsha/settings.py | Commented out AWS MediaLive/MediaPackage settings and removed CloudFront configuration |
| src/backend/marsha/core/utils/cloudfront_utils.py | Deleted CloudFront URL signing utility module |
| src/backend/marsha/core/serializers/* | Updated comments from CloudFront to generic storage references |
| src/backend/marsha/core/tests/* | Removed CloudFront-specific tests and updated test URLs to Scaleway |
| src/aws/* | Deleted all AWS infrastructure files (Lambda functions, Terraform configs, IAM roles) |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
As everything has been migrated out of AWS, lambdas are not used anymore. Removing them from the project.
As everything have now been migrated from AWS to Scaleway, removing all AWS provisioning and configuration.
kernicPanel
force-pushed
the
remove-cloudfront
branch
from
09af162 to
5053f7d
Compare
kernicPanel
approved these changes
Oct 24, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposal
Now that Marsha media files are hosted and delivered via Scaleway, we can safely decommission the unused AWS Lambda functions and remove the CloudFront configurations.
Additionally, the provisioning of related AWS resources can also be cleaned up.