Add ansible role for AWS #6
Conversation
Signed-off-by: Avery Blanchard <[email protected]>
avery-blanchard
force-pushed
the
aws-ansible
branch
from
3d75b71 to
ed1ad30
Compare
Signed-off-by: Avery Blanchard <[email protected]>
avery-blanchard
force-pushed
the
aws-ansible
branch
from
ed1ad30 to
ad3a595
Compare
keylime-ansible-aws/README.md
Outdated
| 3. Select your user | ||
| 4. Select 'Security credentials' | ||
| 5. Click 'Create access key' | ||
| 6. Record your Access key ID and secret key for authenticating the playbook |
There was a problem hiding this comment.
I would add something like "Your access key ID is displayed in the table in the AWS console. Your secret key is the key itself." I think the first 3 times I read this, I thought they were two different keys.
There was a problem hiding this comment.
The secret key is also displayed in the console (only when first created), and is not the .csv file downloaded. I will add more clarity on the keys!
keylime-ansible-aws/README.md
Outdated
| 5. Run script to configure environment for ansible. | ||
| ``` | ||
| ./set_env_var.sh --help | ||
| "Usage: ./set_env_var.sh <AWS access key ID> <AWS secret key> <AWS region>" |
There was a problem hiding this comment.
Is the AWS secret key supposed to be a file path to your key? Or what format does it expect here?
There was a problem hiding this comment.
If you can think of a better way to handle this, let me know. The two keys required to authenticate ansible are just displayed in the console when the access key is created. The .csv contains another value that does not match either the value for the secret key nor the access key ID. Currently, the secret key and access key ID are to be copied by the user when it is created then passed into the script.
There was a problem hiding this comment.
This makes more sense now
Signed-off-by: Avery Blanchard <[email protected]>
|
@mpeters What do you think, can we merge? |
Add ansible role for AWS. This role is not ready for use. The ansible AWS module currently does not have the functionality to create an AMI with UEFI and TPM enabled. An issue has been opened regarding this. Next steps and potential blockers are addressed in the README for when the development of the playbook can resume. @lkatalin