Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
SQS Transport to accept EC2-Profile as Credentials Source #1459
referenced this issue
Oct 12, 2018
You are absolutely right it is not yet ideal how the API keys are managed. The underlying SQS transport uses the standard SDK constructors of the clients thus it would follow the normal credential retrieval hierarchy defined in https://docs.aws.amazon.com/sdk-for-net/v3/developer-guide/net-dg-config-creds.html. So given that we could support it by now longer requiring API keys in the connection string and only promoting environment variables if you specify the keys. Would that work for you? This would assume the default profile would be used or would you have the requirement to specify the profile name in ServiceControl?