Work with dataflows

AWS Ground Station uses a node and edge relationship to construct dataflows to enable stream processing of your data. Each node is represented by a config which describes its expected processing. To illustrate this concept, consider a dataflow of antenna-downlink to a s3-recording. The antenna-downlink node represents the analog to digital transformation of the radio frequency spectrum per the defined parameters on the config. The s3-recording represents a compute node which will receive incoming data and store it in your S3 bucket. The resulting dataflow is an asynchronous data delivery of digitized RF data to an S3 bucket based on your specifications.

Within your mission profile, you can create many dataflows to meet your needs. The following sections describe how to set up your other AWS resources to be used with AWS Ground Station and offers recommendations for constructing dataflows. For detailed information on how each node behaves, including if it is considered a source or destination node, please see Use AWS Ground Station Configs.

AWS Ground Station data plane interfaces

The resulting data structure of your chosen dataflow depends on the source of the dataflow. Details of these formats are provided to you during the onboarding of your satellites. The following summarizes the formats used for each type of dataflow.