Use Drupal AI with amazee.ai¶
The amazee.ai AI Provider module connects Drupal's AI module ecosystem to amazee.ai. Once installed, Drupal's AI-powered features — content generation, translation, moderation, chatbots, image alt text, and more — run through your regional amazee.ai endpoint, keeping your data in the region you choose.
The module provisions both an LLM endpoint and a managed vector database, so RAG-based features work out of the box without separate infrastructure setup.
Prerequisites¶
- Drupal 10.3+ or Drupal 11
- Drush (recommended for setup)
- An amazee.ai account — create one at my.amazee.io or directly inside the module during configuration
The AI module and Key module are required dependencies and will be pulled in automatically by Composer.
Install¶
Configure¶
- Go to Admin → Configuration → AI → AI Settings (
/admin/config/ai/settings) - Select amazee.ai as your AI provider
- Enter your amazee.ai API key
If you don't have an API key yet, you can create an account directly from this screen.
Option: use the configuration recipe¶
For automated setup, the amazee.ai AI Provider Recipe configures the provider and its dependencies in one step:
composer require drupal/ai_provider_amazeeio_recipe:^1.0@beta
drush recipe:apply amazeeio_ai_provider
This is the fastest path for new sites or CI/CD pipelines.
What you can do¶
With the provider active, any Drupal AI module that supports the AI module ecosystem works automatically. Common use cases:
| Feature | What it does |
|---|---|
| Content generation | Draft page content, summaries, and metadata from inside the node editor |
| Translation | Translate content into multiple languages via AI directly in the Drupal UI |
| Image alt text | Auto-generate alt text on image upload |
| Pre-moderation | Flag or approve content before publish |
| Chatbot / search | Replace site search with a conversational assistant |
| Tone adjustment | Rewrite content to match a formal, friendly, or promotional tone |
| Compliance checking | Scan content for policy violations before publish |
| Auto-categorisation | Apply tags and categories based on content |
| Accessibility auditing | Identify missing headings, improper link text, and contrast issues |
| RAG / vector search | Query a managed pgvector database provisioned with your account |
For a broader view of what the Drupal AI ecosystem supports, see Workflows of AI and the Drupal AI module overview.
Data residency¶
Your data is processed in the region you select at my.amazee.io. Available regions:
| Region | Endpoint |
|---|---|
| 🇩🇪 Germany | llm.de103.amazee.ai |
| 🇬🇧 United Kingdom | llm.uk103.amazee.ai |
| 🇨🇭 Switzerland | llm.ch103.amazee.ai |
| 🇺🇸 United States | llm.us103.amazee.ai |
| 🇦🇺 Australia | llm.au103.amazee.ai |
Need a different region? Contact ai.support@amazee.io.
Troubleshooting¶
- API key not accepted
- Confirm the key is entered under AI Settings, not the Key module's generic key list. The Key module stores it, but the provider configuration screen is where you link it.
- No models appear in the model selector
- Clear Drupal's cache (
drush cr) after saving the provider settings. The module fetches the available model list on first save. - Vector database not available
- The managed pgvector instance is provisioned automatically when your account activates. If it doesn't appear, check my.amazee.io → Services or contact support.
- Composer version conflict
- The module requires
drupal/aias a dependency. If you have a conflicting version pinned in yourcomposer.json, resolve that first withcomposer why-not drupal/ai_provider_amazeeio.