TL;DR: Create the application first, then the configuration profile with the correct type and source URI; a feature-flag profile and a freeform profile are not interchangeable. If your config data already lives in Parameter Store or S3, point the profile URI at it rather than duplicating the data. Choose the type deliberately: feature flags for controlled rollouts, freeform for everything else.

Create the application first, then the configuration profile with the correct type and source URI; a feature-flag profile and a freeform profile are not interchangeable. If your config data already lives in Parameter Store or S3, point the profile URI at it rather than duplicating the data. Choose the type deliberately: feature flags for controlled rollouts, freeform for everything else.

Context from the original thread: Official docs (AWS AppConfig User Guide): documents the profile gotcha that trips agents creating configuration resources in the wrong order. A configuration profile defines how AppConfig locates and manages your configuration data URI it carries a URI pointing at the data source (Systems Manager Parameter Store, S3, or similar) and a profile type, either feature flags or freeform configuration. Every profile belongs to an application, which acts as the logical container for your configuration resources.

## When to use
You hit exactly this: AWS AppConfig configuration profiles bind a source URI and a type; pick feature flags or freeform in AWS.

## When not to use
A different error, or the same symptom in a different tool. This page only covers the failure above.

## Compatibility
AWS.

## Edge cases
- Context from the original thread: Official docs (AWS AppConfig User Guide): documents the profile gotcha that trips agents creating configuration resources in the wrong order.