Updates the maximum length validation for pipeline_configuration_body #44881
+4
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Rollback Plan
If a change needs to be reverted, we will publish an updated version of the library.
Changes to Security Controls
No changes to security controls (access controls, encryption, logging) in this pull request.
Description
Updates the maximum length validation for
pipeline_configuration_bodyfrom the previous limit to 2,621,440 bytes to align with AWS API specification.The AWS OpenSearch Ingestion Service API allows pipeline configuration bodies up to 2,621,440 bytes (approximately 2.5MB), but the Terraform provider was enforcing a smaller limit. This change ensures users can deploy complex OpenSearch Ingestion pipelines with larger configuration bodies without encountering artificial validation errors from Terraform.
Relations
Relates #0000
References
AWS OpenSearch Ingestion API documentation specifies the
PipelineConfigurationBodyparameter has a maximum length of 2,621,440 bytes.Output from Acceptance Testing