AWS re:Invent 2023 - Amazon DynamoDB zero-ETL integration with Amazon OpenSearch Service (DAT339)
Vložit
- čas přidán 29. 11. 2023
- Making the most of your data often means using multiple AWS services, including Amazon OpenSearch Service for full-text, geospatial, or vector search. Amazon DynamoDB offers many different ways to build integrations, including export functionality and Amazon DynamoDB Streams. In this session, learn about best practices by seeing how Amazon DynamoDB zero-ETL integration with Amazon OpenSearch Service works within different architecture patterns and sample implementations, including an end-to-end vector search example.
Learn more about AWS re:Invent at go.aws/46iuzGv.
Subscribe:
More AWS videos: bit.ly/2O3zS75
More AWS events videos: bit.ly/316g9t4
ABOUT AWS
Amazon Web Services (AWS) hosts events, both online and in-person, bringing the cloud computing community together to connect, collaborate, and learn from AWS experts.
AWS is the world's most comprehensive and broadly adopted cloud platform, offering over 200 fully featured services from data centers globally. Millions of customers-including the fastest-growing startups, largest enterprises, and leading government agencies-are using AWS to lower costs, become more agile, and innovate faster.
#AWSreInvent #AWSreInvent2023 - Věda a technologie
36:17 The query has a filter on doc_type : question. However, the results are of type answer. I also see item_name in thr results which is not part of the answer schema shown initially (it was part of ASIN type). Does opensearch dynamoDb integration kind of automatically join related data given they share the same partitionKey?
That's a great question! Our community of experts on AWS re:Post might be able to help you troubleshoot this with details on your current configuration. Feel free to share more info, here: go.aws/aws-repost. ^RM
I'm considering switching over from streams and lambda approach to opensearch ingestion.
Will there be expected improvements in latency? What is the expected latency for opensearch ingestion from dynamodb?
You can find more information on using an OpenSearch Ingestion pipeline with Amazon DynamoDB here: go.aws/3w7V70H. In addition, you can also review best practices for Amazon OpenSearch Ingestion, which may prove to be helpful: go.aws/3UtdJ5e. Feel free to reach out to our re:Post community for further guidance: go.aws/aws-repost. ^AM
Will there be CDK support to manage the pipeline configuration?
We appreciate this question! 😀 I've passed this along directly to our team to take a look at. ^AK
Hi there! I'd like to check back in to share the answer that our Service team provided. 💭 Yes, you can use CDK to set up the integration. You can find the GitHub project showing this as described at: go.aws/47cLjPN. ✅ ^AK
At 14:24 you show a generic way of creating the index and document_id, but in the following examples you have ingested from dynamodb using a single-table design. I suppose (but can't get it to work) that OpenSearch will need each unique type in its own index, but using a dynamic field for creating the index like: ${getMetadata(\"item_type\")} results in an error: Failed to setup dynamic index with an exception
Could you provide a link to the exact setup used in the presentation?
Edit: I just re-wathced that part and can see that you load all items to the same index which makes sense in this example. But is it also possible to ingest each item to a dynamic index like suggested above?
Hi there, thanks for reaching out. I have sent your feedback off to our service team for review. ^AM
Hi! 👋 I'd like to circle back around with the feedback our Service team has shared with me regarding your question. With STD, it's possible, but not necessary, to put each unique type into its own index. It depends on your search query pattern. 🔎 If your table holds data about restaurants (say the restaurant metadata, the menu text, the various reviews) then you probably want to search all of those at the same time so thus one index. But if you decide you want separate search indexes, you can use "route." ^AK
@@awssupport Great, thanks for getting back to me :)