I haven’t figured out why some services have the prefix Amazon while others have AWS. For instance it is “Amazon VPC” and “AWS CloudFormation.” Was it a length issue in the AWS UI? Are the AWS prefix services special? Thoughts?
Welcome to the last post in my ElasticBox-supported AWS services! In this blog post, I’d like to introduce you to the wonderful world of Amazon VPCs and AWS CloudFormation!
Amazon VPCs is a logically isolated section of AWS so you can launch AWS resources in a network that you define, giving you full control. Users can define their own IP Address Range, create subnets, configure route tables and network gateways.
A lot of our customers use AWS and want to launch instances to their VPCs. That’s the use case we’re enabling currently. When you’re at the step of deployment, you can select existing VPCs for deployment.
AWS CloudFormation is one of our favorite AWS services. We’ve talked about it before on our blog as well and, very soon, you’ll hear some more exciting news (shh…)
There’s a few interesting uses of AWS CloudFormation in ElasticBox.
- For anything that is not explicitly supported above, the same effect can be achieved by launching a CloudFormation template in ElasticBox. Even if we don’t explicitly support the service, we’ll launch it for you. And you still get all the great benefits of ElasticBox.
- Furthermore, we make it easy to reuse or create a new CloudFormation template and manage the infrastructure deployment once it is launched.
- It gives our users great flexibility. If you’re an expert and want to fine-tune every configuration, have a party with CloudFormation. But then you can just share it with someone in ElasticBox and they don’t have to know how to use CloudFormation and still be able to take advantage of it. If you’re not an expert, you can use our deployment profile and all the other services I mentioned for simpler deployments.