Rules related to AWS provider and Terraform are available. These rules are enabled by default.
These rules relate to AWS provider.
These rules warn of possible errors that can occur at terraform apply. Rules marked with Deep are only used when enabling deep checking:
| Rule | Deep |
|---|---|
| aws_alb_invalid_security_group | ✔ |
| aws_alb_invalid_subnet | ✔ |
| aws_db_instance_invalid_db_subnet_group | ✔ |
| aws_db_instance_invalid_option_group | ✔ |
| aws_db_instance_invalid_parameter_group | ✔ |
| aws_db_instance_invalid_type | |
| aws_db_instance_invalid_vpc_security_group | ✔ |
| aws_elasticache_cluster_invalid_parameter_group | ✔ |
| aws_elasticache_cluster_invalid_security_group | ✔ |
| aws_elasticache_cluster_invalid_subnet_group | ✔ |
| aws_elasticache_cluster_invalid_type | |
| aws_elb_invalid_instance | ✔ |
| aws_elb_invalid_security_group | ✔ |
| aws_elb_invalid_subnet | ✔ |
| aws_instance_invalid_ami | ✔ |
| aws_instance_invalid_iam_profile | ✔ |
| aws_instance_invalid_key_name | ✔ |
| aws_instance_invalid_subnet | ✔ |
| aws_instance_invalid_vpc_security_group | ✔ |
| aws_launch_configuration_invalid_iam_profile | ✔ |
| aws_launch_configuration_invalid_image_id | ✔ |
| aws_route_invalid_egress_only_gateway | ✔ |
| aws_route_invalid_gateway | ✔ |
| aws_route_invalid_instance | ✔ |
| aws_route_invalid_nat_gateway | ✔ |
| aws_route_invalid_network_interface | ✔ |
| aws_route_invalid_route_table | ✔ |
| aws_route_invalid_vpc_peering_connection | ✔ |
| aws_route_not_specified_target | |
| aws_route_specified_multiple_targets |
700+ rules based on the aws-sdk validations are also available. See full list.
These rules suggest to better ways.
- aws_instance_previous_type
- aws_db_instance_previous_type
- aws_db_instance_default_parameter_group
- aws_elasticache_cluster_previous_type
- aws_elasticache_cluster_default_parameter_group
These rules relate to Terraform itself, not providers.
These rules suggest to better ways.