All time show 0 resources

[jpradoar]

Hey rdkis, tnx for share this awesome work. I'm testing your tool and I have problems to run it correctly.
I'm running "run.sh" to test it, but all time I recibe all data on 0, but I have one VPC, one subnet and One ec2 running

Only I modifyed AWS_SESSION_TOKEN variable, to get session token in the moment of deploy

I don't understand whats is wrong in my test
Tnx!

run.sh (modifyed)

#!/usr/bin/env bash
NEO4J_AUTH='neo4j/admin'

if [ -z "$AWS_SECRET_ACCESS_KEY" ] ; then
	# Get from files
	AWS_SECRET_ACCESS_KEY=`grep aws_secret_access_key ~/.aws/credentials | head -n1 | cut -d'=' -f 2 | sed 's/ //g'`
    AWS_ACCESS_KEY_ID=`grep aws_access_key_id ~/.aws/credentials | head -n1 | cut -d'=' -f 2 | sed 's/ //g'`
    AWS_SESSION_TOKEN=`aws sts get-session-token|grep SessionToken| head -n1 | cut -d':' -f 2 | sed 's/ //g;s/,//g'`  # <----- THIS LINE WAS MODIFIED
    AWS_SECURITY_TOKEN=`grep aws_security_token ~/.aws/credentials | head -n1 | cut -d'=' -f 2 | sed 's/ //g'`   # <----- THIS LINE I DONT USE
    AWS_REGION=`grep region ~/.aws/config | head -n1 | cut -d'=' -f 2 | sed 's/ //g'`
fi
docker rm -f neo4j_awless
docker pull rdkls/aws_infra_map_neo4j
echo "docker run -ti \
    --name neo4j_awless \
    --env AWS_SECRET_ACCESS_KEY=$AWS_SECRET_ACCESS_KEY \
    --env AWS_ACCESS_KEY_ID=$AWS_ACCESS_KEY_ID \
    --env AWS_SESSION_TOKEN=$AWS_SESSION_TOKEN \
    --env AWS_TO_NEO4J_LIMIT_REGION=$AWS_REGION  \
    --env NEO4J_AUTH=$NEO4J_AUTH \
    -p 7474:7474 \
    -p 7687:7687 \
    rdkls/aws_infra_map_neo4j"

Output

Now running: `awless sync`
[info]    running sync for region 'us-east-1'
[info]    -> storage: 0 s3object, 0 bucket
[info]    -> lambda: 0 function
[info]    -> cdn: 0 distribution
[info]    -> dns: 0 record, 0 zone
[info]    -> messaging: 0 topic, 0 subscription, 0 queue
[info]    -> access: 0 group, 0 instanceprofile, 0 role, 0 policy, 0 accesskey, 0 user, 0 mfadevice
[info]    -> infra: 0 containercluster, 0 availabilityzone, 0 importimagetask, 0 elasticip, 0 repository, 0 volume, 0 natgateway, 0 dbsubnetgroup, 0 scalingpolicy, 0 subnet, 0 listener, 0 keypair, 0 snapshot, 0 scalinggroup, 0 containertask, 0 vpc, 0 image, 0 database, 0 container, 0 classicloadbalancer, 0 loadbalancer, 0 certificate, 0 instance, 0 securitygroup, 0 routetable, 0 networkinterface, 0 internetgateway, 0 launchconfiguration, 0 containerinstance, 0 targetgroup
[info]    -> cloudformation: 0 stack