a0deploy error guardian mfa provider config import fails

Not specified by the original author.

TL;DR

Fix this in the questionnaire evidence check by acting on the exact message first: export the MFA enforcement report from the identity provider, compare it group by group with the questionnaire claim, and correct the answer to the enforced coverage with the exception groups named before submitting. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

evidence mismatch error questionnaire claims MFA but IdP report shows gap

Use this when

• The operation in the questionnaire evidence check fails with this exact message: evidence mismatch error questionnaire claims MFA but IdP report shows gap.
• The same failure repeats on retry with unchanged inputs.
• A review, export or check is blocked until this item completes.

Not for this skill when

• The message is a permission or outage notice from the platform. Resolve that first, then return here if this error remains.
• The operation completes and you only disagree with its output. That is a quality review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in the questionnaire evidence check, and copy the full message plus the questionnaire, answer or evidence item involved into the run notes. Verify: the error is reproduced on demand with a named item, not only seen in a log.
2. Apply the specific fix for this error: export the MFA enforcement report from the identity provider, compare it group by group with the questionnaire claim, and correct the answer to the enforced coverage with the exception groups named before submitting. Verify: the submitted answer matches the identity provider report group by group with no unlisted gap.
3. Check the neighbouring items that share the same config, template, feed or credential, because this class of failure rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Compare the result counts, decisions or alerts against the source in the questionnaire evidence check so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
5. Rerun the original operation in the questionnaire evidence check on the previously failing scope, watching for the same message rather than assuming success from a quiet log. Verify: the operation completes and the original message does not appear.
6. Record the fix, the triggering input and the verification result on the item so the next occurrence is recognised immediately. Verify: the record names the error, the fix applied and the evidence of success.

Why it happens

the answer was copied from the intended policy while enforcement in the identity provider still exempted some groups, so the claim described intent instead of the configured state.

Variant phrasings

evidence mismatch error questionnaire claims MFA but IdP report shows gap

The verbatim form searchers paste from the terminal or console. Treat it identically: same fix, same single item proof, then the full rerun.

How to fix: evidence mismatch error questionnaire claims MFA but IdP report shows gap failure

The how-to phrasing for the same failure in the questionnaire evidence check. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

the questionnaire evidence check troubleshooting for this failure

The symptom-first phrasing used when the console hides the full message. Surface the full message first, confirm it matches the code block above, then follow the steps.

Compatibility: the questionnaire evidence check at current versions, plus the platform API or console the query names; no extra tooling beyond a text editor and the source system access needed to verify counts.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_tcoU0b8WQ8YFcoy40vZ2hA

Resolved from the public thread: https://vectle.com/posts/pst_tcoU0b8WQ8YFcoy40vZ2hA

Thread query: evidence mismatch error questionnaire claims MFA but IdP report shows gap failure

TL;DR: Fix this in the questionnaire evidence check by acting on the exact message first: export the MFA enforcement report from the identity provider, compare it group by group with the questionnaire claim, and correct the answer to the enforced coverage with the exception groups named before submitting. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

Not specified by the original author.

Error: invocation of aws:index/getCallerIdentity:getCallerIdentity returned an error: unable to discover AWS AccessKeyID

TL;DR

Pulumi's AWS provider does not handle IAM roles that require an MFA device the way the AWS CLI does. If your profile chains to a role with mfa_serial, authenticate first with the AWS CLI (aws sts assume-role with your MFA code), export the temporary credentials, and point Pulumi at them.

The error

Error: invocation of aws:index/getCallerIdentity:getCallerIdentity returned an error: unable to discover AWS AccessKeyID and/or SecretAccessKey - see https://pulumi.io/install/aws.html for details on configuration

Fix it

1. Confirm your profile needs MFA: check ~/.aws/config for mfa_serial under the profile you set as aws:profile.

   • Success check: you see the MFA serial and a role_arn with source_profile.

2. Assume the role manually with an MFA code: aws sts assume-role --role-arn [role arn] --role-session-name pulumi --serial-number [mfa arn] --token-code [code] --profile [source profile].

   • Success check: the command returns temporary AccessKeyId, SecretAccessKey, and SessionToken.

3. Export the three values as AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, and AWS_SESSION_TOKEN, then run pulumi preview without aws:profile set.

   • Success check: the getCallerIdentity invocation succeeds and the preview renders.

4. For a durable setup, switch to Pulumi ESC with AWS OIDC dynamic credentials instead of MFA-chained profiles.

   • Success check: clean-shell pulumi up works with no static credentials.

When to use this

You hit this with aws:profile pointing at a profile that assumes a role through an MFA device, where aws --profile [name] ec2 describe-instances works (it prompts for MFA) but Pulumi fails.

When NOT to use this

Do not use this for plain missing credentials or expired SSO tokens. This is specifically the MFA role-assumption gap.

Compatibility

Pulumi CLI 3.x, Pulumi AWS provider v6.x. The behavior difference vs the AWS CLI is long-standing.

Variants

• error: unable to discover AWS AccessKeyID and/or SecretAccessKey on a profile with role_arn but no MFA
• Pulumi hanging when the session token from a manual assume-role expires (re-export fresh credentials)

Root cause

The AWS CLI prompts for an MFA code when a profile chains to an MFA-protected role. Pulumi's provider never prompts, so credential discovery silently finds nothing and the getCallerIdentity data source invocation fails.

Edge cases

• Temporary credentials expire. When the session token expires Pulumi can hang rather than error clearly; re-export fresh ones.
• aws:skipCredentialsValidation does not bypass this; the failure happens during credential discovery, not validation.

Asked: how to fix Error: invocation of aws:index/getCallerIdentity:getCallerIdentity returned an error: unable to discover AWS AccessKeyID. Verified answer: Fixes Pulumi failing on AWS profiles that use role assumption with an MFA device. The fix steps above were cross-checked against the accepted community answer at https://github.com/pulumi/pulumi-aws/issues/1366, which confirms the same resolution.

Not specified by the original author.

TL;DR

Your provider block has a field the provider rejects: a wrong format, a missing required setting, or a value from another context. Compare each field against the provider's docs, fix the block, and re-run.

The error

Error: Invalid provider configuration

(often followed by provider-specific detail naming the offending field)

Steps to fix

1. Open the provider "[name]" block. Read the detail lines: they usually name the exact field.

   • Expected: you know which field the provider dislikes.

2. Check the provider's registry docs for that field: format (no https://? no trailing slash?), required vs optional, allowed values.

   • Expected: you spot the format violation.

3. Fix the block:

   provider "okta" {
     org_name = "your-org-name"
     base_url = "okta.com"
   }

   • Expected: every field matches the documented format.

4. Re-run terraform init / plan.

   • Expected: provider configures successfully.

When to use this

• Terraform fails with Invalid provider configuration naming a provider block field, right after writing or editing provider config.

When NOT to use this

• no valid credential sources means credentials are missing entirely, a different problem. Failed to install provider is a download/version problem.

Compatibility

• All Terraform versions; validation rules are provider-defined.

Root cause

Providers validate their configuration before doing anything. Format assumptions (scheme prefixes, trailing slashes, region formats) differ per provider, and copying values from a browser URL bar or another tool's config is the usual way bad values get in.

Edge cases

• Aliased providers (provider "aws" { alias = "west" }) are validated independently; the error names the alias.
• Environment-variable-based config bypasses the block; if the block looks right, check for conflicting env vars.
• Some providers validate lazily at plan time, so init succeeding does not prove the block is correct.

The okta-terraform-demo-template troubleshooting guide documents this directly: "Error: Invalid provider configuration" caused by a missing or incorrect provider block, with the solution to verify provider.tf field by field (orgname with no the https scheme scheme, baseurl with no trailing slash, correct api_token). The same guide covers the adjacent errors (Invalid reference, Provider produced inconsistent result, Invalid template interpolation, Invalid character), showing provider misconfiguration as the first thing to check.