Skip to main content

Verify Resources

Admin Only

This page is only visible to organization administrators.

Resource verification confirms that EntryGuard can communicate with your cloud resources and has the necessary permissions to manage IP rules. Only verified resources can be used in sessions.

Verifying a Resource​

Navigate to Resources under the Admin section in the sidebar.

  1. Find the resource you want to verify in the resources table.
  2. Click the Verify capacity button (check icon) in the Actions column.

EntryGuard runs the following checks:

  1. Credential validation — Confirms the associated credential is valid
  2. Resource existence — Verifies the resource exists in the specified region
  3. Permission check — Tests that the credential has the required permissions
  4. Connectivity — Ensures EntryGuard can reach the cloud provider API

After verification, the Health column updates:

  • Valid (green) — All checks passed; ready for sessions
  • Invalid (red) — One or more checks failed; review the configuration

Verification also checks the current rule count against the resource's maximum capacity. See IP Rule Capacity by Resource Type for limits per resource type.

When to Verify​

  • After creating a resource — Always verify immediately after adding a new resource
  • After credential changes — If you rotate access keys, verify all associated resources
  • After failed sessions — If sessions fail to apply rules, re-verify the affected resources
  • Periodically — Verify critical resources weekly and standard resources monthly

Impact on Sessions​

  • Only active (verified) resources can be used in sessions
  • If you start a session and a resource is inactive, that resource is skipped
  • Existing sessions continue to work even if a resource becomes inactive — rules already applied stay in place

Troubleshooting Verification Failures​

"Security Group not found"​

  • Verify the Security Group ID is correct (format: sg-xxxxxxxxxxxxxxxxx)
  • Check the region matches where the Security Group was created
  • Confirm the Security Group hasn't been deleted in AWS

"User is not authorized"​

  • Verify the IAM policy includes the required permissions
  • Check for service control policies (SCPs) blocking the action
  • Review the required IAM policy

"Invalid credentials"​

  • The access key may have been rotated or deleted in AWS
  • Re-create the credential with the current keys

Next Steps​

API Reference: For programmatic access, see Verify Resource.