search

davidski / vulnpryer-aws-orchestration

🎯☁️Automated deployment of a VulnPryer pipline on AWS
http://vulnpryer.net
2 stars 2 forks source link

Stack creation assumes VPC in us-east-1 #6

Closed davidski closed 9 years ago

davidski commented 9 years ago

The stack creation fails as it passes the opsworks_region to the configuration parameter. OpsWorks has endpoints only in us-east-1, but our deployment VPC lives in us-west-2. I have a hack to allow this to work. Raising this here in case there are other region related issued uncovered in testing.

davidski commented 9 years ago

Commit 49b4ef8 fixes this issue.

abbyyacat commented 9 years ago

The OpsWorks stack region should be the same as the VPC region. We have separated region for stack and VPC for more flexibility to accommodate future enhancements if available. Your commit also achieves the desired outcome. Please feel free to close this once satisfied. Thank you.

davidski commented 9 years ago

The pipeline definition for the control instance also assumes that the VPC is in us-east-1. c828ac2e506b86cd420448fb37e6cc768ffd0f1c corrects this problem.

davidski commented 9 years ago

Also had to update deploy script to substitute this new variable in the pipeline. Reference commit: 46dcb40a697f63c6d45dd28bedc2ea58f44eb1f9

Keeping this issue open for any further region issues.