AWS::GroundStation::Config ConfigData - AWS CloudFormation

AWS::GroundStation::Config ConfigData

Config objects provide information to Ground Station about how to configure the antenna and how data flows during a contact.

Syntax

To declare this entity in your AWS CloudFormation template, use the following syntax:

Properties

AntennaDownlinkConfig

Provides information for an antenna downlink config object. Antenna downlink config objects are used to provide parameters for downlinks where no demodulation or decoding is performed by Ground Station (RF over IP downlinks).

Required: No

Type: AntennaDownlinkConfig

Update requires: No interruption

AntennaDownlinkDemodDecodeConfig

Provides information for a downlink demod decode config object. Downlink demod decode config objects are used to provide parameters for downlinks where the Ground Station service will demodulate and decode the downlinked data.

Required: No

Type: AntennaDownlinkDemodDecodeConfig

Update requires: No interruption

AntennaUplinkConfig

Provides information for an uplink config object. Uplink config objects are used to provide parameters for uplink contacts.

Required: No

Type: AntennaUplinkConfig

Update requires: No interruption

DataflowEndpointConfig

Provides information for a dataflow endpoint config object. Dataflow endpoint config objects are used to provide parameters about which IP endpoint(s) to use during a contact. Dataflow endpoints are where Ground Station sends data during a downlink contact and where Ground Station receives data to send to the satellite during an uplink contact.

Required: No

Type: DataflowEndpointConfig

Update requires: No interruption

TrackingConfig

Provides information for a tracking config object. Tracking config objects are used to provide parameters about how to track the satellite through the sky during a contact.

Required: No

Type: TrackingConfig

Update requires: No interruption

UplinkEchoConfig

Provides information for an uplink echo config object. Uplink echo config objects are used to provide parameters for uplink echo during uplink contacts.

Required: No

Type: UplinkEchoConfig

Update requires: No interruption

Examples

Create a ConfigData

A ConfigData can only contain a single config subtype. See the config subtype's documentation for more information on its properties. An example of a TrackingConfig is provided below.

JSON

{ "TrackingConfig": { "Autotrack": "PREFERRED" } }

YAML

TrackingConfig: Autotrack: "PREFERRED"