Amazon Elastic Transcoder VS Identity-Aware Proxy

Alternatively, if your Internet connection can handle it, you could upload your videos to a cloud service that processes them for you. For example, Amazon's AWS has a transcoding service called Elastic, which charges 3 cents per minute of video (half of that if it's lower than 720p). Might be worth the reduced time and effort for business use. Source: 11 months ago

If you're looking for an AWS specific solution, check out Amazon Elastic Transcoder. I think it'll do what you want with a pipeline and you can do it serverless. Source: over 1 year ago

If you use https://aws.amazon.com/elastictranscoder/ then you don’t need a computer, it’s a managed service, get your files to s3 somehow and thats it. There are some other services from other providers that can do the same too, I strongly encourage to look into that, unless you have specific encoding specs that you can’t do somewhere. Source: almost 2 years ago

However compressing on the server is the better option in case you want to generate gifs, thumbnails, and different sizes and formats of the video. A lot of big video streaming companies will use something like Amazons media convert. Source: over 2 years ago

This is how I'd do it, but instead of using EC2 for step 5 I'd look into Elastic Transcoder. Source: over 2 years ago

That is not how you do Zero Trust. You want to use an Identity Aware Proxy. There are lots of ways you can implement this with Google as your core auth. For example Pomerium or oauth2-proxy. Source: 5 months ago

It's like this, which may be what you're referring to: https://cloud.google.com/iap. Source: about 1 year ago

If System A is operated by a user in realtime, I would lean toward using strong user or app identity (Firebase Authentication, Firebase App Check or Identity-Aware Proxy). But that would mean major modifications to System A, and you described it as a "closed system" so maybe that's not possible? Source: about 1 year ago

Put Identity-Aware Proxy in front of your application. It will block anyone who is not from the right domain or in your access control list. This option is useful if you only want to allow a list of users known ahead of time, like for a company-internal app. Source: over 1 year ago

You could use IAP but that would require that they sign in i.e. When they try to access the application, it would ask them to sign in and then it will reject any sign in which is not from the email of *@customerdomain.com. If you don't wish to use IAP, you can also include the entry 'login: always' in your app.yaml which then forces users to sign in and your code will check that the email address is from... Source: over 1 year ago