> For the complete documentation index, see [llms.txt](https://documentation.astera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.astera.com/astera-data-stack-v8/dataflows/sources/data-providers-and-file-formats-supported-in-astera.md).

# Data Providers and File Formats Supported in Astera

Astera can read data from a wide range of file sources and database providers. In this article, we have compiled a list of file formats, data providers, and web applications that are supported for use in Astera.

## **Databases and Data Warehouses**

* Amazon Aurora
* MySQL
* Amazon Aurora Postgres
* Amazon RDS
* Amazon Redshift
* DB2
* Google Cloud SQL
* MariaDB
* Microsoft Azure
* Microsoft Dynamics CRM
* MS Access
* MySQL
* Netezza
* Oracle
* PostgreSQL
* PowerBI
* Salesforce (Legacy)
* Salesforce Rest
* SAP Hana
* Snowflake
* SQL Server
* Sybase
* Tableau
* Teradata
* Vertica

In addition, Astera features an ODBC connector that uses the Open Database Connectivity (ODBC) interface by Microsoft to access data in database management systems using SQL as a standard.

To learn more about how to use the object to read data from the above-mentioned data providers, click [here](/astera-data-stack-v8/dataflows/sources/database-table-source.md).

## **File Formats**

* COBOL
* Delimited files
* Fixed length files
* XML/JSON
* Excel workbooks
* PDFs
* Report sources
* Text files
* EDI formats (including X12, EDIFACT, HL7)

## **Cloud-Based Data Providers**

* Microsoft Dynamics CRM
* PowerBI
* Salesforce
* SAP
* Tableau
* Amazon S3 Bucket Storage
* Microsoft Azure Blob Storage

{% hint style="info" %}
**Note:** Amazon S3 Bucket Storage and Microsoft Azure Blob Storage are planned for the Astera 9.1 release.
{% endhint %}

## **File Systems and Transfer Protocols**

* AS2
* FTP (File Transfer Protocol)
* Email
* HDFS (Hadoop Distributed File System) n/a
* SCP (Secure Copy Protocol)
* SFTP (Secure File Transfer Protocol)

## **Web Services**

* SOAP (Simple Object Access Protocol)
* REST (REpresentational State Transfer)

Using the SOAP and REST web services connector, you can easily connect to any data source that uses SOAP protocol or can be exposed via REST API.

Here are some applications that you can connect to using the REST Client object in Astera:

* FinancialForce
* Force.com Applications
* Google Analytics
* Google Cloud
* Google Drive
* Hubspot
* IBM DB2 Warehouse
* Microsoft Azure
* OneDrive
* Oracle Cloud
* Oracle Eloqua
* Oracle Sales Cloud
* Oracle Service Cloud
* Salesforce Lightning
* ServiceMAX
* SugarCRM
* Veeva CRM

The list is non-exhaustive.

Read: [~~How to connect to Eloqua using REST client object~~](https://docs.astera.com/projects/centerprise/en/7/web-services/how-to-connect-to-eloqua-using-centerprise-rest-api.html#how-to-connect-to-eloqua-using-centerprise-rest-api)

## **Support for Custom Connectors**

You can also build a custom transformation or connector from the ground up quickly and easily using the Microsoft .NET APIs, and retrieve data from various other sources.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://documentation.astera.com/astera-data-stack-v8/dataflows/sources/data-providers-and-file-formats-supported-in-astera.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.