You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If no AWS credentials are provided, module should use AWS IAM role attached to running instance for AWS API.
Current Behavior
Using "pre-generated" AWS API keys is against AWS security guidelines. They recommend using AWS IAM instance role policy to grant those privileges. At the moment most AWS client libraries support this, but this icinga module forces user to enter hardcoded secrets.
Possible Solution
Either add an option to select if IAM role should be used, or just fallback to IAM role if no credentials are configured (backward-compatible and convenient).
Context
We are having audit issues as this icinga module uses bad practices and requires to use static API credentials.
The text was updated successfully, but these errors were encountered:
The problem is that WebUI requires a key in order to add the module... for testing, I've added fake key and applied code change above and everything work.
Use AWS IAM role credentials
Expected Behavior
If no AWS credentials are provided, module should use AWS IAM role attached to running instance for AWS API.
Current Behavior
Using "pre-generated" AWS API keys is against AWS security guidelines. They recommend using AWS IAM instance role policy to grant those privileges. At the moment most AWS client libraries support this, but this icinga module forces user to enter hardcoded secrets.
Possible Solution
Either add an option to select if IAM role should be used, or just fallback to IAM role if no credentials are configured (backward-compatible and convenient).
Context
We are having audit issues as this icinga module uses bad practices and requires to use static API credentials.
The text was updated successfully, but these errors were encountered: