awscurl: Does not support EC2 Instance Profiles
First off, very neat project!
In regards to func load_aws_config. Is there a specific reason you use a ConfigParser?
If you used boto3 you’d end up supporting most credential providers implicitly.
boto3.Session().get_credentials().get_frozen_credentials()
You could construct the session object with a profile and/or keys if provided, or otherwise allow boto to default to its own chain of finding credentials. This would in turn allow it to work from an EC2 instance with an IAM instance profile while maintaining the existing functionality.
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 1
- Comments: 16 (6 by maintainers)
That I have not. But I might give it a try later to see. That would make sense since it hits an extra service. My cluster is only used for logging and I nuke everything older than 30 days in it and use CloudWatch logs for “cold storage.” So I haven’t really worried about backups or anything.
@tinyzimmer hmm, i think this story will continue to evolve, for now created this PR (fallback to botocore… 😱): #63