AWS ground-station documentation change
Summary
Added subnet IP availability as a failure cause and recommendation to check IP addresses
Security assessment
Identifies resource exhaustion (IP addresses) as a failure cause but does not indicate security implications. Focuses on service availability rather than security vulnerabilities.
Diff
diff --git a/ground-station/latest/ug/troubleshooting-failed-contacts.md b/ground-station/latest/ug/troubleshooting-failed-contacts.md index 71f0389e0..8ee587f42 100644 --- a//ground-station/latest/ug/troubleshooting-failed-contacts.md +++ b//ground-station/latest/ug/troubleshooting-failed-contacts.md @@ -22,0 +23,2 @@ The following is the list of common use cases that can result in a **FAILED** co + * **Dataflow endpoint’s subnet is out of available IP addresses** \- AWS Ground Station’s data delivery solution is not able to create an ENI in your private network due to not having any available IP address in the reciever instance's subnet. + @@ -31,0 +34,2 @@ For any dataflow endpoint failure cases, it is recommended to look into the foll + * Ensure you have at least one available IP address per dataflow endpoint per receiver instance subnet. +