Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

overriding subnet ids with the modify command doesn't disassociate the current ones first #20

Open
Guslington opened this issue Mar 30, 2022 · 1 comment
Open

overriding subnet ids with the modify command doesn't disassociate the current ones first #20

Guslington opened this issue Mar 30, 2022 · 1 comment
Labels
bug Something isn't working cfn-vpn

Comments

@Guslington
Copy link
Contributor 

cfn-vpn modify name --subnet-ids subnet-123 subnet-456

produces error

Duplicate subnet detected in az ap-southeast-2a (Service: AmazonEC2; Status Code: 400; Error Code: InvalidClientVpnSubnetId.DuplicateAz; Request ID: ***; Proxy: null)
@Guslington Guslington changed the title overriding subnet ids with the modify command doesn't dissassciate the current ones first overriding subnet ids with the modify command doesn't disassociate the current ones first Mar 30, 2022
@Guslington
Copy link
Contributor Author

work around is to disassociate the current subnets first and then add the new

cfn-vpn modify name --subnet-ids subnet-abc subnet-def

then run

cfn-vpn modify name --subnet-ids subnet-123 subnet-456

@Guslington Guslington added bug Something isn't working cfn-vpn labels Mar 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working cfn-vpn
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Guslington