Configs - AWS Ground Station


Configs are resources that AWS Ground Station uses to define the parameters for each aspect of your contact. Add the configs you want to a mission profile, and then that mission profile will be used when executing the contact. You can define several different types of configs.

Dataflow Endpoint Config

You can use dataflow endpoint configs to specify which dataflow endpoints you want to use during contacts. The two parameters of a dataflow endpoint config specify the name and region of the dataflow endpoint. The example below tells the contact to use a dataflow endpoint with the name DataflowEndpoint1 in the US West (Oregon) Region (us-west-2) region. You can use the example code to create multiple dataflow endpoint groups across the AWS Regions and reuse the same config to execute contacts. If no dataflowEndpointRegion is specified, the dataflow endpoint will default to the region of the ground station.

{ "configData": { "dataflowEndpointConfig": { "dataflowEndpointName": "DataflowEndpoint1", "dataflowEndpointRegion": "us-west-2" } }, "name": "MyDataflowEndpointConfig" }

Tracking Config

You can use tracking configs in the mission profile to determine whether autotrack should be enabled during your contacts. This config has a single parameter: autotrack. The autotrack parameter can have the following values:

  • REQUIRED - Autotrack is required for your contacts.

  • PREFERRED - Autotrack is preferred for contacts, but contacts can still be executed without autotrack.

  • REMOVED - No autotrack should be used for your contacts.

The following is an example tracking config:

{ "configData": { "trackingConfig": { "autotrack": "REMOVED" }, }, "name": "MyTrackingConfig" }

Antenna Downlink Config

You can use antenna downlink configs to configure the antenna during your contact. They consist of a spectrum config that specifies the bandwidth, frequency, and polarization that should be used during your antenna downlink. If your downlink use case requires demodulation or decode, see the Antenna Downlink Demod Decode Config.

The following is an example antenna downlink config:

{ "antennaDownlinkConfig": { "spectrumConfig": { "bandwidth": { "units": "MHz", "value": 25 }, "centerFrequency": { "units": "MHz", "value": 8212.5 }, "polarization": "RIGHT_HAND" } }, "name": "MyAntennaDownlinkConfig" }

Antenna Uplink Config

You can use antenna uplink configs to configure the antenna during your uplink contact. They consist of a spectrum config with frequency, polarization, and targetEirp. For information about how to configure an uplink echo, see Antenna Uplink Echo Config.

The following is an example antenna uplink config:

{ "configData": { "antennaUplinkConfig": { "spectrumConfig": { "centerFrequency": { "units": "MHz", "value": 2091 }, "polarization": "RIGHT_HAND" }, "targetEirp": { "units": "dBW", "value": 20 } } }, "name": "MyAntennaUplinkConfig" }

Antenna Uplink Echo Config

Uplink echo configs tell the antenna how to execute an uplink echo. This echoes the signal sent by the antenna back to your dataflow endpoint. An uplink echo config contains the ARN of an uplink config. The antenna uses the parameters from the uplink config pointed to by the ARN when executing an uplink echo.

The following is an example antenna uplink echo config:

{ "configData": { "uplinkEchoConfig": { "antennaUplinkConfigArn": "arn:aws:groundstation:us-east-2:123456789012:config/antenna-uplink/11111111-2222-3333-4444-555555555555", "enabled": true } }, "name": "MyAntennaUplinkEchoConfig" }

Antenna Downlink Demod Decode Config

Antenna downlink demod decode configs are a more complex and customizable config type that you can use to execute downlink contacts with demod or decode. If you're interested in executing these types of contacts, contact the AWS Ground Station team. We'll help you define the right config and mission profile for your use case.