AWS ground-station documentation change
Summary
Added troubleshooting note about invalid subnets in Dataflow Endpoint Groups and guidance to ensure subnet availability
Security assessment
The changes address general connectivity and configuration issues rather than specific security vulnerabilities. No evidence of security incident remediation or vulnerability disclosure.
Diff
diff --git a/ground-station/latest/ug/troubleshooting-failed-contacts.md b/ground-station/latest/ug/troubleshooting-failed-contacts.md index 8ee587f42..27223bc07 100644 --- a//ground-station/latest/ug/troubleshooting-failed-contacts.md +++ b//ground-station/latest/ug/troubleshooting-failed-contacts.md @@ -24,0 +25,2 @@ The following is the list of common use cases that can result in a **FAILED** co + * **Dataflow endpoint’s subnet is invalid** \- AWS Ground Station’s data delivery solution is not able to create an ENI in your private network due to inability to access the provided subnet specified in the Dataflow Endpoint Group. + @@ -35,0 +38,2 @@ For any dataflow endpoint failure cases, it is recommended to look into the foll + * Ensure subnets associated to your Dataflow Endpoint Group, through dataflows configured in [Set up and configure Amazon VPC](./dataflows.vpc-configuration.html), remain active and available to AWS Ground Station. +