AWS IVS API Rate limit

The IVS rate limits you've mentioned are soft limits, which means they can be increased by contacting AWS Support and requesting a limit increase. However, it's essential to evaluate if the new limits align with your use case.

Given that you expect to delete and recreate 300 stream keys/sec and 300 channels/sec, it exceeds the default rate limits. You should consider implementing a queue to handle these use-cases or optimize your architecture.

Possible approaches:

1. Request a limit increase: Contact AWS Support to request an increase in the rate limits for your specific use case.
2. Implement a queue: You can use a service like Amazon SQS to manage the creation and deletion of stream keys and channels. With a queue in place, your application can process requests at a rate within the IVS limits, while still allowing a larger number of streams to be managed over time.
3. Optimize your architecture: Evaluate if it's necessary to create and delete channels and stream keys for every streaming session. Instead, you might reuse channels and stream keys, reducing the number of API calls you need to make.

Remember to consider the cost implications and operational complexity when selecting the best approach for your use case.