

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
Setup Complexities simplified!
Simple & Easy to use Interface
Airbyte is built to get out of your way. Our clean, modern interface walks you through setup, so you can go from zero to sync in minutes—without deep technical expertise.
Guided Tour: Assisting you in building connections
Whether you’re setting up your first connection or managing complex syncs, Airbyte’s UI and documentation help you move with confidence. No guesswork. Just clarity.
Airbyte AI Assistant that will act as your sidekick in building your data pipelines in Minutes
Airbyte’s built-in assistant helps you choose sources, set destinations, and configure syncs quickly. It’s like having a data engineer on call—without the overhead.
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

Andre Exner

"For TUI Musement, Airbyte cut development time in half and enabled dynamic customer experiences."

Chase Zieman

“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.”

Rupak Patel
"With Airbyte, we could just push a few buttons, allow API access, and bring all the data into Google BigQuery. By blending all the different marketing data sources, we can gain valuable insights."
Start by setting up AWS CloudTrail to record API activity and deliver the log files to an Amazon S3 bucket. Go to the AWS CloudTrail console and create a new trail. Ensure that you specify an S3 bucket where the logs will be delivered. This bucket will serve as the source from which you will extract the logs.
Create an IAM role with the necessary permissions to access the S3 bucket and read CloudTrail logs. Attach policies such as `AmazonS3ReadOnlyAccess` to the IAM role. Additionally, ensure the IAM role has permissions to write to your MongoDB destination if you are using AWS resources like EC2 to perform the data transfer.
Launch an EC2 instance in AWS that will serve as the intermediary to transfer data from S3 to MongoDB. Select an appropriate instance type based on your expected workload. Ensure that the instance has access to the IAM role configured earlier.
SSH into your EC2 instance and install necessary software such as Python and MongoDB client libraries. Use the package manager (like `apt` for Ubuntu) to install Python and then use `pip` to install the `boto3` library for accessing S3 and `pymongo` for connecting to MongoDB.
```bash
sudo apt update
sudo apt install python3-pip
pip3 install boto3 pymongo
```
Write a Python script that uses `boto3` to connect to your S3 bucket and download the CloudTrail logs. Parse these logs to transform them into a format suitable for MongoDB (e.g., JSON documents). Here’s a basic outline of the script:
```python
import boto3
import json
from pymongo import MongoClient
# Connect to S3
s3_client = boto3.client('s3')
bucket_name = 'your-cloudtrail-bucket'
# Connect to MongoDB
mongo_client = MongoClient('mongodb://your-mongodb-uri')
db = mongo_client['your_database']
collection = db['cloudtrail_logs']
# List and download logs
response = s3_client.list_objects_v2(Bucket=bucket_name)
for obj in response.get('Contents', []):
file_content = s3_client.get_object(Bucket=bucket_name, Key=obj['Key'])['Body'].read().decode('utf-8')
logs = json.loads(file_content)
transformed_logs = transform_logs(logs) # Implement this function
collection.insert_many(transformed_logs)
```
Execute the Python script on the EC2 instance to transfer the logs from S3 to your MongoDB database. This step involves processing each log file, transforming it, and then inserting it into the MongoDB collection.
```bash
python3 transfer_script.py
```
To ensure continuous data flow, automate the script execution using cron jobs on your EC2 instance. Edit the crontab file with `crontab -e` and schedule the script to run at regular intervals.
```bash
*/30 * * * * /usr/bin/python3 /path/to/transfer_script.py
```
This setup ensures that your MongoDB database is regularly updated with the latest CloudTrail logs from S3.
By following these steps, you can efficiently transfer data from AWS CloudTrail to a MongoDB destination without relying on third-party connectors or integrations.
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.
AWS CloudTrail is a web service developed to simplify and provide assistance with AWS accounts. Enabling compliance, governance, and operational and risk auditing, it allows users to monitor, log, and document AWS account-related activity in an easily searchable format. With its comprehensive account event history function, CloudTrail helps users analyze and troubleshoot security and operational issues, detect unusual account activity, and much more by increasing visibility into customers’ user and resource activity.
AWS CloudTrail provides access to a wide range of data related to AWS account activity and resource usage. The following are the categories of data that can be accessed through the API:
1. Event history: This includes information about all the events that have occurred in an AWS account, such as API calls, console sign-ins, and resource changes.
2. Resource activity: This category includes data related to the usage of AWS resources, such as EC2 instances, S3 buckets, and RDS databases.
3. User activity: This category includes data related to user activity in an AWS account, such as user sign-ins, password changes, and access key usage.
4. Security analysis: This category includes data related to security events in an AWS account, such as failed login attempts, unauthorized access attempts, and changes to security groups.
5. Compliance auditing: This category includes data related to compliance auditing in an AWS account, such as changes to IAM policies, CloudTrail configuration changes, and VPC network changes.
Overall, the AWS CloudTrail API provides a comprehensive view of AWS account activity and resource usage, making it a valuable tool for monitoring and managing AWS environments.
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: