Open arichtman-srt opened 1 year ago
[Triage] Adding @prudhvigodithi to take a look on this. Thanks.
Hey @arichtman-sr, can you please test with the latest version of the provider? Thank you Adding @phillbaker @bbarani @peterzhuamazon
Hello @peterzhuamazon, I'm getting a 403 Forbidden error when using aws-sso-login-generated tmp credentials. The provider verison is the latest available. I export the env var AWS_PROFILE=admin_profile and configure the provider as the following:
provider "opensearch" { url = "https://${module.opensearch.opensearch_domain_endpoint}" healthcheck = false aws_profile = "${var.aws_profile}" }
It seems to be a problem with this provider, since everything else works fine. Any help or suggestion is welcome.
The error:
│ Error: HTTP 403 Forbidden: Permission denied. Please ensure that the correct credentials are being used to access the cluster. │ │ with module.opensearch_ops.opensearch_ism_policy.otel_ism_policies["otel-v1-metrics-ism-policy"], │ on modules/opensearch-ops/main.tf line 14, in resource "opensearch_ism_policy" "otel_ism_policies": │ 14: resource "opensearch_ism_policy" "otel_ism_policies" {
What is the bug?
When using AWS SSO profiles the provider crashes.
How can one reproduce the bug?
Attempt to apply changes using AWS SSO profiles that rely on
sso_session
.What is the expected behavior?
Graceful shutdown
What is your host/environment?
aarch64-darwin
Do you have any screenshots?
Do you have any additional context?
I believe
sso_session
is unsupported by the AWS GoLang SDK.