Closed ahl closed 6 years ago
+1 - this is breaking my deployment process that uses vpcs. Please merge.
I think this project is dead; we have a fork here with some useful fixes:
https://github.com/transposit/gordon
But we're in the process of migrating off of Gordon.
Really? What do you use instead?
We're just using Terraform. While Gordon is super convenient for stand-alone entities, we found it awkward to have parts of our deployment managed by Gordon and other parts managed by Terraform. In particular have dependencies from Gordon to the Terraform-managed VPC config (apropos of this issue...).
note that this is fixed by https://github.com/jorgebastida/gordon/pull/141/files
My colleague got the following note from AWS support today:
It goes on to explain that while the Lambda's roles has
ec2:CreateNetworkInterface
it lacksec2:DeleteNetworkInterface
andec2:DescribeNetworkInterfaces
which are necessary for proper maintenance.AWS has a new(?) policy for running Lambdas within a VPC: AWSLambdaENIManagementAccess
Gordon should include those privileges in its default profile. We've accepted the PR in our fork: https://github.com/transposit/gordon/pull/2