Copilot init fails with MissingEndpoint: 'Endpoint' configuration is required for this service

[nickponomar]

I am following first tutorial on getting started with copilot -> https://docs.aws.amazon.com/AmazonECS/latest/developerguide/getting-started-aws-copilot-cli.html

At the copilot init step it fails with the following:

demo-app % copilot init
Welcome to the Copilot CLI! We're going to walk you through some questions
to help you get set up with a containerized application on AWS. An application is a collection of
containerized services that operate together.

Application name: demo
✘ ask app init: get application demo: get application demo: MissingEndpoint: 'Endpoint' configuration is required for this service

Just in case:

demo-app % copilot --version
copilot version: v1.28.0

How do I even debug it? This failure message is not really helpful

[Lou1415926]

@nickpnmrv Umm seems like the AWS SDK is complaining that it cannot resolve the endpoint for SSM.

If you have aws-cli installed - are you able to run this command ⬇️ ?

aws ssm get-parameters --names /copilot/applications/demo

In addition, do you have ~/.aws/config and ~/.aws/credentials files?

[nickponomar]

@Lou1415926 both files are there containing aws credentials, here is what I get replaced all the secrets with ***:

demo-app % nano ~/.aws/credentials
aws_access_key_id = ***
aws_secret_access_key = ***

demo-app % nano ~/.aws/config
region = ***
[profile ***]
sso_session = macbook
sso_account_id = ***
sso_role_name = ***
region = eu-central-1
[sso-session macbook]
sso_start_url = ***
sso_region = eu-central-1
sso_registration_scopes = ***

aws ssm get-parameters --names /copilot/applications/demo returns:

Provided region_name 'IQoJb3J***psdddsfVjEKL//////////wEaDGV1LWNlbnR***yYWwtMSJIMEYCIQDZRd/sZxYIKKbEwhfn1rCfyJvzQdVZOLJYaqlUnppihgIhAIyUhG8jjSIzLT***kpk9PZmc6s+fPpDMK90QhsdWkmjmLoy/4p1qDs***etWT' doesn't match a supported format.

'doesn't match a supported format' is probably something that requires a fix?

[Lou1415926]

@nickpnmrv I think your ./aws/credentials and ./aws/config files are probably misconfigured! For example - as far as I know - the credentials file is grouped by "profile":

# This would result in a parsing error.
aws_access_key_id = ***
aws_secret_access_key = ***

# This is fine.
[myprofile]
aws_access_key_id = ***
aws_secret_access_key = ***

The same applies to .aws/config.

In addition, I notice that you are using SSO. As of today, unfortunately you have to use legacy SSO in Copilot (see #4359). You can also take a look at this thread to configure a legacy SSO.

Once we upgrade our AWS SDK, or once aws/aws-sdk-go#4649 is resolved, you will be able to go back to the recommended SSO config. #4359 contains