Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Support all AWS SDK authorization methods #264
Fully support all AWS authorization methods for the new AWS Kinesis integration. Right now, an API key is required. The forces users to generate this extra credential set. It is sometimes more desirable to assume a specific role ARN or use the role of the EC2 instance.
Support the following authorization schemes:
Assuming a role or policy in AWS is a common way to authorize applications running in the AWS environment. See https://docs.aws.amazon.com/STS/latest/APIReference/API_AssumeRole.html for more info. Requiring security keys add unneeded complexity and maintenance burdens for certain configurations.
From talking to @kyleknighted about this, we think it's best to support all AWS SDK authorization options. It's not much more work to support them all, and it provides the most flexibility for our users.
So, on the first page of all AWS integrations, we would present the following three choices:
This way, we support all possible options that could be needed since we are making changes to the auth code (not much more work to support them all).