This has been a huge pain for us, and many other users I know.
There is currently no way to create a VPC connection programmatically. The only way is through the AWS console UI.
Almost everything else can be automated through CloudFormation, including theme changes, which seem so insignificant compared to a VPC connection given how much focus Amazon puts on security and VPC use.
To be clear, there is no CloudFormation nor direct API support for this feature.
Are there any known workarounds? Any ETAs for this to be added to either of the above? Even if it is just gets added to the API, at least we could use CustomResource in CF to create this automatically.
Please refer the blog addressing steps to create VPC,subnet and security group through AWS CLI and again we have API/SDK allowing same - CreateVpc - Amazon Elastic Compute Cloud
Please post your additional questions , if any on this topic.
You can see that QuickSight is creating a ENI and attaching it, you can describe the ENI after its creation but there is no way to create a ‘QuickSight VPC connection’ outside of the QuickSight admin console.
For context here are some other requests/threads regarding this.
Not being able to create a VPC Connection is so frustrating and is limiting our adoption of QuickSight across more accounts, because automatic provisioning is just not possible otherwise. CloudFormation will fail to create DataSources if VPC Connection does not exist. And it needs to be manually created first. But connection details are in the CloudFormation stack, so it’s a and problem.
AvailabilityStatus shows the current availability status of your entire VPC Connection. Now that a VPC Connection is in multiple Availability Zones, if all of the network interfaces are ready, the availability status is AVAILABLE and if none are available, it is UNAVAILABLE. The case for PARTIALLY_AVAILABLE is when one of the network interfaces is currently unavailable but the VPC Connection is still available to use as one or more of the other network interfaces are still available. Documentation on the states can be found here:
@skyram But my point was that this prop is required during the VPC creation call. I.e. you are asking me what the VPC connection status is, at creation time.
Here’s an illustrative example. It is using AWS CDK, which basically maps to CloudFormation 1:1.
When you finish creating a VPC connection, the new connection appears in the Manage VPC connections table. In some cases, the status of the new VPC might be UNAVAILABLE
So this implies that this status should only be known after the connection is created.
In conclusion, I think it is a mistake to ask for this value, ahead of time, at VPC connection creation time in the API.
and 
problem.
