The NetStorage service of Akamai provides many ways to interact with it. The best way from our perspective is to use its HTTP API interface. In this tutorial you will learn how it works and what it needs to obtain proper credentials to create an Akamai NetStorage Input/Output in our service.
The biggest advantage is the recilience of HTTP requests and the amount of parallel connections you can leverage compared to FTP transfers, where it is capped to 25 connections for one akamai upload account. The `
NetStorage HTTP CMS API` however doesn't has such limits and is therefore well suited to handle many parallel chunked transfers in a fast and reliable manner.
So lets look into it how you can configure an Akamai NetStorage to be used for your encodings in our service.
**IMPORTANT**: This tutorial assumes that you already have access to an Akamai NetStorage and Setup and a dedicated Upload Account for it. If you are missing any of it yet, [please read through this tutorial first](🔗) on how to create an Akamai NetStorage and Upload Account before you proceed with this tutorial.
# Create a Bitmovin Akamai NetStorage Input
To create a Bitmovin ["Akamai NetStorage" Input configuration](🔗), that can be used by our encoding service, you need to know the `
HTTP API Key` and `
Username` of your upload account, as well as its `
## Use the Dashboard UI
Select the `
Encoding` menu on the left and go to `
Click on `
Create` in the upper right corner of the Inputs overview
Akamai` as Input type and
Enter all required fields (please see the image below)
Click on `
## Use an Bitmovin API SDK
Each of our Open API SDK's implements the Bitmovin API, and make it easy to start its integration in your project or use-case. Use them to create reusable input resources to be used for your encodings:
**Bitmovin API SDK for Java - Input example**
See all available examples for each of our Bitmovin API SDK's in our [GH Example Repository](🔗).