Closed m-q-t closed 3 years ago
Snippet from bootstrap.json for temporary AWS keys:
"seeds": [{
"entity": "AwsCredential#MyCreds1",
"details": {
"Some_detail": "that's good",
"Anotherdetail": "that's also good"
},
"sensitive_details": {
"aws_access_key_id": "ASIAEXAMPLEKEY",
"aws_secret_access_key": "secret_access_key_here",
"aws_session_token": "session_token_here"
}
}]
}]
Hi team,
Please find attached in this PR the implementation to allow the AWS tasks to support AWS Temporary Keys (generated via STS).
Changes:
The
get_aws_keys_from_entity_type()
helper was refactored in order to support AWS Temporary Keys. The main difference between access keys and temporary keys is that temporary keys include a session token.AwsCredential
entity will support AWS Temporary Keys. The reason behind this is because it doesn't make too much sense adding temporary keys to the task.config when compared to normal access keys.Every task which is a caller of
get_aws_keys_from_entity_type()
has been extended to now support the session token which includes:The
aws_route53.rb
task was renamed toaws_route53_gather_records.rb
in order to follow the naming convention.Thanks.
Best regards, Maxim