---
title: "POST /applications/{ApplicationId}/configurationprofiles"
method: POST
path: "/applications/{ApplicationId}/configurationprofiles"
---

# POST /applications/{ApplicationId}/configurationprofiles

`POST /applications/{ApplicationId}/configurationprofiles`

Creates a configuration profile, which is information that enables AppConfig to access the configuration source. Valid configuration sources include the following:

*   Configuration data in YAML, JSON, and other formats stored in the AppConfig hosted configuration store
    
*   Configuration data stored as objects in an Amazon Simple Storage Service (Amazon S3) bucket
    
*   Pipelines stored in CodePipeline
    
*   Secrets stored in Secrets Manager
    
*   Standard and secure string parameters stored in Amazon Web Services Systems Manager Parameter Store
    
*   Configuration data in SSM documents stored in the Systems Manager document store
    

A configuration profile includes the following information:

*   The URI location of the configuration data.
    
*   The Identity and Access Management (IAM) role that provides access to the configuration data.
    
*   A validator for the configuration data. Available validators include either a JSON Schema or an Amazon Web Services Lambda function.
    

For more information, see [Create a Configuration and a Configuration Profile](http://docs.aws.amazon.com/appconfig/latest/userguide/appconfig-creating-configuration-and-profile.html) in the _AppConfig User Guide_.

## Path parameters

- `ApplicationId` string, required

## Request body

- object
  - `Name` string, required — A name for the configuration profile.
  - `Description` string — A description of the configuration profile.
  - `LocationUri` string, required — <p>A URI to locate the configuration. You can specify the following:</p> <ul> <li> <p>For the AppConfig hosted configuration store and for feature flags, specify <code>hosted</code>.</p> </li> <li> <p>For an Amazon Web Services Systems Manager Parameter Store parameter, specify either the parameter name in the format <code>ssm-parameter://&lt;parameter name&gt;</code> or the ARN.</p> </li> <li> <p>For an Secrets Manager secret, specify the URI in the following format: <code>secrets-manager</code>://&lt;secret name&gt;.</p> </li> <li> <p>For an Amazon S3 object, specify the URI in the following format: <code>s3://&lt;bucket&gt;/&lt;objectKey&gt; </code>. Here is an example: <code>s3://my-bucket/my-app/us-east-1/my-config.json</code> </p> </li> <li> <p>For an SSM document, specify either the document name in the format <code>ssm-document://&lt;document name&gt;</code> or the Amazon Resource Name (ARN).</p> </li> </ul>
  - `RetrievalRoleArn` string — <p>The ARN of an IAM role with permission to access the configuration at the specified <code>LocationUri</code>.</p> <important> <p>A retrieval role ARN is not required for configurations stored in the AppConfig hosted configuration store. It is required for all other sources that store your configuration. </p> </important>
  - `Validators` Validator[] — A list of methods for validating the configuration.
    - `Type` 'JSON_SCHEMA' | 'LAMBDA', required — AppConfig supports validators of type <code>JSON_SCHEMA</code> and <code>LAMBDA</code>
    - `Content` string, password, required — Either the JSON Schema content or the Amazon Resource Name (ARN) of an Lambda function.
  - `Tags` object — Metadata to assign to the configuration profile. Tags help organize and categorize your AppConfig resources. Each tag consists of a key and an optional value, both of which you define.
  - `Type` string — <p>The type of configurations contained in the profile. AppConfig supports <code>feature flags</code> and <code>freeform</code> configurations. We recommend you create feature flag configurations to enable or disable new features and freeform configurations to distribute configurations to an application. When calling this API, enter one of the following values for <code>Type</code>:</p> <p> <code>AWS.AppConfig.FeatureFlags</code> </p> <p> <code>AWS.Freeform</code> </p>

## Response `201`

Success

- ConfigurationProfile
  - `ApplicationId` string — The application ID.
  - `Id` string — The configuration profile ID.
  - `Name` string — The name of the configuration profile.
  - `Description` string — The configuration profile description.
  - `LocationUri` string — The URI location of the configuration.
  - `RetrievalRoleArn` string — The ARN of an IAM role with permission to access the configuration at the specified <code>LocationUri</code>.
  - `Validators` Validator[] — A list of methods for validating the configuration.
    - `Type` 'JSON_SCHEMA' | 'LAMBDA', required — AppConfig supports validators of type <code>JSON_SCHEMA</code> and <code>LAMBDA</code>
    - `Content` string, password, required — Either the JSON Schema content or the Amazon Resource Name (ARN) of an Lambda function.
  - `Type` string — <p>The type of configurations contained in the profile. AppConfig supports <code>feature flags</code> and <code>freeform</code> configurations. We recommend you create feature flag configurations to enable or disable new features and freeform configurations to distribute configurations to an application. When calling this API, enter one of the following values for <code>Type</code>:</p> <p> <code>AWS.AppConfig.FeatureFlags</code> </p> <p> <code>AWS.Freeform</code> </p>

## Other responses

- `480` — BadRequestException
- `481` — ResourceNotFoundException
- `482` — InternalServerException

---

[API](https://skmtc.net/aws/apis/appconfig.md) · [All operations](https://skmtc.net/aws/apis/appconfig/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/aws/appconfig/versions/924584438718/schema)