Deployment issues relating to account permissions and access keys

Last update: Wed Nov 06 2024 00:00:00 GMT+0000 (Coordinated Universal Time)

CREATED FOR:

Developer

This article provides a solution for issues with deploying Adobe Commerce on cloud infrastructure caused by access key ownership conflict.

Affected products and versions

Adobe Commerce on cloud infrastructure, all supported versions

Issue

Prerequisites:

The Cloud license is associated with Contact A (email address: first@e.mail)

Steps to reproduce:

Contact A created Adobe Commerce access keys on their account (Key X) and installed them on the Cloud.
Contact B (email address: second@e.mail) purchased an extension using his account and created the access keys for installing the extension (Key Y).
Contact A then left the company, and the license (ownership) was then transferred to Contact B.
System integrator tries to install the extension on the cloud environment using Key X.

Expected result:

Extension is successfully installed.

Actual result:

Extension is not installed because deployment fails.

Cause

Both keys are assigned to the contact role, which causes a conflict.

Solution

If a deployment failed after a change was made to the Primary Contact on the account (with both the original account and the new account each having their own access keys), and the keys have been transferred from the original account to the new account, you need to disable the keys from the original account. In terms of the example above, the key X should be disabled.