Opensearch ingestion pipeline stuck in stopping stage

When an Amazon OpenSearch Ingestion pipeline gets stuck in the "Stopping" state, it indicates an abnormal situation. Based on the error message you're receiving, the pipeline must reach one of the eligible statuses (UPDATE_FAILED, ACTIVE, START_FAILED, STOPPED, or CREATE_FAILED) before it can be deleted.

A pipeline stuck in the "Stopping" state for an extended period (like a week in your case) is not normal behavior. The "Stopping" status should be a transitional state while the pipeline is being stopped, after which it should move to "Stopped" status.

Since you're unable to delete the pipeline due to its current state, and it's been stuck for an unusually long time, this appears to be a service issue that requires AWS support intervention. The pipeline seems to be in an inconsistent state that prevents normal operations.

For this situation, I recommend:

1. Contact AWS Support directly, as they can investigate why the pipeline is stuck in the "Stopping" state and help resolve the issue at the service level.

2. Provide them with the pipeline name/ARN and details about when it entered the "Stopping" state.

3. AWS Support should be able to either force the pipeline to complete its stopping process or manually intervene to allow deletion.

This is not something you can resolve through the standard API calls or console actions, as the pipeline needs to be in a valid state first before deletion can proceed.
Sources
Stopping an Amazon OpenSearch Ingestion pipeline - Amazon OpenSearch Service
Viewing Amazon OpenSearch Ingestion pipelines - Amazon OpenSearch Service

Moreover, to resolve issue as hot fix we have created another pipeline, but after a few days it also blocked in stopping state