hashicorp / hashicorp/packer-plugin-amazon
amazon-ebs: failed to get shared config profile, default #13533
- Dominant language
- Go
- Stars
- 91
- Forks
- 141
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 3
Description
#### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment
#### Overview of the Issue
The new version 1.8.0 is producing this error,
```
[Container] 2025/11/19 14:42:32.000162 Running command packer plugins install github.com/hashicorp/amazon
--
Installed plugin github.com/hashicorp/amazon v1.8.0 in "/root/.config/packer/plugins/github.com/hashicorp/amazon/packer-plugin-amazon_v1.8.0_x5.0_linux_amd64"
[Container] 2025/11/19 14:42:34.784512 Running command packer build -timestamp-ui -var-file=variables-staging.json ami-code.json
amazon-ebs: output will be in this color.
2025-11-19T14:42:35Z: Build 'amazon-ebs' errored after 841 microseconds: failed to get shared config profile, default
==> Wait completed after 884 microseconds
==> Some builds didn't complete successfully and had errors:
--> amazon-ebs: failed to get shared config profile, default
==> Builds finished but no artifacts were created.
```
#### Reproduction Steps
I'm not sure our config is pretty straight forward
```json
"builders": [
{
"type": "amazon-ebs",
"profile": "default",
"region": "{{user `region` }}",
...
```
### Packer version
From `1.8.0`.
`1.7.1` is fine, so we fixed to that version as a workaround.
Contributor guide
Assessment
This issue has not been assessed yet.