2 Answers
VPCs are isolated from one another (unless you setup a peering connection). I have heard to not delete your default VPC, but have never heard a good justification for it. But to answer your question, the default VPC will not affect anything in a VPC you provisioned yourself.
Hi Chaitanya,
I’ve worked with some companies who, as a matter of policy, removed all default settings for either cleanliness or security…just like you might remove the ec2-user account from an Amazon Linux AMI and create your own service accounts if you need them.
I personally don’t like all the default stuff and I’ll clean it out of a new account because I only want stuff my team explicitly creates in the account. Just personal preference I guess.
Your services and accounts will work just fine without the default stuff there. You might get some errors if you try to launch some other sample stuff, but for production accounts, those are not for "trying out stuff".
–Scott
Thanks Scott, Appreciate your quick response 🙂
Exactly, I had the same understanding and almost went to depression after hearing that from a colleague that "even if you launch your resources into your own VPC, Default VPC is still relevant..", I seriously wanted him to be wrong. But I asked this question because don’t want to leave myself in a doubt over this.
The reason to not delete default VPC was because it was difficult to get it back. You needed to submit a ticket to AWS for them to restore it. That is no longer the case as you can recreate it on your own. Personally, I delete every default VPC and only use custom ones.