AWS outposts documentation change
Summary
Added troubleshooting sections for capacity task conflicts (Outpost-level and asset-level) and invalid AssetID validation, including resolution steps via console/CLI
Security assessment
The changes address operational issues related to capacity task management and asset validation, not security vulnerabilities. No evidence of security patches, access control changes, or vulnerability disclosures. Focus is on resolving task conflicts and state validation.
Diff
diff --git a/outposts/latest/userguide/order-troubleshooting.md b/outposts/latest/userguide/order-troubleshooting.md index cb611ef37..78aad729f 100644 --- a//outposts/latest/userguide/order-troubleshooting.md +++ b//outposts/latest/userguide/order-troubleshooting.md @@ -5 +5 @@ -Order oo-xxxxxx is not associated with Outpost ID op-xxxxxThe capacity plan includes instance types that are not supportedNo Outpost with Outpost ID op-xxxxx +Order oo-xxxxxx is not associated with Outpost ID op-xxxxxThe capacity plan includes instance types that are not supportedNo Outpost with Outpost ID op-xxxxxActive CapacityTask cap-XXXX already found for Outpost op-XXXX Active CapacityTask cap-XXXX already found for Asset XXXX on Outpost op-XXXXAssetId=XXXX is not valid for Outpost=op-XXXX @@ -93,0 +94,117 @@ To resolve this issue: +## Active CapacityTask cap-`XXXX` already found for Outpost op-`XXXX` + +This issue occurs when you use the AWS Outposts console or API to run [StartCapacityTask](https://docs.aws.amazon.com/outposts/latest/APIReference/API_StartCapacityTask.html) on an Outpost and there is already a running capacity task for the Outpost. A capacity task is considered running if it has any of the following statuses: `REQUESTED`, `IN_PROGRESS`, `WAITING_FOR_EVACUATION`, or `CANCELLATION_IN_PROGRESS`. + +To resolve this issue, use the AWS Outposts console or CLI. + +###### Use the console + + 1. Sign in to AWS. + + 2. Open the AWS Outposts console at [https://console.aws.amazon.com/outposts/](https://console.aws.amazon.com/outposts/home). + + 3. From the navigation pane, choose **Capacity tasks**. + + 4. Ensure that there are no running capacity tasks for the OutpostId. + + 5. If there are running capacity tasks for the OutpostId, wait for them to terminate, or cancel them if desired. + + 6. When there no running capacity tasks for the requested OutpostId, retry your request to create the capacity task. + + + + +###### Use the CLI + + 1. Use the [ListCapacityTasks](https://docs.aws.amazon.com/outposts/latest/APIReference/API_ListCapacityTasks.html) command to find running capacity tasks for the Outpost. + + 2. Wait for all running capacity tasks to terminate, or cancel them if desired. + + 3. When there no running capacity tasks for the requested OutpostId, retry your request to create the capacity task. + + + + +## Active CapacityTask cap-`XXXX` already found for Asset `XXXX` on Outpost op-XXXX + +This issue occurs when you use the AWS Outposts console or API to run [StartCapacityTask](https://docs.aws.amazon.com/outposts/latest/APIReference/API_StartCapacityTask.html) on an asset and there is already a running capacity task for the asset. A capacity task is considered running if it has any of the following statuses: `REQUESTED`, `IN_PROGRESS`, `WAITING_FOR_EVACUATION`, or `CANCELLATION_IN_PROGRESS`. + +To resolve this issue, use the AWS Outposts console or CLI. + +###### Use the console + + 1. Sign in to AWS. + + 2. Open the AWS Outposts console at [https://console.aws.amazon.com/outposts/](https://console.aws.amazon.com/outposts/home). + + 3. From the navigation pane, choose **Capacity tasks**. + + 4. Ensure that there are no running capacity tasks for the OutpostId and no running asset-level capacity Tasks for the AssetId. + + 5. If there are running capacity tasks, wait for them to terminate, or cancel them if desired. + + 6. When there no running capacity tasks, retry your request to create the capacity task. + + + + +###### Use the CLI + + 1. Use the [ListCapacityTasks](https://docs.aws.amazon.com/outposts/latest/APIReference/API_ListCapacityTasks.html) command to find running capacity tasks for the OutpostID and AssetID. + + 2. Ensure that there are no running Outpost-level capacity tasks for the OutpostId, and no running asset-level capacity Tasks for the AssetId. + + 3. If there are running capacity tasks, wait for them to terminate, or cancel them if desired. + + 4. Retry your request to create the capacity task. + + + + +## AssetId=`XXXX` is not valid for Outpost=op-`XXXX` + +This issue occurs when you use the AWS Outposts console or API to run [StartCapacityTask](https://docs.aws.amazon.com/outposts/latest/APIReference/API_StartCapacityTask.html) on an asset and the AssetID is not valid for one of the following reasons: + + * The asset is not associated with the Outpost. + + * The asset is isolated. + + + + +To resolve this issue, use the AWS Outposts console or CLI. + +###### Use the console + + 1. Sign in to AWS. + + 2. Open the AWS Outposts console at [https://console.aws.amazon.com/outposts/](https://console.aws.amazon.com/outposts/home). + + 3. Choose **Rack view** for the Outpost. + + 4. Verify that the requested AssetId is associated with the Outpost, and that it is not marked as an Isolated Host. + + 1. If the Asset is isolated, this may be because a capacity task is running on it. You can navigate to the capacity tasks panel and check if there are any running Outpost or asset-level tasks for the OutpostId and AssetId. If there are, then wait for the task to terminate and for the asset to become available again. + + 2. If there are no running capacity tasks for an isolated asset, then the asset may be degraded. + + 5. After you verify that the asset exists and is in a valid state, retry your request to create the capacity task. + + + + +###### Use the CLI + + 1. Use the [ListAssets](https://docs.aws.amazon.com/outposts/latest/APIReference/API_ListAssets.html) command to find the assets associated with the OutpostID. + + 2. Verify that the requested AssetId is associated with the Outpost, and that its State is `ACTIVE`. + + 1. If the asset State is not ACTIVE, this may be because a capacity task is running on it. Use the [ListCapacityTasks](https://docs.aws.amazon.com/outposts/latest/APIReference/API_ListCapacityTasks.html) command to determine if there are running Outpost or asset-level tasks for the OutpostId and AssetId. If there are, then wait for the task to terminate and for the asset to become ACTIVE again. + + 2. If there are no running capacity tasks for an isolated asset, then the asset may be degraded. + + 3. After you verify that the asset exists and is in a valid state, retry your request to create the capacity task. + + + +