Series of functional hooks to integrate GIT with AWS S3 via the AWS CLI and the AWS S3 CLI.

• AWS S3 Instance - A fully configured, Amazon Web Services Simple Storage System (S3) instance. More commonly, we would be using an AWS S3 instance that has been configured to host a static website with GIT based deployments. Static Hosting Guide
• AWS Command Line Interface – The Amazon Web Services command line interface (CLI) available here
• AWS IAM Role - A properly configured and permissioned IAM user account and role with access to secret/private keys. This can also be achieved with environmental variables and configuration settings, but AWS' IAM is the best practice for communicating across the AWSCLI. [AWS IAM] (http://aws.amazon.com/iam/)
• GIT – If you're reading this, there's really no point in explaining this dependency. GIT is awesome. We love GIT.
• UNIX/Bash Compatible Environment –

From a local machine, triggered after each GIT Commit (as this hook is stored in .git/hooks/post-commit), the AWS CLI will connect to a specified S3 bucket via profile specific credentials to automate a secure, recursive copy protocol. This process will remove any remote files that do not currently exist on the local machine, with the exception of any files or expressions declared in the ignore statement. By default, we strictly ignore the .git object and all of its children.