SSO Start URL not working

It seems you're encountering an issue with the SSO start URL while trying to configure AWS for local development using Amplify Gen 2. This is a common problem that can occur for various reasons.

First, make sure you're using the correct SSO start URL. This URL should typically include "awsapps.com/start" in its structure. If you're unsure about the correct URL, you may need to check your email, browser history, or contact your AWS administrator to obtain the correct AWS access portal URL for your organization.

When running the "aws configure sso" command, you'll be prompted to enter several pieces of information. Make sure you're entering the correct SSO start URL, SSO region, and leaving the SSO registration scopes blank if not specified.

If you're certain you're using the correct URL but still encountering issues, there could be a few other factors at play:

1. Browser issues: The SSO process typically attempts to open your default browser automatically. If this fails, you may need to manually copy and paste the provided URL into your browser.

2. Network problems: Although you've tried turning off your firewall, there could be other network-related issues preventing access to the SSO URL. Ensure you have a stable internet connection and that there are no restrictions on accessing AWS domains.

3. AWS CLI version: Ensure you're using the latest version of the AWS CLI, as older versions might have compatibility issues with current SSO processes.

4. AWS CLI now adds PKCE-based Authorization for SSO: The AWS Command Line Interface v2 now supports OAuth 2.0 authorization code flows using the Proof Key for Code Exchange standard starting from version 2.22.0. Hence, you may need to use the previous workflow, which uses the OAuth 2.0 device authorization grant, in environments where the AWS CLI is unable to launch a browser or receive the OAuth callback that is used in the authorization code flow. To continue using the previous workflow specify the new --use-device-code option for aws configure sso:

     `$ aws sso login --profile my-sso-profile --use-device-code`
   

   • https://aws.amazon.com/blogs/developer/aws-cli-adds-pkce-based-authorization-for-sso/

5. Ensure that the “~/.aws/config" is populated correctly.

   • https://docs.amplify.aws/react/start/account-setup/#4-set-up-local-aws-profile

6. Temporary service disruption: While rare, there could be temporary issues with AWS services. You can check the AWS Service Health Dashboard to see if there are any ongoing issues.

If none of these solutions work, you may need to reach out to AWS Support or your organization's AWS administrator for further assistance. They can help verify your account settings and ensure you have the correct permissions to use SSO.
Sources
Configure AWS for local development - React - AWS Amplify Gen 2 Documentation
Troubleshooting AWS account sign-in issues - AWS Sign-In