Use CloudFront

Now that we have a cloudfront distribution that sits in front of our private S3 bucket, let's strip out all that signed URL stuff.

Signed URLs are useful for truly private content, but if all you need is more protection and control over files that you want to make publicly accessible, a CDN is a better choice. CDN's like CloudFront not only offer better security than serving files directly from S3 (due to more granular controls, firewalls, and DDoS protection), but they also offer better performance.

Assignment

Remove all the logic in Tubely related to signing URLs
- Remove generatePresignedURL function and all references to it
- Remove the dbVideoToSignedVideo method and all references to it
- In handlerUploadVideo don't store the bucket and key as comma separated values in the video_url field.
Store an actual URL again in the video_url column, but this time, use the cloudfront URL. Use your distribution's domain name (including the https:// protocol), and then dynamically inject the S3 object's key. Set the distribution's domain name in your .env and grab it from the apiConfig's s3CfDistribution field.
Ensure your Tubely account only has a single video uploaded, and that it's the vertical one.

Run and submit the CLI tests.