Lack of nat_gateways method for Aws::EC2::Vpc makes deletion cumbersome.

[colstrom]

When deleting a VPC, dependent resources must be removed first. nat_gateways is the only dependency not identifiable from an Aws::EC2::Vpc object.

I'm curious about the reasons for this.

• Is it simply a "not implemented yet" scenario?
• Have I overlooked an existing method somewhere?
• Is there a reason (documented or not) why this does not or should not exist?

Alternatively, is there a simpler approach to deleting a VPC?

[trevorrowe]

It has simply not been implemented yet. I'm going to mark this as a feature request so we can add it to our backlog.

[awood45]

Added to feature request backlog.

[mullermp]

Hey @colstrom - I dug out this feature request and added a NAT gateway resource model. Per my testing, I was able to successfully delete a NAT gateway. The changes were pushed to an internal package. When I get the opportunity, I will be sure to push this change out for all of the SDKs.

Aws> r.nat_gateways.first.delete
[Aws::EC2::Client 200 0.136147 0 retries] describe_nat_gateways()  
[Aws::EC2::Client 200 0.048603 0 retries] delete_nat_gateway(nat_gateway_id:"nat-0050e741ba6dbc9c7")  
=> #<struct Aws::EC2::Types::DeleteNatGatewayResult nat_gateway_id="nat-0050e741ba6dbc9c7">