Setup AWS infra (ECS, RDS, S3, Lambda, MediaConvert)

DevOps — incorrectly specified categories?

Project translated automatically. Log in or register, to view the original There is a service that is in the last stages of development.The service works with streaming audio to users (HLS), both one-stream (radio) and multi-stream (music and podcasts).The service consists of: - backend - NodeJS, Docker cms and client frontend - React, Docker - Amazon RDS (PostgreSQL), S3, MediaConvert, Lambda Currently installed S3, MediaConvert and almost finished Lambda, which will take audio, downloaded from the adminke, automatically convert to HLS for streaming and return it to S3.Backend and the two fronts already rolled in Docker work locally and are connected to RDS and S3.Let’s tell you more in detail at the call.Task: You need to deploy the infrastructure in AWS to test to transfer the project to the customer.That is, you need to set up and lift in the AWS Elastic Container Service back and both fronts so that everything worked with MultiAZ without any problems and could be scaled automatically, connected to RDS, worked with the MediaConvert flow and launched streaming for users.Documentation of the process.The customer’s requirements are mainly targeted on the bones: storage only on the S3; virtual on the EC2, small traffic on the CloudFront, etc.The budget of the project is desired to $300 but we can review it.

Proposals 2