Cloud Platform
FAQs
If you received the email for your new Acquia Search powered by SearchStax application but did not activate it within 24 hours, you can follow the link and select Forgot Password. If you require help, contact Acquia Support for assistance.
Yes, you can extract text from the supported file types. In order to do so, use the /extract document extractor endpoint. This endpoint enables you to specify page ranges for paginated files and include file metadata in the response. For additional information, visit Document Extraction API.
To segregate connection configuration between environments:
Integrate with the Drupal Key module. This method maintains credentials in a separate secrets file. For additional information, visit Integrate the Drupal Key Module with SearchStax.
If the Drupal Key module is not an option, override the SearchStax connection settings through settings.php. For additional information, visit How do I override the SearchStax connection settings through settings.php?.
Do not use both methods together to avoid a configuration conflict.
Acquia Search powered by SearchStax supports up to 1,024 nested clauses per query. For additional information, visit Understanding the Nested Clause Limit. If you reach the 1,024 nested clause limit, you can consolidate multiple searchable fields into a single copy field to reduce search complexity. For additional information, visit Reducing Nested Clauses with Copy Fields.
Yes, Acquia Search powered by SearchStax supports Schema modifications. To modify your schema, use the Schema API and a Read/Write token for the application. For additional information, visit Upload Configurations.
All Solr request types from your sites count against the monthly utilization.
To manage utilization when it exceeds the monthly quota:
Implement a Web Application Firewall (WAF) or improve the WAF configuration based on usage analytics.
SearchStax does not allow you to block bot traffic at the API level. Acquia will make this function available in an upcoming release. Acquia recommends that you use a Web Application Firewall (WAF) such as Cloudflare.
Acquia Search powered by SearchStax plans to include FedRAMP compliance in one of the upcoming releases.
Acquia Search powered by SearchStax provides support for multiple languages. This feature includes language-specific analytics, synonyms, stopwords, and ranking. For additional information, visit Supported languages.
Migrate existing Drupal indexes and views to Acquia Search powered by SearchStax manually. For more information, visit Moving Drupal Indexes and Views to Site Search Manually.
Acquia recommends that you use the manual migration guide only in the following scenarios:
The automated migration module supports default Drupal configurations, including customizations such as stopwords, synonyms, and language fields. This module does not handle complex or highly bespoke Solr configurations. You must manually adjust these configurations to ensure compatibility.
Standard Acquia SSO login details do not work during the Migrate server step within the Drupal migration module. The migration module requires direct SearchStax account credentials to authenticate and communicate with the server. Use the specific SearchStax username and password established during initial onboarding. Check the original SearchStax invitation or welcome email for these credentials. Reliance on Acquia SSO might mean a direct password for SearchStax does not exist. If a direct password does not exist, use the password reset or Change Your Password function on the SearchStax login page to generate credentials for module authentication.
Site Factory customers must migrate during the latter stages of the rollout, before FedRAMP customers, to ensure a smooth transition with minimal manual intervention. Although the process involves the migration module, several enhancements to facilitate the transition are in development:
Automated Bulk Migration: This plan uses automated approaches for later phases and bypasses the manual setup.
Automated Provisioning: Automated account and application provisioning through API is on the roadmap for mid-to-late 2026 to enable high-volume concurrent migrations.
Optimized Process: Later schedules for larger cohorts help apply lessons from previous migrations to further streamline automated tools for multisite environments.
Every environment and application must be migrated individually. To test and validate the search functionality, begin with the non-production Development environment. After you confirm the results, proceed with the Staging and Production environments. Acquia Search entitlements remain active until all environments and applications are successfully migrated and validated.
SearchStax structure consists of the following configurations:
Standard setup: One SearchStax application per environment, which totals three applications across Development, Staging, and Production.
ACE multisite customers: Typically one SearchStax application for each production site and one shared application for non-production sites.
Site Factory customers: Typically two or three SearchStax applications for each site such as Site1_dev, Site1_stg, and Site1_prod.
For additional details, refer to Multi-site configuration with a single SearchStax app.
Service Interruption Management: To achieve zero downtime, populate the SearchStax index completely before the final step to switch views. After you verify that the results exist within the SearchStax preview, execute the switch to ensure that the results are immediately available to users.
Configuration Replication: SearchStax does not provide a method to automate the replication or synchronization of configurations between environments. Each environment maps to a distinct and independent SearchStax application with an isolated index. Configuration changes such as synonyms, relevance sliders, rules, or promotions must be manually replicated from the Dev SearchStax dashboard to the Staging and Production applications. While the Drupal codebase promotes through environments, SearchStax dashboard settings remain specific to each application.
A SearchStax application provides a method for local development environment connections. This configuration removes the requirement to run Apache Solr locally and ensures that you accurately replicate Development, Staging, and Production environments.
To index new fields added in Drupal, you must add these fields to the Search API and search fields in SearchStax. You must also reindex in Drupal to collect and index the content in these fields.
The Acquia Search powered by SearchStax onboarding process outlines the setup process. This process includes the following steps:
Access the SearchStax account.
Create a Search application.
Index data into SearchStax.
Configure the initial search.
Build a search page.
Use the most recent version of the Facets module 3.0 branch in Drupal. This version changes facet links from crawlable links to POST forms to prevent crawlers and AI bots from generating unnecessary usage.
Introduce configurable rate limiting through Drupal module directly into the SearchStax module. This feature allows further configuration from Drupal in the future. For additional information, visit Introduce Configurable Rate Limiting via Drupal Module.
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Use the most recent version of the Facets module 3.0 branch in Drupal. This version changes facet links from crawlable links to POST forms to prevent crawlers and AI bots from generating unnecessary usage.
Introduce configurable rate limiting through Drupal module directly into the SearchStax module. This feature allows further configuration from Drupal in the future. For additional information, visit Introduce Configurable Rate Limiting via Drupal Module.
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Cloud Platform