AWS CloudFormation evaluation using the prooV platform
The smart and secure PoC platform, prooV empowers you to run multiple proof-of-concepts, adjust and fine tune as needed and when ready, deploy directly to your AWS Service Catalog.
Get Started!
Whether you want to benchmark different configuration setups of AWS services or evaluate a new integrated solution into any of your existing environments, now you have an easy way to deploy any of your CloudFormations into a prooV PoC environment. Simply share the CloudFormation with the prooV account number provided to you during the registration process.
Fast track the evaluation of eco-system configuration and set-up, or the adoption of new technologies by running decision-aiding PoCs with prooV.
1. Click to sign up with your email and company details.
2. Receive a welcome email that includes your prooV account credentials and instructions with links to further resources.
3. Log in to prooV and start your PoC!
$95/hour as long there are active PoC components in your account.
Data Deep Mirroring if selected, costs an additional $100/hour.
Additional costs may incur for deployed AWS environments and services.
The initial version of this service supports the following AWS resources: VPC, Subnets, Security Groups, EC2 instances (Windows and Linux), RDS, S3 bucket, DynamoDB, EMR, Simple Queue Service (SQS), Simple Notification Service (SNS), Lambda.
While sharing portfolio, please be aware of not sharing resources with specific restrictions such as security groups on specific IPs available only for your organization, etc.
Once the Cloud Formation is deployed in the prooV environment, the following resources will not be visible for the user to manage: VPC, Subnets, Security Groups. The rest will be visible and accessible to manage directly from within the prooV environment and all metrics will be automatically tracked and captured. Your organization may directly consume the created resource. Vendors will receive access to the above mentioned resources via prooV’s Smart Integration Engine.
If the template contains a new EC2 instance with Windows OS with a IamInstanceProfile property attached, the IamInstanceProfile MUST contain the AmazonSSMManagedInstanceCore managed policy.
Export to Service Catalog Limitations: At any stage of running the PoC your organization may export the PoC environment that consists of resources created via a shared Service Catalog portfolio as well prooV-owned resources, into your Service Catalog. Upon export, your organization may launch the exported environment via the Service Catalog product interface. Until then, please create appropriate IAM roles in your account and advise the prooV Support Team accordingly.
To explore a full feature set on the prooV Platform, the CloudFormation template must accept configuration parameters VPC ID and SecurityGroup ID. They should be described as CloudFormation template parameters as in the example below. Note, VPC ID may be omitted completely so a resource belongs to the default VPC - this is a valid configuration as well. In addition, when network access is needed, please assign ElasticIP to your resources.
=== Example ===
{
"AWSTemplateFormatVersion": "2010-09-09",
"Description": "Sample template",
"Parameters": {
"sgId": {
"Type": "String"
},
...
},
"Resources": {
"LinuxEC2Instance": {
"Type": "AWS::EC2::Instance",
"Properties": {
"Tags": [ ... ],
"ImageId": "......",
"InstanceType": "t2.micro",
"KeyName": { ... },
"SecurityGroupIds": [ { "Ref": "sgId" } ],
"BlockDeviceMappings": [...]
}
},
"ElasticIP": {
"Type": "AWS::EC2::EIP",
"Properties": {
"InstanceId": { "Ref": "LinuxEC2Instance" }
}
}
},
"Outputs": {
"EC2": {
"Value": { "Ref": "LinuxEC2Instance" }
},
"EIP": {
"Value": { "Ref": "ElasticIP" }
}
}
}