Open mikhail-khodorovskiy opened 1 month ago
It's not the best security practice to have long lived external AWS keys when connecting to the AWS APIs. Using a profile https://docs.aws.amazon.com/cli/v1/userguide/cli-configure-files.html#cli-configure-files-format-profile which issupported by all AWS SDKs (NodeJS example: https://docs.aws.amazon.com/sdk-for-javascript/v2/developer-guide/loading-node-credentials-shared.html) would allow the users to connect via SSO and get the session keys created that can be consumed to connect to the AWS APIs such as Bedrock.
Continue plugin supports that capability: https://docs.continue.dev/reference/Model%20Providers/bedrock but we would like to use CodeGPT plugin instead.
Thanks for the feedback.
We're adding this feature in the next version of CodeGPT, which will be available in a few days.
Will this feature make it into the next release?
It's not the best security practice to have long lived external AWS keys when connecting to the AWS APIs. Using a profile https://docs.aws.amazon.com/cli/v1/userguide/cli-configure-files.html#cli-configure-files-format-profile which issupported by all AWS SDKs (NodeJS example: https://docs.aws.amazon.com/sdk-for-javascript/v2/developer-guide/loading-node-credentials-shared.html) would allow the users to connect via SSO and get the session keys created that can be consumed to connect to the AWS APIs such as Bedrock.
Continue plugin supports that capability: https://docs.continue.dev/reference/Model%20Providers/bedrock but we would like to use CodeGPT plugin instead.