Dataflow Endpoint Groups - AWS Ground Station

Dataflow Endpoint Groups

Dataflow endpoints define the location where you want the data to be streamed to or from during contacts. The endpoints are identified by a name of your choosing when executing contacts. These names do not need to be unique. This allows multiple contacts to be executed at the same time using the same mission profile.

The endpoint list address consists of the following:

  • name - IP address of this dataflow endpoint.

  • port - The port to connect to.

The security details of an endpoint consist of the following:

  • roleArn - The Amazon Resource Name (ARN) of a role that AWS Ground Station will assume to create Elastic Network Interfaces (ENIs) in your VPC. These ENIs serve as the ingress and egress points of data streamed during a contact.

  • securityGroupIds - The security groups to attach to the elastic network interfaces.

  • subnetIds - A list of subnets where AWS Ground Station places elastic network interfaces to send streams to your instances.

Dataflow endpoints are always created as part of a dataflow endpoint group. By including multiple dataflow endpoints in a group, you are asserting that the specified endpoints can all be used together during a single contact. For example, if a contact needs to send data to three separate dataflow endpoints, you must have three endpoints in a single dataflow endpoint group that match the dataflow endpoint configs in your mission profile.

When one or more resources in a dataflow endpoint group is in use for a contact, the entire group is reserved for the duration of that contact. You may execute multiple contacts concurrently, but those contacts must be executed on different dataflow endpoint groups.

See the following documentation for more information about how to perform operations on dataflow endpoint groups using AWS CloudFormation, the AWS Command Line Interface, or the AWS Ground Station API.