$ terraform validate
79╷
80│ Error: Provider configuration not present
81│
82│ To work with aws_vpc_peering_connection_accepter.accepter its original
83│ provider configuration at
84│ provider["registry.terraform.io/hashicorp/aws"].accepter is required, but
85│ it has been removed. This occurs when a provider configuration is removed
86│ while objects created by that provider still exist in the state. Re-add the
87│ provider configuration to destroy
88│ aws_vpc_peering_connection_accepter.accepter, after which you can remove
89│ the provider configuration again.
90╵
91╷
92│ Error: Provider configuration not present
93│
94│ To work with aws_route.accepter its original provider configuration at
95│ provider["registry.terraform.io/hashicorp/aws"].accepter is required, but
96│ it has been removed. This occurs when a provider configuration is removed
97│ while objects created by that provider still exist in the state. Re-add the
98│ provider configuration to destroy aws_route.accepter, after which you can
99│ remove the provider configuration again.
100╵
You previously created resources using a hashicorp/aws provider with alias accepter.
You have removed the provider configuration with that alias, despite still having resources in the Terraform state, as well as still referencing it in your code:
Since you’re still using it, you need to add it back.
aws_vpc_peering_connection.owner: Creating…
79╷
80│ Error: Error creating VPC Peering Connection: InvalidVpcID.NotFound: The vpc ID ‘vpc-xyz’ does not exist
81│ status code: 400, request id: blabla
82│
83│ with aws_vpc_peering_connection.owner,
84│ on main.tf line 21, in resource “aws_vpc_peering_connection” “owner”:
85│ 21: resource “aws_vpc_peering_connection” “owner” {
79aws_vpc_peering_connection.owner: Still creating… [10s elapsed]
80aws_vpc_peering_connection.owner: Still creating… [20s elapsed]
81aws_vpc_peering_connection.owner: Still creating… [30s elapsed]
82aws_vpc_peering_connection.owner: Still creating… [40s elapsed]
83aws_vpc_peering_connection.owner: Still creating… [50s elapsed]
84aws_vpc_peering_connection.owner: Still creating… [1m0s elapsed]
85╷
86│ Error: Error waiting for VPC Peering Connection to become available: Error waiting for VPC Peering Connection (pcx-xyz) to become available: timeout while waiting for state to become ‘pending-acceptance, active’ (last state: ‘initiating-request’, timeout: 1m0s)