iSharkFly-Docs
/
packer-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

README.md quick-start builder example made more secure 

Adding credentials to a file that may get committed to
a git repository is dangerous; make the example follow
best practices and pull the AWS credentials out of
the environment
This commit is contained in:
Asfand Yar Qazi 2015-12-15 22:33:19 +00:00
parent 8d574962d9
commit eaa088b491
1 changed files with 8 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
README.md
View File

@ -42,15 +42,19 @@ for your operating system or [compile Packer yourself](#developing-packer).
After Packer is installed, create your first template, which tells Packer After Packer is installed, create your first template, which tells Packer
what platforms to build images for and how you want to build them. In our what platforms to build images for and how you want to build them. In our
case, we'll create a simple AMI that has Redis pre-installed. Save this case, we'll create a simple AMI that has Redis pre-installed. Save this
file as `quick-start.json`. Be sure to replace any credentials with your file as `quick-start.json`. Export your AWS credentials as the
own. `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY` environment variables.
```json ```json
{ {
"variables": {
"access_key": "{{env `AWS_ACCESS_KEY_ID`}}",
"secret_key": "{{env `AWS_SECRET_ACCESS_KEY`}}"
},
"builders": [{ "builders": [{
"type": "amazon-ebs", "type": "amazon-ebs",
"access_key": "YOUR KEY HERE", "access_key": "{{user `access_key`}}",
"secret_key": "YOUR SECRET KEY HERE", "secret_key": "{{user `access_key`}}",
"region": "us-east-1", "region": "us-east-1",
"source_ami": "ami-de0d9eb7", "source_ami": "ami-de0d9eb7",
"instance_type": "t1.micro", "instance_type": "t1.micro",