Acquia DAM now supports the Key module for credential management

Acquia DAM now integrates with the Key module for managing API credentials. You can now store your Acquia DAM domain and token using Drupal's Key management system instead of storing them directly in configuration.
This is a backward-compatible enhancement - existing configurations will continue to work without changes.

What's New

The Acquia DAM configuration form now supports two methods for storing credentials:

1. Direct configuration (existing method) - Store credentials directly in configuration
2. Key module integration (new method) - Reference Key entities for secure credential storage

When using the Key module, you can leverage various Key providers:

• File provider - Store credentials in files outside the web root
• Environment provider - Use environment variables
• Configuration provider - Store in configuration (encrypted if using encrypt module)
• Third-party providers - AWS Secrets Manager, HashiCorp Vault, etc.

How to Use

• Install the Key module: composer require drupal/key
• Create keys for domain and token at /admin/config/system/keys
• Configure Acquia DAM at /admin/config/media/acquia_dam to use the keys

No action required for existing sites - migration to Key module is optional.

Benefits

• Better security - Store credentials outside configuration using File, Environment, or third-party Key providers
• DevOps-friendly - Separate credentials from config exports, use different keys per environment

See also: Key module documentation.