Amazon S3 JSON File Connector for PowerShell

In this article you will learn how to integrate Amazon S3 JSON File data in PowerShell without coding in just a few clicks (live / bi-directional connection to Amazon S3 JSON File). Amazon S3 JSON File Connector can be used to read JSON Files stored in AWS S3 Buckets. Using this you can easily integrate AWS S3 JSON File data. It's supports latest security standards, and optimized for large data files. It also supports reading compressed files (e.g. GZip /Zip)..

Using Amazon S3 JSON File Connector you will be able to connect, read, and write data from within PowerShell. Follow the steps below to see how we would accomplish that.

Download Documentation

The driver mentioned above is part of ODBC PowerPack which is a collection of high-performance Drivers for various API data source (i.e. REST API, JSON, XML, CSV, Amazon S3 and many more). Using familiar SQL query language you can make live connections and read/write data from API sources or JSON / XML / CSV Files inside SQL Server (T-SQL) or your favorite Reporting (i.e. Power BI, Tableau, Qlik, SSRS, MicroStrategy, Excel, MS Access), ETL Tools (i.e. Informatica, Talend, Pentaho, SSIS). You can also call our drivers from programming languages such as JAVA, C#, Python, PowerShell etc.

If you are new to ODBC and ZappySys ODBC PowerPack then check the following links to get started.

Connect to Amazon S3 JSON File in other apps

Connect to Amazon S3 JSON File in SSIS

Connect to Amazon S3 JSON File in SQL Server

Connect to Amazon S3 JSON File in Power BI

Connect to Amazon S3 JSON File in SSRS

Connect to Amazon S3 JSON File in Informatica

Connect to Amazon S3 JSON File in MS Access

Connect to Amazon S3 JSON File in MS Excel

Connect to Amazon S3 JSON File in SSAS

Connect to Amazon S3 JSON File in C#

Connect to Amazon S3 JSON File in Python

Connect to Amazon S3 JSON File in JAVA

Connect to Amazon S3 JSON File in Tableau

Connect to Amazon S3 JSON File in SAP Crystal Reports

Connect to Amazon S3 JSON File in Azure Data Factory (Pipeline)

Connect to Amazon S3 JSON File in Azure Data Factory (SSIS)

Connect to Amazon S3 JSON File in Talend Studio

Connect to Amazon S3 JSON File in UiPath

Connect to Amazon S3 JSON File in ODBC

Create ODBC Data Source (DSN) based on ZappySys Amazon S3 JSON Driver

Step-by-step instructions

To get data from Amazon S3 JSON File using PowerShell we first need to create a DSN (Data Source) which will access data from Amazon S3 JSON File. We will later be able to read data using PowerShell. Perform these steps:

Install ZappySys ODBC PowerPack.
Open ODBC Data Sources (x64):
Create a User Data Source (User DSN) based on ZappySys Amazon S3 JSON Driver

ZappySys Amazon S3 JSON Driver

You should create a System DSN (instead of a User DSN) if the client application is launched under a Windows System Account, e.g. as a Windows Service. If the client application is 32-bit (x86) running with a System DSN, use ODBC Data Sources (32-bit) instead of the 64-bit version.
Create and configure a connection for the Amazon S3 storage account.
You can use select your desired single file by clicking [...] path button.

mybucket/dbo.tblNames.json

dbo.tblNames.json

----------OR----------
You can also read the multiple files stored in Amazon S3 Storage using wildcard pattern supported e.g. dbo.tblNames*.json.
```
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.json (will read only single .JSON file)
mybucket/dbo.tbl*.json (all files starting with file name)
mybucket/*.json (all files with .json Extension and located under folder subfolder)
```
mybucket/dbo.tblNames*.json

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

mybucket/dbo.tblNames*.gz
Now select/enter Path expression in Path textbox to extract only specific part of JSON string as below ($.value[*] will get content of value attribute from JSON document. Value attribute is array of JSON 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.
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.json

vt__Orders
DataPath=mybucket_2/orders.json

vt__Products
DataPath=mybucket_3/products.json
```
  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.
Click OK to finish creating the data source
That's it; we are done. In a few clicks we configured the to Read the Amazon S3 JSON File data using ZappySys Amazon S3 JSON File Connector

Read Amazon S3 JSON File data in PowerShell

Sometimes, you need to quickly access and work with your Amazon S3 JSON File data in PowerShell. Whether you need a quick data overview or the complete dataset, this article will guide you through the process. Here are some common scenarios:

Viewing data in a terminal

Quickly peek at Amazon S3 JSON File data
Monitor data constantly in your console

Saving data to a file

Export data to a CSV file so that it can be sliced and diced in Excel
Export data to a JSON file so that it can ingested by other processes
Export data to an HTML file for user-friendly view and easy sharing
Create a schedule to make it an automatic process

Saving data to a database

Store data internally for analysis or for further ETL processes
Create a schedule to make it an automatic process

Sending data to another API

Integrate data with other systems via external APIs

In this article, we will delve deeper into how to quickly view the data in PowerShell terminal and how to save it to a file. But let's stop talking and get started!

Reading individual fields

Open your favorite PowerShell IDE (we are using Visual Studio Code).

Then simply follow these instructions:

"DSN=AmazonS3JsonFileDSN"

Read API data with PowerShell using ODBC DSN in Visual Code

For your convenience, here is the whole PowerShell script:

# Configure connection string and query
$connectionString = "DSN=AmazonS3JsonFileDSN"
$query = "SELECT * FROM Customers"

# Instantiate OdbcDataAdapter and DataTable
$adapter = New-Object System.Data.Odbc.OdbcDataAdapter($query, $connectionString)
$table = New-Object System.Data.DataTable

# Fill the table with data
$adapter.Fill($table)

# Since we know we will be reading just 4 columns, let's define format for those 4 columns, each separated by a tab
$format = "{0}`t{1}`t{2}`t{3}"

# Display data in the console
foreach ($row in $table.Rows)
{
    # Construct line based on the format and individual Amazon S3 JSON File fields
    $line = $format -f ($row["CustomerId"], $row["CompanyName"], $row["Country"], $row["Phone"])
    Write-Host $line
}

Access specific Amazon S3 JSON File table field using this code snippet:

$field = $row["ColumnName"]

You will find more info on how to manipulate DataTable.Rows property in Microsoft .NET reference.

For demonstration purposes we are using sample tables which may not be available in Amazon S3 JSON File.

To read values in a console, save the script to a file and then execute this command inside PowerShell terminal:
You can also use even a simpler command inside the terminal, e.g.:
```
. 'C:\Users\john\Documents\dsn.ps1'
```

Retrieving all fields

However, there might be case, when you want to retrieve all columns of a query. Here is how you do it:

"DSN=AmazonS3JsonFileDSN"

Read all API columns from ODBC data source in PowerShell

Again, for your convenience, here is the whole PowerShell script:

# Configure connection string and query
$connectionString = "DSN=AmazonS3JsonFileDSN"
$query = "SELECT CustomerId, CompanyName, Country, Phone FROM Customers"

# Instantiate OdbcDataAdapter and DataTable
$adapter = New-Object System.Data.Odbc.OdbcDataAdapter($query, $connectionString)
$table = New-Object System.Data.DataTable

# Fill the table with data
$adapter.Fill($table)

# Display data in the console
foreach ($row in $table.Rows) {
    $line = ""
    foreach ($column in $table.Columns) {
        $value = $row[$column.ColumnName]

        # Let's handle NULL values
        if ($value -is [DBNull])
        {
            $value = "(NULL)"
        }
        $line += $value + "`t"
    }
    Write-Host $line
}

You can limit the numbers of lines to retrieve by using a LIMIT keyword in the query, e.g.:

SELECT * FROM Customers LIMIT 10

Using a full ODBC connection string

In the previous steps we used a very short format of ODBC connection string - a DSN. Yet sometimes you don't want a dependency on an ODBC data source (and an extra step). In those times, you can define a full connection string and skip creating an ODBC data source entirely. Let's see below how to accomplish that in the below steps:

Open ODBC data source configuration and click Copy settings:

ZappySys Amazon S3 JSON Driver - Amazon S3 JSON File

Amazon S3 JSON File Connector can be used to read JSON Files stored in AWS S3 Buckets. Using this you can easily integrate AWS S3 JSON File data. It's supports latest security standards, and optimized for large data files. It also supports reading compressed files (e.g. GZip /Zip).

AmazonS3JsonFileDSN
The window opens, telling us the connection string was successfully copied to the clipboard:
Then just paste the connection string into your script:
You are good to go! The script will execute the same way as using a DSN.

Have in mind that using a full connection string has length limitations.

Proceed to the next step to find out the details.

Write Amazon S3 JSON File data to a file in PowerShell

Save data to a CSV file

Export data to a CSV file so that it can be sliced and diced in Excel:

# Configure connection string and query
$connectionString = "DSN=AmazonS3JsonFileDSN"
$query = "SELECT * FROM Customers"

# Instantiate OdbcDataAdapter and DataTable
$adapter = New-Object System.Data.Odbc.OdbcDataAdapter($query, $connectionString)
$table = New-Object System.Data.DataTable

# Fill the table with data
$adapter.Fill($table)

# Export table data to a file
$table | ConvertTo-Csv -NoTypeInformation -Delimiter "`t" | Out-File "C:\Users\john\saved-data.csv" -Force

Save data to a JSON file

Export data to a JSON file so that it can ingested by other processes (use the above script, but change this part):

# Export table data to a file
$table | ConvertTo-Json | Out-File "C:\Users\john\saved-data.json" -Force

Save data to an HTML file

Export data to an HTML file for user-friendly view and easy sharing (use the above script, but change this part):

# Export table data to a file
$table | ConvertTo-Html | Out-File "C:\Users\john\saved-data.html" -Force

Check useful PowerShell cmdlets other than ConvertTo-Csv, ConvertTo-Json, and ConvertTo-Html for other data manipulation scenarios.

Advanced topics

Create Custom Stored Procedure in ZappySys Driver

You can create procedures to encapsulate custom logic and then only pass handful parameters rather than long SQL to execute your API call.

Steps to create Custom Stored Procedure in ZappySys Driver. You can insert Placeholders anywhere inside Procedure Body. Read more about placeholders here

Go to Custom Objects Tab and Click on Add button and Select Add Procedure:
Enter the desired Procedure name and click on OK:
Select the created Stored Procedure and write the your desired stored procedure and Save it and it will create the custom stored procedure in the ZappySys Driver:
Here is an example stored procedure for ZappySys Driver. You can insert Placeholders anywhere inside Procedure Body. Read more about placeholders here
```
CREATE PROCEDURE [usp_get_orders]
    @fromdate = '<<yyyy-MM-dd,FUN_TODAY>>'
 AS
    SELECT * FROM Orders where OrderDate >= '<@fromdate>';
```
That's it now go to Preview Tab and Execute your Stored Procedure using Exec Command. In this example it will extract the orders from the date 1996-01-01:
```
Exec usp_get_orders '1996-01-01';
```
Let's generate the SQL Server Query Code to make the API call using stored procedure. Go to Code Generator Tab, select language as SQL Server and click on Generate button the generate the code.
As we already created the linked server for this Data Source, in that you just need to copy the Select Query and need to use the linked server name which we have apply on the place of [MY_API_SERVICE] placeholder.
```
SELECT * FROM OPENQUERY([MY_API_SERVICE], 'EXEC usp_get_orders @fromdate=''1996-07-30''')
```
Now go to SQL served and execute that query and it will make the API call using stored procedure and provide you the response.

Create Custom Virtual Table in ZappySys Driver

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.

If you're dealing with Microsoft Access and need to import data from an SQL query, it's important to note that Access doesn't allow direct import of SQL queries. Instead, you can create custom objects (Virtual Tables) to handle the import process.

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 URLs with slight variations you can create virtual tables with just URL as Parameter setting.

Go to Custom Objects Tab and Click on Add button and Select Add Table:
Enter the desired Table name and click on OK:
And it will open the New Query Window Click on Cancel to close that window and go to Custom Objects Tab.
Select the created table, Select Text Type AS SQL and write the your desired SQL Query and Save it and it will create the custom table in the ZappySys Driver:
Here is an example SQL query for ZappySys Driver. You can insert Placeholders also. Read more about placeholders here
```
SELECT
  "ShipCountry",
  "OrderID",
  "CustomerID",
  "EmployeeID",
  "OrderDate",
  "RequiredDate",
  "ShippedDate",
  "ShipVia",
  "Freight",
  "ShipName",
  "ShipAddress",
  "ShipCity",
  "ShipRegion",
  "ShipPostalCode"
FROM "Orders"
Where "ShipCountry"='USA'
```
That's it now go to Preview Tab and Execute your custom virtual table query. In this example it will extract the orders for the USA Shipping Country only:
```
SELECT * FROM "vt__usa_orders_only"
```
Let's generate the SQL Server Query Code to make the API call using stored procedure. Go to Code Generator Tab, select language as SQL Server and click on Generate button the generate the code.
As we already created the linked server for this Data Source, in that you just need to copy the Select Query and need to use the linked server name which we have apply on the place of [MY_API_SERVICE] placeholder.
```
SELECT * FROM OPENQUERY([MY_API_SERVICE], 'EXEC [usp_get_orders] ''1996-01-01''')
```
Now go to SQL served and execute that query and it will make the API call using stored procedure and provide you the response.

Conclusion

In this article we discussed how to connect to Amazon S3 JSON File in PowerShell and integrate data without any coding. Click here to Download Amazon S3 JSON File Connector for PowerShell and try yourself see how easy it is. If you still have any question(s) then ask here or simply click on live chat icon below and ask our expert (see bottom-right corner of this page).

Download Amazon S3 JSON File Connector for PowerShell Documentation

More integrations

Other application integration scenarios for Amazon S3 JSON File

SSIS

SQL Server

Power BI

SSRS

Informatica

MS Access

MS Excel

SSAS

Python

JAVA

Tableau

SAP Crystal Reports

Azure Data Factory (Pipeline)

Azure Data Factory (SSIS)

Talend Studio

UiPath

ODBC

Other connectors for PowerShell

Amazon Ads

Amazon MWS

Amazon Selling Partner (SP-API)

Asana

Azure DevOps

Cosmos DB

DropBox

FastSpring

Google Drive

Hubspot

Jira

Mailchimp

ManagedEngine ServiceDesk Plus (Zoho)

Nativo

OData

OneDrive

Outlook Mail (Office 365)

Power BI

ServiceNow

SharePoint Online

Shopify

Smartsheet

Stripe

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

Download Amazon S3 JSON File Connector for PowerShell Documentation

Common Searches:

How to connect Amazon S3 JSON File in PowerShell?
How to get Amazon S3 JSON File data in PowerShell?
How to read Amazon S3 JSON File data in PowerShell?
How to load Amazon S3 JSON File data in PowerShell?
How to import Amazon S3 JSON File data in PowerShell?
How to pull Amazon S3 JSON File data in PowerShell?
How to push data to Amazon S3 JSON File in PowerShell?
How to write data to Amazon S3 JSON File in PowerShell?
How to POST data to Amazon S3 JSON File in PowerShell?
Call Amazon S3 JSON File API in PowerShell
Consume Amazon S3 JSON File API in PowerShell
Amazon S3 JSON File PowerShell Automate
Amazon S3 JSON File PowerShell Integration
Integration Amazon S3 JSON File in PowerShell
Consume real-time Amazon S3 JSON File data in PowerShell
Consume real-time Amazon S3 JSON File API data in PowerShell
Amazon S3 JSON File ODBC Driver | ODBC Driver for Amazon S3 JSON File | ODBC Amazon S3 JSON File Driver | SSIS Amazon S3 JSON File Source | SSIS Amazon S3 JSON File Destination
Connect Amazon S3 JSON File in PowerShell
Load Amazon S3 JSON File in PowerShell
Load Amazon S3 JSON File data in PowerShell
Read Amazon S3 JSON File data in PowerShell
Amazon S3 JSON File API Call in PowerShell