Are api call rate quotas adjustable in ivs?

The Amazon IVS API transactions per second (TPS) rate is not currently adjustable. It does not appear that there are often cases where more than 5 channels would need to be created within a second, however, we would be happy to evaluate your use case as a product feature request.

1. Depending on the application of the videos, the video resolution can either be set on the broadcaster side or the player side. For implementation on the broadcaster side, the videos could be combined into a single stream that is then passed to Amazon IVS. An example of this would be a scene within OBS that includes all 4 videos at their respective resolutions. An alternative solution to this would be to have 4 players on the viewer side that are set to different resolutions. Using IVS Player methods such as setQuality (https://aws.github.io/amazon-ivs-player-docs/1.2.0/web/interfaces/player.html#setquality) or setAutoMaxQuality (https://aws.github.io/amazon-ivs-player-docs/1.2.0/web/interfaces/player.html#setautomaxquality) would allow for the player(s) to playback at a specified quality (or max ABR quality). However, it is worth noting that each implementation has it's respective pros and cons. For example, having multiple players on the viewer side requires a decent network connection and hardware.

One demo/sample application that may help provide some guidance on how to achieve multiple players, is the Multiple-Players sample application (https://github.com/aws-samples/amazon-ivs-basic-web-sample), which shows how to instantiate multiple Amazon IVS players simultaneously.

2. Amazon IVS currently works with AWS Lambda function(s). However, please feel free to specify a more specific question regarding the integration of Amazon IVS and AWS Lambda.

Thanks for your help.
When users load and play the video, I want to use AWS Lambda functions to validate the request before aws returns the live streaming. I didn't find where to add the AWS Lambda functions when I edited the ivs channel.