Amazon Virtual Private Cloud (VPC) vs. AWS CloudFormation

If you are going to deploy within AWS, you need to know how to leverage VPCs. VPCs have several items you must configure for them to be usable and to even link one VPC to another. If you are only going to deploy a few resources or use some of the default configurations, you still need to have working knowledge of how a VPC functions. If you are used to working with VLANs and the ideology behind those, that is the best direct reference to how a VPC can be described, but with additional layers on top of that with route tables, internet gateways, etc.

Incentivized

AWS CloudFormation is well suited for scenarios where all of your resources need to be provisioned on AWS but it is not suited for hybrid cloud deployments. It's very easy for someone new to learn. The level of customization offered as part of the template specifically for AWS services is great. There is also a UI tool where we can drag and drop the services we want and it generates an yaml file which is very easy to use. The visibility of stacks and its resources and one place where we can track and identify the issues in deployment is great.

Incentivized

• Pricing model & On demand service commitment.
• Well, architectural infrastructure development processing before spending the money.
• AWS VPC are providing hassle-free using with all others services from AWS very easily.
• AWS business support is very helpful & [gives] the right direction according to client’s situations.

Incentivized

• SaaS
• Paas
• Iaas
• On promises

Incentivized

• The biggest issue with VPC networks is knowing how you can leverage VPC endpoints to ensure your resources within the VPC are not reaching out over the Internet to get to AWS services such as S3 and others.

Incentivized

• Error Description upon Failure Needs to be Improved.
• Slow to create, delete or update.
• Need to delete resources manually. It can ask before starting deletion whether to skip those resources or delete them.

Incentivized

Incentivized

We didn't look into anything else as Cloudformation was "built-in" for AWS, it just kind of made sense to go with that. Terraform was something that we briefly looked into Terraform but decides to stick with Cloudformation because our task was relatively "simple". Apparently if it's a bit more complex, Terraform might be the way to go.

Incentivized

• AWS VPCs are actively used for following various compliance and regulatory needs such as network separation for PCI DSS. The ability to keep resources and access to those resources controlled through the initial steps of creating VPCs has helped tremendously.

Incentivized

• It has a positive ROI
• Less time inverted in bugs
• More stable source code

Incentivized