Christoph Jud
09/02/2024, 8:14 AMenvironment = [
{ name = "LAKEFS_DATABASE_TYPE", value = "dynamodb" }, # Specify the internal database to be DynamoDB
{ name = "LAKEFS_BLOCKSTORE_TYPE", value = "s3" }, # Specify the internal storage type to be S3
{ name = "LAKEFS_DATABASE_DYNAMODB_TABLE_NAME", value="${var.project_name}-${var.lakefs_dynamodb_table_name}" },
{ name = "LAKEFS_BLOCKSTORE_S3_ENDPOINT", value = "<http://s3>.${var.aws_region}.amazonaws.com/${aws_s3_bucket.lakefs_bucket.bucket}" },
{ name = "AWS_REGION", value = var.aws_region },
{ name = "LAKEFS_BLOCKSTORE_S3_REGION", value = var.aws_region },
{ name = "LAKEFS_GATEWAYS_S3_REGION", value = var.aws_region },
{ name = "LAKEFS_AUTH_ENCRYPT_SECRET_KEY", value = random_password.lakefs_encryption_secret.result },
{ name = "LAKEFS_LISTEN_ADDRESS", value = ":8000" },
{ name = "LAKEFS_STATS_ENABLED", value = "false" }, # Disable sending statistics to treeverse
{ name = "LAKEFS_LOGGING_AUDIT_LOG_LEVEL", value = "NONE"},
{ name = "LAKEFS_EMAIL_SUBSCRIPTION_ENABLED", value = "false" }
even with disabling the audit logs, the error persists.
Any ideas?
EDIT:
The error might not come from this error exactly. But still I'd like to disable the audit log to be send externally.
Offir Cohen
09/02/2024, 9:08 AMChristoph Jud
09/02/2024, 9:12 AMChristoph Jud
09/02/2024, 9:16 AMChristoph Jud
09/02/2024, 9:17 AMsecurity.audit_check_interval
(duration : 24h)
- Duration in which we check for security audit.
can I disable this? or set it to infinity?Christoph Jud
09/02/2024, 9:21 AMresource "aws_iam_policy" "lakefs_s3_policy" {
name = "lakefs-s3-policy"
description = "Policy for LakeFS to access S3"
policy = jsonencode({
Version = "2012-10-17",
Statement = [
{
Sid = "lakeFSObjects",
Action = [
"s3:GetObject",
"s3:PutObject",
"s3:AbortMultipartUpload",
"s3:ListMultipartUploadParts"
],
Effect = "Allow",
Resource = "${aws_s3_bucket.lakefs_bucket.arn}/*"
},
{
Sid = "lakeFSBucket",
Action = [
"s3:ListBucket",
"s3:GetBucketLocation",
"s3:ListBucketMultipartUploads"
],
Effect = "Allow",
Resource = aws_s3_bucket.lakefs_bucket.arn
}
]
})
}
Christoph Jud
09/02/2024, 9:24 AMChristoph Jud
09/02/2024, 9:25 AMOffir Cohen
09/02/2024, 9:40 AMOffir Cohen
09/02/2024, 9:46 AMChristoph Jud
09/02/2024, 9:47 AMChristoph Jud
09/02/2024, 9:47 AMChristoph Jud
09/02/2024, 9:48 AMOffir Cohen
09/02/2024, 9:49 AMOffir Cohen
09/02/2024, 10:05 AMOffir Cohen
09/02/2024, 10:06 AMChristoph Jud
09/02/2024, 10:08 AMChristoph Jud
09/02/2024, 10:17 AMChristoph Jud
09/02/2024, 10:17 AMOffir Cohen
09/02/2024, 10:21 AMChristoph Jud
09/02/2024, 10:28 AMChristoph Jud
09/02/2024, 10:28 AMOffir Cohen
09/02/2024, 10:42 AMOffir Cohen
09/02/2024, 10:45 AMOffir Cohen
09/02/2024, 10:55 AMChristoph Jud
09/02/2024, 11:14 AMOffir Cohen
09/02/2024, 12:15 PMJonathan Rosenberg
09/02/2024, 12:47 PMLAKEFS_BLOCKSTORE_S3_ENDPOINT
variable. You use a path-style URL, yet, itβs not specified in the configurations (the default style is virtual-hosting style). Can you try and add:
LAKEFS_BLOCKSTORE_S3_FORCE_PATH_STYLE
with the value true
and try again?
In addition, I can see that you didnβt configure any credentials for S3. That means that your default ~/.aws/credentials
with the default profile will be used, unless youβve configured the env vars with different values. Thatβs perfectly fine, but you need to make sure that they allow you to access your bucket.
It actually doesnβt explain how youβve succeeded with the lakectl calls. Iβll have another look.Christoph Jud
09/02/2024, 1:11 PMChristoph Jud
09/02/2024, 1:38 PMJonathan Rosenberg
09/02/2024, 1:53 PMChristoph Jud
09/02/2024, 1:53 PMChristoph Jud
09/02/2024, 2:06 PMChristoph Jud
09/02/2024, 2:06 PM{ name = "LAKEFS_DATABASE_TYPE", value = "dynamodb" }, # Specify the internal database to be DynamoDB
{ name = "LAKEFS_DATABASE_DYNAMODB_TABLE_NAME", value="${var.project_name}-${var.lakefs_dynamodb_table_name}" },
{ name = "LAKEFS_BLOCKSTORE_TYPE", value = "s3" }, # Specify the internal storage type to be S3
{ name = "LAKEFS_BLOCKSTORE_S3_REGION", value = var.aws_region },
{ name = "LAKEFS_BLOCKSTORE_S3_ENDPOINT", value = "<https://s3>.${var.aws_region}.<http://amazonaws.com/|amazonaws.com/>" },
{ name = "LAKEFS_BLOCKSTORE_S3_FORCE_PATH_STYLE", value = "true"},
{ name = "LAKEFS_BLOCKSTORE_s3_DISCOVER_BUCKET_REGION", value = "false"},
{ name = "AWS_REGION", value = var.aws_region },
{ name = "LAKEFS_GATEWAYS_S3_REGION", value = var.aws_region },
{ name = "LAKEFS_AUTH_ENCRYPT_SECRET_KEY", value = random_password.lakefs_encryption_secret.result },
{ name = "LAKEFS_LISTEN_ADDRESS", value = ":8000" },
{ name = "LAKEFS_STATS_ENABLED", value = "false" }, # Disable sending statistics to treeverse
{ name = "LAKEFS_LOGGING_LEVEL", value = "TRACE"},
{ name = "LAKEFS_EMAIL_SUBSCRIPTION_ENABLED", value = "false" }
Christoph Jud
09/02/2024, 2:08 PMChristoph Jud
09/02/2024, 2:15 PMItai Admi
09/02/2024, 2:23 PMChristoph Jud
09/02/2024, 2:29 PMItai Admi
09/02/2024, 2:31 PMLAKEFS_BLOCKSTORE_S3_ENDPOINT
then? Sorry for all the back and forth, I have some assumption that some of these values collide.Christoph Jud
09/02/2024, 2:31 PMChristoph Jud
09/02/2024, 2:36 PMItai Admi
09/02/2024, 2:37 PMChristoph Jud
09/02/2024, 2:38 PMChristoph Jud
09/02/2024, 2:39 PMChristoph Jud
09/02/2024, 2:40 PMItai Admi
09/02/2024, 2:42 PMChristoph Jud
09/02/2024, 2:43 PMItai Admi
09/02/2024, 2:43 PMChristoph Jud
09/02/2024, 2:44 PMItai Admi
09/02/2024, 2:44 PMChristoph Jud
09/02/2024, 2:49 PMItai Admi
09/02/2024, 2:50 PMChristoph Jud
09/02/2024, 2:53 PMItai Admi
09/02/2024, 2:53 PMChristoph Jud
09/02/2024, 2:54 PMItai Admi
09/02/2024, 2:57 PMmain
? I think thatβs why your writes are bring blocked with 403
s. Iβm not sure if the sample repo does that by defaultChristoph Jud
09/02/2024, 2:58 PMChristoph Jud
09/02/2024, 2:58 PMChristoph Jud
09/02/2024, 2:58 PMChristoph Jud
09/02/2024, 3:00 PMChristoph Jud
09/02/2024, 3:02 PMItai Admi
09/02/2024, 3:02 PMlakectl fs download <lakefs://test-repository5/main/README.md> /tmp --pre-sign=false
Christoph Jud
09/02/2024, 3:03 PMItai Admi
09/02/2024, 3:04 PMChristoph Jud
09/02/2024, 3:04 PMItai Admi
09/02/2024, 3:09 PMChristoph Jud
09/02/2024, 3:09 PMChristoph Jud
09/02/2024, 3:12 PMChristoph Jud
09/02/2024, 3:12 PMChristoph Jud
09/02/2024, 3:12 PMItai Admi
09/02/2024, 3:13 PMChristoph Jud
09/02/2024, 3:13 PMChristoph Jud
09/02/2024, 3:13 PMItai Admi
09/02/2024, 3:16 PMChristoph Jud
09/02/2024, 3:16 PMItai Admi
09/02/2024, 3:16 PMChristoph Jud
09/02/2024, 3:17 PMItai Admi
09/02/2024, 3:18 PMChristoph Jud
09/02/2024, 3:20 PMChristoph Jud
09/02/2024, 3:22 PMChristoph Jud
09/02/2024, 3:25 PM