Architect

Infrastructure Management

The Infrastructure tab provides a unified view of all your cloud resources across providers. Monitor status, access servers, stream logs, and manage resources without leaving your IDE.

  • Unified view of resources across all cloud providers in one place
  • Real-time status monitoring with automatic refresh
  • One-click SSH access to servers directly from your IDE
  • Live log streaming and metrics from any resource
  • Drift detection to identify manual changes to infrastructure

Viewing Infrastructure

Open the Infrastructure tab in the Architect panel to see your resources.

Grouping Options

View resources grouped by different criteria:

By Provider
AWS, Azure, Hetzner, GCP, and more
By Type
Compute, Database, Storage, Networking
By Environment
Development, Staging, Production (via tags)

Click the grouping dropdown to switch views.

Resource Tree

Resources appear in a tree structure:

A H W e S t z E R n S C D e e 2 S r r v I w w D m e a n e e a a r p s b b t i s i t - - a n - a s s b - s n e e a d e c r r s b r e v v e v s e e s 🟢 e r r r - - 1 2 🟡 🟢 🟢
Note Expand providers and categories to see individual resources. Use the search box to quickly find specific resources by name.

Status Icons

Each resource shows a status indicator:

Running (Green)
Resource is healthy and operational
Warning (Yellow)
Resource is degraded or needs attention
Stopped/Error (Red)
Resource is stopped or has failed
Unknown (Grey)
Status cannot be determined
Syncing
Status is being updated

Status Details

Click any resource to see detailed status information:

  • Current state and health
  • Uptime duration
  • Last status change
  • Any warning or error messages
Note Status details update in real-time. The panel shows the last update timestamp so you know how current the information is.

Resource Actions

Right-click any resource to see available actions.

Compute Resources (Servers/VMs)

Action Description
Start Power on a stopped server
Stop Gracefully shut down
Restart Reboot the server
SSH/Connect Open terminal session
View Logs Stream server logs
View Metrics CPU, memory, disk usage
Open in Console Open cloud provider console
Copy Resource ID Copy to clipboard
Delete Remove the resource

Database Resources

Action Description
Connect Open database client
View Backups List available backups
Scale Storage Increase storage size
View Metrics Connections, queries, storage
Open in Console Open cloud provider console

All Resources

Action Description
View in Designer Show resource on canvas
Open in Cloud Console Open provider’s web console
Copy Resource ID Copy identifier to clipboard
Refresh Update status immediately
Warning The Delete action permanently removes resources from your cloud provider. This action cannot be undone. Always verify you’re deleting the correct resource.

SSH Access

Connect to servers directly from your IDE.

One-Click SSH

  1. Find the server in the Infrastructure tree
  2. Right-click → SSH/Connect
  3. Terminal opens with active connection
Note Use keyboard shortcuts for faster access. Select a server and press Enter to quickly open an SSH session.

SSH Configuration

Architect uses credentials from:

  1. Credential Vault (if SSH key stored)
  2. Standard SSH config (~/.ssh/config)
  3. Cloud provider’s SSH keys (auto-detected)

Supported Protocols

SSH
Standard secure shell for servers with public IP
SSM AWS
AWS Session Manager for instances without public IP

Log Streaming

View real-time logs from any resource.

Viewing Logs

  1. Right-click a resource → View Logs
  2. Log viewer opens with streaming output
  3. New log entries appear automatically

Log Controls

Control Function
Pause Stop auto-scroll, keep receiving
Clear Clear the log display
Search Find text in logs
Filter Filter by level (info, warn, error)
Download Save logs to file
Tail Lines Number of historical lines to load

Multi-Resource Logs

View combined logs from multiple resources:

  1. Select multiple resources (Ctrl/Cmd + click)
  2. Right-click → View Combined Logs
  3. Logs interleaved with resource labels
Note Combined logs are color-coded by source, making it easy to trace issues across multiple services.

Real-Time Metrics

View live resource utilization.

Available Metrics

Metric Resources
CPU Usage Servers, containers
Memory Usage Servers, containers, databases
Disk Usage Servers, volumes
Network I/O Servers, load balancers
Connections Databases, load balancers
Request Rate Load balancers, APIs

Metrics Display

  • Sparkline graphs show trends
  • Current value with percentage
  • Warning thresholds highlighted
  • Click to expand detailed view
Note Metrics require appropriate monitoring agents or cloud provider APIs. AWS CloudWatch, Azure Monitor, and similar services provide the underlying data.

Refreshing Data

Automatic Refresh

Infrastructure data refreshes automatically:

  • Default interval: 60 seconds
  • Configurable in settings: architect.autoRefreshInterval

Manual Refresh

  • Click Refresh button in toolbar
  • Press Ctrl+R / Cmd+R
  • Right-click → Refresh

Refresh Scope

Refresh All
Update all providers and resources
Refresh Provider
Update a single cloud provider
Refresh Resource
Update a single resource

Detecting Drift

Architect can detect when deployed infrastructure differs from your design.

Drift Indicators

In Sync
Design matches deployed state
Drifted
Manual changes detected
Missing
Resource exists in design but not deployed
Extra
Resource deployed but not in design

Resolving Drift

  1. Click a drifted resource
  2. Review the differences
  3. Choose:
    • Update Design: Match design to reality
    • Apply Design: Override with design (redeploy)
Warning Applying your design to drifted resources may cause downtime or data loss. Always review the changes carefully before proceeding.

Troubleshooting

No infrastructure detected
  • Verify your project has .tf, .env, or terraform.tfstate files
  • Check credentials are configured in the Vault
  • Ensure cloud provider API is accessible
  • Click Refresh to reload
Connection failed for SSH
  • Verify the server has a public IP or VPN access
  • Check SSH keys are configured
  • Ensure security groups allow SSH (port 22)
  • Try connecting via cloud console first
Metrics unavailable
  • Some metrics require agents (CloudWatch, metrics-server)
  • Verify the resource supports metrics
  • Check cloud provider permissions
Status not updating
  • Check internet connectivity
  • Verify cloud credentials haven’t expired
  • Try manual refresh
  • Check for API rate limiting

Best Practices

Organizing Resources
  • Use consistent naming conventions
  • Tag resources with environment (dev/staging/prod)
  • Group related resources in the same view
Monitoring
  • Enable alerting in your cloud provider
  • Check infrastructure status regularly
  • Set up dashboards for critical resources
Security
  • Use least-privilege credentials
  • Audit SSH access regularly
  • Keep security groups restrictive
  • Monitor for unexpected resources

Next Steps