Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Multimodal data does not get stored in specified S3 bucket - AWS Knowledge Base #41384

Open
srishtigulechar opened this issue Feb 13, 2025 · 1 comment
Labels
bug Addresses a defect in current functionality. service/bedrockagent Issues and PRs that pertain to the bedrockagent service.

Comments

@srishtigulechar
Copy link

Terraform Core Version

1.8.5

AWS Provider Version

5.86.0

Affected Resource(s)

aws_bedrockagent_knowledge_base
supplemental_data_storage_configuration

Expected Behavior

aws_bedrockagent_knowledge_base has support for multimodal storage when parsing strategy is enabled. This can be configured using supplemental_data_storage_configuration block. Once terraform apply is run, the knowledge base should get created with s3 bucket for multimodal storage destination. When sync runs and gets completed, multimodal data from documents should be stored in that s3 bucket.

Actual Behavior

Once terraform apply is run, the knowledge base gets created with s3 bucket for multimodal storage destination. But when sync completes, no multimodal data gets stored in specified s3 bucket and it does not throw any permission errors either.

Relevant Error/Panic Output Snippet

Terraform Configuration Files

resource "aws_bedrockagent_knowledge_base" "example" {
  name     = "example"
  role_arn = aws_iam_role.example.arn
  knowledge_base_configuration {
    vector_knowledge_base_configuration {
      embedding_model_arn = "arn:aws:bedrock:us-west-2::foundation-model/amazon.titan-embed-text-v2:0"

      supplemental_data_storage_configuration {
        storage_location {
          type = "S3"

          s3_location {
            uri = "s3://my-bucket/chunk-processor/"
          }
        }
      }
    }
    type = "VECTOR"
  }
  storage_configuration {
    type = "RDS"
    rds_configuration {
      resource_arn           = "resource_arn"
      credentials_secret_arn = "credentials_secret_arn"
      database_name          = "database_name"
      table_name             = "table_name"
      field_mapping {
        vector_field      = "vector_field"
        text_field        = "text_field"
        metadata_field    = "metadata_field"
        primary_key_field = "primary_key_field"
      }
    }
  }
}
resource "aws_bedrockagent_data_source" "example" {
  knowledge_base_id = "bkb-id"
  name              = "example"
  data_source_configuration {
    type = "S3"
    s3_configuration {
      bucket_arn = "arn:aws:s3:::example-bucket"
      inclusion_prefixes = ["prefix-1"]
    }
  }
  vector_ingestion_configuration {
    parsing_configuration {
      parsing_strategy = "BEDROCK_FOUNDATION_MODEL"
      bedrock_foundation_model_configuration {
        model_arn = "parsing_model_arn"
      }
    }
  }
}

Steps to Reproduce

  • Create aws_bedrockagent_knowledge_base with supplemental_data_storage_configuration block
  • Create aws_bedrockagent_data_source with parsing_configuration
  • Run terraform apply
  • Upload and sync a document with multimodal data in Knowledge base
  • Check the multimodal storage s3 bucket to check if data gets stored

Debug Output

No response

Panic Output

No response

Important Factoids

No response

References

#40737
https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/bedrockagent_knowledge_base#supplemental_data_storage_configuration-block

Would you like to implement a fix?

No

@srishtigulechar srishtigulechar added the bug Addresses a defect in current functionality. label Feb 13, 2025
Copy link

Community Note

Voting for Prioritization

  • Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
  • Please see our prioritization guide for information on how we prioritize.
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

  • If you are interested in working on this issue, please leave a comment.
  • If this would be your first contribution, please review the contribution guide.

@github-actions github-actions bot added service/bedrockagent Issues and PRs that pertain to the bedrockagent service. needs-triage Waiting for first response or review from a maintainer. labels Feb 13, 2025
@justinretzolk justinretzolk removed the needs-triage Waiting for first response or review from a maintainer. label Feb 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Addresses a defect in current functionality. service/bedrockagent Issues and PRs that pertain to the bedrockagent service.
Projects
None yet
Development

No branches or pull requests

2 participants