AWS managedservices medium security documentation change
Summary
Added documentation for four new change types: Remediate DNS scavenging issue, Delete VPC route, Update parameter group of DB instance or cluster, and Replace Site-to-Site VPN tunnel. Includes detailed procedures, console screenshots, and CLI examples for each change type.
Security assessment
The 'Remediate DNS scavenging issue' change type directly addresses a security vulnerability related to DNS scavenging misconfigurations that could lead to DNS cache poisoning, DNS spoofing, or service disruption. DNS scavenging issues are known security concerns in Active Directory environments where stale records can be exploited. The documentation provides a specific remediation procedure using AWSManagedServices-UpdateClusterNodeRecordPermissions-Admin document, indicating this addresses a concrete security weakness.
Diff
diff --git a/managedservices/latest/ctexguide/review-walkthroughs.md b/managedservices/latest/ctexguide/review-walkthroughs.md index c4a286690..b703f85dc 100644 --- a//managedservices/latest/ctexguide/review-walkthroughs.md +++ b//managedservices/latest/ctexguide/review-walkthroughs.md @@ -5 +5 @@ -Create a DHCP option setCreate ELB Listener RuleUpdate VPC Endpoint PolicyDelete NAT gateway (Managed Automation)Update EC2 Instance Metadata Service (IMDS) Region SettingCreate a computer object's SPNDelete target groups (Managed Automation)Create application load balancer (ALB)Update application load balancer (ALB)Create listenerHigh availability one-tier stacks: CreatingCreate IAM entity or policy (Managed Automation)Continue rollback on custom CloudFormation stackManage the VPC Subnet IPv4 Address Auto AssigmentSchedule addDelete EBS snapshot (Managed Automation)Update SNS topicCreate an S3 access pointCreate Custom RDS Parameter GroupAdd event notification to an Amazon S3 bucketUpdate custom deny list for AMS Automated IAM ProvisioningMigrate AWS Managed Account DNS resolver to Route 53 for SALZ accounts (Managed Automation)Disassociate resolver rules from VPCUpdate Enhanced MonitoringAssociate VPC with Resolver RuleDeploy AMS pattern (Managed Automation)Share AWS KMS KeyCreate Active Directory TrustOverride Stack Access Duration (Managed automation)Enable automated IAM provisioning with read-write permissionsAdd VPC static route (Managed Automation)Create IAM entity or policyUpdate IAM entity or policyDelete IAM entity or policyUpdate detailed monitoringShare directoryUnshare directoryCreate VPC endpointUpdate RDS storageUpdate an RDS multi-AZ deploymentUpdate an RDS instance typeUpdate S3 bucket versioningUpdate S3 bucket encryptionUpdating an application account (Managed Automation)Associate private IP addresses (Managed Automation) ct-1pvlhug439gl2Create Amazon RDS option group (Managed Automation)Remove TGW static routeCreate for WIGS (Managed Automation)Modify EBS volumeUpdate AWS Backup plan (Managed Automation)Confirm offboardingManagement account: Offboard Application accountDeploy AMS Resource Scheduler SolutionUpdate AMS Resource Scheduler SolutionDelete or deactivate access keyCreate access keyEnable Detailed MonitoringUpdate the DeleteOnTermination option (Managed Automation)Update RDS maintainance window (Managed Automation)Update RDS performance insights (Managed Automation)Create security group (Managed Automation) +Remediate DNS scavenging issueDelete VPC routeUpdate parameter group of DB instance or clusterReplace Site-to-Site VPN tunnelCreate a DHCP option setCreate ELB Listener RuleUpdate VPC Endpoint PolicyDelete NAT gateway (Managed Automation)Update EC2 Instance Metadata Service (IMDS) Region SettingCreate a computer object's SPNDelete target groups (Managed Automation)Create application load balancer (ALB)Update application load balancer (ALB)Create listenerHigh availability one-tier stacks: CreatingCreate IAM entity or policy (Managed Automation)Continue rollback on custom CloudFormation stackManage the VPC Subnet IPv4 Address Auto AssigmentSchedule addDelete EBS snapshot (Managed Automation)Update SNS topicCreate an S3 access pointCreate Custom RDS Parameter GroupAdd event notification to an Amazon S3 bucketUpdate custom deny list for AMS Automated IAM ProvisioningMigrate AWS Managed Account DNS resolver to Route 53 for SALZ accounts (Managed Automation)Disassociate resolver rules from VPCUpdate Enhanced MonitoringAssociate VPC with Resolver RuleDeploy AMS pattern (Managed Automation)Share AWS KMS KeyCreate Active Directory TrustOverride Stack Access Duration (Managed automation)Enable automated IAM provisioning with read-write permissionsAdd VPC static route (Managed Automation)Create IAM entity or policyUpdate IAM entity or policyDelete IAM entity or policyUpdate detailed monitoringShare directoryUnshare directoryCreate VPC endpointUpdate RDS storageUpdate an RDS multi-AZ deploymentUpdate an RDS instance typeUpdate S3 bucket versioningUpdate S3 bucket encryptionUpdating an application account (Managed Automation)Associate private IP addresses (Managed Automation) ct-1pvlhug439gl2Create Amazon RDS option group (Managed Automation)Remove TGW static routeCreate for WIGS (Managed Automation)Modify EBS volumeUpdate AWS Backup plan (Managed Automation)Confirm offboardingManagement account: Offboard Application accountDeploy AMS Resource Scheduler SolutionUpdate AMS Resource Scheduler SolutionDelete or deactivate access keyCreate access keyEnable Detailed MonitoringUpdate the DeleteOnTermination option (Managed Automation)Update RDS maintainance window (Managed Automation)Update RDS performance insights (Managed Automation)Create security group (Managed Automation) @@ -10,0 +11,8 @@ Create a DHCP option setCreate ELB Listener RuleUpdate VPC Endpoint PolicyDelete + * Remediate DNS scavenging issue + + * Delete VPC route + + * Update parameter group of DB instance or cluster + + * Replace Site-to-Site VPN tunnel + @@ -135,0 +144,377 @@ Create a DHCP option setCreate ELB Listener RuleUpdate VPC Endpoint PolicyDelete +## Remediate DNS scavenging issue + +The following shows this change type in the AMS 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**. + + 2. 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. + + 3. 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. + + 4. 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**. + + 5. 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. + + + + +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. + + 2. 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 protected]\"]}}"` 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-3k67klld7cimj" --change-type-version "1.0" --title "Remediate DNS scavenging issue" --execution-parameters "{\"DocumentName\":\"AWSManagedServices-UpdateClusterNodeRecordPermissions-Admin\",\"Parameters\":{\"ClusterCNOName\":[\"CLUSTER_CNO_NAME\"],\"ClusterNodeComputerNames\":[\"NODE_NAME_1\",\"NODE_NAME_2\"],\"ClusterVCONames\":[\"VCO_NAME_1\",\"VCO_NAME_2\"]},\"Region\":\"us-east-1\"}" + +_TEMPLATE CREATE_ : + + 1. Output the execution parameters JSON schema for this change type; this example names it RemediateDnsScavengingParams.json: + + aws amscm get-change-type-version --change-type-id "ct-3k67klld7cimj" --query "ChangeTypeVersion.ExecutionInputSchema" --output text > RemediateDnsScavengingParams.json + + 2. Modify and save the execution parameters JSON file. For example, you can replace the contents with something like this: + + { + "DocumentName": "AWSManagedServices-UpdateClusterNodeRecordPermissions-Admin", + "Region": "us-east-1", + "Parameters": { + "ClusterCNOName": ["CLUSTER_CNO_NAME"], + "ClusterNodeComputerNames": ["NODE_NAME_1", "NODE_NAME_2"], + "ClusterVCONames": ["VCO_NAME_1", "VCO_NAME_2"] + } + } + + 3. Output the RFC template JSON file; this example names it RemediateDnsScavengingRfc.json: + + aws amscm create-rfc --generate-cli-skeleton > RemediateDnsScavengingRfc.json + + 4. Modify and save the RemediateDnsScavengingRfc.json file. For example, you can replace the contents with something like this: + + { + "ChangeTypeVersion" : "1.0", + "ChangeTypeId" : "ct-3k67klld7cimj", + "Title" : "Remediate DNS scavenging issue" + } + + 5. Create the RFC, specifying the RemediateDnsScavengingRfc file and the RemediateDnsScavengingParams file: + + aws amscm create-rfc --cli-input-json file://RemediateDnsScavengingRfc.json --execution-parameters file://RemediateDnsScavengingParams.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. + + + + +## Delete VPC route + +The following shows this change type in the AMS 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**. + + 2. 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. + + 3. 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. + + 4. 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**. + + 5. 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. + + + + +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. + + 2. 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 protected]\"]}}"` 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-1nusoameibz5p" --change-type-version "1.0" --title "Delete VPC route" --execution-parameters "{\"DocumentName\":\"AWSManagedServices-DeleteRoute\",\"Region\":\"us-east-1\",\"Parameters\":{\"RouteTableId\":\"rtb-1234abcd12345abcd\",\"DestinationCidrBlock\":\"10.0.0.0/8\"}}" + +_TEMPLATE CREATE_ : + + 1. Output the execution parameters JSON schema for this change type; this example names it DeleteVPCRouteParams.json: + + aws amscm get-change-type-version --change-type-id "ct-1nusoameibz5p" --query "ChangeTypeVersion.ExecutionInputSchema" --output text > DeleteVPCRouteParams.json + + 2. Modify and save the execution parameters JSON file. For example, you can replace the contents with something like this: + + { + "DocumentName": "AWSManagedServices-DeleteRoute", + "Region": "us-east-1", + "Parameters": { + "RouteTableId": "rtb-1234abcd12345abcd", + "DestinationCidrBlock": "10.0.0.0/8", + "DestinationPrefixListId": "pl-abcd1234" + } + } + + 3. Output the RFC template JSON file; this example names it DeleteVPCRouteRfc.json: + + aws amscm create-rfc --generate-cli-skeleton > DeleteVPCRouteRfc.json + + 4. Modify and save the DeleteVPCRouteRfc.json file. For example, you can replace the contents with something like this: + + { + "ChangeTypeVersion" : "1.0", + "ChangeTypeId" : "ct-1nusoameibz5p", + "Title" : "Delete VPC route" + } + + 5. Create the RFC, specifying the DeleteVPCRouteRfc file and the DeleteVPCRouteParams file: +