|  | @@ -9,7 +9,7 @@ Inspired by
 | 
	
		
			
				|  |  |  [How I hacked Slack into a community platform with Typeform](https://levels.io/slack-typeform-auto-invite-sign-ups/)
 | 
	
		
			
				|  |  |  and Socket.io's Slack page.
 | 
	
		
			
				|  |  |  
 | 
	
		
			
				|  |  | -This project supports Heroku, Azure and Cloud Foundry.
 | 
	
		
			
				|  |  | +This project supports Heroku, Azure, Cloud Foundry, and Amazon Web Services (AWS).
 | 
	
		
			
				|  |  |  
 | 
	
		
			
				|  |  |  [](https://heroku.com/deploy)
 | 
	
		
			
				|  |  |  [](https://azuredeploy.net/)
 | 
	
	
		
			
				|  | @@ -67,6 +67,20 @@ You can test your token via curl:
 | 
	
		
			
				|  |  |  
 | 
	
		
			
				|  |  |  Add the application settings that are defined in the environment variables above.
 | 
	
		
			
				|  |  |  
 | 
	
		
			
				|  |  | +### Amazon Web Services (AWS)
 | 
	
		
			
				|  |  | +
 | 
	
		
			
				|  |  | +If you have an AWS account and have already installed and configured the AWS CLI tool, you can easily deploy this application to API Gateway and Lambda via CloudFormation in a few minutes.
 | 
	
		
			
				|  |  | +
 | 
	
		
			
				|  |  | +Instead of editing `config.js`, take these steps:
 | 
	
		
			
				|  |  | +
 | 
	
		
			
				|  |  | +1. Copy `aws/config.example.sh` to `aws/config.sh`
 | 
	
		
			
				|  |  | +2. Edit the values in `aws/config.sh`, which correspond to the variables described above, plus these:
 | 
	
		
			
				|  |  | +    * `StackName`: the name of the CloudFormation stack to create
 | 
	
		
			
				|  |  | +    * `S3BucketArtifacts`: the name of an existing S3 bucket you have write access to, for storing deployment artifacts
 | 
	
		
			
				|  |  | +    * `S3PrefixArtifacts`: the prefix to use within that S3 bucket for all deployment artifacts written
 | 
	
		
			
				|  |  | +3. Run `aws/deploy.sh` to create the CloudFormation stack and deploy your application, outputting the URL
 | 
	
		
			
				|  |  | +4. (Optional) For a friendlier URL, log into the AWS web console and establish a custom domain pointing to the API Gateway stage deployed in step 3.
 | 
	
		
			
				|  |  | +
 | 
	
		
			
				|  |  |  ## Run
 | 
	
		
			
				|  |  |  [Node.js](http://nodejs.org/) is required.
 | 
	
		
			
				|  |  |  
 |