cloudnative/lambda-chat

A chat application without servers - using only AWS Lambda, S3, DynamoDB and SNS

lambda-chat's Issues

Add to awesome-functions

It looks like a good candidate for https://github.com/plutov/awesome-functions

Why is polling used?

Isn't it possible to subscribe to push notification without the need of polling S3 for updates?

Document SNS payload format

What is in the SNS message?

Write instructions to provision Lambda dependencies

• IAM Policies and Roles
• SNS topic and subscriptions
• DynamoDB table

Write website code that sends msgs to SNS

Have a simple way to update the lambda function code

Both functions. Perhaps kappa?

A Chatbot Nobody can Chat.

LOL.

Have a simple way to update the website code

Document this

Write Lambda function: SNS -> DynamoDB

Read the payload of the SNS message and put that into a DynamoDB table

Write initial setup instructions for website

This could be a shell script of AWS CLI commands

kappa commands are outdated

The kappa commands in the README are not up to date.

Amazing!

That's all.

Document S3 object JSON format

The file written by Lambda, and read by the website

Pease update README for DynamoDB

How do we setup DynamoDB Stream aspect of this?

Store config somewhere

We have a little config issue - it needs to be stored somewhere so it can be ready by

• the website
• the setup scripts
• the lambda functions

Config are things like

• the region
• the S3 bucket and key
• the DyanmoDB table name
• the SNS name or ARN

Ideas?

When do ./resources.py cf

Hi, Thanks for your good demo codes. When I do ./resource.py cf, there is as following error.

ERROR
Resource Subscription required in type AWS::SNS::Topic
Resource Subscription required in type AWS::SNS::Topic`

profile argument to resources.py?

I am following your instructions, but when I get to the point of running resources.py, the "cf" bit seems to work, but the next step fails because the resources.py script is looking for a --profile argument and you instructions say nothing about that:

./resources.py launch --region=us-west-2
Usage:
resources.py cf
resources.py launch --region= --profile=
resources.py update --region= --profile=
resources.py delete --region= --profile=
resources.py output --region= --profile=

Document the clean up process

To delete all resources created as part of getting this up and running.

It might also be worth having a reset script that clear any state and gets the system back to the initial one without any data. I'm sure we will use this as part of testing.

Write Lambda function: DynamoDB stream -> S3 object

Take the last 20(?) messages from DynamoDB and put them into an S3 object to be read by the website