Inline way differences when define AWS Routes

Hi, i’m trying to setup route dynamically in aws_route_table resource definition, well, writing it the classic way:

 resource "aws_route_table" "tm_private_route_table" {
  vpc_id = "vpc-1111111111"
  route {
    cidr_block = "0.0.0.0/0"
    nat_gateway_id = "nat-1111111111"
  }

it works perfect, but, if i’m try to write as a list of multiple blocks as documented in https://www.terraform.io/docs/configuration/attr-as-blocks.html#defining-a-fixed-object-collection-value :

resource "aws_route_table" "tm_private_route_table" {
  vpc_id = "vpc-1111111111"
  route = [
    {
      cidr_block = "0.0.0.0/0"
      nat_gateway_id = "nat-1111111111"
    }
  ]

It throws an error:

Inappropriate value for attribute "route": element 0: attributes "egress_only_gateway_id", "gateway_id", "instance_id", "ipv6_cidr_block", "network_interface_id", "transit_gateway_id", and "vpc_peering_connection_id" are required.

Any idea ?