Bitten by the bug of a new technology you spend an afternoon immersing yourself in the current state of the art. You deftly search your way to one after another fascinating blog posts, GitHub projects, and product offerings.
Before you know it your browser has so many tabs that there is no longer room for favicons, and the fan in your laptop sounds like a helicopter about to take off.
After a couple hours of reading you decide to give the tech a whirl and settle on what seems to be the most promising post that combines the necessary conditions of being sufficiently complex to be of interest and simultaneously achievable for a rookie. The post promises that with an investment of a few minutes of your time you'll have everything up and running.
Meanwhile back in the real world you are still hacking away two hours later with more questions than answers.
This is exactly what happened to me on my first excursion through the serverless world and a test run of AWS Lambda. I read about the new AWS Lambda integration blueprints and attempted to use the
slack-echo-command blueprint that was purported to make it "even easier" to get started. Unfortunately, after following the rather vague steps and piecing together information from across the AWS documentation all I had accomplished was generating several different error messages.
What broke the logjam was a post by Tony Hirst on the OUseful.info blog. Although a few things have changed in the AWS UI since the post was published in March 2016 it is still accurate enough to not warrant a re-write. Instead I'll include the links below in the case it saves someone else an hour or two:
- Implementing Slack Slash Commands Using Amazon Lambda Functions – Getting Started
- Implementing Slash Commands Using Amazon Lambda Functions – Encrypting the Slack Token