Troubleshooting capacity task issues

PDFRSS

Review the following known issues to resolve an issue related to capacity management in a new order. If you do not see your issue listed, contact Support.

Order oo-xxxxxx is not associated with Outpost ID op-xxxxx

This issue occurs when you use the AWS CLI or API to run the StartCapacityTask and the Outpost ID in the request does not match the Outpost ID in the order.

To resolve this issue:

1. Sign in to AWS.

2. Open the AWS Outposts console at https://console.aws.amazon.com/outposts/.

3. From the navigation pane, choose Orders.

4. Select the order and verify that the order status is one of the following: PREPARING, IN_PROGRESS, or ACTIVE.

5. Note the Outpost ID in the order.

6. Enter the correct Outpost ID in the StartCapacityTask API request.

The capacity plan includes instance types that are not supported

This issue occurs when you use the AWS CLI or API to create or modify the capacity task and the request contains unsupported instances types.

To resolve this issue, use the console or CLI.

Use the console

1. Sign in to AWS.

2. Open the AWS Outposts console at https://console.aws.amazon.com/outposts/.

3. From the navigation pane, choose Capacity task.

4. Use the Upload a capacity configuration option to upload a JSON with the same list of instance types.

5. The console displays an error message with the list of supported instance types.

6. Correct the request to remove the unsupported instance types.

7. Create or modify the capacity task on the console using the corrected JSON or use the CLI or API with this corrected list of instance types.

Use the CLI

1. Use the GetOutpostSupportedInstanceTypes command to see the list of supported instance types.

2. Create or modify the capacity task with the correct list of instance types.

No Outpost with Outpost ID op-xxxxx

This issue occurs when you use the AWS CLI or API to run the StartCapacityTask and the request contains an Outpost ID that is not valid for one of the following reasons:

• The Outpost is in a different AWS Region.

• You do not have permissions to this Outpost.

• The Outpost ID is incorrect.

To resolve this issue:

1. Note the AWS Region that you used in the StartCapacityTask API request.

2. Use the ListOutposts API action to get a list of Outposts that you own in the AWS Region.

3. Check if the Outpost ID is listed.

4. Enter the correct Outpost ID in the StartCapacityTask request.

5. If you do not find the Outpost ID, use the ListOutposts API action again to check if the Outpost exists in a different AWS Region.