AWS ground-station documentation change
Summary
Added troubleshooting step to check available IP addresses in receiver instance subnets to prevent dataflow issues
Security assessment
Change addresses operational reliability by ensuring sufficient IP addresses for ENI creation. No evidence of security vulnerability mitigation or security feature documentation added.
Diff
diff --git a/ground-station/latest/ug/troubleshooting-contact.md b/ground-station/latest/ug/troubleshooting-contact.md index 7a49e65e5..a98f09b1d 100644 --- a//ground-station/latest/ug/troubleshooting-contact.md +++ b//ground-station/latest/ug/troubleshooting-contact.md @@ -5 +5 @@ -Step 1: Verify that your EC2 instance is running Step 2: Determine type of dataflow application used Step 3: Verify that dataflow application is runningStep 4: Verify that your dataflow application stream is configured +Step 1: Verify that your EC2 instance is running Step 2: Determine type of dataflow application used Step 3: Verify that dataflow application is runningStep 4: Verify that your dataflow application stream is configuredStep 5: Ensure you have enough available IP addresses in your receiver instance(s) subnet @@ -117 +117,26 @@ If DataDefender is running after checking your Amazon VPC settings, continue to -You have now ensured that your Amazon EC2 instance and DataDefender are both running and configured properly to receive data from AWS Ground Station. If you continue experience issues, [contact AWS Support](https://aws.amazon.com/support/createCase). +You have now ensured that your Amazon EC2 instance and DataDefender are both running and configured properly to receive data from AWS Ground Station. Continue to Step 5: Ensure you have enough available IP addresses in your receiver instance(s) subnet. + +## Step 5: Ensure you have enough available IP addresses in your receiver instance(s) subnet + +The following procedure shows how to find the number of available IP addresses in an Amazon EC2 reciever instance in the console. + + 1. For each Amazon EC2 receiver instance that was used for the contact you are troubleshooting. Use the following steps: + + 1. In your **AWS CloudFormation** dashboard, select the stack that contains your Amazon EC2 instance. + + 2. Choose the **Resources** tab and locate your Amazon EC2 instance in the **Logical ID** column. Verify that the instance is created in the **Status** column. + + 3. In the **Physical ID** column, choose the link for your Amazon EC2 instance. This will take you to the Amazon EC2 management console. + + 2. In the Amazon EC2 management console, find and click the **Subnet ID** link in your Amazon EC2 receiver instance's **Instance Summary**. This will take you to the corresponding Amazon VPC management console. + + 3. Select the matching subnet in the Amazon VPC management console and check the **Details** of your subnet for **Available IPv4 addresses**. If this number is not at least as many as dataflow endpoints that use this Amazon EC2 receiver instance do the following: + + 1. Update your AWS CloudFormation template's corresponding subnet **CidrBlock** to be sized correctly. For more details on subnet sizing see, [Subnet CIDR blocks](https://docs.aws.amazon.com/vpc/latest/userguide/subnet-sizing.html). + + 2. Redeploy your stack with your updated AWS CloudFormation template. + + + + +If you continue to experience issues, [contact AWS Support](https://aws.amazon.com/support/createCase).