search

webdigi / AWS-VPN-Server-Setup

Setup your own private, secure, free* VPN on the Amazon AWS Cloud in 10 minutes. CloudFormation
Other
760 stars 163 forks source link

Error in create VPNSecurityGroup #3

Closed diogopms closed 7 years ago

diogopms commented 9 years ago

Hi, When i am trying to use your template, cloudformation tries to create a security group gives me this error.

10:59:54 UTC+0100   ROLLBACK_IN_PROGRESS    AWS::CloudFormation::Stack  MyVPN   The following resource(s) failed to create: [VPNSecurityGroup]. . Rollback requested by user.

Do you know if this template support the logic of VPC, associated with the security groups?

Is good to add in the documentation how can we add more that one user :)

I can do a pull request if you what after i resolve this problem.

Thanks

webdigi commented 7 years ago

Did you manage to sort this? Pull requests are welcome

ShiplakeCS commented 7 years ago

I too have had this same issue when attempting to roll out the template today. Any ideas on how to overcome it? Sorry, I'm new to AWS so am not sure about setting up security groups, etc.

See screenshot of event history below.

screen shot 2017-06-01 at 14 24 09
webdigi commented 7 years ago

Thanks for the screenshot. Please see https://forums.aws.amazon.com/thread.jspa?threadID=97448 "In order to subscribe to AWS services you must have a valid credit card listed on the account. This is true even if you've received promotional credits for usage."

Please check and report back.

@diogopms did you have a valid credit card too?

ShiplakeCS commented 7 years ago

@webdigi I did/do have a valid credit card on the account, however I think the issue was down to my creating a new AWS account only very shortly before attempting to create the VPN stack. I have since tried again (waiting 24 hours) and it worked. So, I can only assume it takes a certain amount of time for all services to become active for new accounts.

webdigi commented 7 years ago

@ShiplakeCS - Thanks for getting back. A few users have mentioned this previously and we were never able to understand the cause. We will also have the blog and github readme updated with this notice.