We are storing our PHP project on github.
For fast deployment we are using .bat file for git pushing changes to AWS Elastic Beanstalk cloud:
\"C:\\P
I implemented a workaround because this is a bug of Amazon.
I setup a git account in a server (I used Gitlab, free private repositories and unlimited collaborators), you can use any that you want (github, gitlab, your server).
The process between you and the git server is reliable, you only push the changes, always. In the EC2 server, I setup a git repository (you can use the configuration file .ebextensions/*.config or do manual, I suggest manual to not setup in all your instances) which is connected to my git server and from EC2 server execute git pull and a git aws.push.
You are able to setup for example a Web Hook to notify when you do a git push and then do the git pull and git aws.push automatically. in my case I prefer decide when deploy using SSH, and this is not always when I push commits to my git server.
In this way, do the git aws.push from EC2 server to Elastic Beanstalk server is very fast, doesn't matter if it push everything or only the changes.