Troubleshooting invalid ephemerides

When a custom ephemeris is uploaded to AWS Ground Station it goes through an asynchronous validation workflow before becoming ENABLED. This workflow ensures that the satellite identifiers, metadata, and trajectory are valid.

When an ephemeris fails validation, DescribeEphemeris will return an EphemerisInvalidReason, which provides insight into why the ephemeris failed validation. The potential values of the EphemerisInvalidReason are as follows:

Value	Description	Troubleshooting Action
METADATA_INVALID	Provided spacecraft identifiers such as satellite ID are invalid	Check the NORAD ID or other identifiers provided in the ephemeris data
TIME_RANGE_INVALID	Start, end, or expiration time(s) are invalid for the provided ephemeris	Make sure the Start time is before `now` (it is recommended to set the start time a few minutes in the past), that the end time is after the start time, and that the end time is after the expiration time
TRAJECTORY_INVALID	Provided ephemeris defines an invalid spacecraft trajectory	Confirm that the provided trajectory is continuous and is for the correct satellite.
VALIDATION_ERROR	Internal service error occurred while processing ephemeris for validation	Retry Upload

An example DescribeEphemeris response for an INVALID ephemeris is provided below:

{
  "creationTime": 1000000000.00,
  "enabled": false,
  "ephemerisId": "d5a8a6ac-8a3a-444e-927e-EXAMPLE1",
  "name": "Example",
  "priority": 2,
  "status": "INVALID",
  "invalidReason": "METADATA_INVALID",
  "suppliedData": {
    "tle": {
      "sourceS3Object": {
        "bucket": "my-s3-bucket",
        "key": "myEphemerisKey",
        "version": "ephemerisVersion"
      }
    }
  },
}

Note

If an ephemeris's status is ERROR, the ephemeris is not ENABLED due to a problem with the AWS Ground Station service. You should try providing the ephemeris again via CreateEphemeris. The new ephemeris may become ENABLED if the problem was transient.