Skip to content

README.md

Latest commit

 

History

History
56 lines (45 loc) · 2.43 KB

README.md

File metadata and controls

56 lines (45 loc) · 2.43 KB

apex-telegram-lambda-bot

This project is telegram simple-bot with Apex and AWS Lambda and python.

Getting Started

Project description

  • telegram bot : two example 'echo bot' and 'flickr interest photo bot'
  • Language : Python 3.x (tesed on 3.6)
  • Run on AWS Lambda and Apex

Example telegram bot

Install

First, Make sure that Apex is installed.

$ curl https://raw.githubusercontent.com/apex/apex/master/install.sh | sh

Second, Change your IAM role and telegram token.

  • project.json : 'role' field
  • functions/echo/main.py, functions/echo/main.py : 'TELEGRAM_TOKEN', 'FLICKR_API_KEY' field

Third, deploy and build API Gateway

Deploy your api with Apex

$ apex deploy

After deploying, you can find "telegrambot_echo" and "telegrambot_flickr" on your AWS Lambda console. Then, add trigger to AWS API Gateway with public access. Now, you can get api url on API Gateway console. (eg. https://sometoken.execute-api.us-east-1.amazonaws.com/prod/telegrambot_flickr)

Finally, connect telegram setWebhook

Add telegram bot with webhook method like 'https://api.telegram.org/bot{YOUR_TELEGRAM_BOT_TOKEN}/setWebhook?url={YOUR_API_GATEWAY_URL}'

$ curl -XPOST "https://api.telegram.org/bot12345:FAKEkeyyupcjzzuyaIOXI/setWebhook?url=https://sometoken.execute-api.us-east-1.amazonaws.com/prod/telegrambot_flickr" -v

Addtional note for Python pip package on Lambda

I used pip packages on Lamba deploy. Please see 'function.json'. On 'apex deploy', it will invoke trigger 'pip3 install'. ('setup.cfg' file is need for pip3 command. If that file is not exist, pip3 occured error.)

{
    "description": "sample for telegram echo bot",
    "hooks":{
      "build": "pip3 install -r requirements.txt -t modules",
      "clean" : "rm -rf modules"
    }
  }

See also