AWS amazonq documentation change
Summary
Moved 'Known limitations' section to a separate linked page and restructured headings
Security assessment
Purely organizational changes to documentation structure. Limitations mentioned (data tracking, field size) are functional constraints without security implications.
Diff
diff --git a/amazonq/latest/qbusiness-ug/postgresql-connector.md b/amazonq/latest/qbusiness-ug/postgresql-connector.md index 51634cee5..37582a220 100644 --- a//amazonq/latest/qbusiness-ug/postgresql-connector.md +++ b//amazonq/latest/qbusiness-ug/postgresql-connector.md @@ -5,2 +4,0 @@ -Known limitations - @@ -23 +21 @@ As a best practice, provide Amazon Q with read-only database credentials. Also, - * Known limitations for the PostgreSQL connector + * [Known limitations for the PostgreSQL connector](./postgresql-limitations.html) @@ -55,13 +52,0 @@ As a best practice, provide Amazon Q with read-only database credentials. Also, -## Known limitations for the PostgreSQL connector - - * Deleted database rows will not be tracked in when Amazon Q checks for updated content. - - * The size of field names and values in a row of your database can't exceed 400KB. - - * Column names should only contain alphanumeric characters and not spaces. - - * If you have a large amount of data in your database data source, and do not want Amazon Q to index all your database content after the first sync, you can choose to sync only new, modified, or deleted documents. - - - - @@ -76 +61 @@ IAM role -Overview +Known limitations