Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

report error when we cannot delete a network interface #2830

Closed
brianbegy opened this issue Nov 30, 2016 · 6 comments · Fixed by #2983
Closed

report error when we cannot delete a network interface #2830

brianbegy opened this issue Nov 30, 2016 · 6 comments · Fixed by #2983
Milestone

Comments

@brianbegy
Copy link

So I found out about this from our AWS account manager when I exceeded quota.

Running serverless deploy with the VPC, SecurityGroupIds, and SubnetIds defined seems to create a new network interface on each deploy, but doesn't clean up old, unused network interfaces.

This is happening in 1.1.0.

Is this a known issue?

@pmuens pmuens added the bug label Nov 30, 2016
@laardee
Copy link
Member

laardee commented Nov 30, 2016

Hi @brianbegygr, does your execution role have ec2:DetachNetworkInterface and ec2:DeleteNetworkInterface permissions?

@brianbegy
Copy link
Author

Good catch, it did not. Once it has permissions, it seems to clean up after itself.

However, I would have expected it to report an error when it couldn't do so.

Is it appropriate to put a feature request in for "report error when we cannot delete a network interface?"

@mthenw mthenw changed the title Serverless deploy appears to not clean up network interfaces report error when we cannot delete a network interface Dec 1, 2016
@nicka
Copy link
Member

nicka commented Dec 20, 2016

@braahyan PR #2983 will add the correct IAM VPC permissions by default 👍

@braahyan
Copy link

@nicka I think you mean @brianbegygr, but this is great!

@nicka
Copy link
Member

nicka commented Dec 21, 2016

@braahyan Sorry 😊

@brianbegy
Copy link
Author

It's ok. I'm happy about it too! :)

@pmuens pmuens added this to the 1.8 milestone Feb 8, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
6 participants