Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lambda invokeMode as RESPONSE_STREAM is not set in deployment #12409

Open
ibrahimjelliti opened this issue Apr 2, 2024 · 0 comments
Open

Lambda invokeMode as RESPONSE_STREAM is not set in deployment #12409

ibrahimjelliti opened this issue Apr 2, 2024 · 0 comments

Comments

@ibrahimjelliti
Copy link

Issue description

Hi,
I am create a lambda with response stream as response type. i define the response type in serverless.yml but its not applying to the deployed lambda or appears as option in "Type": "AWS::Lambda::Url" so the URL takes the default value BUFFERED.

Context

serverless.yml

  Filters:
    handler: src/functions/filters.handler
    memorySize: 128
    timeout: 30
    url:
      invokeMode: RESPONSE_STREAM

cloudformation update stack json:

    "FiltersLambdaFunctionUrl": {
      "Type": "AWS::Lambda::Url",
      "Properties": {
        "AuthType": "NONE",
        "TargetFunctionArn": {
          "Fn::GetAtt": [
            "FiltersLambdaFunction",
            "Arn"
          ]
        },
        "Cors": {
          "AllowHeaders": [
            "Content-Type",
            "X-Amz-Date",
            "Authorization",
            "X-Api-Key",
            "X-Amz-Security-Token",
            "X-Amzn-Trace-Id"
          ],
          "AllowMethods": [
            "*"
          ],
          "AllowOrigins": [
            "*"
          ]
        }
      }
    },

I am expecting to have invoke mode in the json as RESPONSE_STEAM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant