Create Configuration Profile
Remember, AWS AppConfig requires that you create resources and deploy a configuration in the following order:
- Create an application
- Create an environment
- Create a configuration profile
- Create a deployment strategy
- Deploy the configuration
In this section, we will continue with the Create a configuration profile step which establishes a reference to where your configuration data is stored.
AWS AppConfig currently supports storing configuration data in the following formats and locations:
- YAML, JSON, or text documents in the AWS AppConfig hosted configuration store
- Objects in an Amazon Simple Storage Service (Amazon S3) bucket
- Documents in the Systems Manager document store
- Parameters in Parameter Store
- Any integration source action supported by AWS CodePipeline
During this lab, we wil use the AWS AppConfig hosted configuration store - an internal or hosted configuration store. Configurations must be 64 KB or smaller. The AWS AppConfig hosted configuration store provides the following benefits over other configuration store options.
- You don’t need to set up and configure other services such as Amazon Simple Storage Service (Amazon S3) or Parameter Store.
- You don’t need to configure AWS Identity and Access Management (IAM) permissions to use the configuration store.
- You can store configurations in YAML, JSON, or as text documents.
- There is no cost to use the store.
- You can create a configuration and add it to the store when you create a configuration profile.
Use the following procedure to create a configuration profile for storing your configuration data in AWS AppConfig hosted configuration store.
- Select the Configuration profiles tab.
- Select Create configuration profile and enter AppConfigLabHostedConfigurationProfile in the Name field and AppConfig Lab hosted configuration profile in the Description field.
- Select Next.
- Select AWS AppConfig hosted configuration from the Configuration source options presented.
- Select JSON from the Content options presented.
- Copy and paste the JSON below into the area provided..
{
"boolEnableLimitResults": false,
"intResultLimit": 0
}
- Select Next.
- Select Remove in the Validator 1 section. We will not create a validator at this time. We will revisit JSON Schema and AWS Lambda validators in later sections of the lab.
- Select Create configuration profile.