

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”
1. Sign in to the AWS Management Console.
2. Navigate to the CloudTrail service.
3. Click on "Create trail."
4. Enter a name for your trail.
5. Set "Apply trail to all regions" to Yes if you want to collect logs from all regions.
6. Under "Management events," choose "Read/Write events" to log all or select specific events.
7. In the "Data events" section, you can choose to log data events for S3 or Lambda.
8. For "Storage location," create or select an existing S3 bucket to store your logs.
9. Click "Create."
1. Navigate to the IAM service in the AWS Management Console.
2. Go to "Roles" and click "Create role."
3. Choose "Lambda" as the use case and click "Next: Permissions."
4. Attach the following policies: `AmazonS3ReadOnlyAccess`, `AmazonDynamoDBFullAccess`, and `CloudWatchLogsFullAccess` (or more restrictive policies if you prefer).
5. Review, name the role, and create it.
1. Go to the DynamoDB service in the AWS Management Console.
2. Click "Create table."
3. Enter a table name and primary key details (e.g., "EventID" as the primary key).
4. Configure table settings according to your requirements.
5. Click "Create."
1. Navigate to the Lambda service in the AWS Management Console.
2. Click "Create function."
3. Choose "Author from scratch."
4. Enter a function name.
5. Choose the runtime as Python, Node.js, or any other supported runtime.
6. Under "Permissions," choose "Use an existing role" and select the role created in Step 2.
7. Click "Create function."
In the Lambda function editor, write the code to:
- Read the CloudTrail log file from the S3 bucket.
- Parse the log data.
- Write the relevant data to the DynamoDB table.
Here's a Python example to get you started:
import boto3
import json
s3_client = boto3.client('s3')
dynamodb = boto3.resource('dynamodb')
def lambda_handler(event, context):
# Get the S3 object from the event
bucket_name = event['Records'][0]['s3']['bucket']['name']
object_key = event['Records'][0]['s3']['object']['key']
# Get the log file from S3
log_file = s3_client.get_object(Bucket=bucket_name, Key=object_key)
log_data = json.loads(log_file['Body'].read())
# Process log data and write to DynamoDB
table = dynamodb.Table('YourDynamoDBTableName')
for record in log_data['Records']:
# You can add logic here to filter or modify the records as needed
table.put_item(Item=record)
return 'Success'
1. In the Lambda function dashboard, click on "Add trigger."
2. Select "S3" from the trigger configuration services.
3. Choose the S3 bucket where CloudTrail logs are stored.
4. Set the event type to "PUT" or "Object Created (All)."
5. Click "Add."
1. Generate some events that CloudTrail will log (e.g., create an S3 bucket, start an EC2 instance).
2. CloudTrail writes logs to the S3 bucket.
3. The Lambda function triggers upon log file creation.
4. Check the DynamoDB table for the new entries.
1. Monitor the Lambda function executions in the AWS Lambda console.
2. Check the CloudWatch Logs for any error messages.
3. Adjust the Lambda function code and permissions as needed based on the logs.
1. Fine-tune the IAM policies to follow the principle of least privilege.
2. Optimize the Lambda function for performance and cost.
3. Set up alarms and notifications for any operational issues.
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: