# AMI \$1 Share
Share an AMI with multiple AMS accounts or Organizational Units (OUs).
**Full classification:** Management \$1 Advanced stack components \$1 AMI \$1 Share
## Change Type Details
****
| | |
| --- |--- |
| Change type ID | ct-1eiczxw8ihc18 |
| Current version | 2.0 |
| Expected execution duration | 60 minutes |
| AWS approval | Required |
| Customer approval | Not required |
| Execution mode | Automated |
## Additional Information
### Share AMIs
#### Sharing an AMI with the console
The following shows this change type in the AMS console.
![\[Share AMI interface showing ID, execution mode, version, classification, and description.\]](http://docs.aws.amazon.com/managedservices/latest/ctref/images/guiAmiShareCT.png)
How it works:
1. Navigate to the **Create RFC** page: In the left navigation pane of the AMS console click **RFCs** to open the RFCs list page, and then click **Create RFC**.
1. Choose a popular change type (CT) in the default **Browse change types** view, or select a CT in the **Choose by category** view.
+ **Browse by change type**: You can click on a popular CT in the **Quick create** area to immediately open the **Run RFC** page. Note that you cannot choose an older CT version with quick create.
To sort CTs, use the **All change types** area in either the **Card** or **Table** view. In either view, select a CT and then click **Create RFC** to open the **Run RFC** page. If applicable, a **Create with older version** option appears next to the **Create RFC** button.
+ **Choose by category**: Select a category, subcategory, item, and operation and the CT details box opens with an option to **Create with older version** if applicable. Click **Create RFC** to open the **Run RFC** page.
1. On the **Run RFC** page, open the CT name area to see the CT details box. A **Subject** is required (this is filled in for you if you choose your CT in the **Browse change types** view). Open the **Additional configuration** area to add information about the RFC.
In the **Execution configuration** area, use available drop-down lists or enter values for the required parameters. To configure optional execution parameters, open the **Additional configuration** area.
1. When finished, click **Run**. If there are no errors, the **RFC successfully created** page displays with the submitted RFC details, and the initial **Run output**.
1. Open the **Run parameters** area to see the configurations you submitted. Refresh the page to update the RFC execution status. Optionally, cancel the RFC or create a copy of it with the options at the top of the page.
#### Sharing an AMI with the CLI
How it works:
1. Use either the Inline Create (you issue a `create-rfc` command with all RFC and execution parameters included), or Template Create (you create two JSON files, one for the RFC parameters and one for the execution parameters) and issue the `create-rfc` command with the two files as input. Both methods are described here.
1. Submit the RFC: `aws amscm submit-rfc --rfc-id ID` command with the returned RFC ID.
Monitor the RFC: `aws amscm get-rfc --rfc-id ID` command.
To check the change type version, use this command:
```
aws amscm list-change-type-version-summaries --filter Attribute=ChangeTypeId,Value=CT_ID
```
**Note**
You can use any `CreateRfc` parameters with any RFC whether or not they are part of the schema for the change type. For example, to get notifications when the RFC status changes, add this line, `--notification "{\"Email\": {\"EmailRecipients\" : [\"email@example.com\"]}}"` to the RFC parameters part of the request (not the execution parameters). For a list of all CreateRfc parameters, see the [AMS Change Management API Reference](https://docs.aws.amazon.com/managedservices/latest/ApiReference-cm/API_CreateRfc.html).
*INLINE CREATE*:
Issue the create RFC command with execution parameters provided inline (escape quotation marks when providing execution parameters inline), and then submit the returned RFC ID. For example, you can replace the contents with something like this:
```
aws amscm create-rfc --change-type-id "ct-1eiczxw8ihc18" --change-type-version "2.0" --title "Share AMI" --execution-parameters "{ \"DocumentName\": \"AWSManagedServices-ShareAMI\", \"Region\": \"us-east-1\", \"Parameters\": { \"ImageId\": \"amiid\" , \"OrganizationalUnitARNs\": \"ouarn\" } }"
```
*TEMPLATE CREATE*:
1. Output the execution parameters JSON schema for this change type to a file; this example names it ShareAmiParams.json:
```
aws amscm get-change-type-version --change-type-id "ct-1eiczxw8ihc18" --query "ChangeTypeVersion.ExecutionInputSchema" --output text > ShareAmiParams.json
```
1. Modify and save the execution parameters JSON file. The JSON for only the required parameters and for all the parameters are shown. For example, you can replace the contents with something like this:
Only required parameters:
```
{
"DocumentName": "AWSManagedServices-ShareAMI",
"Region": "us-east-1",
"Parameters": {
"ImageId": "amiid"
}
}
```
All parameters:
```
{
"DocumentName": "AWSManagedServices-ShareAMI",
"Region": "us-east-1",
"Parameters": {
"AccountIds": "awsaccountid",
"ImageId": "amiid",
"OrganizationalUnitARNs": "ouarn",
"ShareSnapshots": "false"
}
}
```
1. Output the RFC template JSON file; this example names it ShareAmiRfc.json:
```
aws amscm create-rfc --generate-cli-skeleton > ShareAmiRfc.json
```
1. Modify and save the ShareAmiRfc.json file. For example, you can replace the contents with something like this:
```
{
"ChangeTypeVersion": "2.0",
"ChangeTypeId": "ct-1eiczxw8ihc18",
"Title": "Share"
}
```
1. Create the RFC, specifying the ShareAmiRfc file and the ShareAmiParams file:
```
aws amscm create-rfc --cli-input-json file://ShareAmiRfc.json --execution-parameters file://ShareAmiParams.json
```
You receive the ID of the new RFC in the response and can use it to submit and monitor the RFC. Until you submit it, the RFC remains in the editing state and does not start.
#### Tips
+ An AMS AMI can't be shared to a non-AMS account. This change type copies an AMI from the source AWS Region to the same Region in the destination account. You must be onboarded to AMS in the destination AWS Region of the specified TargetAwsAccountId, or the shared AMI is unusable in the target account.
+ Additionally, encrypted AMIs can't be shared between accounts without the involvement of the AD administrator and an AMS Operations Engineer. If you want to do this, file a Management \$1 Other \$1 Other \$1 Create (ct-1e1xtak34nx76) with AMS with the AMI ID, account information, and full details.
+ This change type is now at version 2.0.
**Important**
When sharing a custom AMI that you created from an instance in your AMS account, ensure that the AMI is usable in the new account. In particular, the instance used to create the AMI must have been separated from its domain. For more information, see [Create an AMI](deployment-advanced-ami-create.md#ex-ami-create-col).
To learn more about sharing AMIs, see [Sharing an AMI with specific AWS accounts](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/sharingamis-explicit.html).
## Execution Input Parameters
For detailed information about the execution input parameters, see [Schema for Change Type ct-1eiczxw8ihc18](schemas.md#ct-1eiczxw8ihc18-schema-section).
## Example: Required Parameters
```
{
"DocumentName": "AWSManagedServices-ShareAMI",
"Region": "us-east-1",
"Parameters": {
"ImageId": "ami-12345678"
}
}
```
## Example: All Parameters
```
{
"DocumentName": "AWSManagedServices-ShareAMI",
"Region": "us-east-1",
"Parameters": {
"ImageId": "ami-12345678",
"AccountIds": "123456789012",
"OrganizationalUnitARNs": "arn:aws:organizations::111111111111:organization/o-rkw1234jc5",
"ShareSnapshots": true
}
}
```