Getting Started
Linking Your Cloud Account

Linking Your Cloud Account

Ferry is the first cloud-agnostic developer platform for building & deploying edge applications, integrating natively with your AWS and Azure cloud accounts. It deploys your applications to physical devices utilizing cloud resources which you have full control over at all times (AWS IoT Core & Greengrass; Azure IoT Edge) - whilst giving users a seamless no-code solution to initiate, manage & scale deployments across device fleets.

Ferry is built with a set of core principles in mind:

  1. Provide users with full control & visibility over their cloud resources. Every resource in Ferry is backed by equivalent cloud resources in your own AWS or Azure account. Ferry deploys applications to your devices via your AWS Greengrass or Azure IoT Edge resources. This means that you have full visibility into your cloud edge resources at all times, both through Ferry, and through your cloud provider.

  2. Provide users with full control over their data. All data collected from your devices sent to the cloud resides in your own cloud accounts; it does not get transferred through Ferry.

  3. Provide a simple yet powerful no-code deployment solution built on the public cloud. Both AWS and Azure are tried & trusted public cloud platforms. Ferry automates the tedious infrastructure set-up that users would need to undertake if they were to interact with the cloud providers directly, to accelerate time-to-market with security best practices in mind.

  4. Allow interoperability with existing cloud investments. Companies often having existing services provisioned via AWS and Azure for their cloud native services. Ferry allows companies to add edge & IoT functionality within their existing cloud provider, allowing for easy interoperability with the rest of their tech stack.

Ferry requires minimal identity & access management permissions to integrate with your cloud provider to provision devices & deploy applications to them. Further details, including how to set-up integrations for AWS here (opens in a new tab), and for Azure here (opens in a new tab).

Why Ferry is cloud-agnostic

There are many benefits that a cloud-agnostic edge platform provide to companies & enterprises:

  1. Avoid vendor lock-in. Seamlessly transition devices and edge workloads from one cloud provider to another & manage costs.

  2. Different geographical regions may require different cloud providers. Jurisdictions vary on their data privacy and residency requirements, which in turn determines which cloud providers companies can use for their IoT and edge deployments across regions.

  3. Leverage existing multi-cloud investments. Companies often need to integrate their edge & IoT offerings with existing IT and operational systems. As companies & enterprises transition to a multi-cloud framework across the rest of their digital infrastructure, IoT & edge solutions need to follow suit for interoperability with the rest of the technological stack.

  4. Be flexible for end-customer needs. Depending on their own requirements, end-customers often have a preference for one cloud provider over another, and companies need flexibility to be able to serve their end-customers needs. Ferry provides that flexibility out-of-the-box.

The relationship between objects in Ferry and AWS / Azure

All objects in Ferry are synced with your cloud provider so you have full visibility and control over your cloud resources and devices. Below is how Ferry objects relate to cloud resources we help you manage in AWS and Azure.

Ferry Objects

AWS Objects

Azure Objects

Workspace

N/A

Resource Group

Node Group

Thing Groups (IoT Core)

[This does not exist within Azure, we tag your Devices with the Node Group ID for tracking]

Node

Thing (IoT Core) When a Node is provisioned in AWS Greengrass, a matching Core Device (Greengrass) is created.

Device To provision your Nodes with Azure, we create a corresponding Azure IoT Device Provisioning Service

Component

Component (Greengrass)

Blob Storage for file storage

Component Version

Component (Greengrass) Code versions are stored within the a dedicated S3 bucket for your Workspace

Blob Storage for file storage Azure IoT Edge uses Docker containers. We build the Docker containers in your Azure account, and store the built images in an Azure Container Registry that we auto-provision for you

Deployment

N/A Ferry abstracts the complexity of handling AWS Greengrass deployments.

N/A Ferry abstracts the complexity of handling Azure IoT Edge deployments

You can find out more about how Ferry works with your AWS and Azure accounts below: