Skip to content

Latest commit

 

History

History
20 lines (14 loc) · 2.46 KB

README.md

File metadata and controls

20 lines (14 loc) · 2.46 KB

CloudFormation Configuration

The CloudFormation configuration follows the Quick Start guide published by AWS and its CloudFormation template. I recommend to read the guide before reading any further.

Here below I am describing the step-by-step procedure I follow to set this up and the changes I've made.

  1. Go to CloudFormation -> Create a new Stack, then Choose a template -> Upload a template to Amazon S3 and upload this CloudFormation template. This is basically the same CloudFormation template provided in the Quick Start guide but I added few IP addresses related to GitHub webhooks (useful if you're integrating this with GitHub). Please check that the three GitHub hooks IP addresses are still valid here (GitHub changes them for time to time). If not, add the new ones under AllowedIps in the CloudFormation template.
  2. Put a name for Stack Name and leave the rest as it is.
  3. Click on Next then tick the box to allow to create a role, click OK and wait for the CloudFormation template to complete.
  4. Click on Output and copy the values of GitPullWebHookApi and PublicSSHKey. You will need these values in the next steps.
  5. Create the webhook in GitHub following these instructions. Use the value of GitPullWebHookApi as Payload URL. At the end take note of the secret as you will need it later.
  6. Add the public key in your GitHub repo under Settings -> Deploy keys. Use the value of PublicSSHKey retrieved previously.
  7. Go back to CloudFormation and modify the value of parameter ApiSecret. Use the secret set up in the GitHub webhook and update the CloudFormation stack.

Test the webhook

  1. Push a dummy commit, then go to Settings -> Webhooks -> Edit and check under Recent Deliveries that the webhook has been triggered from GitHub. You can redeliver a trigger under Recent Deliveries by clicking on the three dots and then on the Redeliver button.
  2. Check that the S3 bucket associated with the webhook contains the zip file with the GitHub repo. Note that the S3 buckets replicates the URL structure of your branch.
  3. If nothing happened, check that the Lambda function was triggered under Lambda -> Monitoring and check the CloudWatch logs to see what happened.