Amazon CloudWatch Logs removes Log Stream transaction quota and SequenceToken requirement

Starting today, Amazon CloudWatch Logs is removing the 5 requests per second log stream quota when calling Amazon CloudWatch Logs PutLogEvents API. There will be no new per log stream quota. With this change we have removed the need for splitting your log ingestion across multiple log streams to prevent log stream throttling.

Amazon CloudWatch Logs is also removing the requirement of providing a sequence token when calling Amazon CloudWatch Logs PutLogEvents API. CloudWatch Logs will still accept PutLogEvents API request with sequence token and return a PutLogEvents API response with a sequence token to maintain backwards compatibility. Your PutLogEvents API calls will be accepted, and CloudWatch Logs won't return InvalidSequenceToken errors irrespective of providing an invalid sequence token. We expect this change to simplify your integration with CloudWatch Logs because you won't need to coordinate across different clients writing to the same log stream.

With the above improvements, you can call PutLogEvents API in parallel on the same log stream with higher throughput which is now only bound by your per account and per region PutLogEvents quota. These improvements to our PutLogEvents API’s are available in all AWS Commercial regions.

Refer to our PutLogEvent’s API, LogStream API, and quota documentation for more information.