# Profile key not respected in serverless.yml

**URL:** <https://forum.serverless.com/t/profile-key-not-respected-in-serverless-yml/1874>\
**Category:** Serverless Framework\
**Created:** [May 15, 2017, 9:59pm UTC](https://forum.serverless.com/t/profile-key-not-respected-in-serverless-yml/1874 "2017-05-15T21:59:48Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![jjfine](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/jjfine/32/660_2.png) [@jjfine](https://forum.serverless.com/u/jjfine)\
**Post date:** [May 15, 2017, 9:59pm UTC](https://forum.serverless.com/t/profile-key-not-respected-in-serverless-yml/1874/1 "2017-05-15T21:59:48Z")

</div>

In my `serverless.yml` I’ve got:

```
provider:
  name: aws
  runtime: java8
  profile: test

```

Seems like it’s using my `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY` environment variables instead of this profile. Is this expected?

---

<div class="post-metadata">

**Author:** ![DavidWells](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/davidwells/32/201_2.png) [@DavidWells](https://forum.serverless.com/u/DavidWells)\
**Post date:** [May 15, 2017, 10:10pm UTC](https://forum.serverless.com/t/profile-key-not-respected-in-serverless-yml/1874/2 "2017-05-15T22:10:00Z")

</div>

Do you have a profile named `test` in the `/Users/xxxx/.aws/credentials` file?

---

<div class="post-metadata">

**Author:** ![DavidWells](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/davidwells/32/201_2.png) [@DavidWells](https://forum.serverless.com/u/DavidWells)\
**Post date:** [May 15, 2017, 10:11pm UTC](https://forum.serverless.com/t/profile-key-not-respected-in-serverless-yml/1874/3 "2017-05-15T22:11:12Z")

</div>

The aws credentials file should look like:

```auto
[default]
aws_access_key_id=xxxxxxxxxxx
aws_secret_access_key=aaaaaaaaaaaaaaaaaa
[test]
aws_access_key_id=yyyyyyyyyyyyyyy
aws_secret_access_key=zzzzzzzzzzzzzzzzzzz

```

---

<div class="post-metadata">

**Author:** ![rowanu](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/rowanu/32/75_2.png) [@rowanu](https://forum.serverless.com/u/rowanu)\
**Post date:** [May 15, 2017, 10:33pm UTC](https://forum.serverless.com/t/profile-key-not-respected-in-serverless-yml/1874/4 "2017-05-15T22:33:58Z")

</div>

While I haven’t tested it extensively, I think I’ve seen the AWS SDK (which Serverless uses) prioritise the `AWS_ACCESS_KEY_ID` and `AWS_ACCESS_KEY_ID` variables over a specific profile, which would explain what you’re seeing (assuming your profiles are setup correctly, as per @DavidWells’s question).

---

<div class="post-metadata">

**Author:** ![jjfine](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/jjfine/32/660_2.png) [@jjfine](https://forum.serverless.com/u/jjfine)\
**Post date:** [May 16, 2017, 1:38pm UTC](https://forum.serverless.com/t/profile-key-not-respected-in-serverless-yml/1874/5 "2017-05-16T13:38:57Z")

</div>

Yeah, that must be it. Thanks.