Amazon S3 XML File Connector for SSRS Amazon S3 XML File Connector can be used to read XML Files stored in AWS S3 Buckets. Using this you can easily integrate AWS S3 XML File data. It's supports latest security standards, and optimized for large data files. It also supports reading compressed files (e.g. GZip /Zip). In this article you will learn how to quickly and efficiently integrate Amazon S3 XML File data in SSRS without coding. We will use high-performance Amazon S3 XML File Connector to easily connect to Amazon S3 XML File and then access the data inside SSRS. Let's follow the steps below to see how we can accomplish that! Download Documentation Amazon S3 XML File Connector for SSRS is based on ZappySys Amazon S3 XML Driver which is part of ODBC PowerPack. It is a collection of high-performance ODBC drivers that enable you to integrate data in SQL Server, SSIS, a programming language, or any other ODBC-compatible application. ODBC PowerPack supports various file formats, sources and destinations, including REST/SOAP API, SFTP/FTP, storage services, and plain files, to mention a few.

Connect to Amazon S3 XML File in other apps Connect to Amazon S3 XML File in SSIS Connect to Amazon S3 XML File in SQL Server Connect to Amazon S3 XML File in Power BI Connect to Amazon S3 XML File in Informatica Connect to Amazon S3 XML File in MS Access Connect to Amazon S3 XML File in MS Excel Connect to Amazon S3 XML File in SSAS Connect to Amazon S3 XML File in C# Connect to Amazon S3 XML File in Python Connect to Amazon S3 XML File in JAVA Connect to Amazon S3 XML File in Tableau Connect to Amazon S3 XML File in SAP Crystal Reports Connect to Amazon S3 XML File in Azure Data Factory (Pipeline) Connect to Amazon S3 XML File in Azure Data Factory (SSIS) Connect to Amazon S3 XML File in Talend Studio Connect to Amazon S3 XML File in UiPath Connect to Amazon S3 XML File in PowerShell Connect to Amazon S3 XML File in ODBC

Create Data Source in ZappySys Data Gateway based on ZappySys Amazon S3 XML Driver

1. Download and install ZappySys ODBC PowerPack.

2. Search for gateway in start menu and Open ZappySys Data Gateway:
   

3. Go to Users Tab to add our first Gateway user. Click Add; we will give it a name tdsuser and enter password you like to give. Check Admin option and click OK to save. We will use these details later when we create linked server:
   

4. Now we are ready to add a data source. Click Add, give data source a name (Copy this name somewhere, we will need it later) and then select Native - ZappySys Amazon S3 XML Driver. Finally, click OK. And it will create the Data Set for it and open the ZS driver UI.

   AMAZONS3-XMLFILEDSN

   Native - ZappySys Amazon S3 XML Driver

   

5. Create and configure a connection for the Amazon S3 storage account.

   

6. You can use select your desired single file by clicking [...] path button.

   mybucket/dbo.tblNames.xml

   dbo.tblNames.xml

   
   
   
   ----------OR----------

   You can also read the multiple files stored in Amazon S3 Storage using wildcard pattern supported e.g. dbo.tblNames*.xml.
   

   Note: If you want to operation with multiple files then use wild card pattern as below 
   (when you use wild card pattern in source path then system will treat target path as folder regardless you end with slash)
   
   mybucket/dbo.tblNames.xml (will read only single .XML file)
   mybucket/dbo.tbl*.xml (all files starting with file name)
   mybucket/*.xml (all files with .xml Extension and located under folder subfolder)
   

   mybucket/dbo.tblNames*.xml

   
   
   
   ----------OR----------

   You can also read the zip and gzip compressed files also without extracting it in using Amazon S3 XML Source File Task.

   mybucket/dbo.tblNames*.gz

   

7. Now select/enter Path expression in Path textbox to extract only specific part of XML string as below ($.value[*] will get content of value attribute from XML document. Value attribute is array of XML documents so we have to use [*] to indicate we want all records of that array)
   

   NOTE: Here, We are using our desired filter, but you need to select your desired filter based on your requirement.
   

8. Navigate to the Preview Tab and let's explore the different modes available to access the data.
   

   1. --- Using Direct Query ---

      Click on Preview Tab, Select Table from Tables Dropdown and select [value] and click Preview.
      

   2. --- Using Stored Procedure ---

      Note : For this you have to Save ODBC Driver configuration and then again reopen to configure same driver. For more information click here.
      

      Click on the Custom Objects Tab, Click on Add button and select Add Procedure and Enter an appropriate name and Click on OK button to create.
      

      1. --- Without Parameters ---

         Now Stored Procedure can be created with or without parameters (see example below). If you use parameters then Set default value otherwise it may fail to compilation)
         
         

      2. --- With Parameters ---

         Note : Here you can use Placeholder with Paramters in Stored Procedure.
         Example : SELECT * FROM $ WHERE OrderID = '<@OrderID, FUN_TRIM>' or CustId = '<@CustId>' and Total >= '<@Total>'
         

         

   3. --- Using Virtual Table ---

      Note : For this you have to Save ODBC Driver configuration and then again reopen to configure same driver. For more information click here.
      

      ZappySys APi Drivers support flexible Query language so you can override Default Properties you configured on Data Source such as URL, Body. This way you don't have to create multiple Data Sources if you like to read data from multiple EndPoints. However not every application support supplying custom SQL to driver so you can only select Table from list returned from driver.

      Many applications like MS Access, Informatica Designer wont give you option to specify custom SQL when you import Objects. In such case Virtual Table is very useful. You can create many Virtual Tables on the same Data Source (e.g. If you have 50 Buckets with slight variations you can create virtual tables with just URL as Parameter setting).

      vt__Customers
      DataPath=mybucket_1/customers.xml
      
      vt__Orders
      DataPath=mybucket_2/orders.xml
      
      vt__Products
      DataPath=mybucket_3/products.xml
      

      1. Click on the Custom Objects Tab, Click on Add button and select Add Table and Enter an appropriate name and Click on OK button to create.
         
      2. Once you see Query Builder Window on screen Configure it.
         
      3. Click on Preview Tab, Select Virtual Table(prefix with vt__) from Tables Dropdown or write SQL query with Virtual Table name and click Preview.
         

9. Click OK to finish creating the data source

10. That's it; we are done. In a few clicks we configured the to Read the Amazon S3 XML File data using ZappySys Amazon S3 XML File Connector

Read data in SSRS from ZappySys Data Gateway

1. Open Visual Studio and create a new SSRS project

2. Then add a new Shared Data Source (you can create a non-shared data source inside report too):

   

3. Continue with creating the Shared Data Source. Select Microsoft SQL Server as Type and hit Build button to proceed further:

   

4. Once a window opens, configure it similarly. Configure "AmazonS3XmlFileDSN" as database name. Finally, hit Test Connection and OK:

   AmazonS3XmlFileDSN

   

5. Another window opens, and it should look similarly to this one below which ends the creation of a Data Source:

   DataSource=localhost,5000;Initial Catalog=AmazonS3XmlFileDSN

   

6. Now it's time to create a Dataset. If you don't have a report created, in one of the wizard's steps it will look like this:

   SELECT * FROM Tickets

   

7. Finally, once you complete the report, similar results will show up:

   

Passing Parameters to SSRS Report / Filter data

If you want to parameterize your report, then refer to this article

Conclusion

In this article we showed you how to connect to Amazon S3 XML File in SSRS and integrate data without any coding, saving you time and effort. It's worth noting that ZappySys Amazon S3 XML Driver allows you to connect not only to Amazon S3 XML File, but to any Java application that supports JDBC (just use a different JDBC driver and configure it appropriately).

We encourage you to download Amazon S3 XML File Connector for SSRS and see how easy it is to use it for yourself or your team.

If you have any questions, feel free to contact ZappySys support team. You can also open a live chat immediately by clicking on the chat icon below.

Download Amazon S3 XML File Connector for SSRS Documentation

More integrations

Other connectors for SSRS

Amazon Ads

Amazon Athena

Amazon Selling Partner (SP-API)

Apache Derby

Apache Hive

Apache Spark

Asana

Azure DevOps

Cosmos DB

DropBox

ElasticSearch

FastSpring

Google Ads

Google BigQuery

Google Calendar

Google Drive

Google Sheets

Hubspot

Infor Data Lake

Jira

Mailchimp

ManagedEngine ServiceDesk Plus (Zoho)

MariaDB

OData

OneDrive

Outlook Mail (Office 365)

Power BI

ServiceNow

SharePoint Online

Shopify

Smartsheet

Starburst

Stripe

Trino

YouTube

Zendesk

Zoho CRM

Zoho SalesIQ

Zoom

REST API

JSON

JSON File

XML

SOAP

XML File

JDBC-ODBC Bridge

Salesforce

CSV

Amazon S3 JSON File

Amazon S3 XML File

Amazon S3 CSV File

Azure Blob JSON File

Azure Blob XML File

Azure Blob CSV File

FTP/SFTP JSON File

FTP/SFTP XML File

FTP/SFTP CSV File

Build your own Custom API Connector

Other application integration scenarios for Amazon S3 XML File

SSIS

SQL Server

Power BI

Informatica

MS Access

MS Excel

SSAS

C#

Python

JAVA

Tableau

SAP Crystal Reports

Azure Data Factory (Pipeline)

Azure Data Factory (SSIS)

Talend Studio

UiPath

PowerShell

ODBC

Common Searches: