# Monitoring and Notification Subcategory
**Topics**
+ [CloudWatch \$1 Create Alarms](deployment-monitoring-cloudwatch-create-alarms.md)
+ [CloudWatch \$1 Create LogGroup](deployment-monitoring-cloudwatch-create-loggroup.md)
+ [GuardDuty IP Set \$1 Create (Managed Automation)](deployment-monitoring-guardduty-ip-set-create-managed-automation.md)
+ [GuardDuty Threat Intel Set \$1 Create (Managed Automation)](deployment-monitoring-guardduty-threat-intel-set-create-managed-automation.md)
+ [SNS \$1 Create (Topic and Subscription)](deployment-monitoring-sns-create-topic-and-subscription.md)
+ [SQS \$1 Create](deployment-monitoring-sqs-create.md)
# CloudWatch \$1 Create Alarms
Create one or more CloudWatch alarms. For detailed information on CloudWatch alarm properties, see AWS documentation "Creating CloudWatch Alarms".
**Full classification:** Deployment \$1 Monitoring and notification \$1 CloudWatch \$1 Create alarms
## Change Type Details
****
| | |
| --- |--- |
| Change type ID | ct-361vpyun9a9dd |
| Current version | 1.0 |
| Expected execution duration | 60 minutes |
| AWS approval | Required |
| Customer approval | Not required |
| Execution mode | Automated |
## Additional Information
### Create CloudWatch alarm
#### Creating a CloudWatch alarm with the console
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.
#### Creating a CloudWatch alarm 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 --profile saml --region us-east-1 amscm create-rfc --change-type-id "ct-361vpyun9a9dd" --change-type-version "1.0" --title "Test Create CloudWatch Alarms" --execution-parameters "{\"Alarms\": [{\"ActionsEnabled\": true,\"AlarmActions\": [\"arn:aws:sns:us-east-1:000000000000:SNS-Topic\"],\"AlarmDescription\": \"Test alarm description.\",\"AlarmName\": \"Test alarm name\",\"ComparisonOperator\": \"GreaterThanThreshold\",\"DatapointsToAlarm\": 1,\"Dimensions\": [{\"Name\": \"InstanceId\",\"Value\": \"i-12345678901234567\"}],\"EvaluateLowSampleCountPercentile\": \"ignore\",\"EvaluationPeriods\": 2,\"InsufficientDataActions\": [\"arn:aws:sns:us-east-1:000000000000:SNS-Topic\"],\"MetricName\": \"TestMetric\",\"Namespace\": \"AWS/Test\",\"OkActions\": [\"arn:aws:sns:us-east-1:000000000000:SNS-Topic\"],\"Period\": 300,\"Statistic\": \"Average\",\"Threshold\": 85,\"TreatMissingData\": \"breaching\",\"Unit\": \"Percent\"}],\"Region\": \"us-east-1\"}"
```
*TEMPLATE CREATE*:
1. Output the execution parameters JSON schema for this change type to a file in your current folder; this example names it CwAlarmsParams.json:
```
aws amscm get-change-type-version --change-type-id "ct-361vpyun9a9dd" --query "ChangeTypeVersion.ExecutionInputSchema" --output text > CwAlarmsParams.json
```
1. Modify and save the CwAlarmsParams.json file. For example, you can replace the contents with something like this:
```
{
"Alarms": [
{
"ActionsEnabled": true,
"AlarmActions": ["arn:aws:sns:us-east-1:000000000000:SNS-Topic"],
"AlarmDescription": "Test alarm description.",
"AlarmName": "Test alarm name",
"ComparisonOperator": "GreaterThanThreshold",
"DatapointsToAlarm": 1,
"Dimensions": [
{
"Name": "InstanceId",
"Value": "i-12345678901234567"
}
],
"EvaluateLowSampleCountPercentile": "ignore",
"EvaluationPeriods": 2,
"InsufficientDataActions": ["arn:aws:sns:us-east-1:000000000000:SNS-Topic"],
"MetricName": "TestMetric",
"Namespace": "AWS/Test",
"OkActions": ["arn:aws:sns:us-east-1:000000000000:SNS-Topic"],
"Period": 300,
"Statistic": "Average",
"Threshold": 85,
"TreatMissingData": "breaching",
"Unit": "Percent"
}
],
"Region": "us-east-1"
}
```
1. Output the JSON template for CreateRfc to a file in your current folder; this example names it CwAlarmsRfc.json:
```
aws amscm create-rfc --generate-cli-skeleton > CwAlarmsRfc.json
```
1. Modify and save the CwAlarmsRfc.json file. For example, you can replace the contents with something like this:
```
{
"ChangeTypeVersion": "1.0",
"ChangeTypeId": "ct-361vpyun9a9dd",
"Title": "CW-ALARMS-RFC"
}
```
1. Create the RFC, specifying the CwAlarmsRfc file and the execution parameters file:
```
aws amscm create-rfc --cli-input-json file://CwAlarmsRfc.json --execution-parameters file://CwAlarmsParams.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
To learn more about CloudWatch, see [Creating Amazon CloudWatch Alarms](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/AlarmThatSendsEmail.html).
## Execution Input Parameters
For detailed information about the execution input parameters, see [Schema for Change Type ct-361vpyun9a9dd](schemas.md#ct-361vpyun9a9dd-schema-section).
## Example: Required Parameters
```
Example not available.
```
## Example: All Parameters
```
{
"Alarms": [
{
"ActionsEnabled": true,
"AlarmActions": ["arn:aws:sns:us-east-1:000000000000:SNS-Topic"],
"AlarmDescription": "Test alarm description.",
"AlarmName": "Test alarm name",
"ComparisonOperator": "GreaterThanThreshold",
"DatapointsToAlarm": 1,
"Dimensions": [
{
"Name": "InstanceId",
"Value": "i-12345678901234567"
}
],
"EvaluateLowSampleCountPercentile": "ignore",
"EvaluationPeriods": 2,
"InsufficientDataActions": ["arn:aws:sns:us-east-1:000000000000:SNS-Topic"],
"MetricName": "TestMetric",
"Namespace": "AWS/Test",
"OkActions": ["arn:aws:sns:us-east-1:000000000000:SNS-Topic"],
"Period": 300,
"Statistic": "Average",
"Threshold": 85,
"TreatMissingData": "breaching",
"Unit": "Percent"
}
],
"Region": "us-east-1"
}
```
# CloudWatch \$1 Create LogGroup
Creates a CloudWatch LogGroup with optional subscription filter, up to 5 log streams and up to 5 metric filters.
**Full classification:** Deployment \$1 Monitoring and notification \$1 CloudWatch \$1 Create LogGroup
## Change Type Details
****
| | |
| --- |--- |
| Change type ID | ct-0cyqd7laxyhlm |
| Current version | 1.0 |
| Expected execution duration | 60 minutes |
| AWS approval | Required |
| Customer approval | Not required |
| Execution mode | Automated |
## Additional Information
### Create CloudWatch LogGroup
#### Creating a CloudWatch LogGroup with the console
![\[CloudWatch LogGroup details showing ID, version, and execution mode for log streams and metric filters.\]](http://docs.aws.amazon.com/managedservices/latest/ctref/images/guiCwCreateLGCT.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.
#### Creating a CloudWatch LogGroup 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 --profile saml --region us-east-1 create-rfc --change-type-id "ct-0cyqd7laxyhlm" --change-type-version "1.0" --title 'CloudWatch LogGroup' --description "CloudWatch LogGroup" --execution-parameters "{\"Description\":\"My Test LogGroup\",\"VpcId\":\"VPC_ID\",\"Name\":\"Test LogGroup\",\"StackTemplateId\":\"stm-8ian3plt5a6jbv7jt\",\"TimeoutInMinutes\":60,\"Parameters\": {\"LogGroupName\":\"customer-testloggroup\",\"LogStream1Name\":\"LogStream1\",\"SubscriptionFilterPattern\":\"test\",\"SubscriptionDestinationARN\":\"arn:aws:lambda:us-east-1:123456789012:function:test_lambda\",\"MetricFilter1Name\":\"test_metric_filter1\",\"MetricFilter1Namespace\":\"test_metric_filter1_namespace\",\"MetricFilter1Pattern\":\"{$.eventType=\\\"test_event\\\"}\",\"MetricFilter1Value\":\"10\"}}"
```
*TEMPLATE CREATE*:
1. Output the execution parameters JSON schema for this change type to a file in your current folder; this example names it CwLGParams.json:
```
aws amscm get-change-type-version --change-type-id "ct-ct-0cyqd7laxyhlm" --query "ChangeTypeVersion.ExecutionInputSchema" --output text > CwLGParams.json
```
1. Modify and save the CwLGParams.json file. For example, you can replace the contents with something like this:
```
{
"Description": "Test CloudWatch Description",
"VpcId": "VPC_ID",
"StackTemplateId": "stm-8ian3plt5a6jbv7jt",
"Name": "My_CW_Loggroup",
"TimeoutInMinutes": 60,
"Parameters": {
"LogGroupName": "customer-testloggroup",
"LogStream1Name": "LogStream1",
"SubscriptionFilterPattern": "test",
"SubscriptionDestinationARN": "arn:aws:lambda:us-east-1:123456789012:function:test_lambda",
"MetricFilter1Name": "test_metric_filter1",
"MetricFilter1Namespace": "test_metric_filter1_namespace",
"MetricFilter1Pattern": "{$.eventType=\"test_event\"}",
"MetricFilter1Value": "10"
}
}
```
1. Output the JSON template for CreateRfc to a file in your current folder; example names it CwLGRfc.json:
```
aws amscm create-rfc --generate-cli-skeleton > CwLGRfc.json
```
1. Modify and save the CwLGRfc.json file. For example, you can replace the contents with something like this:
```
{
"ChangeTypeVersion": "1.0",
"ChangeTypeId": "ct-0cyqd7laxyhlm",
"Title": "CW-LG-RFC"
}
```
1. Create the RFC, specifying the CwLGRfc file and the execution parameters file:
```
aws amscm create-rfc --cli-input-json file://CwLGRfc.json --execution-parameters file://CwLGParams.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
To learn more about CloudWatch, see [Creating Amazon CloudWatch Alarms](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/AlarmThatSendsEmail.html).
## Execution Input Parameters
For detailed information about the execution input parameters, see [Schema for Change Type ct-0cyqd7laxyhlm](schemas.md#ct-0cyqd7laxyhlm-schema-section).
## Example: Required Parameters
```
{
"Description": "This is a test description",
"VpcId": "vpc-1234567890abcdef0",
"StackTemplateId": "stm-8ian3plt5a6jbv7jt",
"Name": "Test Stack",
"Tags": [
{
"Key": "foo",
"Value": "bar"
},
{
"Key": "testkey",
"Value": "testvalue"
}
],
"TimeoutInMinutes": 60,
"Parameters": {
"LogGroupName": "customer-testloggroup"
}
}
```
## Example: All Parameters
```
{
"Description": "This is a test description",
"VpcId": "vpc-1234567890abcdef0",
"StackTemplateId": "stm-8ian3plt5a6jbv7jt",
"Name": "Test Stack",
"Tags": [
{
"Key": "foo",
"Value": "bar"
},
{
"Key": "testkey",
"Value": "testvalue"
}
],
"TimeoutInMinutes": 60,
"Parameters": {
"LogGroupName":"customer-test",
"LogGroupRetentionInDays":"7",
"LogStream1Name":"logstream1",
"LogStream2Name":"logstream2",
"LogStream3Name":"logstream3",
"LogStream4Name":"logstream4",
"LogStream5Name":"logstream5",
"SubscriptionFilterIAMroleARN":"arn:aws:iam::123456789012:role/example-role",
"SubscriptionFilterPattern":"Error",
"SubscriptionDestinationARN":"arn:aws:kinesis:us-east-1:123456789012:stream/example-stream-name",
"MetricFilter1Name":"metricfilter1",
"MetricFilter1Namespace":"metricfilter1namespace",
"MetricFilter1Pattern":"Error",
"MetricFilter1Value":"10",
"MetricFilter1DefaultValue":"1",
"MetricFilter2Name":"metricfilter2",
"MetricFilter2Namespace":"metricfilter2namespace",
"MetricFilter2Pattern":"Error",
"MetricFilter2Value":"20",
"MetricFilter2DefaultValue":"1",
"MetricFilter3Name":"metricfilter3",
"MetricFilter3Namespace":"metricfilter3namespace",
"MetricFilter3Pattern":"Error",
"MetricFilter3Value":"30",
"MetricFilter3DefaultValue":"1",
"MetricFilter4Name":"metricfilter4",
"MetricFilter4Namespace":"metricfilter4namespace",
"MetricFilter4Pattern":"40",
"MetricFilter4Value":"2",
"MetricFilter4DefaultValue":"1",
"MetricFilter5Name":"metricfilter5",
"MetricFilter5Namespace":"metricfilter5namespace",
"MetricFilter5Pattern":"Error",
"MetricFilter5Value":"50",
"MetricFilter5DefaultValue":"1"
}
}
```
# GuardDuty IP Set \$1 Create (Managed Automation)
Use to create an Amazon GuardDuty IPSet instance which is a list of trusted IP addresses that have been whitelisted for highly secure communication with your AWS environment.
**Full classification:** Deployment \$1 Monitoring and notification \$1 GuardDuty IP set \$1 Create (managed automation)
## Change Type Details
****
| | |
| --- |--- |
| Change type ID | ct-08avsj2e9mc7g |
| Current version | 1.0 |
| Expected execution duration | 240 minutes |
| AWS approval | Required |
| Customer approval | Not required if submitter |
| Execution mode | Manual |
## Additional Information
### Create GuardDuty IP set (Managed Automation)
#### Creating an IP set for GuardDuty (Managed Automation) with the console
The following shows this change type in the AMS console.
![\[alt text not found\]](http://docs.aws.amazon.com/managedservices/latest/ctref/images/guiGuardDutyIpSetCreateRrCT.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.
#### Creating an IP set for GuardDuty (Managed Automation) 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 quotes 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-08avsj2e9mc7g" --change-type-version "1.0" --title "Create Amazon GuardDuty IP Set" --execution-parameters "{\"Activate\": true, \"DetectorId\": \"00000000000000000000000000000000\", \"Format\": \"TXT\", \"Name\": \"trusted-ips\", \"IpSet\": \"https://s3.us-west-2.amazonaws.com/bucket-name/my-object-key\", \"Region\": \"us-east-1\"}"
```
*TEMPLATE CREATE*:
1. Output the execution parameters JSON schema for this change type to a file; this example names it CreateGdIpSetParams.json.
```
aws amscm get-change-type-version --change-type-id "ct-08avsj2e9mc7g" --query "ChangeTypeVersion.ExecutionInputSchema" --output text > CreateGdIpSetParams.json
```
1. Modify and save the CreateGdIpSetParams file. For example, you can replace the contents with something like this:
```
{
"Activate": true,
"DetectorId": "00000000000000000000000000000000",
"Format": "TXT",
"Name": "trusted-ips",
"IpSet": "https://s3.us-west-2.amazonaws.com/bucket-name/my-object-key",
"Region": "us-east-1"
}
```
1. Output the RFC template JSON file to a file named CreateGdIpSetRfc.json:
```
aws amscm create-rfc --generate-cli-skeleton > CreateGdIpSetRfc.json
```
1. Modify and save the CreateGdIpSetRfc.json file. For example, you can replace the contents with something like this:
```
{
"ChangeTypeVersion": "1.0",
"ChangeTypeId": "ct-08avsj2e9mc7g",
"Title": "CREATE_GD_IP_SET"
}
```
1. Create the RFC, specifying the CreateGdIpSet Rfc file and the CreateGdIpSetParams file:
```
aws amscm create-rfc --cli-input-json file://CreateGdIpSetRfc.json --execution-parameters file://CreateGdIpSetParams.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
This is a manual change type (an AMS operator must review and run the CT), which means that the RFC can take longer to run and you might have to communicate with AMS through the RFC details page correspondance option. Additionally, if you schedule a manual change type RFC, be sure to allow at least 24 hours, if approval does not happen before the scheduled start time, the RFC is rejected automatically.
To learn more about Amazon GuardDuty and creating IP sets, see [Amazon Guard​Duty](https://aws.amazon.com/guardduty/) and [CreateIPSet](https://docs.aws.amazon.com/guardduty/latest/APIReference/API_CreateIPSet.html).
## Execution Input Parameters
For detailed information about the execution input parameters, see [Schema for Change Type ct-08avsj2e9mc7g](schemas.md#ct-08avsj2e9mc7g-schema-section).
## Example: Required Parameters
```
{
"Region": "us-east-1",
"Name": "Sample IPSet",
"IpSet": "https://s3.amazonaws.com/guarddutylists/sample.txt"
}
```
## Example: All Parameters
```
{
"Activate": true,
"DetectorId": "12abc34d567e8fa901bc2d34e56789f0",
"Region": "us-east-1",
"Name": "Sample IPSet",
"IpSet": "https://s3.amazonaws.com/guarddutylists/sample.txt",
"Format": "TXT",
"Priority": "Medium"
}
```
# GuardDuty Threat Intel Set \$1 Create (Managed Automation)
Use to create an Amazon GuardDuty ThreatIntelSet instance, which is a list of known malicious IP addresses that have been blacklisted for communication with your AWS environment.
**Full classification:** Deployment \$1 Monitoring and notification \$1 GuardDuty threat intel set \$1 Create (managed automation)
## Change Type Details
****
| | |
| --- |--- |
| Change type ID | ct-25v6r7t8gvkq5 |
| Current version | 1.0 |
| Expected execution duration | 240 minutes |
| AWS approval | Required |
| Customer approval | Not required if submitter |
| Execution mode | Manual |
## Additional Information
### Create GuardDuty Threat intel set (Managed Automation)
#### Creating a Threat intel set for GuardDuty (Managed Automation) with the console
The following shows this change type in the AMS console.
![\[alt text not found\]](http://docs.aws.amazon.com/managedservices/latest/ctref/images/guiGuardDutyThreatIntelSetCreateRrCT.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.
#### Creating a Threat intel set for GuardDuty (Managed Automation) 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 quotes 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-25v6r7t8gvkq5" --change-type-version "1.0" --title "Create Amazon GuardDuty Threat Intel Set" --execution-parameters "{\"Activate\": true, \"DetectorId\": \"00000000000000000000000000000000\", \"Format\": \"TXT\", \"Name\": \"blacklisted-ips\", \"ThreatIntelSet\": \"https://s3.us-west-2.amazonaws.com/bucket-name/my-object-key\", \"Region\": \"us-east-1\"}"
```
*TEMPLATE CREATE*:
1. Output the execution parameters JSON schema for this change type to a file; this example names it CreateGdThreatIntelSetParams.json.
```
aws amscm get-change-type-version --change-type-id "ct-25v6r7t8gvkq5" --query "ChangeTypeVersion.ExecutionInputSchema" --output text > CreateGdThreatIntelSetParams.json
```
1. Modify and save the CreateGdThreatIntelSetParams file. For example, you can replace the contents with something like this:
```
{
"Activate": true,
"DetectorId": "00000000000000000000000000000000",
"Format": "TXT",
"Name": "blacklisted-ips",
"ThreatIntelSet": "https://s3.us-west-2.amazonaws.com/bucket-name/my-object-key",
"Region": "us-east-1"
}
```
1. Output the RFC template JSON file to a file named CreateGdThreatIntelSetRfc.json:
```
aws amscm create-rfc --generate-cli-skeleton > CreateGdThreatIntelSetRfc.json
```
1. Modify and save the CreateGdThreatIntelSetRfc.json file. For example, you can replace the contents with something like this:
```
{
"ChangeTypeVersion": "1.0",
"ChangeTypeId": "ct-25v6r7t8gvkq5",
"Title": "CREATE_GD_THREAT_INTEL_SET"
}
```
1. Create the RFC, specifying the CreateGdIpSet Rfc file and the CreateGdThreatIntelSetParams file:
```
aws amscm create-rfc --cli-input-json file://CreateGdThreatIntelSetRfc.json --execution-parameters file://CreateGdThreatIntelSetParams.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
This is a manual change type (an AMS operator must review and run the CT), which means that the RFC can take longer to run and you might have to communicate with AMS through the RFC details page correspondance option. Additionally, if you schedule a manual change type RFC, be sure to allow at least 24 hours, if approval does not happen before the scheduled start time, the RFC is rejected automatically.
For more information about Amazon GuardDuty and creating Threat Intel sets, see [Amazon Guard​Duty](https://aws.amazon.com/guardduty/) and [CreateThreatIntelSet](https://docs.aws.amazon.com/guardduty/latest/APIReference/API_CreateThreatIntelSet.html).
## Execution Input Parameters
For detailed information about the execution input parameters, see [Schema for Change Type ct-25v6r7t8gvkq5](schemas.md#ct-25v6r7t8gvkq5-schema-section).
## Example: Required Parameters
```
{
"Region": "us-east-1",
"Name": "Sample Threat Intel Set",
"ThreatIntelSet": "https://s3.amazonaws.com/guarddutylists/sample.txt"
}
```
## Example: All Parameters
```
{
"Activate": true,
"DetectorId": "12abc34d567e8fa901bc2d34e56789f0",
"Region": "us-east-1",
"Name": "Sample Threat Intel Set",
"ThreatIntelSet": "https://s3.amazonaws.com/guarddutylists/sample.txt",
"Format": "TXT",
"Priority": "Medium"
}
```
# SNS \$1 Create (Topic and Subscription)
Create an SNS topic and up to five subscriptions.
**Full classification:** Deployment \$1 Monitoring and notification \$1 SNS \$1 Create (topic and subscription)
## Change Type Details
****
| | |
| --- |--- |
| Change type ID | ct-3dfnglm4ombbs |
| Current version | 1.0 |
| Expected execution duration | 60 minutes |
| AWS approval | Required |
| Customer approval | Not required |
| Execution mode | Automated |
## Additional Information
### Create SNS topic and subscription
#### Creating an SNS topic and subscription (up to 5) with the Console
Screenshot of this change type in the AMS console:
![\[Change type details for creating an SNS topic with ID, version, and execution mode.\]](http://docs.aws.amazon.com/managedservices/latest/ctref/images/guiSnsTopSubCreateCT.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.
#### Creating an SNS topic and subscription (up to 5) 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 quotes 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-3dfnglm4ombbs" --change-type-version "1.0" --title "CREATE_SNS_TOPIC" --execution-parameters "{\"Description\":\"SNS_TOPIC_DESCRIPTION\",\"VpcId\":\"VPC_ID\",\"Name\":\"SNS_TOPIC_NAME\",\"StackTemplateId\":\"stm-eakrsalqo9m62tpun\",\"TimeoutInMinutes\":60,\"Parameters\":{\"TopicName\":\"mytopic-cli\"}}"
```
*TEMPLATE CREATE*:
1. Output the execution parameters JSON schema for this change type to a file; this example names it CreateSnsTopicSubParams.json.
```
aws amscm get-change-type-version --change-type-id "ct-3dfnglm4ombbs" --query "ChangeTypeVersion.ExecutionInputSchema" --output text > CreateSnsTopicSubParams.json
```
1. Modify and save the CreateSnsTopicSubParams file. For example, you can replace the contents with something like this:
```
{
"Description": "SnsTopicSub-Create",
"VpcId": "VPC_ID",
"Name": "My-SnsTopicSub",
"Parameters":{
"TopicName": "mytopic-cli-all-params",
"DisplayName": "testsns",
"Subscription1Protocol": "email",
"Subscription1Endpoint": "abc@xyz.com",
"Subscription1RawMessageDelivery": "false",
"Subscription2Protocol": "sms",
"Subscription2Endpoint": "+61500444777",
"Subscription2RawMessageDelivery": "false",
"KmsMasterKeyId": "arn:aws:kms:us-east-1:123456789101:key/cfe0542d-3be9-4166-9eac-d0cd6af61445"
}
}
```
1. Output the RFC template JSON file to a file named CreateSnsTopicSubRfc.json:
```
aws amscm create-rfc --generate-cli-skeleton > CreateSnsTopicSubRfc.json
```
1. Modify and save the CreateSnsTopicSubRfc.json file. For example, you can replace the contents with something like this:
```
{
"ChangeTypeVersion": "1.0",
"ChangeTypeId": "ct-3dfnglm4ombbs",
"Title": "SnsTopicSub-Create-RFC"
}
```
1. Create the RFC, specifying the CreateSnsTopicSub Rfc file and the CreateSnsTopicSubParams file:
```
aws amscm create-rfc --cli-input-json file://CreateSnsTopicSubRfc.json --execution-parameters file://CreateSnsTopicSubParams.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
To learn more about AWS Simple Notification Service (SNS) and creating SNS topics and subscriptions, see [Amazon Simple Notification Service](https://aws.amazon.com/sns/). Also see [Getting Started with Amazon SNS](https://docs.aws.amazon.com/sns/latest/dg/sns-getting-started.html). For pricing information, see [Amazon SNS pricing](https://aws.amazon.com/sns/pricing/).
## Execution Input Parameters
For detailed information about the execution input parameters, see [Schema for Change Type ct-3dfnglm4ombbs](schemas.md#ct-3dfnglm4ombbs-schema-section).
## Example: Required Parameters
```
{
"Description" : "Creates SNS Topic using random Topic name with no input or parameter given.",
"VpcId" : "vpc-12345678901234567",
"Name" : "TestStack",
"StackTemplateId" : "stm-eakrsalqo9m62tpun",
"TimeoutInMinutes" : 60,
"Parameters" : { }
}
```
## Example: All Parameters
```
{
"Description" : "Creates just SNS Topic per the given name",
"VpcId" : "vpc-12345678",
"Name" : "TestStack",
"Tags" : [
{
"Key" : "foo",
"Value" : "bar"
}
],
"StackTemplateId" : "stm-eakrsalqo9m62tpun",
"TimeoutInMinutes" : 60,
"Parameters" : {
"TopicName" : "MySNSTopic",
"DisplayName" : "",
"Subscription1Endpoint" : "",
"Subscription1RawMessageDelivery" : "false",
"Subscription2Endpoint" : "",
"Subscription2RawMessageDelivery" : "false",
"Subscription3Endpoint" : "",
"Subscription3RawMessageDelivery" : "false",
"Subscription4Endpoint" : "",
"Subscription4RawMessageDelivery" : "false",
"Subscription5Endpoint" : "",
"Subscription5RawMessageDelivery" : "false",
"KmsMasterKeyId" : ""
}
}
```
# SQS \$1 Create
Use to create an Amazon Simple Queue Service instance for messages to be shared by system components.
**Full classification:** Deployment \$1 Monitoring and notification \$1 SQS \$1 Create
## Change Type Details
****
| | |
| --- |--- |
| Change type ID | ct-1vbv99ko7bsrq |
| Current version | 1.0 |
| Expected execution duration | 60 minutes |
| AWS approval | Required |
| Customer approval | Not required |
| Execution mode | Automated |
## Additional Information
### Create SQS queue
#### Creating an SQS queue with the Console
Screenshot of this change type in the AMS console:
![\[Change type details for creating an Amazon SQS instance, including description and execution mode.\]](http://docs.aws.amazon.com/managedservices/latest/ctref/images/guiSqsCreateCT.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.
#### Creating an SQS queue 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 quotes 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-1vbv99ko7bsrq" --change-type-version "1.0" --title "Create Amazon SQS Queue" --execution-parameters "{\"Description\": \"SQS-Queue-Create-RFC\", \"VpcId\": \"VPC_ID\", \"StackTemplateId\": \"stm-s1ejpr80000000000\", \"Name\": \"MySqsQueue\", \"Tags\": [{\"Key\": \"my-tag-1\", \"Value\": \"my-tag-value-1\"}, {\"Key\": \"my-tag-2\", \"Value\": \"my-tag-value-2\"}], \"TimeoutInMinutes\": 60, \"Parameters\": {\"SQSDelaySeconds\": 0, \"SQSMaximumMessageSize\": 262144, \"SQSMessageRetentionPeriod\": 345600, \"SQSQueueName\": \"MyQueueName\", \"SQSReceiveMessageWaitTimeSeconds\": 0, \"SQSVisibilityTimeout\": 60}}"
```
*TEMPLATE CREATE*:
1. Output the execution parameters JSON schema for this change type to a file; this example names it CreateSqsInstanceParams.json.
```
aws amscm get-change-type-version --change-type-id "ct-1vbv99ko7bsrq" --query "ChangeTypeVersion.ExecutionInputSchema" --output text > CreateSqsInstanceParams.json
```
1. Modify and save the CreateSqsInstanceParams file. For example, you can replace the contents with something like this:
```
{
"Description": "SQS-Queue-Create-RFC",
"VpcId": "VPC_ID",
"StackTemplateId": "stm-s1ejpr80000000000",
"Name": "MySqsQueue",
"Tags": [{
"Key": "my-tag-1",
"Value": "my-tag-value-1"
}, {
"Key": "my-tag-2",
"Value": "my-tag-value-2"
}],
"TimeoutInMinutes": 60,
"Parameters": {
"SQSDelaySeconds": 0,
"SQSMaximumMessageSize": 262144,
"SQSMessageRetentionPeriod": 345600,
"SQSQueueName": "MyQueueName",
"SQSReceiveMessageWaitTimeSeconds": 0,
"SQSVisibilityTimeout": 60
}
}
```
1. Output the RFC template JSON file to a file named CreateSqsInstanceRfc.json:
```
aws amscm create-rfc --generate-cli-skeleton > CreateSqsInstanceRfc.json
```
1. Modify and save the CreateSqsInstanceRfc.json file. For example, you can replace the contents with something like this:
```
{
"ChangeTypeVersion": "1.0",
"ChangeTypeId": "ct-1vbv99ko7bsrq",
"Title": "Sqs-Instance-Create-RFC"
}
```
1. Create the RFC, specifying the CreateSqsInstance Rfc file and the CreateSqsInstanceParams file:
```
aws amscm create-rfc --cli-input-json file://CreateSqsInstanceRfc.json --execution-parameters file://CreateSqsInstanceParams.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
To learn more about Amazon Simple Queue Service (SQS), see [Amazon Simple Queue Service](https://aws.amazon.com/sqs/).
## Execution Input Parameters
For detailed information about the execution input parameters, see [Schema for Change Type ct-1vbv99ko7bsrq](schemas.md#ct-1vbv99ko7bsrq-schema-section).
## Example: Required Parameters
```
{
"Description": "This is a test description",
"VpcId": "vpc-01234567890abcdef",
"StackTemplateId": "stm-s1ejpr80000000000",
"Name": "Test Stack",
"TimeoutInMinutes": 60,
"Parameters": {
"SQSQueueName": "mytestsqs"
}
}
```
## Example: All Parameters
```
{
"Description": "This is a test description",
"VpcId": "vpc-12345678",
"StackTemplateId": "stm-s1ejpr80000000000",
"Name": "Test Stack",
"Tags": [
{
"Key": "foo",
"Value": "bar"
},
{
"Key": "testkey",
"Value": "testvalue"
}
],
"TimeoutInMinutes": 60,
"Parameters": {
"SQSDelaySeconds": 0,
"SQSMaximumMessageSize": 262144,
"SQSMessageRetentionPeriod": 345600,
"SQSQueueName": "mytestsqs",
"SQSReceiveMessageWaitTimeSeconds": 0,
"SQSVisibilityTimeout": 0
}
}
```