Support AWS Secret Manager to keep the configuration values

[cafeliker]

Anchore user name and password are required as the configuration items, and it's not a best secure approach to keep them as a plain text or k8s secrets.

We plan to enable the support with AWS Secret Manager which will be used to store the configuration as json format as below; and the adpater will read it during the runtime.
{
"endpoint": "http://anchore-anchore-engine-api.default.svc.cluster.local:8228",
"username": "harbor",
"password": "harboruserpass123",
"timeoutSeconds": 10,
"filterVendorIgnoredVulns": false
}

[zhill]

thanks! do you have a preferred way of accessing values from AWS SM inside K8s? I'm not aware of any direct integrations, thought it would be nice to have a secret csi driver. Another option is a direct client call, but that will also require some IAM context in the pod or keys loaded directly.

[cafeliker]

We can assign the AWS secret manager access role to the adapter pod with the IAM Roles for Service Accounts feature, and get the secrets with the aws api calls.