Lambda Function URL: Handling High Concurrency Without 429 Errors

I have a Lambda function with the following SAM template configuration:

AWSTemplateFormatVersion: '2010-09-09'
Transform: AWS::Serverless-2016-10-31
Description: An AWS Serverless Application Model template describing your function.
Resources:
  SIMKULIAHendpointscrappingscheduleandfillattendace:
    Type: AWS::Serverless::Function
    Properties:
      CodeUri: .
      Description: 
      MemorySize: 1000
      Timeout: 900
      Architectures:
        - x86_64
      EphemeralStorage:
        Size: 1000
      Environment:
        Variables:
          # Environment variables omitted for brevity
      EventInvokeConfig:
        MaximumEventAgeInSeconds: 21600
        MaximumRetryAttempts: 2
      FunctionUrlConfig:
        AuthType: NONE
        InvokeMode: BUFFERED
        Cors:
          AllowCredentials: false
          AllowOrigins:
            - '*'
          ExposeHeaders: []
          AllowHeaders:
            - autosim_usk_api_key
          AllowMethods:
            - GET
            - POST
          MaxAge: 0
      ImageUri: >-
    
      PackageType: Image
      # Other properties omitted for brevity

I'm experiencing throttling issues with CloudWatch when my Lambda function is invoked concurrently. This is causing problems with logging and monitoring my function's performance. My questions are:

How can I increase the CloudWatch throttling limits for my Lambda function to handle a higher number of concurrent invocations? Are there any specific settings in the Lambda or CloudWatch configuration that I should adjust to mitigate this throttling issue? What are the best practices for scaling CloudWatch usage in high-concurrency Lambda scenarios?

Any insights or suggestions on how to resolve this CloudWatch throttling problem would be greatly appreciated. Thank you!