AWS CLI - couldn t connect to endpoint URL

Question

$ aws s3 ls

Could not connect to the endpoint URL: "https://s3.us-east-1a.amazonaws.com/"

What could be the problem?

Answer 1

You probably have something wrong in your default profile for the default region.

Check your file at ~/.aws/config, you have something like

[default] region=us-east-1a ...

Fix the region to region=us-east-1 and then the command will work correctly

 

Comments

yes changed the region to us-east-1 from default region. Its working now. But not sure why it is not working with default region

---

region named us-east-1a is not a valid endpoint. The valid endpoint is us-east-1.

---

It works  for me and you are correct

---

Thanks alot it worked

---

Thanks It is work  and you are correct

Answer 2

Valid endpoint names for this region:

• s3.amazonaws.com

• s3.us-east-1.amazonaws.com

• s3-external-1.amazonaws.com

• s3.dualstack.us-east-1.amazonaws.com**

• account-id.s3-control.us-east-1.amazonaws.com

• account-id.s3-control.dualstack.us-east-1.amazonaws.com**

Comments

Thanks, that was helpful.

Answer 3

I am using AWS Powershell and was recieving same error. When I logged into powershell to use the list s3 buckets command I kept getting

$ aws s3 ls
"Could not connect to the endpoint URL: "https://s3.us-east-1a.amazonaws.com/"

I made a few AWS default profiles within C:\Users\USERNAME\.aws  Credentials file. From what I have gathered you are able to login and switch user profiles while in the same windows powershell session. Let's say for example in my credentials file I have 3 different profiles: test, test2, and account3

[default]
aws_access_key_id =
aws_secret_access_key =

[test]
aws_access_key_id =
aws_secret_access_key =

[test2]
aws_access_key_id =
aws_secret_access_key =

[account3]
aws_access_key_id =
aws_secret_access_key =

It seems you must specify the user profile in your command, since you have multiple profies setup in the credentials. Try adding your profile --profile 

$ aws s3 ls --profile test

$ aws s3 ls --profile test1

$ aws s3 ls --profile account3

Get an in-depth understanding from the AWS Course in Bangalore.

Comments

Hi @jgentsch, I didn't know this feature was available. Using s3 buckets from different profiles is pretty cool and might be very useful for people. I had the same error but was solved using @Archana's answer. I did not use multiple profiles. Shall try it sometime though. Thank:)

Answer 4

I too had same issue but I was providing IAM user credential and that user didn,t had any permission,so I attached permission of full access and then it is working for me

Comments

Hey @Archana, did you give full console and programmatic access?

---

yes that i have given,but here I am mentioning IAM policy so that IAM user can able to access resources.

---

Thanks for the response. I have given the FullAccess. Still stuck with the same error.