A scan reported as incomplete is never a clean result. Any check veriQU could not resolve is listed as unresolved, with the question a person needs to answer.

The documentation pack covers incident response, disaster recovery, data handling and more.

Each remediation is a Yes/No with exactly what it changes and what it costs. Paid services, alarms and anything risky start at No. Alarms and notifications need an alert email, entered on the same page.

This updates the veriQU stack already in your account. The remediations you approved before are carried into it.

You create or update the stack under your own login. It makes the changes you chose in this account and records each one in its log group.

Once a day, the daily pass checks with veriQU that your plan still covers this account. If it no longer does, it stops making changes and emails your alert address.

Delete the stack once your rescan confirms the changes: its runner function would otherwise appear in your next scan.

No scan can see these: they are statements about how your company works. Answer only what is true today. A "yes" appears in your next report as answered by you, with your name and the date; veriQU never answers for you.

Your documentation pack has blanks only your company can fill in. Answer each one here, or let Ask veriQU ask you the questions. You save every answer yourself; the assistant cannot save anything.

Answers are saved in your own AWS account, encrypted in its Parameter Store. veriQU keeps only which blanks are filled, so a saved answer is not shown here: saving again replaces it. Your stack rebuilds the documents in your own account after each new scan (it checks once a day) and when you click Rebuild.

The documents are built from your own answers and your scan. They are your statements: veriQU drafts them and does not verify or certify them.

1. veriQU creates the review in your own AWS account through your Continuous stack, named after your solution, with you as the reviewer. It never changes a review veriQU did not create.
2. It selects or clears only the answers your latest scan verified, and notes which of your finished documents answer each question. Your own notes are kept.
3. Ask veriQU walks you through the questions the scan could not answer. Each answer is saved in your review when you click Save.
4. "Build my FTR report" saves a milestone and puts the report PDF in your documents bucket. Upload it in AWS Partner Central with your solution's FTR.

FTR asks for a Well-Architected review with no high-risk issues in Security, Operational Excellence and Reliability.

1. Enter your solution name as it appears in Partner Central, and the reviewer's full name and email.
2. The stack creates the review, or updates one veriQU drafted from an earlier scan. It never touches a review veriQU did not create.
3. It selects or clears only answers this scan verified, and leaves a note on every question you still need to answer. Your notes and the answers the scan cannot check are kept. Deleting the stack keeps the review.
4. Finish it in the Well-Architected Tool, generate the report, and upload it in Partner Central.