# Using Elastic Beanstalk saved configurations
You can save your environment's configuration as an object in Amazon Simple Storage Service (Amazon S3) that can be applied to other environments during environment creation, or applied to a running environment. *Saved configurations* are YAML formatted templates that define an environment's [platform version](concepts.platforms.md), [tier](concepts.md#concepts-tier), [configuration option](command-options.md) settings, and tags.
You can apply tags to a saved configuration when you create it, and edit tags of existing saved configurations. The tags applied to a saved configuration aren't related to the tags specified in a saved configuration using the `Tags:` key. The latter are applied to an environment when you apply the saved configuration to the environment. For details, see [Tagging saved configurations](environment-configuration-savedconfig-tagging.md).
**Note**
You can create and apply saved configurations to your Elastic Beanstalk environments using several methods. These include the Elastic Beanstalk console, the EB CLI, and the AWS CLI.
See the following topics for examples of alternate methods for creating and applying saved configurations:
[Setting configuration options before environment creation](environment-configuration-methods-before.md)
[Setting configuration options during environment creation](environment-configuration-methods-during.md)
[Setting configuration options after environment creation](environment-configuration-methods-after.md)
Create a saved configuration from the current state of your environment in the Elastic Beanstalk management console.
**To save an environment's configuration**
1. Open the [Elastic Beanstalk console](https://console.aws.amazon.com/elasticbeanstalk), and in the **Regions** list, select your AWS Region.
1. In the navigation pane, choose **Environments**, and then choose the name of your environment from the list.
1. Choose **Actions**, and then choose **Save configuration**.
1. Use the on-screen form to name the saved configuration. Optionally, provide a brief description, and add tag keys and values.
1. Choose **Save**.
![\[Save Configuration page on the Elastic Beanstalk console\]](http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/images/environment-cfg-saveconfiguration-dialog.png)
The saved configuration includes any settings that you have applied to the environment with the console or any other client that uses the Elastic Beanstalk API. You can then apply the saved configuration to your environment at a later date to restore it to its previous state, or apply it to a new environment during [environment creation](environments-create-wizard.md).
You can download a configuration using the EB CLI [**eb config**](eb3-config.md) command, as shown in the following example. *NAME* is the name of your saved configuration.
```
eb config get NAME
```
**To apply a saved configuration during environment creation (Elastic Beanstalk console)**
1. Open the [Elastic Beanstalk console](https://console.aws.amazon.com/elasticbeanstalk), and in the **Regions** list, select your AWS Region.
1. In the navigation pane, choose **Applications**, and then choose your application's name from the list.
1. In the navigation pane, find your application's name and choose **Saved configurations**.
1. Select the saved configuration you want to apply, and then choose **Launch environment**.
1. Proceed through the wizard to create your environment.
Saved configurations don't include settings applied with [configuration files](ebextensions.md) in your application's source code. If the same setting is applied in both a configuration file and saved configuration, the setting in the saved configuration takes precedence. Likewise, options specified in the Elastic Beanstalk console override options in saved configurations. For more information, see [Precedence](command-options.md#configuration-options-precedence).
Saved configurations are stored in the Elastic Beanstalk S3 bucket in a folder named after your application. For example, configurations for an application named `my-app` in the us-west-2 region for account number 123456789012 can be found at `s3://elasticbeanstalk-us-west-2-123456789012/resources/templates/my-app/`.
View the contents of a saved configuration by opening it in a text editor. The following example configuration shows the configuration of a web server environment launched with the Elastic Beanstalk management console.
```
EnvironmentConfigurationMetadata:
Description: Saved configuration from a multicontainer Docker environment created with the Elastic Beanstalk Management Console
DateCreated: '1520633151000'
DateModified: '1520633151000'
Platform:
PlatformArn: arn:aws:elasticbeanstalk:us-east-2::platform/Java 8 running on 64bit Amazon Linux/2.5.0
OptionSettings:
aws:elasticbeanstalk:command:
BatchSize: '30'
BatchSizeType: Percentage
aws:elasticbeanstalk:sns:topics:
Notification Endpoint: me@example.com
aws:elb:policies:
ConnectionDrainingEnabled: true
ConnectionDrainingTimeout: '20'
aws:elb:loadbalancer:
CrossZone: true
aws:elasticbeanstalk:environment:
ServiceRole: aws-elasticbeanstalk-service-role
aws:elasticbeanstalk:application:
Application Healthcheck URL: /
aws:elasticbeanstalk:healthreporting:system:
SystemType: enhanced
aws:autoscaling:launchconfiguration:
IamInstanceProfile: aws-elasticbeanstalk-ec2-role
InstanceType: t2.micro
EC2KeyName: workstation-uswest2
aws:autoscaling:updatepolicy:rollingupdate:
RollingUpdateType: Health
RollingUpdateEnabled: true
EnvironmentTier:
Type: Standard
Name: WebServer
AWSConfigurationTemplateVersion: 1.1.0.0
Tags:
Cost Center: WebApp Dev
```
You can modify the contents of a saved configuration and save it in the same location in Amazon S3. Any properly formatted saved configuration stored in the right location can be applied to an environment by using the Elastic Beanstalk management console.
The following keys are supported.
+ **AWSConfigurationTemplateVersion** (required) – The configuration template version (1.1.0.0).
```
AWSConfigurationTemplateVersion: 1.1.0.0
```
+ **Platform** – The Amazon Resource Name (ARN) of the environment's platform version. You can specify the platform by ARN or solution stack name.
```
Platform:
PlatformArn: arn:aws:elasticbeanstalk:us-east-2::platform/Java 8 running on 64bit Amazon Linux/2.5.0
```
+ **SolutionStack** – The full name of the [solution stack](concepts.platforms.md) used to create the environment.
```
SolutionStack: 64bit Amazon Linux 2017.03 v2.5.0 running Java 8
```
+ **OptionSettings** – [Configuration option](command-options.md) settings to apply to the environment. For example, the following entry sets the instance type to t2.micro.
```
OptionSettings:
aws:autoscaling:launchconfiguration:
InstanceType: t2.micro
```
+ **Tags** – Up to 47 tags to apply to resources created within the environment.
```
Tags:
Cost Center: WebApp Dev
```
+ **EnvironmentTier** – The type of environment to create. For a web server environment, you can exclude this section (web server is the default). For a worker environment, use the following.
```
EnvironmentTier:
Name: Worker
Type: SQS/HTTP
```
**Note**
You can create and apply saved configurations to your Elastic Beanstalk environments using several methods. These include the Elastic Beanstalk console, the EB CLI, and the AWS CLI.
See the following topics for examples of alternate methods for creating and applying saved configurations:
[Setting configuration options before environment creation](environment-configuration-methods-before.md)
[Setting configuration options during environment creation](environment-configuration-methods-during.md)
[Setting configuration options after environment creation](environment-configuration-methods-after.md)
# Tagging saved configurations
You can apply tags to your AWS Elastic Beanstalk saved configurations. Tags are key-value pairs associated with AWS resources. For information about Elastic Beanstalk resource tagging, use cases, tag key and value constraints, and supported resource types, see [Tagging Elastic Beanstalk application resources](applications-tagging-resources.md).
You can specify tags when you create a saved configuration. In an existing saved configuration, you can add or remove tags, and update the values of existing tags. You can add up to 50 tags to each saved configuration.
## Adding tags during saved configuration creation
When you use the Elastic Beanstalk console to [save a configuration](environment-configuration-savedconfig.md), you can specify tag keys and values on the **Save Configuration** page.
If you use the EB CLI to save a configuration, use the `--tags` option with **[eb config](eb3-config.md)** to add tags.
```
~/workspace/my-app$ eb config --tags mytag1=value1,mytag2=value2
```
With the AWS CLI or other API-based clients, add tags by using the `--tags` parameter on the **[create-configuration-template](https://docs.aws.amazon.com/cli/latest/reference/elasticbeanstalk/create-configuration-template.html)** command.
```
$ aws elasticbeanstalk create-configuration-template \
--tags Key=mytag1,Value=value1 Key=mytag2,Value=value2 \
--application-name my-app --template-name my-template --solution-stack-name solution-stack
```
## Managing tags of an existing saved configuration
You can add, update, and delete tags in an existing Elastic Beanstalk saved configuration.
**To manage a saved configuration's tags using the Elastic Beanstalk console**
1. Open the [Elastic Beanstalk console](https://console.aws.amazon.com/elasticbeanstalk), and in the **Regions** list, select your AWS Region.
1. In the navigation pane, choose **Applications**, and then choose your application's name from the list.
1. In the navigation pane, find your application's name and choose **Saved configurations**.
1. Select the saved configuration you want to manage.
1. Choose **Actions**, and then choose **Manage tags**.
1. Use the on-screen form to add, update, or delete tags.
1. To save the changes choose **Apply** at the bottom of the page.
If you use the EB CLI to update your saved configuration, use **[eb tags](eb3-tags.md)** to add, update, delete, or list tags.
For example, the following command lists the tags in a saved configuration.
```
~/workspace/my-app$ eb tags --list --resource "arn:aws:elasticbeanstalk:us-east-2:my-account-id:configurationtemplate/my-app/my-template"
```
The following command updates the tag `mytag1` and deletes the tag `mytag2`.
```
~/workspace/my-app$ eb tags --update mytag1=newvalue --delete mytag2 \
--resource "arn:aws:elasticbeanstalk:us-east-2:my-account-id:configurationtemplate/my-app/my-template"
```
For a complete list of options and more examples, see `eb tags`.
With the AWS CLI or other API-based clients, use the **[list-tags-for-resource](https://docs.aws.amazon.com/cli/latest/reference/elasticbeanstalk/list-tags-for-resource.html)** command to list the tags of a saved configuration.
```
$ aws elasticbeanstalk list-tags-for-resource --resource-arn "arn:aws:elasticbeanstalk:us-east-2:my-account-id:configurationtemplate/my-app/my-template"
```
Use the **[update-tags-for-resource](https://docs.aws.amazon.com/cli/latest/reference/elasticbeanstalk/update-tags-for-resource.html)** command to add, update, or delete tags in a saved configuration.
```
$ aws elasticbeanstalk update-tags-for-resource \
--tags-to-add Key=mytag1,Value=newvalue --tags-to-remove mytag2 \
--resource-arn "arn:aws:elasticbeanstalk:us-east-2:my-account-id:configurationtemplate/my-app/my-template"
```
Specify both tags to add and tags to update in the `--tags-to-add` parameter of **update-tags-for-resource**. A nonexisting tag is added, and an existing tag's value is updated.
**Note**
To use some of the EB CLI and AWS CLI commands with an Elastic Beanstalk saved configuration, you need the saved configuration's ARN. To construct the ARN, first use the following command to retrieve the saved configuration's name.
```
$ aws elasticbeanstalk describe-applications --application-names my-app
```
Look for the `ConfigurationTemplates` key in the command's output. This element shows the saved configuration's name. Use this name where `my-template` is specified in the commands mentioned on this page.