Why repeatedly Amazon Q Developer goes into an invalid state?

Question

Each time I go to Settings link under Amazon Q Developer console. It pops up this error message asking user to delete the profile "The Amazon Q Developer application has been deleted from your IAM Identity Center, leaving Amazon Q Developer in an invalid state. To continue to use Amazon Q Developer, the Amazon Q Developer profile must first be deleted." and gives warning like below
"Proceeding with this action will permanently delete this profile including all settings, associated user data, customizations and user access."

After deleting the profile and subscribing again for the same user, the error goes away and it works as expected. But the same error keeps repeats when I go back to some other AWS Service Console and comeback.

Sequence of Steps leading to the error.
1. Enable IAM Identity Center at Account level
2. Create a user and verify email
3. Subscribe user with Amazon Q Developer Pro
4. Click on Settings link under Amazon Q Developer Console.

re:Post Agent · Answer

The issue you're experiencing with Amazon Q Developer repeatedly going into an invalid state is likely related to a synchronization problem between the Amazon Q Developer application and IAM Identity Center. This can happen due to several reasons:

1. Delayed propagation: When you make changes to user access or subscriptions, there can be a delay in propagating these changes across AWS services. This delay can sometimes cause the system to temporarily perceive the application as deleted or in an invalid state.

2. Session management: If you're switching between different AWS service consoles, there might be issues with session management or identity-aware console sessions not being properly configured or maintained.

3. Subscription activation delay: When you're newly added to a group or your subscription is recently activated, it can take up to 24 hours for the access to be fully activated and recognized across all AWS services.

4. IAM permissions: There might be insufficient or conflicting IAM permissions that are causing issues with maintaining the connection between Amazon Q Developer and IAM Identity Center.

To mitigate this issue:

1. Ensure that you have the necessary IAM permissions to access and manage Amazon Q Developer.

2. Wait for at least 24 hours after subscribing or making changes to allow for full propagation of access across AWS services.

3. Make sure identity-aware console sessions are properly set up and enabled for your account.

4. If the issue persists, contact AWS support to investigate if there are any underlying configuration problems or known issues with the service.

Remember that deleting the profile and re-subscribing is a temporary fix and not a long-term solution. If the problem continues to occur frequently, it may indicate a more significant issue that requires attention from AWS support.  
**Sources**  
[Troubleshooting Amazon Q Developer Pro subscriptions - Amazon Q Developer](https://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/q-admin-setup-subscribe-troubleshooting.html)  
[Amazon Q in Amazon SageMaker Unified Studio - Amazon SageMaker Unified Studio](https://docs.aws.amazon.com/sagemaker-unified-studio/latest/adminguide/amazonq.html)

Why repeatedly Amazon Q Developer goes into an invalid state?

Add your answer

Relevant content