Not sure if this is relevant. But my question is if we delete the default VPC and add a new VPC and launched our infra components in that new VPC, are we supposed to expect problems? there is a link which specifies this, would love to have your view: https://aws.amazon.com/premiumsupport/knowledge-center/deleted-default-vpc/
Does default VPC play a role in routing to our VPC’s (I think it should not given my understanding of shared infra model but came across this situation recently in my work.)
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.
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".