How to load data from Apify Dataset to S3 Glue
Learn how to use Airbyte to synchronize your Apify Dataset data into S3 Glue within minutes.
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.
Building in-house pipelines
- Inconsistent and inaccurate data
- Laborious and expensive
- Brittle and inflexible
After Airbyte
- 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
Streamline AI workflows with Airbyte: load unstructured data into vector stores like Pinecone, Weaviate, and Milvus. Supports RAG transformations with LangChain chunking and embeddings from OpenAI, Cohere, etc., all in one operation.
Move Large Volumes, Fast
Quickly get up and running with a 5-minute setup that enables both incremental and full refreshes for databases of any size, seamlessly scaling to handle large data volumes. Our optimized architecture overcomes performance bottlenecks, ensuring efficient data synchronization even as your datasets grow from gigabytes to petabytes.
An Extensible Open-Source Standard
More than 1,000 developers contribute to Airbyte’s connectors, different interfaces (UI, API, Terraform Provider, Python Library), and integrations with the rest of the stack. Airbyte’s AI Connector Builder lets you edit or add new connectors in minutes.
Full Control & Security
Airbyte secures your data with cloud-hosted, self-hosted or hybrid deployment options. Single Sign-On (SSO) and Role-Based Access Control (RBAC) ensure only authorized users have access with the right permissions. Airbyte acts as a HIPAA conduit and supports compliance with CCPA, GDPR, and SOC2.
Fully Featured & Integrated
Airbyte automates schema evolution for seamless data flow, and utilizes efficient Change Data Capture (CDC) for real-time updates. Select only the columns you need, and leverage our dbt integration for powerful data transformations.
Enterprise Support with SLAs
Airbyte Self-Managed Enterprise comes with dedicated support and guaranteed service level agreements (SLAs), ensuring that your data movement infrastructure remains reliable and performant, and expert assistance is available when needed.
What our users say
Raman Singh
Predictable, straightforward pricing model that simplified budgeting and significantly reduced overall spend
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."
How to Sync to Manually
Step 1: Extract Data from Apify
To begin, use Apify's API to extract data. If you have an Apify actor, you can run it via the API and access the dataset. Use HTTP requests to fetch the data in JSON format. For example, you can use Python's `requests` library to send a GET request to `https://api.apify.com/v2/datasets/{datasetId}/items?format=json`.
Step 2: Transform Data Locally
Once you have your data in JSON format, transform it as needed. This might involve cleaning the data, filtering out unnecessary fields, or converting it into a tabular format like CSV if required. Use data processing libraries such as Pandas in Python to manipulate the data efficiently.
Step 3: Configure AWS CLI
Ensure the AWS Command Line Interface (CLI) is installed and configured on your machine. Set up your AWS credentials by running `aws configure` and entering your Access Key ID, Secret Access Key, region, and output format. This step is crucial for interacting with AWS services programmatically.
Step 4: Upload Data to S3
Use the AWS CLI to upload your transformed data to an S3 bucket. Create an S3 bucket if you don’t have one already. Use the command `aws s3 cp /path/to/your/file s3://your-bucket-name/` to copy your data file from your local machine to S3. Make sure to specify the correct file path and S3 bucket path.
Step 5: Set Up AWS Glue Crawler
In the AWS Management Console, navigate to AWS Glue and create a new crawler. Configure it to point to your S3 bucket where the data is stored. Define a new database or choose an existing one for the crawler to store the metadata. This step will catalog the data, making it accessible for querying.
Step 6: Run AWS Glue Crawler
Execute the crawler to scan the data in your S3 bucket and populate the Glue Data Catalog with table definitions. This process will automatically infer the schema of your data and store it in your specified database.
Step 7: Verify Data in AWS Glue
After the crawler completes, verify that the data has been correctly cataloged in AWS Glue. Check the table schema and sample the data to ensure it matches your expectations. You can now use AWS Glue to perform ETL operations or query the data using AWS Athena.
By following these steps, you'll be able to move data from Apify to AWS S3 and prepare it for AWS Glue without relying on third-party connectors or integrations.