Cloud Config
- Cloud Configuration Options in AIQ
- Amazon EC2 Configuration for AIQ
- Legacy SoftLayer Configuration Reference
- Configure Grid Execution in AIQ
Cloud Configuration Options in AIQ
Last reviewed: September 24, 2026
Use Cloud Configuration to manage the environment options that support AIQ execution across cloud resources, grid execution, and connected test nodes.
Recommended guidance
- Use current cloud and grid runbooks for active environments instead of older provider-specific links.
- Confirm provider credentials, execution capacity, network routes, and browser availability before enabling a cloud-backed run.
- Keep legacy provider references only when they are still needed for an existing customer environment.
Validation workflow
- Review the active cloud or grid provider used by the AIQ environment.
- Confirm that test nodes can reach AIQ services and the application under test.
- Run a small validation execution before assigning production workloads to the cloud or grid configuration.
Note: SoftLayer-era configuration is legacy content. Prefer current cloud or grid deployment guidance for new work.
Last updated: September 24, 2026
If you have feedback on this topic, contact documentation@appvance.ai.
Amazon EC2 Configuration for AIQ
Amazon EC2 Configuration for AIQ
Use this article when configuring Amazon EC2 resources for AIQ environments. Align instance sizing, networking, storage, security groups, and IAM access with the expected execution workload.
Configuration checklist
- Select instance types based on Controller, Test Node, database, or supporting-service responsibilities.
- Configure VPC, subnet, security groups, DNS, and routing so AIQ components can communicate securely.
- Use encrypted volumes and plan disk size for logs, execution artifacts, browser caches, and database growth.
- Attach IAM roles instead of static access keys whenever possible.
- Tag resources with environment, owner, cost center, and lifecycle information.
Validation workflow
- Confirm required ports and hostnames from the Controller and Test Nodes.
- Run AIQ login and small execution smoke tests.
- Monitor CPU, memory, disk, and network metrics during the validation run.
- Document AMI, instance type, storage, security group, and IAM role details.
Last updated: October 8, 2026
Legacy SoftLayer Configuration Reference
Last reviewed: September 24, 2026
This page is retained only as a legacy reference for environments that still mention SoftLayer-era cloud configuration.
Recommended guidance
- Do not use SoftLayer as the default cloud-provider recommendation for new AIQ deployments.
- Prefer current cloud, grid, or test-node configuration guidance.
- Keep this page only for historical support cases or migrations from older environments.
Validation workflow
- Confirm whether the customer environment still depends on SoftLayer settings.
- If not, redirect the work to the current cloud or grid configuration article.
- If yes, document the legacy dependency and plan a migration path.
Note: SoftLayer content is obsolete for most current AIQ deployments and should be treated as legacy support material.
Last updated: September 24, 2026
If you have feedback on this topic, contact documentation@appvance.ai.
Configure Grid Execution in AIQ
Last reviewed: September 24, 2026
Grid execution lets AIQ distribute scenario runs across available nodes when the environment is sized and connected correctly.
Recommended guidance
- Align grid capacity with expected browser, API, or performance-test concurrency.
- Confirm node reachability, browser versions, driver compatibility, and firewall rules before a production run.
- Monitor node health during execution so failed nodes do not distort results.
Validation workflow
- Validate each grid node from the AIQ controller.
- Run a small scenario against the grid before increasing load.
- Review execution output and results to confirm work was distributed as expected.
Last updated: September 24, 2026
If you have feedback on this topic, contact documentation@appvance.ai.