ERROR REFERENCE
The Cloud Control API operation did not complete
The SDK stopped waiting for a Cloud Control resource operation. The wrapper is not the root cause; inspect the nested ProgressEvent before changing IAM or retrying.
WHAT IT MEANS
The nested status identifies the actual failure
Error: AWS SDK Go Service Operation Incomplete
Waiting for Cloud Control API service CreateResource operation completion returned: waiter state transitioned to FAILED. StatusMessage: the resource handler rejected the request. ErrorCode: InvalidRequest
Cloud Control operations are asynchronous. The SDK wrapper only says
that the wait ended without success; the useful evidence is the
operation status, resource type, identifier, StatusMessage,
ErrorCode, and request token.
NEXT CHECK
Recover the ProgressEvent before choosing a fix
-
Preserve the complete nested response. Record
OperationStatus,ErrorCode,StatusMessage,TypeName, identifier, Region, andRequestToken. -
Query the request token. When one is present, run
aws cloudcontrol get-resource-request-status --request-token <token>in the same account and Region for the latest ProgressEvent. - Follow the nested cause. Check the resource handler, schema, service role, or downstream AWS service named by the status before retrying; do not change IAM from this wrapper alone.
AUTOMATE THE TRIAGE
Keep the check in your normal workflow
SAM Doctor recognizes AWS SDK Go Service Operation Incomplete
with low confidence and keeps the advice focused on the nested status.
Runs locally; no AWS access, no log upload.
python -m pip install sam-doctor
sam-doctor diagnose deployment.log --format markdownRELATED
Related errors
- CloudFormation deploy wrapper failed - fetch the earliest resource event instead of diagnosing the wrapper.
- Resource did not stabilize - inspect the nested handler reason behind a waiter timeout.
- Unknown AWS service - an endpoint cannot route the request to a known service target.