Troubleshooting AWS CLI Error: "Found request with the same client request token, but parameters do not match" when adding Cloud9 Environment Membership

Introduction: When working with AWS CLI to create environment memberships for a Cloud9 resource, you may encounter an error message stating: "An error occurred (BadRequestException) when calling the CreateEnvironmentMembership operation: Found request with the same client request token, but parameters do not match. Try again with a new token." This article will guide you through the possible cause of this error and provide a solution to resolve it.


Error Explanation: The above error occurs when you attempt to create an environment membership while logged in as a different user. The AWS CLI command fails to match the user information and the ownership of the Cloud9 environment, resulting in the error message. Consequently, you cannot open your Cloud9 IDE.

aws cli command

aws cloud9 create-environment-membership --environment-id abcdenvironmentid --user-arn arn:aws:iam::123123123:user/theusername --permissions read-write


Troubleshooting Steps: If you encounter this error, follow the steps below to diagnose and resolve the issue:


  1. Step 1: Check your AWS Account Login: Verify the user account you are currently logged in with. Ensure that it matches the intended user you wish to grant ownership of the Cloud9 environment to.

  2. Step 2: Verify Cloud9 Environment Ownership

    1. Determine the role owner for Cloud9 environments. You can find this information by looking at the "Owner ARN" column.

  1. Carefully examine the aws cloud9 command you executed. In our example, it is arn:aws:iam::123123123:user/theusername. If you encountered the error mentioned earlier, the user obtained in Step 2a and Step 2b should be the same.

  1. Compare Users: Compare the user from Step 1 (your logged-in user) with the user from Step 2 (the Cloud9 environment's role owner). If they are different, this is likely the cause of the error.


Solution: To resolve this error, log in to your AWS account as the user obtained in Step 2 above. This user should be the intended owner of the Cloud9 environment. Now you should be able to open the Cloud9 IDE.


Conclusion: When encountering the error above while using the AWS CLI to create environment memberships for Cloud9 resources, it is important to verify your logged-in user and ensure it matches the intended owner of the Cloud9 environment. By carefully comparing users and logging in as the correct user, you can successfully resolve this error and proceed with creating environment memberships.


Remember to double-check your command parameters and permissions to ensure a smooth experience when working with AWS CLI and Cloud9 environments.



Resources:

  1. Error explanation on cloud9 access IDE in eksworkshop.com 

  2. IAM user sign in tutorial

  3. Root user sign in tutorial


Comments

Post a Comment