Difference between revisions of "Error: no matching EC2 Subnet found"
Jump to navigation
Jump to search
| (4 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
Error: no matching [[EC2 Subnet]] found | Error: no matching [[EC2 Subnet]] found | ||
| + | with module.xxxxS.module.cni.data.aws_subnet.vpc_cni_subnet["subnet-12345"], | ||
| + | on .terraform/modules/xx/modules/cni/main.tf line 1, in data "aws_subnet" "vpc_cni_subnet":1: data "aws_subnet" "vpc_cni_subnet" | ||
| + | |||
| + | == Related == | ||
| + | * <code>[[terraform plan]]</code> | ||
| + | * [[AWS subnets]] | ||
== See also == | == See also == | ||
* {{EC2}} | * {{EC2}} | ||
| − | [[Category: | + | [[Category:AWS]] |
Latest revision as of 17:08, 21 February 2024
Error: no matching EC2 Subnet found
with module.xxxxS.module.cni.data.aws_subnet.vpc_cni_subnet["subnet-12345"], on .terraform/modules/xx/modules/cni/main.tf line 1, in data "aws_subnet" "vpc_cni_subnet":1: data "aws_subnet" "vpc_cni_subnet"
Related[edit]
See also[edit]
- AWS EC2, Amazon EC2 API,
aws ec2, AWS::EC2, Amazon EC2 Spot Instances, CPU credits, Instance type, EC2 limitations, 169.254.169.254, Instance metadata and user data (IMDS),InstanceType, InstanceId, Amazon EC2 Auto Scaling, AWS EC2 Instance Connect, launch template, lifecycle, AWS Security group (SG), Amazon EC2 Recycle Bin, Amazon EC2 Mac Instances, Global View
Advertising:
