ngo-fabric-client-node always shows the ROLLBACK_COMPLETE status in ColudFormation section

[rageshzerone]

Hi all,

I am a newbie in the AWS Blockchain development. I have a corporate AWS account on behalf of my employer, and I am trying to create this non-profit-blockchain environment in our AWS portal. I already set up the AWS Cloud9 IDE, and successfully execute the first step ( Step 1 - Create the Hyperledger Fabric blockchain network ) and the second step ( Step 2 - Check the network is AVAILABLE ).

But after the Step 3 execution, it shows output in the console like the below.

rageshxxxxxxxxxxxxxx:~/non-profit-blockchain/ngo-fabric (master) $ ./vpc-client-node.sh
Creating VPC - TODO. Create the VPC, subnets, security group, EC2 client node, VPC endpoint
Create a keypair
Searching for existing keypair named ngo-keypair

An error occurred (InvalidKeyPair.NotFound) when calling the DescribeKeyPairs operation: The key pair 'ngo-keypair' does not exist
Creating a keypair named ngo-keypair. The .pem file will be in your /home/ec2-user directory
Create the VPC, the Fabric client node and the VPC endpoints

Waiting for changeset to be created..
Waiting for stack create/update to complete

Failed to create/update the stack. Run the following command
to fetch the list of events leading up to the failure
aws cloudformation describe-stack-events --stack-name ngo-fabric-client-node
rageshxxxxxxxxxxxxxx:~/non-profit-blockchain/ngo-fabric (master) $ aws cloudformation describe-stack-events --stack-name ngo-fabric-client-node

An error occurred (ValidationError) when calling the DescribeStackEvents operation: Stack [ngo-fabric-client-node] does not exist

Created items are reflected in the CloudFormation section please refer to the below image.

In this image you can see there is a status shown in the ngo-fabric-client-node item. I already tried to recreate the fabric-node-client again but the output messages are the same in both times.

Any help is much appreciated.

[rageshzerone]

Is this a dead project repository?

[jpramirez]

it seems that the AMI needs to be changed on the cloud formation tempalate for this to work correctly, specially at this step.
But, that being said, the ami exposed in the template only works for us-east-1.
Issue is that in the readme says you can "copy" the ami to the region you want and change to the appropriate ami-id, but that image cannot be copied or at least my root account does not have permissions over the ebs storage of that public ami.

how we can copy this ami ?

[jpramirez]

I can confirm that this example works on us-east-1, so the question will be, can we get permission or the requirements for the ami- that is failing or we cannot copy ?
'ami-0434d5878c6ad6d4c'

[leonardoacosta91]

I have the same problem, have you been able to solve it?