Use Disconnect in Connect AWS when you intend to remove the module’s saved Bedrock connection. First identify whether it uses your own existing key or a key generated by the module, because the cleanup differs.

Check what will be affected

Open Addons → PD Modules, choose PD AI Assistant, then open Settings → Provider & connection. Record the active provider and model without copying any secret. The Connect AWS summary distinguishes your own key from an auto-generated connection.

If Bedrock is active, removing its connection prevents Bedrock replies and custom Knowledge operations until a suitable connection is restored. Review enabled customer chat and automated work before proceeding.

If you intend to move to a different provider, use the provider-change guide and verify the replacement first. Disconnecting AWS is not a global off switch for another provider that remains active.

Disconnect an existing key you supplied

1. Open the Connect AWS panel and confirm that the saved connection is the one you intend to remove.
2. Click Disconnect and read Disconnect AWS carefully.
3. Confirm the action when ready.
4. Check that the saved connection summary has been replaced by the connection options.

For a key you supplied, this removes the module’s saved active credentials; it does not revoke the credential in AWS. Have the person who manages that key retire it through AWS if it is no longer needed, after checking whether another service uses it.

Handle a generated key carefully

For an auto-generated connection, the confirmation also describes deleting the dedicated AWS key and user. The module attempts that cleanup using the saved account key. If that account key has been forgotten, is no longer authorised, or cleanup fails, local disconnection can still complete.

Do not treat a success message as proof that the remote key and user were removed. Ask your AWS administrator to verify cleanup of the specifically identified generated identity. If anything remains, have your AWS administrator handle the identified identity through your authorised cleanup process and retain the redacted outcome; local disconnection is not confirmation of remote removal.

Forget account key is a separate action for the saved key used to generate and clean up dedicated credentials. It does not disconnect the active Bedrock key. Plan remote cleanup before forgetting that account key; do not retain unnecessary credentials indefinitely.

Confirm the final state

Check the active provider summary and the AWS panel. Removing the AWS connection does not erase chat history, Memory, indexed Knowledge or existing proposals. A replacement provider may also require rebuilding custom Knowledge.

If the visible result is unclear, inspect the panel before repeating the operation. Retain the original redacted message while your hosting team checks the final state; keep credentials and customer conversations out of diagnostics.

See the PD AI Assistant WHMCS guide for related tasks, or explore PD AI Assistant.