You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jul 3, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Jul 3, 2023. It is now read-only.
I just wanted to try the "Quickstart" but got the following errors when running "terraform apply" command:
Error applying plan:
7 error(s) occurred:
aws_subnet.internal.1: Error creating subnet: InvalidParameterValue: Value (us-west-2b) for parameter availabilityZone is invalid. Subnets can currently only be created in the following availability zones: us-east-1a, us-east-1b, us-east-1d, us-east-1e.
status code: 400, request id: 18263fde-a8ef-4696-a08a-f0f4c7a76856
aws_subnet.internal.2: Error creating subnet: InvalidParameterValue: Value (us-west-2c) for parameter availabilityZone is invalid. Subnets can currently only be created in the following availability zones: us-east-1a, us-east-1b, us-east-1d, us-east-1e.
status code: 400, request id: 30d9c3c5-ab70-4607-ac53-727e89b99d95
aws_subnet.internal.0: Error creating subnet: InvalidParameterValue: Value (us-west-2a) for parameter availabilityZone is invalid. Subnets can currently only be created in the following availability zones: us-east-1a, us-east-1b, us-east-1d, us-east-1e.
status code: 400, request id: eabdf1f0-0e82-410e-843c-cf61968af01e
aws_subnet.external.1: Error creating subnet: InvalidParameterValue: Value (us-west-2b) for parameter availabilityZone is invalid. Subnets can currently only be created in the following availability zones: us-east-1a, us-east-1b, us-east-1d, us-east-1e.
status code: 400, request id: 692192b3-822b-4149-9294-ac710b353586
aws_subnet.external.2: Error creating subnet: InvalidParameterValue: Value (us-west-2c) for parameter availabilityZone is invalid. Subnets can currently only be created in the following availability zones: us-east-1a, us-east-1b, us-east-1d, us-east-1e.
status code: 400, request id: 38847188-311a-4edb-9c76-3a2782087f6f
aws_subnet.external.0: Error creating subnet: InvalidParameterValue: Value (us-west-2a) for parameter availabilityZone is invalid. Subnets can currently only be created in the following availability zones: us-east-1a, us-east-1b, us-east-1d, us-east-1e.
status code: 400, request id: 3885f22e-823d-4d51-aa7b-1884feaf3dcd
aws_launch_configuration.main: InvalidAMIID.NotFound: The image id '[ami-f3985d93]' does not exist
status code: 400, request id: dc5aebf9-3abd-4232-a45d-71f75a3f5654
Ah, @backnight by default we boot all of the instances in us-west-2. If you want to use a different region, you'll have to pass in your own availability zones for it:
We've copied the AMIs to all EC2 regions, they will be selected automatically by default if you change the region.
For the availability zones (and by extension the subnets) you should specify them manually, it's the best we can do for now. I tried to give a shot at having terraform dynamically select the right AZ and generate the subnets accordingly but it doesn't work, the subnet resources are generated dynamically via the count property and terraform needs to know how many it has to create or the plan fails (no dynamically computed value can be given to the count property unfortunately).
If you know of a better way feel free to let me know and I'll give it a shot.
Is somebody updating the AMIs? Did a terraform apply earlier today no problems. Tried it again just now in us-east-1 to be greeted with:
aws_launch_configuration.main: InvalidAMIID.NotFound: The image id '[ami-f3985d93]' does not exist; status code: 400, request id: 68e2242a-c53d-4380-9274-16f3bca2deaf
The AMIs were not changed to the best of my knowledge, however this AMI seems to be available for us-west-2, in us-east-1 the AMI id is ami-5f3ff932, not sure why the modules haven't selected the right AMI here :/
I reverted to Terraform v0.6.16, as I believe one of my other issues stemmed from 0.7. I am now currently trying to do a terraform get of the master branch, and am receiving the error
Error loading Terraform: Error downloading modules: module vpc: Error loading .terraform/modules/<long id>/main.tf: Variable 'external_subnets' must be of type string or map - 'list' is not a valid type
@adambarthelson Just by looking at the stack config, i think you're missing the region:
module"stack" {
source="github.com/segmentio/stack?ref=0.1"name="clientname"environment="demo"key_name="bastion-ssh"availability_zones="us-east-1d,us-east-1a,us-east-1b"region="us-east-1"// <- Missing from your config?
}
If you're just getting started, i suggest you use the latest terraform, lots of fixes and new features!
Activity
calvinfo commentedon Jun 17, 2016
Ah, @backnight by default we boot all of the instances in
us-west-2. If you want to use a different region, you'll have to pass in your own availability zones for it:calvinfo commentedon Jun 17, 2016
As far as the image not being found, cc @achille-roussel can you double check the public settings?
achille-roussel commentedon Jun 17, 2016
AMIs are local to the region as well. I'll copy them to other regions.
achille-roussel commentedon Jun 19, 2016
We've copied the AMIs to all EC2 regions, they will be selected automatically by default if you change the region.
For the availability zones (and by extension the subnets) you should specify them manually, it's the best we can do for now. I tried to give a shot at having terraform dynamically select the right AZ and generate the subnets accordingly but it doesn't work, the subnet resources are generated dynamically via the
countproperty and terraform needs to know how many it has to create or the plan fails (no dynamically computed value can be given to thecountproperty unfortunately).If you know of a better way feel free to let me know and I'll give it a shot.
See these PR for reference:
backnight commentedon Jun 21, 2016
Thanks guys for the reactivity.
Just wanted to add a little information about @calvinfo first comment:
There is a mistyping, the AZ us-east1-c doesn't exist, there are : us-east-1d and us-east-1e BUT NO us-east1-c (for those who will copy past it).
Have a nice day!
calvinfo commentedon Jun 21, 2016
Whoops, my mistake. Thanks for the feedback @backnight, I'll close this for now :)
adambarthelson commentedon Oct 6, 2016
Is somebody updating the AMIs? Did a terraform apply earlier today no problems. Tried it again just now in
us-east-1to be greeted with:achille-roussel commentedon Oct 6, 2016
The AMIs were not changed to the best of my knowledge, however this AMI seems to be available for us-west-2, in us-east-1 the AMI id is ami-5f3ff932, not sure why the modules haven't selected the right AMI here :/
Was it working in a different region?
achille-roussel commentedon Oct 6, 2016
Also can you confirm you're using the up-to-date master branch?
adambarthelson commentedon Oct 10, 2016
I reverted to Terraform v0.6.16, as I believe one of my other issues stemmed from 0.7. I am now currently trying to do a
terraform getof the master branch, and am receiving the erroradambarthelson commentedon Oct 10, 2016
This is fixed by specifying
source = "github.com/segmentio/stack?ref=0.1"in the stack module:adambarthelson commentedon Oct 10, 2016
Terraform v0.6.16
Stack v0.1
Here's my current base stack setup for
us-east-1:It's currently failing due to it finding the correct AMI when trying to setup the bastion server.
I noticed the region is set incorrectly when running
terraform plan:It's also causing the incorrect AMI to be specified for ECS cluster and bastion servers.
yields commentedon Oct 11, 2016
@adambarthelson Just by looking at the stack config, i think you're missing the
region:If you're just getting started, i suggest you use the latest terraform, lots of fixes and new features!