I want to add collaborators to my Amplify Gen2 application

It sounds like you're facing a common challenge when collaborating on an Amplify Gen2 project. Even though your friends are part of your organization and have similar permissions, they're unable to see your Amplify project. This is likely due to how AWS Amplify manages access and resources across accounts within an organization.

First, it's important to note that creating individual "amplify-admin" accounts for each collaborator isn't typically necessary. Instead, you should be able to add them to your existing AWS organization and grant them appropriate permissions.

The fact that your friends are seeing the "Create your first Amplify app" view suggests that they don't have the correct permissions to view existing Amplify projects in your account. This is likely an IAM (Identity and Access Management) issue.

To resolve this:

1. Ensure that your friends have the correct IAM policies attached to their roles or users. They should have permissions that include actions like amplify:GetApp, amplify:ListApps, and amplify:ListBranches.

2. Double-check that you've granted them access to the specific Amplify project. Sometimes, Amplify projects require explicit sharing with team members.

3. Verify that they're accessing the AWS console using the correct AWS account - it should be your organization's account, not their personal accounts.

4. If you're using AWS SSO (Single Sign-On), make sure the permission sets assigned to your friends include the necessary Amplify permissions.

5. Check if there are any Service Control Policies (SCPs) in your organization that might be restricting access to Amplify services.

Regarding the sandbox environments, it's normal for each developer to have their own sandbox stack in their resources. This allows them to work independently without affecting the main project until they're ready to merge their changes.

If you've confirmed all these points and the issue persists, you may need to review the CloudTrail logs for any denied actions related to Amplify. This can help identify any missing permissions or other access issues.

Remember, setting up proper access for a collaborative Amplify project can be complex, so don't hesitate to reach out to AWS Support if you continue to face difficulties after trying these steps.
Sources
Organization Members cannot see or access my amplify projects. | AWS re:Post
Organization Members cannot see or access my amplify projects | AWS re:Post