

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."
AWS CloudTrail needs to be enabled in your AWS account to start logging API calls and other events. Go to the AWS CloudTrail console, create a new trail, and configure it to log all management and data events. Ensure that you specify an S3 bucket where CloudTrail will deliver the log files.
If you haven't done so already, create an S3 bucket specifically for storing CloudTrail logs. This will be the destination bucket where CloudTrail logs will be sent. Ensure the bucket has the appropriate permissions for CloudTrail to write logs to it. You can configure bucket policies to allow CloudTrail to deliver logs securely.
Set up AWS Identity and Access Management (IAM) roles and policies to allow AWS Glue to access the S3 bucket containing CloudTrail logs. Create an IAM role with the necessary permissions for AWS Glue, including `s3:GetObject`, `s3:PutObject`, and `s3:ListBucket` for your specific S3 bucket.
Go to the AWS Glue console and set up a new Glue job. The Glue job will be responsible for processing the CloudTrail logs stored in S3. Define the job's IAM role, which should have the permissions created in the previous step, and specify the allocated resources.
Create a Glue Crawler to automatically infer the schema of the CloudTrail logs. Configure the crawler to look at the S3 bucket where the logs are stored. Run the crawler to populate the Glue Data Catalog with the metadata about the CloudTrail logs.
Develop an Extract, Transform, Load (ETL) job in AWS Glue. Write a script using Python or Scala to process the CloudTrail logs as needed. This can include transformations, filtering, or aggregating the data. Specify the source as the CloudTrail data in the Glue Data Catalog and define the target as another S3 bucket or a different storage solution.
Schedule the Glue job to run at desired intervals using AWS Glue's scheduling capabilities. This can be done using cron expressions directly in the Glue console. Monitor the performance and logs of the Glue job using CloudWatch to ensure data is being processed correctly and to troubleshoot any issues that arise.
By following these steps, you can efficiently move data from AWS CloudTrail to Amazon S3 and process it using AWS Glue, all within the AWS ecosystem, 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: