VPC Connection automation

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.

Hi @m0ltar -

I don’t believe there’s any workaround for this. It’s great you are highlighting the need here.

To help clarify some possible confusion regarding your question.

QuickSight VPC Configuration
You are talking about the ability to configure a QuickSight VPC connection programmatically (API/SDK/CDK).

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.

AWS VPC Creation
As @Neeraj pointed out this can be done various ways, for example using CDK

Thanks @robdhondt.

You are talking about the ability to configure a QuickSight VPC connection programmatically (API/SDK/CDK).

Yes, that. :white_check_mark:

I’m also a participant of those threads on GitHub :smile:

Is there some technical limitation to having this be part of CloudFormation? Or was it just not prioritized?


I’ll communicate this feature request to the relevant team. Thanks

1 Like

Noted the feature request. Thanks for raising this. I’ll add this our list for prioritization.

Can I get a bu bu bump! :slight_smile:

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 :chicken: and :egg: problem.