Set to use a basic Windows source AMI that qualifies for free tier usage

This commit is contained in:
DanHam 2017-10-13 20:55:12 +01:00
parent ed0a60bd61
commit e4985ae6f6
1 changed files with 12 additions and 6 deletions

View File

@ -319,11 +319,17 @@ amazon-ebs output will be in this color.
### A Windows Example ### A Windows Example
Note that this uses a larger instance. You will be charged for it. Also keep As with the Linux example above, should you decide to follow along and
in mind that using windows AMIs incurs a fee that you don't get when you use build an AMI from the example template, provided you qualify for free tier
linux AMIs. usage, you should not be charged for actually building the AMI.
However, please note that you will be charged for storage of the snapshot
associated with any AMI that you create.
If you wish to avoid further charges, follow the steps in the [Managing the
Image](/intro/getting-started/build-image.html#managing-the-image) section
above to deregister the created AMI and delete the associated snapshot once
you're done.
You'll need to have a boostrapping file to enable ssh or winrm; here's a basic You'll need to have a bootstrapping file to enable ssh or winrm; here's a basic
example of that file. example of that file.
```powershell ```powershell
@ -398,11 +404,11 @@ windows in addition to the powershell and windows-restart provisioners:
"access_key": "{{ user `aws_access_key` }}", "access_key": "{{ user `aws_access_key` }}",
"secret_key": "{{ user `aws_secret_key` }}", "secret_key": "{{ user `aws_secret_key` }}",
"region": "us-east-1", "region": "us-east-1",
"instance_type": "m3.medium", "instance_type": "t2.micro",
"source_ami_filter": { "source_ami_filter": {
"filters": { "filters": {
"virtualization-type": "hvm", "virtualization-type": "hvm",
"name": "*WindowsServer2012R2*", "name": "*Windows_Server-2012-R2*English-64Bit-Base*",
"root-device-type": "ebs" "root-device-type": "ebs"
}, },
"most_recent": true, "most_recent": true,