One method you could use to approach this would be to utilize a scheduled EventBridge rule to trigger the Lambdas automatically every 24 hours and trigger an S3 Export Task for the most recent day's log data.
However, another way to ensure that log data is continually archived from CloudWatch to S3 without losing data outside the window of running the Lambdas would be to utilize a subscription filter on the log groups you wish to archive, to be delivered to a Kinesis Firehose delivery stream with an S3 destination.
[CW Log Group Subscription Filter] -> [Kinesis Firehose] -> [S3]
By setting the Filter Pattern on the Subscription Filter to capture all logs, this will forward all log data ingested in to the log group to S3 via the Kinesis Firehose delivery stream without needing to run the lambda's to export data. Note that this will only send logs ingested after the creation of the subscription filter to S3. Any logs ingested prior to the subscription filter creation would still need to be exported.
Resources for configuring this can be found here:
S3 server access logs to Cloudwatch?Accepted Answerasked 4 years ago
Cloudwatch logs to S3 continuous exportasked 4 months ago
Specific Cloudwatch log groups not responding to queriesasked 6 months ago
Are we able to export only parts of the Amazon CloudWatch logs to Amazon S3?Accepted Answerasked 2 years ago
How to stream CloudFront real time logs to cloudwatchasked 6 months ago
Archiving CloudWatch logs no with data lossasked a month ago
RDS/Postgres logs to S3Accepted Answerasked 4 years ago
how to push only error and warning logs to cloudwatchasked 6 days ago
Is CloudWatch "Vended Log" cost for VPC Flow Log delivery to S3 calculated on GB before or after compression?asked 8 months ago
save logs of each outbound data transfer response from cloudfront to s3asked 3 months ago