Cloudify: No default VPC for this user

Question

I'm going trough Cloudify documentation and trying to deploy it in our AWS

I did checkout latest code of Cloudify Manager Blueprint from GitHub

Updated inputs.yaml file and when i run it with command:

cfy bootstrap -p aws-ec2-manager-blueprint.yaml -i inputs.yaml --task-retries 10

It passing all validation steps, generating keys, security groups and then throw me a lot of errors of:

NonRecoverableError: EC2ResponseError: 400 Bad Request
<?xml version="1.0" encoding="UTF-8"?>
<Response>
    <Errors>
        <Error>
            <Code>VPCIdNotSpecified</Code>
            <Message>No default VPC for this user</Message>
        </Error>
    </Errors>
    <RequestID>some-blah-blah-blah</RequestID>
</Response>

Could anyone please suggest where, in which config under which tag should I specify VPS I want to use? Nor I didnt find anything in AWS AMI how to set default VPC per specific user - as I did created Cloudify-bot service account with access key

What am I doing wrong?

Answer 1

As Google brought me here as the top answer in May 2019 I'm confirming what David Resnick points to above. Creating a default VPC

Answer 2

Regarding Default VPC and Subnets:
If you deleted your default VPC and created your own custom VPC with SubNets you cant make it Default. Here is a Quote from official AWS documentation:

You cannot mark an existing VPC as a default VPC. If you delete a default subnet and then need to restore it, create a new subnet in your default VPC, and then contact AWS Support to mark the subnet as a default subnet.

Regarding Cloudify and custom VPC handling:
It seems that custom VPC handling is available trough "AWS VPC Plugin" which belong only to Pro version - pay version, not Open Source. What is more it is marked to be included only in Cloudify v3.3 - current one is v3.2 - so it seems not ready yet

Answer 3

It seems functionality has changed. In December 2017, I ran into "No Default VPC for user" when creating EC2 machine with packer. I was able to create a new VPC from the AWS console, under VPC's. There was a button "Create Default VPC". I pressed it, and viola - I could create machines again.