# Cloud Configuration # Cloud Configuration - [Test Deployment in a Cloud ](https://docs.appvance.net/Content/AIQ/Cloud_Config/Test_Deployment_in_a_Cloud.htm) - [onnEC2 Configuration ](https://docs.appvance.net/Content/AIQ/Global_Options/CloudConfig/Amazon_EC2_Configurator.htm) - [Cloud Architecture ](https://docs.appvance.net/Content/AIQ/Cloud_Config/Cloud_Architecture.htm) - [Features and Benefits ](https://docs.appvance.net/Content/AIQ/Cloud_Config/Features_and_Benefits.htm) - [Grid Configuration ](https://docs.appvance.net/Content/AIQ/Global_Options/CloudConfig/Grid_Testing.htm) - [Softlayer Configuration ](https://docs.appvance.net/Content/AIQ/Global_Options/CloudConfig/SoftLaye_Config.htm) - [Cloud Testing Options ](https://docs.appvance.net/Content/AIQ/Cloud_Config/Cloud_Testing_Options.htm) - [Scriptless Test Deployment Configuration ](https://docs.appvance.net/Content/AIQ/Cloud_Config/Scriptless_Test_Deployment_Configuration.htm) - [Cloud Config - FAQ ](https://docs.appvance.net/Content/AIQ/Cloud_Config/Cloud_Config___FAQ.htm)
--- Last updated: July 17, 2023 If you have any feedback on this topic, please contact us at
# Test Deployment in a Cloud AIQ is a distributed test environment. AIQ runs your tests on a Grid of your test equipment, in a Cloud Computing environment, or both. AIQ provides specific commands to support the automatic deployment and operation of your tests in a grid of servers and a Cloud Testing environment. For example, identify a cloud testing service like Amazon EC2 in a Test Scenario. AIQ creates the Test Nodes in EC2 instances, runs the test, retrieves the results, and takes down the EC2 instances. AIQ deploys and operates tests in a "lights out" manner for full Cloud Test automation. Appvance IQ works on-premises behind your firewall or in your favorite cloud environment, or both in hybrid mode. It supports integration with the following: 1. Amazon Web Services 2. IBM Softlayer 3. OpenStack Cloud Software AIQ Grid technology works in your QA lab, in the Cloud, or both. Identify a set of TestNodes running in your QA lab to AIQ. AIQ automatically selects the available TestNodes to deploy and operate your tests. Appvance provides Test OnDemand Testing as a Service (TAAS) services to host your tests.
--- Last updated: June 02, 2023 If you have any feedback on this topic, please contact us at
# AIQ Cloud Architecture Overview # AIQ Cloud Architecture Overview AIQ cloud deployments use controller, execution, storage, and integration components sized for the target workload. Exact architecture depends on the customer environment, deployment model, and AIQ release. ## Core areas - Controller services coordinate users, projects, executions, and reporting. - Execution capacity is provided by Test Nodes or equivalent worker resources. - Storage and data services retain configuration, execution results, and operational test data. - Networking, certificates, proxy rules, and integrations connect AIQ to the systems under test. ## Operational checklist 1. Document ports, domains, certificates, and proxy requirements. 2. Size execution capacity for the expected browser, service, mobile, or performance workload. 3. Monitor controller, database, and Test Node health during high-volume runs. 4. Review security, access, backup, and retention requirements with the environment owner. **Last updated:** September 18, 2026 # Features and Benefits Cloud Computing and AIQ Grid technology provide huge new benefits to app performance solutions: - Run At User Levels Never Before Possible - Building a test lab used to be prohibitively costly for medium and large-scale load tests. Cloud computing delivers bandwidth and computing power to achieve tests in the millions-of-users levels at commodity prices - Run From Multiple Locations Around The World - Cloud Testing environments are a worldwide phenomenon. AIQ runs tests in multiple Cloud Testing environments. This makes it possible to manage performance from your user's geographic location - Pay As You Go, Pay Only For What You Need - Cloud Testing eliminates the cost of building and maintaining a test lab for load and performance testing. No longer is there a need to provision expensive and difficult to manage quality test labs. Appvance Cloud Testing lets you pay as you operate tests. - Ideal for automating test operation from a Continuous Integration environment. The CI platform starts a Test Scenario test and AIQ automatically provisions and deploys tests to the available TestNodes in your own Grid or in a Cloud Testing environment - Test In Your Environment, In A Cloud Environment, Or Both - Appvance delivers ultimate flexibility
--- Last updated: June 02, 2023 If you have any feedback on this topic, please contact us at
# Cloud Testing Options Appvance IQ provides several options for running tests in a Cloud Testing environment. These options are configured in a **TestScenario** and determine how AIQ provisions, uses, and manages TestNode instances during test execution. The Scenario Builder supports the following Cloud Testing settings. ## Name The **Name** identifies the Cloud Testing environment configuration used to manage the cloud resources. ## Type The **Type** specifies the cloud environment to use. Available options include: - **EC2** - **SoftLayer** - **Grid** - **OpenStack** ## Beginning The **Beginning** setting determines how Appvance IQ provisions or starts TestNode instances when staging the test. Available options are: 1. **Create All** — Creates new instances for all required TestNodes. 2. **None** — Does not start or create any instances. 3. **Create Required** — Uses available running instances and creates new instances only when additional machines are required. For example, if three machines are required and one is already running, AIQ uses the existing machine and creates the remaining two. 4. **Start All** — Starts all stopped instances. This option requires all machines to be stopped. If some machines are already running while others are stopped, an error may occur. ## End The **End** setting determines what Appvance IQ does with the TestNode instances when the test finishes. Available options are: 1. **Terminate All** — Terminates all instances. 2. **Started** — Terminates only the instances that were started for the test. 3. **None** — Does not terminate or stop any instances. 4. **Stop All** — Stops all running instances. ## Reboot The **Reboot** setting determines whether AIQ reboots TestNode instances after test execution. Rebooting can help release resources when an application under test leaves network connections open or otherwise prevents resources such as memory and network connections from being released properly. Available options are: - **After** — Reboots the node after the test. AIQ does not reboot machines that have already been terminated. - **Never** — Does not reboot the node after the test. ## All Available Machines **All Available Machines** specifies the desired number of TestNode instances available for the test. ## Config **Config** specifies the path to the AIQ Cloud Testing configuration file. The configuration file contains the cloud access credentials, security keys, and account preferences required to access the selected Cloud Testing environment. ## Network Bandwidth **Network Bandwidth** specifies the network bandwidth, in Kbps, to use for tests running in the specified location. ## Username and Password **Username** and **Password** specify the credentials used to log in to the TestNode machine. These credentials should correspond to the original credentials of the machine used to create the AMI. If the default credentials were used when creating the AMI, leave these fields blank. --- **Last updated:** August 19, 2026 If you have any feedback on this topic, please contact us at . # Configure Scriptless Test Deployment Use scriptless test deployment configuration to prepare Scenario Editor tests for execution in the intended AIQ environment. Keep deployment settings aligned with the target environment, Test Node capacity, browser support, and test data strategy. ## Before deployment - Confirm the target environment, browser or device requirements, and Test Node availability. - Validate test data and credentials using approved secure configuration methods. - Review scenario waits, locators, and validations for maintainability. - Run a focused validation execution before adding the test to a larger suite. ## Deployment notes 1. Document environment-specific settings and avoid hard-coding them into steps. 2. Keep reusable data in DPLs or approved data sources. 3. Review output after the first scheduled or suite execution. **Last updated:** September 18, 2026 # Cloud Configuration FAQ for AIQ **Last reviewed:** September 25, 2026 Use this FAQ to answer common AIQ cloud configuration questions without duplicating provider-specific setup steps. ## What changed in this article - Moved the FAQ toward cloud/grid decision points instead of old one-off provider instructions. - Clarified when to use cloud execution, grid execution, or local test nodes. - Added checks for credentials, network reachability, browser availability, and capacity before troubleshooting a cloud run. ## Validation workflow 1. Identify whether the question is about cloud provider setup, grid capacity, or node connectivity. 2. Verify credentials, routing, firewall rules, and browser versions before changing AIQ settings. 3. Use a small validation run before scaling to a full cloud execution. **Review note:** Connected this FAQ to the newer cloud/grid configuration articles and treated old provider-specific details as legacy. --- Last updated: September 25, 2026 If you have feedback on this topic, contact .