Error with lambda request entity too large

[themr97]

I am currently trying to run multiple scenarios for testing my api gateway, whenever i start this run it gives me the following error as mentioned in my screenshots

this is the command i generally use

artillery run-lambda --region ap-south-1 --count 10 filename.yaml

config:
  target: "https://xx.cloud"  # The target API URL
  phases:
    - duration: 60  # Duration of the test in seconds
      arrivalRate: 100  # Number of requests per second
  http:
    requestTimeout: 60000  # Timeout for each request set to 60 seconds
  plugins:
    expect: {}

scenarios:
  - name: "1"
    flow:
      - get:
          url: "/livefeed/"
          headers:
            accept: "text/plain"
            Authorization: "Bearer xx"
          expect:
            - statusCode: 200
  - name: "2"
    flow:
      - get:
          url: "/feed/"
          headers:
            accept: "text/plain"
            Authorization: "Bearer xx"
          expect:
            - statusCode: 200
  - name: "3"
    flow:
      - get:
          url: "/livefeed/"
          headers:
            accept: "text/plain"
            Authorization: "Bearer xx"
          expect:
            - statusCode: 200

[tganeesh]

I'm also facing similar issue, were you able to resolve this issue?
@Team: When i try with higher configuration like below. It actually completes the test but seems its failed to create the json file

• name: Warm up
  duration: 30
  arrivalRate: 10
  rampTo: 30
  - name: Ramp upto peak
  duration: 60
  arrivalRate: 50
  rampTo: 100
  - name: Sustain peak load
  duration: 60
  arrivalRate: 100
  - name: Cooldown
  duration: 30
  arrivalRate: 75
  rampTo: 20

Below is the command i used to run the test
run-lambda --output ./load-test-report.json --region us-east-1 --environment ${{ inputs.environment }} load-test.yaml

I was able to run the test successfully and create the report if i'm using smaller configuration(minimal load)

I'm using below version to run the artillery in github action

• name: Run Load Test
  uses: artilleryio/action-cli@v1

[tganeesh]

Seems like its an issue with output json size. We had 18 scenarios and this will generate json with more than 2mb