Best strategy to deploy static site to s3 on github push? [closed]

Answer 1

I had the same goal some time ago and have now released a little tool, which solves the problem at least for me. It uses AWS Lambda and deploys a specific branch of the repository to S3 after push. You can take full advantage of the GitHub deploy key, which has fewer permissions as personal access tokens and can be configured per repository.

Please take a look at github-bucket, it might help you too.

Answer 2

You can set this up with a very simple 2-step CodePipeline. Basically, you just fill out the different sections in the AWS Console. There's no need for a separate CI tool and its added complexity.

In the first step of the pipline, pull from Github and store in S3. You can easily set this up through the AWS Console.

In the next CodeDeploy step, you can use the AWS CLI (pre-installed in CodeDeploy) to do a

cd /path/to/public/directory && aws s3 sync --acl public-read --delete . s3://your.bucket.name

You'll have to set the environment variables for AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY so that AWS CLI can run during your deploy step, and that can also be done in the AWS console for CodeDeploy, in the Advanced section under "environment variables". Once the environment variables have been set and if that AWS user has the correct permissions, you can run any aws-cli command you want inside your CodeDeploy.

Once this is done, when you check in to Github, CodePipeline will kick off, and a few minutes later your files will be on S3.

Answer 3

If you are using TravisCI, the deployment is pretty straight forward. The only part you will need to add to your .travis.yml is :

deploy:                         
  provider: s3                         
  access_key_id: "YOUR AWS ACCESS KEY"
  secret_access_key:
    secure: "w/DlbHt1+IAMENCRYPTED"
  bucket: "YOUR BUCKET"

My blog post explains all the details for the AWS side (user setup, IAM and S3 bucket configurations) as well as the github and travisCI side.

Answer 4

Perhaps overpowered for your simple use case, but you could create a very simple CodePipeline to push your github repository to S3.

Answer 5

I have used Deploy Bot in the past and I have been quite happy with it.

It can push to S3 or even FTP via Git and also it can run your build scripts and even push a notification to Slack for you.

https://deploybot.com/

Answer 6

I know it's not git deploy.... But Instead of setting up a CI box, I just used s3cmd.

http://s3tools.org/s3cmd

Executing this command syncs my build directory with s3.

s3cmd sync -r ~/code/mysite/build s3://www.mysite.com --delete-removed

I'm using it on Linux. Not sure what their OSX and Windows stories are.

If you're really after a git push solution, you could set up a timed job which pulls your git repo to a folder and then executes this against it. I do this elsewhere on a cheap Linux VM. Unless you're going to go full CI though, there's probably not much point.