

Building your pipeline or Using Airbyte
Airbyte is the only open source solution empowering data teams to meet all their growing custom business demands in the new AI era.
- Inconsistent and inaccurate data
- Laborious and expensive
- Brittle and inflexible
- Reliable and accurate
- Extensible and scalable for all your needs
- Deployed and governed your way
Start syncing with Airbyte in 3 easy steps within 10 minutes



Take a virtual tour
Demo video of Airbyte Cloud
Demo video of AI Connector Builder
What sets Airbyte Apart
Modern GenAI Workflows
Move Large Volumes, Fast
An Extensible Open-Source Standard
Full Control & Security
Fully Featured & Integrated
Enterprise Support with SLAs
What our users say


"The intake layer of Datadog’s self-serve analytics platform is largely built on Airbyte.Airbyte’s ease of use and extensibility allowed any team in the company to push their data into the platform - without assistance from the data team!"


“Airbyte helped us accelerate our progress by years, compared to our competitors. We don’t need to worry about connectors and focus on creating value for our users instead of building infrastructure. That’s priceless. The time and energy saved allows us to disrupt and grow faster.”


“We chose Airbyte for its ease of use, its pricing scalability and its absence of vendor lock-in. Having a lean team makes them our top criteria. The value of being able to scale and execute at a high level by maximizing resources is immense”
- AWS Account: Ensure you have access to an AWS account with permissions to access DynamoDB and Elasticsearch Service.
- Elasticsearch Cluster: Set up an Elasticsearch cluster in AWS Elasticsearch Service or on your own servers.
- Development Environment: Set up a development environment with AWS SDK (for the language of your choice), and Elasticsearch client libraries.
- Choose a Method for Data Extraction:
- DynamoDB Scan: Use the Scan operation to retrieve all items from the table.
- DynamoDB Streams: If your data is continuously changing, consider using DynamoDB Streams to capture changes in real-time.
- Write a Script to Extract Data:
- Initialize the AWS SDK with your credentials and set the region.
- Use the Scan API to retrieve the data from the DynamoDB table.
- Paginate through the results if your dataset is larger than the maximum items returned in a single scan.
- Data Mapping: Map the DynamoDB data types to the corresponding Elasticsearch data types.
- Data Transformation: Write a script or a function to transform the data into JSON documents that are compatible with Elasticsearch.
- Initialize Elasticsearch Client: Set up the Elasticsearch client using the necessary credentials and endpoint of your Elasticsearch cluster.
- Create an Index: If not already created, define an index in Elasticsearch where the data will be stored.
- Bulk Indexing: Use the Elasticsearch Bulk API to index multiple documents at once for better performance.
- Combine the Steps: Combine the extraction, transformation, and loading steps into a single script or application.
- Error Handling: Implement error handling to manage issues like network interruptions, throttling, or indexing errors.
- Logging: Add logging to your application to track the progress and any issues that arise during the data transfer process.
- Test with a Small Dataset: Before transferring all your data, test the process with a small subset to ensure everything works as expected.
- Run the Data Transfer: Execute your script or application to transfer the data from DynamoDB to Elasticsearch.
- Monitor the Process: Monitor the data transfer process for any errors or performance bottlenecks.
- Check Data Count: Ensure the number of documents in Elasticsearch matches the number of items in DynamoDB.
- Sample Data Verification: Query several items in Elasticsearch and compare them with the source data in DynamoDB to verify accuracy.
- Automation: If your data needs to be updated regularly, consider automating the process with AWS Lambda functions triggered by DynamoDB Streams or scheduled events.
- Remove Temporary Resources: If you created any temporary resources (like EC2 instances) for the data transfer, terminate them to avoid unnecessary charges.
Additional Considerations
- Security: Ensure that all data transfers are done securely, using encryption in transit and at rest.
- Throttling: Be mindful of read and write throughput limits on both DynamoDB and Elasticsearch to avoid throttling.
- Cost: Consider the cost implications of data transfer and storage in both services.
FAQs
What is ETL?
ETL, an acronym for Extract, Transform, Load, is a vital data integration process. It involves extracting data from diverse sources, transforming it into a usable format, and loading it into a database, data warehouse or data lake. This process enables meaningful data analysis, enhancing business intelligence.
Amazon DynamoDB is a fully managed proprietary NoSQL database service that supports key–value and document data structures and is offered by Amazon.com as part of the Amazon Web Services portfolio. DynamoDB exposes a similar data model to and derives its name from Dynamo, but has a different underlying implementation.
What is ELT?
ELT, standing for Extract, Load, Transform, is a modern take on the traditional ETL data integration process. In ELT, data is first extracted from various sources, loaded directly into a data warehouse, and then transformed. This approach enhances data processing speed, analytical flexibility and autonomy.
Difference between ETL and ELT?
ETL and ELT are critical data integration strategies with key differences. ETL (Extract, Transform, Load) transforms data before loading, ideal for structured data. In contrast, ELT (Extract, Load, Transform) loads data before transformation, perfect for processing large, diverse data sets in modern data warehouses. ELT is becoming the new standard as it offers a lot more flexibility and autonomy to data analysts.
What should you do next?
Hope you enjoyed the reading. Here are the 3 ways we can help you in your data journey: