

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


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


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

"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."
Begin by creating a new CloudTrail trail or use an existing one. Ensure that the trail is configured to deliver log files to an S3 bucket. This is crucial as it allows you to access the logs needed for analysis. Go to the AWS Management Console, navigate to CloudTrail, and follow the steps to set up or edit a trail, specifying the target S3 bucket for log delivery.
Make sure the S3 bucket specified for CloudTrail logs has the correct permissions. The bucket should allow CloudTrail to write logs into it. Go to the S3 console, and under your bucket's permissions tab, confirm that the bucket policy allows `s3:PutObject` permission from the CloudTrail service.
Create a Lambda function to parse and transform CloudTrail data into a format suitable for Redshift. Use the AWS Lambda console to create a new function, selecting the appropriate runtime (e.g., Python or Node.js). This function will be triggered by S3 events (when new logs are added to the bucket) and will process the logs, preparing them for Redshift ingestion.
Develop an IAM role with the necessary permissions for your Lambda function. This role should have policies that allow reading from the S3 bucket where CloudTrail logs are stored and writing to another S3 bucket (or the same one) where processed data will be stored. Attach the `AWSLambdaBasicExecutionRole` managed policy to this role for basic Lambda execution permissions.
Modify your Lambda function to transform the CloudTrail logs into a CSV or JSON format suitable for Redshift. Once transformed, store these files in an S3 bucket. Ensure your Lambda function is configured to trigger on new log file uploads and that it outputs the transformed data files back to the S3 bucket.
If you do not have an Amazon Redshift cluster set up, create one using the Amazon Redshift console. When configuring your cluster, ensure it has the necessary compute resources and is located in the same region as your S3 bucket to minimize data transfer costs. Note the connection details (endpoint, database name, and port) for use in the next step.
Use the COPY command in Redshift to load data from your S3 bucket. Connect to your Redshift cluster using a SQL client, and execute the COPY command, specifying the S3 path to your transformed data files. Ensure your Redshift cluster has the necessary IAM roles attached to access the S3 bucket. For example:
```sql
COPY my_table
FROM 's3://my-transformed-data-bucket/path/'
IAM_ROLE 'arn:aws:iam::account-id:role/MyRedshiftRole'
FORMAT AS CSV;
```
Adjust the format and options in the COPY command according to the data format used (CSV, JSON, etc.).
Following these steps will enable you to move data from AWS CloudTrail to Amazon Redshift without the need for 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: