You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reposition CustomConfigPath parameter after Pattern 3 parameters
- Moved CustomConfigPath parameter definition to appear after Pattern 3 configuration
- Created separate 'Custom Configuration' parameter group in CloudFormation interface
- Removed CustomConfigPath from General Configuration group
- Parameter now appears in logical order: Pattern selection → Pattern configs → Custom config → Other features
Copy file name to clipboardExpand all lines: template.yaml
+16-2Lines changed: 16 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -86,6 +86,17 @@ Parameters:
86
86
Description: >-
87
87
Built-in IDP workflow patterns - see README for pattern descriptions.
88
88
89
+
# Custom Configuration Path
90
+
91
+
CustomConfigPath:
92
+
Type: String
93
+
Default: ""
94
+
Description: >-
95
+
S3 URI pointing to your custom configuration YAML file. When provided, this configuration overrides the selected pattern preset and applies to all processing patterns.
96
+
Leave blank to use the selected pattern configuration preset. For example s3://my-bucket/custom-config/config.yaml
ConstraintDescription: Must be empty or a valid S3 URI (e.g., s3://my-bucket/custom-config/config.yaml)
99
+
89
100
# Pattern 1 Parameters
90
101
91
102
Pattern1BDAProjectArn:
@@ -144,7 +155,7 @@ Parameters:
144
155
Description: >-
145
156
Select the configuration preset for Pattern 3. Each configuration contains pre-tuned settings for specific document processing scenarios - see https://github.com/aws-samples/sample-genai-idp/blob/main/config_library/README.md. Note: Custom configuration overrides the selected pattern configuration when provided.
0 commit comments