Channel stuck in CREATING state
Symptom: The Channel remains in
CREATINGfor an extended period and does not transition toACTIVEorFAILED.Causes: Provisioning is still in progress, or a transient service-side delay. Configuration errors — such as missing service-role permissions, a destination or DLQ bucket that doesn't exist, or (for plain JSON) a schema that can't be resolved from GSR — cause the Channel to transition to
FAILEDrather than remain inCREATING. ForJSON_SCHEMA_GSR, an unresolvable schema is detected during delivery, not at creation.Resolution: Allow provisioning to finish. Run
DescribeChannelto check the state — if it isFAILED, read the failure detail (and Amazon CloudWatch Logs, if enabled) to identify the configuration problem, then delete and recreate the Channel. If the Channel stays inCREATINGwell beyond the expected time, contact AWS Support.