Elastic bean stitch has no concept of repo. An application version is just a package that is stored on S3.
What you need to do is post the repo anywhere, like Github or Bitbucket. Then you share your changes, as with any other project. When the time comes to deploy the version on Elastic Beanstalk, you should run git aws.push , not something like git push origin . Of course, this assumes that you have already configured AWS git dev tools .
As an aside, I would recommend that you set up an IAM user account for each developer so that everyone has their own set of AWS passkeys. This will allow you to revoke deployment access for a person without affecting anyone.
source share