https://lakefs.io/ logo
Join Slack
Powered by
<@U017YJ22161> Thanks for the fast response! 1. It...
# help
y
@Yoni Augarten Thanks for the fast response! 1. It gave me message like 
FailedMount MountVolume.SetUp failed for volume 'lakefs-config': configmap not found
2. Sorry, maybe I am not clear about the S3 gateway domain. Should I add those domains to ingress? Or should I change access point on S3? Again sorry for my lack of understanding. 3. I will add logs on the reply! Thank you so much!
2021-08-04T143031.715242609Z time=“2021-08-04T143031Z” level=error msg=“bad S3 PutObject response” func=“pkg/block/s3.(*Adapter).streamToS3” file=“build/pkg/block/s3/adapter.go:228" error=“s3 error: <?xml version=\“1.0\” encoding=\“UTF-8\“?>\n<Error><Code>AccessDenied</Code><Message>Access Denied</Message><RequestId>**</RequestId><HostId>**</HostId></Error>” host=“localhost:55049" method=POST operation=PutObject path=/api/v1/repositories request_id=67a753c3-2e64-4831-91e6-b61769a88c44 service_name=rest_api status_code=403 url=“https://kunlun-lakefs-poc.s3.amazonaws.com/dummy”
Copy code
secrets:
  databaseConnectionString: <postgres://AAA:BBBB@CCCC.XXXX.us-east-1.rds.amazonaws.com:5432/postgres?sslmode=disable>
  authEncryptSecretKey: 'XXXX'

lakefsConfig: |
  blockstore:
    type: s3
    s3:
      credentials:
        access_key_id: MY ACCESS KEY
        secret_access_key: MY SECRET KEY
      region: us-east-1

  gateways:
    s3:
      domain_name: s3.lakefs.***.io
Copy code
ingress:
  enabled: true
  annotations: {}
  hosts:
    - host: lakefs-dev.****.io
      paths:
        - /
  tls:
    - secretName: lakefs-dev.****.io.tls
      hosts:
        - lakefs-dev.****.io
g
Hey @Yongchan Hong According to 2: the s3 domain is used by lakeFS to distinguish between s3 requests to other requests ( regardless of the routing configuration) . For example If your domain is example.io And you configured the s3 gateway to be s3.example.io So A request to my-bucket.s3.example.Io will be handled as an s3 request with our s3 gateway to my-bucket repository Any other request would be handled with our rest API
According to 3 It seems like there is a problem with the credentials Are you able to access kunlun-lakefs-poc bucket in s3 with the credentials you used in lakectl.yaml?
Open in Slack
PreviousNext
Powered by