You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have been following the deployment instructions in diego-release/examples/aws to deploy CF + Diego on AWS in eu-central-1.
When executing ./deploy_aws_environment create-stack deploy-bosh "$BOSH_DEPLOYMENT_DIR" "$DEPLOYMENT_DIR" "$STACK_NAME", the script calls boosh generate resulting in the following error:
Obviously the NAT AMI is not currently part of the NAT_AMIs known to boosh.
I have tried to add a NAT AMI to boosh, but to no avail. The deploy_aws_environment definitely uses my customized boosh, but still reports the NAT image as missing like above. Am I missing something?
The text was updated successfully, but these errors were encountered:
I have been following the deployment instructions in diego-release/examples/aws to deploy CF + Diego on AWS in
eu-central-1
.When executing
./deploy_aws_environment create-stack deploy-bosh "$BOSH_DEPLOYMENT_DIR" "$DEPLOYMENT_DIR" "$STACK_NAME"
, the script callsboosh generate
resulting in the following error:Obviously the NAT AMI is not currently part of the NAT_AMIs known to boosh.
I have tried to add a NAT AMI to boosh, but to no avail. The
deploy_aws_environment
definitely uses my customized boosh, but still reports the NAT image as missing like above. Am I missing something?The text was updated successfully, but these errors were encountered: