Skip to content

lambda.md

Latest commit

 

History

History
45 lines (34 loc) · 1.72 KB

lambda.md

File metadata and controls

45 lines (34 loc) · 1.72 KB
Raw

Running Welt on AWS Lambda

Instead of a resident process, Welt also runs on AWS Lambda: lambda_function.py serves the same conversation flow on the Lambda Python runtime. template.yaml is an AWS SAM template that creates the function, its IAM role, and the Function URL.

The setup below assumes your agent is already deployed on AgentCore Runtime and your Slack app is created.

Setup

  1. Clone this repository, build the function package, and deploy:

    git clone https://github.com/iwamot/welt.git
cd welt
sam build
sam deploy --guided

    During sam deploy --guided:

    • The stack parameters are SlackBotToken, SlackSigningSecret (Basic Information > Signing Secret), and AgentArn.
    • Answer y to WeltFunction Function Url has no authentication — Slack requests are verified with the signing secret instead.
    • Note the FunctionUrl stack output; the next step needs it.

  2. In the Slack app manifest, start from manifest.yml and replace its settings: section — HTTP serving turns Socket Mode off and receives both events and button presses at the Function URL:

    settings:
  event_subscriptions:
    request_url: https://<url-id>.lambda-url.<region>.on.aws/  # the FunctionUrl output
    bot_events:
      - message.channels
      - message.groups
      - message.im
      - message.mpim
  interactivity:
    is_enabled: true
    request_url: https://<url-id>.lambda-url.<region>.on.aws/  # the same FunctionUrl
  socket_mode_enabled: false

Notes

  • Agent replies are bounded by Lambda's 15-minute cap.
  • sam build && sam deploy redeploys after a change.
  • sam delete removes everything the setup created.