doitintl / awslack Goto Github PK

Just trying out your awesome system here and I've hit a snag.

The API Token I used was (sorry folks its invalid now) was:
xoxb-314645039731-388829491314-kG1gSKFcztlKBqymDWybdNWU

I tried regenerating and changing several times to no avail.

I'm going to work around this by downloading the template and removing the param constraint. Figured I'd let you know at any rate.

I would like to replace aSlack to AWSlack everywhere, including:

• code
• CloudFormation URL
• Readme
• etc.

Deploying is failing if the current region is not US-East-1, to overcome it, it is required to create a bucket in the specific region, upload the code.zip to there and change the template to point to the new bucket.

I would like to have more ready-to-go templates such as

• New EC2 Instance Started/Stopped
• Autoscaler events (EC2 Instance Added/Removed to/from the group)
• Fix a typo from 'Bucket bucket-name create' to 'Bucket bucket-name created'
• Health Events
• AWS Console Sign-In Events

I tried to deploy the CFN but I get the following error:

GetObject for awslack/source/code.zip. S3 Error Code: AllAccessDisabled. S3 Error Message: All access to this object has been disabled

Hi,

If I want to get events from all regions in an account I have to create the solution in each region.

This creates a DynamoDB table in every region. Which means I have lots of tables with lots of rules to manage.

How hard would it be to create a "Centralised" Dynamo version of this for those of us living in multiple accounts in multiple regions?

We could run a master template in the master account which would init the db tables.
Then we could use a child account stack set to push out from a master account to the child accounts one that doesn't create a table rather refers to the central table in the master account instead.

A bit trickier to setup no doubt but easier to manage once setup (esp from a rules perspective).
The only downside would be if I wanted different rules for an account / region. Then the rules would need additional information to help with that and the rule checker would need to validate this additional information.

This is more a feature request than an issue so I don't mind you closing this down as I don't know where else to put this :) If I get time I will work on this in a fork but I can't help but think you'd be quicker than me at resolving this one :D

As someone mentioned, this is what we should be doing so the bot avatar will be displayed correcly

If you set `username` (which I was already doing) and `as_user` to true (I wasn't doing this) then it shows the avatar correctly.

@srfrnk - can you please add a bit more explanations to the AWSlack README regarding the tests, messages etc like we have on gSlack?

Can we please rename the tables to:

• awslack.configs
• awslack.tests