Answer: You can test connectivity any time for public internet, and for AWS PrivateLink or Amazon VPC Lattice you should test before you publish to find a missing step, then after you publish when the connection is ready. Status: Confirmed Entry: tool/kiro/admin-and-enterprise/when-to-test-connection Revision: 2 Digest: sha256:850907b85fb9b509 (changes whenever the content changes) Timeline: Created: 2026-11-17T13:49:23Z Last changed: 2026-11-20T13:27:07Z (Amazon VPC Lattice wait: — → up to about 15 minutes) Last verified: 2026-11-20T13:27:07Z Next check: 2026-11-21T13:27:07Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Unit | Source | As of Public internet timing | Any time, also before you publish | | [1] | 2026-11-20 AWS PrivateLink timing | Before you publish, to find a missing step. Then after you publish, when the connection is ready. | | [1] | 2026-11-20 AWS PrivateLink wait | up to about 10 minutes | minutes | [1] | 2026-11-20 Amazon VPC Lattice timing | Before you publish, to find a missing step. Then after you publish, when the connection is ready. | | [1] | 2026-11-20 Amazon VPC Lattice wait | up to about 15 minutes | minutes | [1] | 2026-11-20 Sources: [1] Amazon Web Services. "Test the connection - Monitor per-user activity - Monitor and track - Enterprise - Docs - Kiro". https://kiro.dev/docs/enterprise/monitor-and-track/user-activity/test-connection/ Role: primary. Accessed: 2026-11-20T13:27:07Z Quote: "Any time, also before you publish" (Supports: Public internet timing) Quote: "Before you publish, to find a missing step. Then after you publish, when the connection is ready." (Supports: AWS PrivateLink timing, Amazon VPC Lattice timing) Quote: "That can take up to about 10 minutes" (Supports: AWS PrivateLink wait) Quote: "That can take up to about 15 minutes" (Supports: Amazon VPC Lattice wait) Published: 2026-11-20T07:39:25Z Snapshot SHA-256: 3766270b267ca84b927080adc32a5e8ac6db3d5092b9217b8386a7dbae192e67 (captured 2026-11-20T13:27:07Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. Cross-check: not-available at 2026-11-20T13:27:07Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:27:07Z Last attempt: 2026-11-20T13:27:07Z Notes and limitations: Extracted automatically from a single official source (section "When to test"). Related: https://latestn.com/tool/kiro/admin-and-enterprise/why-two-okta-applications Why does Kiro require two Okta applications for SSO and SCIM? https://latestn.com/tool/kiro/agents-and-automation/acp-agent-harness How do I choose the agent harness for Kiro's ACP quick start? https://latestn.com/tool/kiro/agents-and-automation/add-backend-cron How do I add a backend or cron job to a Kiro Crew app? https://latestn.com/tool/kiro/admin-and-enterprise/view-usage-dashboard How do I view Kiro usage on the enterprise dashboard? https://latestn.com/tool/kiro/admin-and-enterprise/web-tools-enterprise-governance How does enterprise governance control web tools in Kiro? https://latestn.com/tool/kiro/admin-and-enterprise/what-test-sends What data does the Kiro connection test send? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-20T13:27:07Z | changed | Amazon VPC Lattice wait: — → up to about 15 minutes | [1] 2026-11-20T13:27:07Z | changed | AWS PrivateLink wait: — → up to about 10 minutes | [1] 2026-11-20T13:27:07Z | changed | Amazon VPC Lattice wait time: 15 minutes → — | [1] 2026-11-20T13:27:07Z | changed | AWS PrivateLink wait time: up to about 10 minutes → — | [1] 2026-11-17T13:49:23Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/admin-and-enterprise/when-to-test-connection/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/kiro/admin-and-enterprise/when-to-test-connection POST: https://latestn.com/dispute/tool/kiro/admin-and-enterprise/when-to-test-connection with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/admin-and-enterprise/when-to-test-connection?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). When should I run the Kiro user activity connection test? Revision 2, last verified 2026-11-20T13:27:07Z. https://latestn.com/tool/kiro/admin-and-enterprise/when-to-test-connection (accessed 2026-11-21T10:04:16Z). @misc{LatestN_tool_kiro_admin_and_enterprise_when_to_test_connection_r2, title = {When should I run the Kiro user activity connection test?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/admin-and-enterprise/when-to-test-connection}}, note = {Revision 2; digest sha256:850907b85fb9b509; last verified 2026-11-20T13:27:07Z; accessed 2026-11-21T10:04:16Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/kiro/admin-and-enterprise/when-to-test-connection