terraform - terrafrom aws_instance subnet_id - Error launching source instance: Unsupported: The requested configuration is currently not supported -


i trying build vpc , subnet within vpc. thirdly trying create aws instances within subnet. sounds simple, subnet_id parameter seems break terraform 'apply' (plan works fine). missing something?

extract main.tf 

resource "aws_vpc" "poc-vpc" {   cidr_block       = "10.0.0.0/16"   instance_tenancy = "dedicated"   enable_dns_hostnames = "true" }  resource "aws_subnet" "poc-subnet" {   vpc_id     = "${aws_vpc.poc-vpc.id}"   cidr_block = "10.0.1.0/24"   map_public_ip_on_launch = "true"   availability_zone = "${var.availability_zone}" }   resource "aws_instance" "poc-instance" {   ami = "${lookup(var.amis, var.region)}"   instance_type = "${var.instance_type}"   availability_zone = "${var.availability_zone}"   associate_public_ip_address = true   key_name = "pipeline-poc-key-pair"   vpc_security_group_ids = ["${aws_security_group.poc-sec-group.id}"]   subnet_id = "${aws_subnet.poc-subnet.id}" }

if remove subnet_id 'apply' works, instance created in default vpc. not aim.

any appreciated. newbie terraform please gentle.

i worked out , wanted post saves others time.

the issue conflict of subnet_id in aws_instance provisioner , instance_tennancy in aws_vpc provisioner. remove instance tenancy , fixed (or set default)

the error message meaningless. i've asked whether can improved.


Comments

Post a Comment

Popular posts from this blog

javascript - Create a stacked percentage column -

i have collection of data : var data = [ {"p301a":"10","p301b":"7","p301c":"7","p301d":"3","p301e":"8","p301f":"8","p301g":"8","p301h":"8","p301i":"8","p301j":"8","p301k":"8","p301l":"8","p301m":"8","p301n":"8","p301o":"8","age":"31-40 years","profesion":"2","position":"2"}, {"p301a":"5","p301b":"4","p301c":"4","p301d":"4","p301e":"4","p301f":"4","p301g":"4","p301h":"4","p301i":"4","p301j":"4","p301k":"4...
Read more

Optimising Firebase database by automatically overwriting data -

in firebase app have following structure: posts latest all users can write posts > latest . want limit entries 20 posts save space in database. , posts beyond 20 unnecessary never shown on homepage. how can limit posts 20, when user writes posts > latest posts @ end drop off (be deleted) automatically? this sample should you. you need : const max_log_count = 20; exports.removeold = functions.database.ref('/posts/latest/{postid}').oncreate(event => { const parentref = event.data.ref.parent; return parentref.once('value').then(snapshot => { if (snapshot.numchildren() >= max_log_count) { let childcount = 0; const updates = {}; snapshot.foreach(function(child) { if (++childcount <= snapshot.numchildren() - max_log_count) { updates[child.key] = null; } }); // update parent. removes children. ...
Read more

javascript - Angular UI-Grid customTemplate directive causing rows to load slowly/? -

Image
each grid cell can have more 1 customtemplate loaded. have directive holds watcher on model_col_field listen cell updates on scroll when dom rows updated , recompile celltemplate . without watcher , $compile rows repeat on scroll, showing same set of rows. is there more angular way of approaching or way improve performance? relevant controller code: create gridoptions.data & gridoptions.columndefs : var customtemp = '<div ng-repeat="opt in grid.appscope.colvalueoptionsmodel" ng-init="tempstring=model_col_field.clazz+opt.key;"><comparison-directive dbo="model_col_field" attobj="opt" fff="grid.appscope.getattributetemplate(tempstring)" /></div>'; $scope.gridoptions.columndefs = [ { name:'yindex',pinnedleft:true,celltemplate: customtemp, displayname:'index'}, { name:'col1',celltemplate: customtemp}, { name:'col2',celltemplate: c...
Read more