# Can't associate the 100.64.0.0/10 range as a secondary range to VPC with terraform

**URL:** <https://discuss.hashicorp.com/t/cant-associate-the-100-64-0-0-10-range-as-a-secondary-range-to-vpc-with-terraform/24947>\
**Category:** AWS\
**Created:** [May 31, 2021, 1:26pm UTC](https://discuss.hashicorp.com/t/cant-associate-the-100-64-0-0-10-range-as-a-secondary-range-to-vpc-with-terraform/24947 "2021-05-31T13:26:40Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ecerulm](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/ecerulm/32/10829_2.png) [@ecerulm](https://discuss.hashicorp.com/u/ecerulm)\
**Post date:** [May 31, 2021, 1:26pm UTC](https://discuss.hashicorp.com/t/cant-associate-the-100-64-0-0-10-range-as-a-secondary-range-to-vpc-with-terraform/24947/1 "2021-05-31T13:26:40Z")

</div>

```
resource "aws_vpc_ipv4_cidr_block_association" "eks_vpc_secondary_cidr" {
  vpc_id = module.eks-vpc.vpc_id
  cidr_block = "100.64.0.0/10"
}

```

`Error: expected "cidr_block" to contain a network Value with between 16 and 28 significant bits, got: 10`

I’m using terraform “0.13.5” and aws provider “3.16.0”,

As far as I know “100.64.0.0/10” is a perfectly valid secondary CIDR for VPC and I have it configured it in the past (via the AWS console). It’s is used frequently when setting up EKS with CNI custom networking (where the pods are given IPs in the 100.64.0.0/10 range).

See [Amazon EKS now supports additional VPC CIDR blocks](https://aws.amazon.com/about-aws/whats-new/2018/10/amazon-eks-now-supports-additional-vpc-cidr-blocks/)

---

<div class="post-metadata">

**Author:** ![ecerulm](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/ecerulm/32/10829_2.png) [@ecerulm](https://discuss.hashicorp.com/u/ecerulm)\
**Post date:** [May 31, 2021, 1:32pm UTC](https://discuss.hashicorp.com/t/cant-associate-the-100-64-0-0-10-range-as-a-secondary-range-to-vpc-with-terraform/24947/2 "2021-05-31T13:32:16Z")

</div>

It’s the same with terraform 0.15.4 and aws provider 3.42.0 which are the lastest versions now (2021-05-31)

---

<div class="post-metadata">

**Author:** ![ecerulm](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/ecerulm/32/10829_2.png) [@ecerulm](https://discuss.hashicorp.com/u/ecerulm)\
**Post date:** [May 31, 2021, 1:49pm UTC](https://discuss.hashicorp.com/t/cant-associate-the-100-64-0-0-10-range-as-a-secondary-range-to-vpc-with-terraform/24947/3 "2021-05-31T13:49:41Z")

</div>

I filled a [GitHub issue 19595](https://github.com/hashicorp/terraform-provider-aws/issues/19595).