Verbose debug for LFS:
mkdir my-project cd my-project git init git remote add origin s3://my-git-bucket/my-repo
on your local machine if you haven't already. Verify the installation with git lfs version . lfs s3 account
Assign a dedicated IAM User with an explicit, least-privilege JSON policy.
"Version": "2012-10-17", "Statement": [ "Effect": "Allow", "Action": [ "s3:PutObject", "s3:GetObject", "s3:DeleteObject", "s3:ListBucket" ], "Resource": [ "arn:aws:s3:::company-git-lfs-store", "arn:aws:s3:::company-git-lfs-store/*" ] ] Use code with caution. Step 3: Deploy the LFS-S3 Bridge Verbose debug for LFS: mkdir my-project cd my-project
Here is a helpful review covering the setup, benefits, and potential pitfalls.
+------------+ +------------------+ +------------+ | | 1. Git Push | | 2. Authenticate | | | Git Client| ---------------> | Git Server | ---------------> | AWS IAM | | (Local) | | (GitHub/GitLab) | | | | | +------------------+ +------------+ | | | | | | 3. Request Token v | | | <-------------------------+ | | | | | | 4. Upload/Download LFS Binaries v | | <=======================================================> [ S3 Bucket ] +------------+ +------------+ The Three-Core Components Git Push | | 2
Open your local .git/config file (or create a root .lfsconfig file to share with the team) and specify your custom S3-backed LFS server URL: [lfs] url = "https://company.com" Use code with caution.