’m currently testing Elementary and I’m running into an issue when executing:

edr report

I get the following error:

{"info": {"name": "RunningOperationCaughtError", "code": "Q001", "msg": 
"Encountered an error while running operation: Database Error
('connection time out', TimeoutError(10060))"}}

From what I understand,

edr report

queries the Elementary tables stored in my data warehouse (Redshift). My Redshift cluster is deployed inside a private VPC, and I suspect the timeout happens because my current IP address is not allowed to access it. So my assumption is: • The error is network-related • I probably need to request access (IP whitelisting / VPN / bastion / security group update) Does that sound correct? error :

TimeoutError(10060)

when running

edr report

Your reasoning is aligned with what we see in similar cases.

edr report

runs dbt operations against the Elementary tables in your warehouse using the

elementary

profile, so any network / connectivity restriction between where you run

edr

and Redshift will surface as connection timeouts. In a very similar Redshift case, support confirmed that the issue was that Elementary could not reach the warehouse and the fix was to allow the relevant IP in the warehouse’s allowlist. [Redshift connect; IP allowlist] Given: • Redshift is in a private VPC • The error is

('connection time out', TimeoutError(10060))

during

edr report

• dbt/Elementary need to open a TCP connection to Redshift it is very likely network-related (security group, NACL, VPN, bastion, or IP allowlist). Concrete next steps: 1. Verify basic dbt connectivity from the same machine/user Run a simple dbt command with the same profile Elementary uses, e.g.:

dbt debug --target elementary

or any

dbt run-operation

using that profile. If this also times out, it confirms a pure connectivity issue rather than something specific to Elementary. [Local report timeout] 2. Check network / access controls Work with your infra team to ensure that from the host where you run `edr report`: ◦ The IP (or NAT IP) is allowed in Redshift’s security group / firewall. ◦ Any required VPN / bastion / SSH tunnel is up and used by that process. ◦ If you’re using IP allowlists, add the relevant client IP (similar to how Elementary Cloud requires its IP to be allowlisted). [Redshift connect; IP allowlist] 3. Confirm the

elementary

profile is correct Ensure

~/.dbt/profiles.yml

has an

elementary

profile that points to the same Redshift host, port, database, and credentials you use successfully elsewhere. If you haven’t already, generate it via:

dbt run-operation elementary.generate_elementary_cli_profile

and then test again. [Local report timeout] If dbt commands work from that machine with the

elementary

profile but

edr report

still times out, the knowledge sources don’t provide a more specific root cause beyond “network / connection to DWH,” so at that point sharing full

edr.log

with the Elementary team on Slack would be the recommended next step. 👍 0 button 👎 0 button ℹ️ Tip: Mention @elementary.ai in the thread for follow-ups or DM the app for 1-to-1 help.