I am trying to deploy LakeFS on AWS ECS with a load balancer in front. I can connect to the landing page just fine using the ALB DNS name ( have not created an Alias record yet as I am just testing). My issue is using the AWS CLI to copy a file into my repo. I followed the steps: 1. Configure profile "lakefs", adding the access keys and region. 2. Created a repo with the storage namespace

<s3://example-bucket/poc/>

3. attempted to copy my file with

aws --profile lakefs --endpoint-url <http://alb_dns_name.amazonaws.com> s3 cp myfile.txt <s3://example-bucket/poc/>

I have checked the security groups and IAM policies but I am at a loss for what is causing this

Hi @tgosselin!

hello

Can you please try the same cp command but use the lakefs URI instead of the repo storage namespace as the copy destination? that is, change

aws --profile lakefs --endpoint-url <http://alb_dns_name.amazonaws.com> s3 cp myfile.txt <s3://example-bucket/poc/>

into

aws --profile lakefs --endpoint-url <http://alb_dns_name.amazonaws.com> s3 cp myfile.txt <<lakefs://your-repo/your-branch/path>>

usage: aws s3 cp <LocalPath> <S3Uri> or <S3Uri> <LocalPath> or <S3Uri> <S3Uri> Error: Invalid argument type

1. Can you please share the command you are running? 2. Can you please look if you see any errors in the lakefs logs?

that is what I was using before and was getting the error? does repo = bucket?

Based on your example (bullets 2-3), you used the repo storage namespace as opposed to the repo and branch name.

1. Configure profile “lakefs”, adding the access keys and region.

2. Created a repo with the storage namespace

<s3://example-bucket/poc/>

3. attempted to copy my file with

aws --profile lakefs --endpoint-url <http://alb_dns_name.amazonaws.com> s3 cp myfile.txt <s3://example-bucket/poc/>

A repository is a lakeFS concept, and it has a storage namespace associated with it. that is repo != bucket