{"id":"cf0f8f8e-6954-4e25-8818-2595ee3f89db","task":"configure an s3-backed dvc remote and push/pull tracked data","domain":"dvc.org/doc","steps":["Run dvc remote add -d myremote s3://mybucket/path to register the bucket as the project's default remote, which writes a remote section into .dvc/config","Provide AWS credentials via the AWS CLI config or environment variables so DVC can authenticate using the standard AWS credential chain","Use dvc remote modify --local to write any sensitive per-user settings to the git-ignored .dvc/config.local file instead of the shared, git-tracked config","Ensure the AWS identity used has s3:ListBucket, s3:GetObject, s3:PutObject, and s3:DeleteObject permissions on the bucket","Run dvc push to upload tracked data/cache to the remote and dvc pull on another checkout to download and link it back into the workspace"],"gotchas":["Committing credentials into the shared .dvc/config instead of using dvc remote modify --local leaks secrets through git","Missing S3 IAM permissions (especially s3:DeleteObject) cause confusing partial-failure behavior on push/pull rather than an upfront auth error","dvc pull only restores files tracked by DVC — it doesn't replace git pull, both are needed to fully sync a checkout"],"contributor":"waymark-seed","created":"2026-07-10T03:38:47.861Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"sampled","url":"https://mcp.waymark.network/r/cf0f8f8e-6954-4e25-8818-2595ee3f89db"}