Skip to content

Docs for worksheets NLQ Feature#1653

Open
noah-paige wants to merge 9 commits intogh-pagesfrom
docs/nlq
Open

Docs for worksheets NLQ Feature#1653
noah-paige wants to merge 9 commits intogh-pagesfrom
docs/nlq

Conversation

@noah-paige
Copy link
Contributor

@noah-paige noah-paige commented Oct 21, 2024

Feature or Bugfix

  • Documentation

Detail

  • Docs for NLQ Worksheet Feature

Relates

Security

Please answer the questions below briefly where applicable, or write N/A. Based on
OWASP 10.

  • Does this PR introduce or modify any input fields or queries - this includes
    fetching data from storage outside the application (e.g. a database, an S3 bucket)?
    • Is the input sanitized?
    • What precautions are you taking before deserializing the data you consume?
    • Is injection prevented by parametrizing queries?
    • Have you ensured no eval or similar functions are used?
  • Does this PR introduce any functionality or component that requires authorization?
    • How have you ensured it respects the existing AuthN/AuthZ mechanisms?
    • Are you logging failed auth attempts?
  • Are you using or adding any cryptographic features?
    • Do you use a standard proven implementations?
    • Are the used keys controlled by the customer? Where are they stored?
  • Are you introducing any new policies/roles/users?
    • Have you used the least-privilege principle? How?

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

SofiaSazonova and others added 5 commits August 30, 2024 08:25
@SofiaSazonova
GH pages: new config.json property described (log query period) (#1504)
1a994c0 
### Feature or Bugfix
<!-- please choose -->
- Feature


### Detail
- Config changes are described

### Relates
- #1502 

### Security
Please answer the questions below briefly where applicable, or write
`N/A`. Based on
[OWASP 10](https://owasp.org/Top10/en/).

- Does this PR introduce or modify any input fields or queries - this
includes
fetching data from storage outside the application (e.g. a database, an
S3 bucket)?
  - Is the input sanitized?
- What precautions are you taking before deserializing the data you
consume?
  - Is injection prevented by parametrizing queries?
  - Have you ensured no `eval` or similar functions are used?
- Does this PR introduce any functionality or component that requires
authorization?
- How have you ensured it respects the existing AuthN/AuthZ mechanisms?
  - Are you logging failed auth attempts?
- Are you using or adding any cryptographic features?
  - Do you use a standard proven implementations?
  - Are the used keys controlled by the customer? Where are they stored?
- Are you introducing any new policies/roles/users?
  - Have you used the least-privilege principle? How?


By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache 2.0 license.

Co-authored-by: Sofia Sazonova <sazonova@amazon.co.uk>
@noah-paige
Add docs on log retention and allowed origins, fix cdkproxy docs (#1554)
3bdfa9f 
### Feature or Bugfix
<!-- please choose -->
- Documentation



### Detail
- Add docs on configurable CloudWatch log retention
- Add docs on allowed origin configuration
- Update docs on cdkproxy code walkthrough


### Relates
- #1527
- #1486

### Security
Please answer the questions below briefly where applicable, or write
`N/A`. Based on
[OWASP 10](https://owasp.org/Top10/en/).

- Does this PR introduce or modify any input fields or queries - this
includes
fetching data from storage outside the application (e.g. a database, an
S3 bucket)?
  - Is the input sanitized?
- What precautions are you taking before deserializing the data you
consume?
  - Is injection prevented by parametrizing queries?
  - Have you ensured no `eval` or similar functions are used?
- Does this PR introduce any functionality or component that requires
authorization?
- How have you ensured it respects the existing AuthN/AuthZ mechanisms?
  - Are you logging failed auth attempts?
- Are you using or adding any cryptographic features?
  - Do you use a standard proven implementations?
  - Are the used keys controlled by the customer? Where are they stored?
- Are you introducing any new policies/roles/users?
  - Have you used the least-privilege principle? How?


By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache 2.0 license.
@noah-paige
Pipeline Module Documentation Updates (#1617)
c58a785 
### Feature or Bugfix
<!-- please choose -->
- Refactoring

### Detail
- Update notices on GH Pages 
    - For support of AWS CodeCommit deploying data.all solution
    - For support of pipelines data.all resource modules


### Relates
- 

### Security
Please answer the questions below briefly where applicable, or write
`N/A`. Based on
[OWASP 10](https://owasp.org/Top10/en/).

- Does this PR introduce or modify any input fields or queries - this
includes
fetching data from storage outside the application (e.g. a database, an
S3 bucket)?
  - Is the input sanitized?
- What precautions are you taking before deserializing the data you
consume?
  - Is injection prevented by parametrizing queries?
  - Have you ensured no `eval` or similar functions are used?
- Does this PR introduce any functionality or component that requires
authorization?
- How have you ensured it respects the existing AuthN/AuthZ mechanisms?
  - Are you logging failed auth attempts?
- Are you using or adding any cryptographic features?
  - Do you use a standard proven implementations?
  - Are the used keys controlled by the customer? Where are they stored?
- Are you introducing any new policies/roles/users?
  - Have you used the least-privilege principle? How?


By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache 2.0 license.
@TejasRGitHub
Adding docs for GH-1528 (#1575)
ce378fe 
### Feature or Bugfix
- Feature ( Docs ) 


### Detail
- Added in the "Deploy to AWS" section 

### Relates
- #1559

### Security
Please answer the questions below briefly where applicable, or write
`N/A`. Based on
[OWASP 10](https://owasp.org/Top10/en/).

- Does this PR introduce or modify any input fields or queries - this
includes
fetching data from storage outside the application (e.g. a database, an
S3 bucket)?
  - Is the input sanitized?
- What precautions are you taking before deserializing the data you
consume?
  - Is injection prevented by parametrizing queries?
  - Have you ensured no `eval` or similar functions are used?
- Does this PR introduce any functionality or component that requires
authorization?
- How have you ensured it respects the existing AuthN/AuthZ mechanisms?
  - Are you logging failed auth attempts?
- Are you using or adding any cryptographic features?
  - Do you use a standard proven implementations?
  - Are the used keys controlled by the customer? Where are they stored?
- Are you introducing any new policies/roles/users?
  - Have you used the least-privilege principle? How?


By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache 2.0 license.
@noah-paige
Docs for worksheets NLQ Feature
ee7d738
@noah-paige noah-paige self-assigned this Oct 22, 2024
@noah-paige noah-paige linked an issue Oct 24, 2024 that may be closed by this pull request
Natural Language Querying (NLQ) using genAI #1659
Open
dlpzx
dlpzx reviewed Oct 31, 2024
View reviewed changes
pages/deploy/deploy_aws.md
| show_stack_logs | environments | Enable / Disable showing stack logs to users or only allow admins to view stack logs. When "Enabled", users who have access to stack can view the logs. With "admin-only", only Data.all admins can view the stack logs and when "Disabled", no user can see the stack logs. Please check out the config.json in step 7 for more details |

### (Optional) Additional Set Up For Worksheets GenAI Natural Language Query (NLQ) Features

Copy link
Contributor

@dlpzx dlpzx Oct 31, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

typo: your. data.all

Copy link
Contributor

@dlpzx dlpzx Oct 31, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

typo: must enable

dlpzx
dlpzx approved these changes Oct 31, 2024
View reviewed changes
Copy link
Contributor

@dlpzx dlpzx left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some typos, fix them and merge :)

@petrkalos petrkalos changed the base branch from gh-pages-v2m7m0 to gh-pages October 10, 2025 12:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@dlpzx dlpzx dlpzx approved these changes

Assignees

@noah-paige noah-paige

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Natural Language Querying (NLQ) using genAI

5 participants

@noah-paige @dlpzx @SofiaSazonova @TejasRGitHub @petrkalos