AWS opensearch-service documentation change
Summary
Clarified data reprocessing behavior for pull-based pipelines when stopped/started
Security assessment
Change documents expected data reprocessing behavior without addressing security vulnerabilities or introducing security features. It's an operational clarification about pipeline functionality.
Diff
diff --git a/opensearch-service/latest/developerguide/pipeline--stop-start.md b/opensearch-service/latest/developerguide/pipeline--stop-start.md index 0ee6cb289..9c3b5246f 100644 --- a//opensearch-service/latest/developerguide/pipeline--stop-start.md +++ b//opensearch-service/latest/developerguide/pipeline--stop-start.md @@ -9 +9 @@ You can start and stop ingestion pipelines in Amazon OpenSearch Ingestion to con -Starting and stopping simplifies the setup and teardown processes for pipelines that you use for development, testing, or similar activities that don't require continuous availability. While your pipeline is stopped, you aren't charged for any Ingestion OCU hours. You can still update stopped pipelines, and they receive automatic minor version updates and security patches. Restarting a pipeline resumes processing from new incoming data. +Starting and stopping simplifies the setup and teardown processes for pipelines that you use for development, testing, or similar activities that don't require continuous availability. While your pipeline is stopped, you aren't charged for any Ingestion OCU hours. You can still update stopped pipelines, and they receive automatic minor version updates and security patches. Stopping and starting a pipeline will result in reprocessing all the data from the beginning for pull based pipelines (DDB, S3, DocDB, etc).