error configuring Terraform AWS Provider

[RamanaChowdam]

i have Terraform v0.12.28

• provider.aws v3.0.0
• provider.null v2.1.2

when i run terraform apply and plan it giving below error
error configuring Terraform AWS Provider: Error creating AWS session: SharedConfigLoadError: failed to load config file, /home/wavemaker/.aws/config
caused by: INIParseError: invalid state with ASTKind {completed_stmt {0 NONE 0 []} false [{section_stmt {1 STRING 0 [78 111 110 101]} true []}]} and TokenType op

on main.tf line 1, in provider "aws":
1: provider "aws" {

but i am passing access_key and secret_key using env variables to the terraform main file

[ewbankkit]

Similar:

• Version 3.0.0 provider giving INIParseError: invalid state with ASTKind #14439

[RamanaChowdam]

Similar:

• Version 3.0.0 provider giving INIParseError: invalid state with ASTKind #14439

but i didn't have any session token details in my config file

[Andrew13648]

@RamanaChowdam If I had to guess, I think the issue is with having a null/None value in your config file and not specifically tied to a session token (if you run an ASCII to text converter for 078 111 110 101 you get a value of None). Do you have any None values / blank values set in your config file?

[lispnik]

I had a fairly new awscli installation and my ~/.aws/config had nonsense like (literally):

[default]
aws_secret_access_key = [secretKey]
...

My credentials where in ~/.aws/credentials, of course. Removing the offending lines allows the INIParser to proceed.

The error message is pretty brutal though.

[e-power]

So this also breaks when you have valid config i.e. in ~/.aws/config file

cli_pager=

Which sends aws command output to STDOUT.

Am I going to have comment this out every time I wish to run terraform vs awscli?

[bflad]

Hi folks 👋 Any issues with parsing AWS configuration files, such as incorrect handling with certain options or hard to understand INIParseError errors, will need bug reports filed upstream in the AWS Go SDK. The Terraform AWS Provider is wholly dependent on the AWS Go SDK to properly work with INI files that are also supported by other AWS SDKs and the AWS CLI (boto/Python).

[KaibaLopez]

Hi, It might be a matter of updating the dependencies on the project, this problem should already have been fixed as of version 1.35 of the Go SDK. Here's the PR that fixes it.

[dimisjim]

@KaibaLopez This doesn't seem to be the case: aws/aws-sdk-go#3756 (comment)

[dimisjim]

@bflad

The issue can be fixed if one adds a newline at the end of their .aws/config file: aws/aws-sdk-go#3756 (comment)

[llamafilm]

I had this problem due to some junk characters in the config file

[github-actions]

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!

[sleonardprove]

This issue may be stale, but it is still a problem.