AWS, Credential must have exactly 5 slash-delimited elements,

Question

During executing eb init on Ubuntu 16.04 I faced an error Credential must have exactly 5 slash-delimited elements, e.g. keyid/date/region/service/term,.

I understand that my keyid has slashes but they must be there, key was provided by AWS and it is generated. I have no idea how to skip this validation. As I know on MAC this problem is not present.

How can I deal with this error? thanks

In may case I was using access_key as secret_key and secrect_key as access_key :D — Adiii, Sep 16 '19 at 11:01
@Moshe haha then I think it's not bad idea to post as an answer :D — Adiii, Oct 12 '20 at 16:49

score 29 · Answer 1 · answered Jun 15 '18 at 11:45

An AWS Access Key ID does not have any slashes. It is comprised of uppercase ASCII letters only, and begins with AKIA... or ASIA....

One possible explanation is that you have transposed your access key ID with the accompanying secret access key, which does often have slashes.

Access keys consist of an access key ID (for example, AKIAIOSFODNN7EXAMPLE) and a secret access key (for example, wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY).

https://docs.aws.amazon.com/general/latest/gr/aws-sec-cred-types.html#access-keys-and-secret-access-keys

If you have indeed transposed these values in your configuration, you should deactivate these credentials and create new ones before proceeding, because you may have inadvertently exposed your secret key.

score 21 · Answer 2 · answered Oct 13 '20 at 14:14

In my case, I was using access_key as secret_key and secrect_key as access_key.

So better to double-check the secret.

Also access key should not contain any special character. Plus one easy to identify the access key is to looking into prefix of the key.

The access key begins with the prefix ASIA, otherwise it beings with AKIA. All random looking ID’s on AWS have their own 4 letter prefixes that identify what they are.

aws_security_credential_formats

Thanks for the reminder, I was also using them in opposite order, silly me — Ebin Xavier, Jun 28 '22 at 05:43

score 3 · Answer 3 · answered May 13 '20 at 05:01

3

i have environmental variables for access id and secret key, i had them interchanged, that was the issue, once i set those correctly it works

answered May 13 '20 at 05:01

Akhil

69
1
5

score 0 · Answer 4 · answered Dec 21 '22 at 14:01

0

In my case, env keys were lowercase. Making them uppercase solved my issue

aws_access_key_id -> AWS_ACCESS_KEY_ID

aws_secret_access_key -> AWS_SECRET_ACCESS_KEY

answered Dec 21 '22 at 14:01

Mustafa Candan

76
7

AWS, Credential must have exactly 5 slash-delimited elements,

4 Answers4