We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi I am getting a below error message when tried to create a packer for nginx on windows 10.
Error: NoCredentialProviders: no valid providers in chain. Deprecated. For verbose messaging see aws.Config.CredentialsChainVerboseErrors
Can you help me to resolve. Thanks kalyan
{ "variables": { "aws_access_key": "", "aws_secret_key": "" }, "builders": [ { "type": "amazon-ebs", "access_key": "{{ user aws_access_key }}", "secret_key": "{{ user aws_secret_key }}", "region": "us-east-2", "source_ami": "ami-00399ec92321828f5", "instance_type": "t2.micro", "ssh_username": "ubuntu", "ami_name": "kalyan-packer1 {{timestamp}}" } ], "provisioners": [ { "type": "shell", "inline": [ "sudo apt-get update", "sudo apt-get install nginx -y" ] } ] }
aws_access_key
aws_secret_key
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hi
I am getting a below error message when tried to create a packer for nginx on windows 10.
Error: NoCredentialProviders: no valid providers in chain. Deprecated.
For verbose messaging see aws.Config.CredentialsChainVerboseErrors
Can you help me to resolve.
Thanks
kalyan
{
"variables": {
"aws_access_key": "",
"aws_secret_key": ""
},
"builders": [
{
"type": "amazon-ebs",
"access_key": "{{ user
aws_access_key
}}","secret_key": "{{ user
aws_secret_key
}}","region": "us-east-2",
"source_ami": "ami-00399ec92321828f5",
"instance_type": "t2.micro",
"ssh_username": "ubuntu",
"ami_name": "kalyan-packer1 {{timestamp}}"
}
],
"provisioners": [
{
"type": "shell",
"inline": [
"sudo apt-get update",
"sudo apt-get install nginx -y"
]
}
]
}
The text was updated successfully, but these errors were encountered: