# AWS AppConfig BadRequestException (configuration profile) in CI

> Fix AWS AppConfig "BadRequestException" for a configuration profile in CI - the application, environment, or configuration profile identifier is wrong or the session request is malformed.

Source: https://latchkey.dev/learn/ci-integrations/aws-appconfig-badrequestexception-profile-in-ci  
Updated: 2026-06-30

AWS AppConfig Data rejected the request with BadRequestException. The application, environment, or configuration profile identifier does not exist (or is a name where an ID is required), or the StartConfigurationSession parameters are invalid. The call fails before any configuration is returned.

## Diagnose it: did the report reach the service?

Coverage and quality integrations fail in two distinct places: the report was never produced, or it was produced and the upload was rejected. Establish which before touching tokens.

```Terminal
# 1. does the report exist and is it non-empty?
ls -la coverage/ && head -5 coverage/lcov.info

# 2. does it reference paths the service can map to the repo?
grep "^SF:" coverage/lcov.info | head -5

# 3. did the upload actually succeed, or just not fail the step?
# most uploaders exit 0 on a rejected upload unless told otherwise
```

> Absolute paths in an lcov report break file mapping on the service side, so coverage appears as zero even though the upload succeeded. Generate reports with paths relative to the repository root.

## FAQ

### What causes AWS AppConfig BadRequestException (configuration profile) in CI?

There are 2 common causes: an identifier does not exist or is a name, not an id and the session parameters are malformed. The application, environment, or configuration profile ID is wrong for the account and region, so AppConfig cannot locate the profile.

### How do I fix AWS AppConfig BadRequestException (configuration profile) in CI?

There are 2 fixes depending on which cause you have: use the correct identifiers for the region and start a session then get the latest configuration. Work through them in order, since the first is the most common.

### What does AWS AppConfig BadRequestException (configuration profile) in CI actually mean?

The AppConfig call fails with "BadRequestException" naming an invalid application, environment, or configuration profile identifier, and no configuration data is retrieved.

### How do I stop AWS AppConfig BadRequestException (configuration profile) in CI happening again?

Reference AppConfig applications, environments, and profiles by ID. The prevention section lists 3 changes that keep it from recurring.

---

Latchkey runs CI/CD that repairs its own failures. Agent entry points: https://latchkey.dev/agent.txt, https://latchkey.dev/openapi.json, https://latchkey.dev/llms.txt