AWS configured properly

[mickymkumar]

I am getting the following error - I have my AWS configured properly

ubuntu@ip-172-31-45-146:~/magma/experimental/cloudstrapper/playbooks$ ansible-playbook aws-prerequisites.yaml -e 'awsTargetRegion=ca-central-1' -e "dirInventory=${VAR_DIR}" --tags keyCreate
[WARNING]: provided hosts list is empty, only localhost is available. Note that the implicit localhost does not match 'all'

PLAY [localhost] ****************************************************************************************************************

TASK [Gathering Facts] **********************************************************************************************************
fatal: [localhost]: FAILED! => {"msg": "The field 'environment' has an invalid value, which includes an undefined variable. The error was: 'awsAccessKey' is undefined"}

PLAY RECAP **********************************************************************************************************************
localhost : ok=0 changed=0 unreachable=0 failed=1 skipped=0 rescued=0 ignored=0

[arunuke]

@Micky-Kumar To deploy any resource on AWS via APIs, you would need an AWS Access Key and a Secret Key, both of which you can generate for an IAM user. The Cloudstrapper uses these keys to authenticate itself and then deploys the resources as desired. On top of the README file, the prerequisites section talks about artifacts that are required before starting the installation.

In this specific case the secrets.yaml file, which holds authentication information for AWS, Docker and Github is missing or it is incorrect.

[tashingamusiya]

[tashingamusiya]

[mickymkumar]

was this resolved I have been having the exact problem for sometime.

Yes see above comments

[tashingamusiya]

thanks for the reply much appreciated, so maybe it's a different problem I am having because you will see in the screenshot above I show that the secrets file is present but somehow it keeps mising it even after putting eaxct path something not right either syntax would you have the correct command ?

[tashingamusiya]

@arunuke @micky-kumar

[arunuke]

Hello @tashingamusiya

Did you get a chance to look at the documentation available from Magma Docs that describes this process? From what I see, it appears you are setting secrets.yaml in the repo instead of your configuration environment. From the documentation I cited above,

_Copy the secrets.yaml file and update the credentials for AWS:

cp roles/vars/secrets.yaml ~/magma-dev/_