Creating Edge Delta Cloud Fleets

Installing Edge Delta Cloud Fleets.

  4 minute read  

Beta

Overview

Cloud Fleets are Edge Delta Fleets that are hosted in cloud infrastructure owned and managed by the Edge Delta team. You might decide to use Cloud Fleets in the following scenarios:

  • data sources are serverless workloads such as AWS Lambda functions or events generated from Amazon Kinesis.
  • lightweight edge environments host thin data producers, such as Internet of Things.
  • you do not want to take on resource management associated with hosting an additional workload.
  • security limitations exist for deploying a fleet in your environment.

You can create, configure, and remove fleet configurations using the Edge Delta interface. The Cloud Fleet expose an HTTP, HTTPS, or GRPCS endpoint so you can push data to it. If you don’t create an HTTPS endpoint, you can still pull data into the Fleet by specifying a pull data source in the Pipeline configuration. When you create a Cloud Fleet, you should select a location that is logically close to your data source, for example, in the same region or hosted on the same provider.

Push or Pull Data Inputs

Cloud Fleets cater for both push or pull data input integrations. To push data to the Cloud Fleet, configure an endpoint and configure your sources such as a CDN or Amazon Kinesis to push data to that endpoint. To pull data into the Cloud Fleet, add a source node configured with your data source’s endpoint to the Cloud Fleet’s pipeline configuration.

Managing a Cloud Fleet

Click Pipelines and select Cloud Fleets from the filter on the Fleets table.

Creating a Cloud Fleet

  1. Click Pipelines.
  2. Click New Fleet.
  3. Select Cloud Fleet
  4. Optionally, expand Advanced fleet configuration and choose a pipeline configuration to duplicate for the cloud fleet. If you don’t select one, a default configuration will be used.
  5. Click Continue.
  6. Specify a name to identify the Fleet.
  7. Optionally, expand Advanced Settings and select Compute Units based on your estimated traffic volume. This is the maximum bandwidth the agent can handle before signalling an error. The number of compute units used per hour counts towards your plan usage.
  8. Optionally, specify an agent version. The interface lists the current stable version (the latest version number) and most recent candidate version (containing rc). Choose the current stable version. If this configuration doesn’t work you can contact Edge Delta support to experiment with the candidate.
  9. Optionally, select protocols for endpoints on the Cloud Fleet that your sources can push data to. The default is an HTTPS endpoint.
  10. Click Deploy Cloud Fleet.

The new Cloud fleet is added to the Cloud Fleets table. If you configured an endpoint, the URL is listed on the Fleet’s details pane. Configure your workloads to push to this endpoint. When an HTTPS endpoint is configured, an HTTP source node is added to the Fleet’s Pipeline configuration.

If you created a Cloud Fleet with an existing pipeline configuration in step 7, and you selected an endpoint to push traffic to it, you need to add this node manually.

If you created a Cloud Fleet without an endpoint, you need to add a source node to its pipeline and specify your data source’s endpoint to pull traffic from your data source.

Cloud Fleet Resources

You can change a Cloud Fleet’s Compute Units setting. This is the maximum bandwidth the agent can handle before signalling an error:

  1. Select the cloud fleet on the Pipelines page.
  2. Click Options and select Edit Fleet Settings.

The Edit Cloud Fleet Settings page opens and you can make the changes to the resource settings.

Bear in mind the number of compute units you use per hour contribute to your plan usage.

Delete a Cloud Fleet

To delete a Cloud Fleet: Select the fleet on the Pipelines page. Click Options and select Delete Fleet.

Suspend a Cloud Fleet s

To suspend a Cloud Fleet: Select the fleet on the Pipelines page. Click Options and select Suspend Cloud Fleet.