Once your routing has been configured and you have established a connection between your internal corporate network and AWS VPC, you will still need to configure and update your security groups to allow the required access inbound from your corporate network.
For example, if you intended to remotely connect to instances running in VPC from your corporate network using protocols such as RDP or SSH, then you need to open up these protocols within the security groups associated with your instances.
Using this VPC connection is one option of securing connectivity between your corporate infrastructure and AWS, which uses the internet as the underlying backbone of your connection. Now, let's take a look at AWS Direct Connection, which uses private infrastructure instead.
