id
stringlengths 8
78
| source
stringclasses 743
values | chunk_id
int64 1
5.05k
| text
stringlengths 593
49.7k
|
|---|---|---|---|
ams-ug-195 | ams-ug.pdf | 195 | AWS Managed Services FAQs Common questions and answers: Q: How do I request access to AWS X-Ray in my AMS account? Request access by submitting a Management | AWS service | Self-provisioned service | Add (ct-1w8z66n899dct) change type. This RFC provisions the following IAM role to your account: customer_xray_console_role. After it's provisioned in your account, you must onboard the role in your federation solution. Additionally, you must have the customer_xray_daemon_write_instance_profile to push data from your Amazon EC2 instances to X-Ray. This instance profile is created when you receive the customer_xray_console_role. You can submit a service request to AMS Operations to assign the customer_xray_daemon_write_policy to the existing instance profile, or you can use the instance profile that is created when AMS Operations enables X-Ray for you. Q: What are the restrictions to using AWS X-Ray in my AMS account? Full functionality of AWS X-Ray is available in your AMS account except for encryption with AWS KMS key (KMS key). AWS X-Ray encrypts all trace data by default. By default, X-Ray encrypts traces and related data at rest. If you need to encrypt data at rest with a key, you can choose either AWS- managed KMS key (aws/xray) or KMS Customer-Managed key. For KMS Customer-Managed key for X-Ray encryption, submit a Management | Other | Other | Create change type (ct-1e1xtak34nx76). Q: What are the prerequisites or dependencies to using AWS X-Ray in my AMS account? AWS X-Ray has a dependency on Amazon S3, CloudWatch, and CloudWatch Logs, which are already implemented in AMS accounts. Transitive dependencies vary based on data sources and other AWS service AWS X-Ray that features may be interacting with (for example, Amazon Redshift, Amazon RDS, Athena). AWS X-Ray Version May 08, 2025 513 AMS Advanced User Guide AMS Advanced Concepts and Procedures Use AMS SSP to provision VM Import/Export in your AMS account Use AMS Self-Service Provisioning (SSP) mode to access VM Import/Exportcapabilities directly in your AMS managed account. VM Import/Export enables you to easily import virtual machine images from your existing environment to Amazon EC2 instances and export them back to your on- premises environment. This offering allows you to leverage your existing investments in the virtual machines that you have built to meet your IT security, configuration management, and compliance requirements by bringing those virtual machines into Amazon EC2 as ready-to-use instances. You can also export imported instances back to your on-premises virtualization infrastructure, allowing you to deploy workloads across your IT infrastructure. To learn more, see VM Import/Export. VM Import/Export in AWS Managed Services FAQs Common questions and answers: Q: How do I request access to VM Import/Export in my AMS account? Request access to VM Import/Export by submitting an RFC with the Management | AWS service | Self-provisioned service | Add change type (ct-1w8z66n899dct). This RFC provisions the following IAM policy to your account: customer_vmimport_policy. After it's provisioned in your account, you must onboard the role in your federation solution. An additional role, the VM Import/Export Service role, is required for the service to perform actions in your account. Q: What are the restrictions to using VM Import/Export in my AMS account? • Functionality to import custom machine images and data volumes is both available in AMS VM Import/Export. However, permissions to S3 have been scoped down to limit actions to buckets matching the name customer-vmimport-* in order to limit access to information within the account. • Image and snapshot import is supported in AMS VM Import/Export. However, instance import and instance export functionality is not available due to security measures. • Additionally, export functionality has been disabled to mitigate the risk of exporting restricted and sensitive data. Q: What are the prerequisites or dependencies to using VM Import/Export in my AMS account? VM Import/Export Version May 08, 2025 514 AMS Advanced User Guide AMS Advanced Concepts and Procedures • You must provide a supported disk image to import into the AWS environment. For information, see VM Import/Export Requirements. • Note: VM Import/Export is not accessible through the AWS console. The service can only be accessed through the AWS CLI, AWS Tools for PowerShell, and the AWS SDKs. A VM Import/ Export enabled role must be requested by an AMS RFC (Management | Other | Other | Create), and then you have to access the service directly with the previously mentioned tools. Alternatively, you can request an instance profile by request for change (RFC, ct-19jq3ulr3g9zg) through which the tools can perform commands from an instance. Customer Managed mode AWS Managed Services (AMS) Customer Managed mode provides a governance model that is flexible and can be adapted to your requirements. This can be considered a fallback option for services and applications that AMS is unable to operate for you. AMS does not operate infrastructure hosted in accounts created under this mode. However, you can |
ams-ug-196 | ams-ug.pdf | 196 | Other | Other | Create), and then you have to access the service directly with the previously mentioned tools. Alternatively, you can request an instance profile by request for change (RFC, ct-19jq3ulr3g9zg) through which the tools can perform commands from an instance. Customer Managed mode AWS Managed Services (AMS) Customer Managed mode provides a governance model that is flexible and can be adapted to your requirements. This can be considered a fallback option for services and applications that AMS is unable to operate for you. AMS does not operate infrastructure hosted in accounts created under this mode. However, you can leverage centralized multi-account management in this mode. The following Multi-Account Landing Zone features can be leveraged in this mode: • Automated Account deployment • Connectivity through Transit Gateway in networking account • AMS Config Rules library • Store copies of logs in logging account • Aggregation of customer managed Guard Duty alerts to Security account • Consolidated Billing • Enablement of custom Service Control Policies. For example: If you want to run workloads on Ubuntu Pro, which is not an Operating System managed by AMS, you could use a customer managed account for hosting it. You can also consolidate workloads through customer managed accounts, to take advantage of the bulk discount on Reserved Instances/Sharing Plans available through sharing across an AWS organization. Customer Managed mode Version May 08, 2025 515 AMS Advanced User Guide AMS Advanced Concepts and Procedures Getting started with Customer Managed mode The AMS Customer Managed mode is available through a special multi-account landing zone Application account. For details, including how to create a Customer Managed Application account, see Customer Managed application accounts. AMS and AWS Service Catalog Service Catalog in AWS Managed Services (AMS) allows organizations to create and manage catalogs of AWS information technology (IT) services and enables IT administrators to create, manage, and distribute catalogs of approved products to end users in their accounts, who can then access the products they need in a personalized portal of services. Administrators can control which users have access to each product to enforce compliance with organizational business policies. Administrators can also set up roles so that end users only require IAM access to Service Catalog in order to deploy approved resources. Service Catalog allows your organization to benefit from increased agility and reduced costs because end users can find and launch only the products they need from a catalog that you control. Service Catalog provides you with an alternative to the AMS request for change (RFC) process for provisioning and updating resources in your AMS managed account(s). AMS manages all of the infrastructure operations tasks needed to run AWS at scale for all infrastructure resources provisioned through Service Catalog including security, compliance, provisioning, availability, patch, monitoring, alerting, reporting, incident response, and cost optimization. Utilizing Service Catalog in your AMS managed account provides you with a mechanism to centrally manage commonly deployed IT services and helps you achieve consistent governance while enabling users to quickly deploy only the approved IT services they need into their managed environments. Getting started with Service Catalog To get started with Service Catalog in AMS, submit a service request through the AMS console to request access to Service Catalog. Upon submission of the request, three IAM roles will be deployed into your account(s) along with an AMS managed stack containing the CloudFormation macro that invokes the AMS Transform (described previously) so we can register the products in our systems, and to perform operations against the infrastructure provisioned through Service Catalog. The three IAM roles deployed include a role for IT admins to manage products as Service Catalog admins; a role for application owners and end-users to configure, launch, and manage Getting started with Customer Managed mode Version May 08, 2025 516 AMS Advanced User Guide AMS Advanced Concepts and Procedures products; and a role that will be used as a launch constraint, that defines the permissions that Service Catalog will use while launching or updating the your product. Service Catalog in AMS before you begin Does Service Catalog replace the existing AMS request for change (RFC) process? In accounts where Service Catalog is enabled, it will act as the change management system in which you provision and update IT services in your AMS account through your predefined product catalog; AMS will provide a default portfolio/product catalog, and your IT admins can create and configure your own. Service Catalog will only acknowledge stacks provisioned through Service Catalog. Likewise, services provisioned through Service Catalog will not be modifiable through the AMS RFC process as modification outside of Service Catalog will drift the stack from the approved product configuration. Can I see stacks provisioned through service catalog in the AMS Console? Yes. You can view all stacks provisioned through service catalog in the AMS console. Stacks |
ams-ug-197 | ams-ug.pdf | 197 | which you provision and update IT services in your AMS account through your predefined product catalog; AMS will provide a default portfolio/product catalog, and your IT admins can create and configure your own. Service Catalog will only acknowledge stacks provisioned through Service Catalog. Likewise, services provisioned through Service Catalog will not be modifiable through the AMS RFC process as modification outside of Service Catalog will drift the stack from the approved product configuration. Can I see stacks provisioned through service catalog in the AMS Console? Yes. You can view all stacks provisioned through service catalog in the AMS console. Stacks provisioned through service catalog are easily identifiable by the stack ID of "SC-". Although stacks are viewable in the AMS console you will not be able to update through the AMS RFC process. Access to the AMS change management system (RFCs) is limited to access request, patch orchestration and back-up RFCs only. If I provision and/or update a stack through Service Catalog will there be a corresponding RFC in the AMS Console? The only RFC that will show in the AMS console is an RFC to register the stack with AMS when a stack is initially provisioned. This RFC is filed automatically by the AMS validation process that is triggered when a stack is launched through Service Catalog. All other provisioning and changes are tracked directly in Service Catalog and are viewable in the Service Catalog console. Furthermore, you can use the Provisioned Product Plan feature in Service Catalog to view the list of changes that will be made to the resources in advance of provisioning or updating the product. Do I have to do anything specific for provisioning products in my AMS managed account? Yes. All Service Catalog products provisioned in AMS accounts must contain this line of JSON in the CFN template that defines that product: "Transform":{"Name":"AmsStackTransform","Parameters":{"StackId": {"Ref":"AWS::StackId"}}} Service Catalog in AMS before you begin Version May 08, 2025 517 AMS Advanced User Guide AMS Advanced Concepts and Procedures This snippet of CloudFormation code triggers the AMS validations required before the resource can be provisioned in your AMS managed account. It is your responsibility to include this line of code as part of the product definition. If it is not included, provisioning will fail and the following error message will be displayed: "Failed to create product. This account is managed by AMS. All products in AMS accounts must have the AMS Transform code in the template." Is there any Service Catalog functionality not available and/or limited for AMS customers at launch? Yes, the following SC features are not available for AMS customers at initial launch: • Account Creation through Service Catalog • Ability to launch all AWS Services through Service Catalog into an AMS-managed account. AWS Service availability is limited to AMS supported services (managed and self-provisioned). For more information on AMS-supported services, see the AMS service description. • Service Catalog IT service manager (ITSM) connectors will not communicate with AMS incident reports, and service requests. • Ability to leverage Service Catalog quick starts and reference architectures without modification. Remember that Service Catalog products for AMS accounts must contain this line of JSON code: "Transform":{"Name":"AmsStackTransform","Parameters":{"StackId": {"Ref":"AWS::StackId"}}} in the CNF template. Note that this line is not part of a typical AWS CloudFormation template and must be explicitly added. • Terraform is not currently supported by AMS for provisioning Service Catalog products. • AWS CFN stacksets are not supported in AMS. • You cannot create custom IAM roles. • Service Actions are limited to: • AWS-RebootRdsInstance • AWS-RestartEC2Instance • AWS-StartEC2Instance • AWS-StartRdsInstance • AWS-StopEC2Instance • AWS-StopRdsInstance Service Catalog in AMS before you begin Version May 08, 2025 518 AMS Advanced User Guide AMS Advanced Concepts and Procedures • AWS-CreateImage • AWS-CreateRdsSnapshot • AWS-CreateSnapshot Note When creating service actions, you can configure the execution role to be the end user's permissions, the launch role, or a custom IAM role of your choosing. The selected execution role must have sufficient permissions to perform the service action, and have a TrustPolicy that allows it to be assumed by Service Catalog, otherwise that service action will fail at execution time. We recommend using the AWSManagedServicesServiceCatalogLaunchRole, which has the correct permissions and trust policy to be used as a service action. What will I still need to use the AMS RFC system for? At general availability (GA) you will still need to use RFCS to run the following actions: • Configuring Patch Orchestrator • Configuring Back up policies • Requesting instance access • Creating and assigning security groups that fall outside AMS guidelines. • Performing workload ingest (WIGS) • Creating IAM roles Can I use the Service Catalog CLI to access Service Catalog in my AMS managed account? Yes, Service Catalog APIs are available and enabled through the CLI. Actions from the management of |
ams-ug-198 | ams-ug.pdf | 198 | to be used as a service action. What will I still need to use the AMS RFC system for? At general availability (GA) you will still need to use RFCS to run the following actions: • Configuring Patch Orchestrator • Configuring Back up policies • Requesting instance access • Creating and assigning security groups that fall outside AMS guidelines. • Performing workload ingest (WIGS) • Creating IAM roles Can I use the Service Catalog CLI to access Service Catalog in my AMS managed account? Yes, Service Catalog APIs are available and enabled through the CLI. Actions from the management of Service Catalog artifacts through the provisioning and terminating of those artifacts, are available. For more information, see AWS Service Catalog Resources, or download the latest AWS SDK or CLI. Who creates, manages, and distributes customers' catalogs of approved products? The customer's catalog administrator and/or IT administrator, or assigned resource, is responsible for the management of your Service Catalog catalogs and approved products. Can I use AMS AMIs? AMS AMIs vended after March 2020 can be deployed through AWS Service Catalog. Service Catalog in AMS before you begin Version May 08, 2025 519 AMS Advanced User Guide AMS Advanced Concepts and Procedures How do I migrate to AMS using Service Catalog? To migrate your workload to AMS using Service Catalog you begin by following the Workload Ingest (WIGs) process to create an AMI in AMS. You use the AMI produced by WIGS to create a product in Service Catalog. How to do this is detailed in AWS Service Catalog - Getting Started. Service Catalog in AMS before you begin Version May 08, 2025 520 AMS Advanced User Guide AMS Advanced Concepts and Procedures Finding the data you need (SKMS), AMS Finding the data you need when using your AWS Managed Services (AMS) accounts calls on the AMS service knowledge management, or SKMS, system. AMS. SKMS stands for service knowledge management system and refers to all information related to the AWS Managed Services (AMS) service for a customer. AMS has an SKMS API for finding data. Topics • What Is service knowledge management? • Finding VPC IDs in AMS • Finding subnet IDs in AMS • Find AMI IDs, AMS • Find security group (SG) IDs, AMS • Find IAM entities in AMS • Find stack IDs in AMS • Find instance IDs or IP addresses in AMS • Find Amazon Resource Names (ARNs) in AMS • Find resources by ARN in AMS • Find AMS account settings What Is service knowledge management? Service knowledge management is the store of all information on your AMS account. Information about the following is obtained from the AMS service knowledge management system (SKMS), through the AMS SKMS API or through the AMS Console: • VPCs • Managed subnets • Stacks and stack components, including Amazon EC2 instances and other resources • Amazon Machine Images (AMIs) What Is service knowledge management? Version May 08, 2025 521 AMS Advanced User Guide AMS Advanced Concepts and Procedures You can use information from the SKMS to understand the infrastructure under management and as input to change management and service requests to create, change, or remove infrastructure. Note All AMS SKMS API calls are recorded in AWS CloudTrail. Access the SKMS through the AMS SKMS API, which provides operations for discovering information about an environment (VPCs and subnets) and the application resources (stacks, Amazon EC2 instances, and instance images or AMIs) that can be deployed there. VPCs and instance images are set up in an account, with the necessary access permissions, during onboarding. After they have been established, you can use the change management system to populate the VPCs with working stacks. Finding VPC IDs in AMS A virtual private cloud (VPC) has one or more subnets. In AMS your VPC is in an AWS Region and you have private and public subnets. See also Finding subnet IDs in AMS. Some CTs require the VpcId. To find a VPC ID, you can use either the AMS console or API/CLI. AMS Console: In the navigation pane, select VPCs and the relevant VPC. The VPC details page for the selected VPC opens with information including the VPC ID. AMS SKMS API ListVpcSummaries or CLI: Note The AMS CLI must be installed for these commands to work. To install the AMS API or CLI, go to the AMS console Developers Resources page. For reference material on the AMS CM API or AMS SKMS API, see the AMS Information Resources section in the User Guide. You may need to add a --profile option for authentication; for example, aws amsskms ams-cli-command --profile SAML. You may also need to add the --region option as Find VPC IDs Version May 08, 2025 522 AMS Advanced User Guide AMS Advanced Concepts and Procedures all AMS commands run out |
ams-ug-199 | ams-ug.pdf | 199 | or CLI: Note The AMS CLI must be installed for these commands to work. To install the AMS API or CLI, go to the AMS console Developers Resources page. For reference material on the AMS CM API or AMS SKMS API, see the AMS Information Resources section in the User Guide. You may need to add a --profile option for authentication; for example, aws amsskms ams-cli-command --profile SAML. You may also need to add the --region option as Find VPC IDs Version May 08, 2025 522 AMS Advanced User Guide AMS Advanced Concepts and Procedures all AMS commands run out of us-east-1; for example aws amscm ams-cli-command -- region=us-east-1. Note The AMS API/CLI (amscm and amsskms) endpoints are in the AWS N. Virginia Region, us-east-1. Depending on how your authentication is set, and what AWS Region your account and resources are in, you may need to add --region us-east-1 when issuing commands. You may also need to add --profile saml, if that is your authentication method. 1. In the following examples, the first command requests a list of summaries for all VPCs in the account. The second command requests the list of VPCs, with a query filter to list only those VPCs created in 2016, and output the CreatedTime, VpcId, and Name. Note You can obtain the AMS SKMS CLI through the Developer's Resources page in the AMS console. aws amsskms list-vpc-summaries --output table ----------------------------------------------------- | ListVPCSummaries | +---------------------------------------------------+ | VPCSummaries | |+------------------+-------------------------------| | CreatedTime | 2016-01-15T18:50:11Z | | VpcId | vpc-01234567890abcdef | | LastModifiedTime| 2016-01-15T18:50:11Z | | Name | 952444781316-initial-vpc | |+------------------+-------------------------------| | Visibility | |+------------------+-------------------------------| | Id | PrivateAndPublic | | Name | PrivateAndPublic | Find VPC IDs Version May 08, 2025 523 AMS Advanced User Guide AMS Advanced Concepts and Procedures |+------------------+-------------------------------| 2. This time with a query: aws amsskms list-VPC-summaries --query "VPCSummaries[? starts_with(@.CreatedTime,to_string(`2016`))].[CreatedTime, VpcId, Name]" --output table ------------------------------------------------------------------------- | ListVPCSummaries | +---------------------+-----------------------+--------------------------+ |2016-01-15T18:50:11Z | vpc-01234567890abcdef | 952444781316-initial-VPC | +---------------------+-----------------------+--------------------------+ Finding subnet IDs in AMS Several resources require that you specify a subnet, or list of subnets, at configuration time. To find subnets, you can use either the AMS console or AMS SKMS API/CLI. Note that the AMS SKMS API/ CLI is private and must be installed before you can use it. AMS Console: 1. In the navigation pane, select VPCs and the relevant VPC. The VPC details page for the selected VPC opens with a table of subnets, click a subnet ID to open the details page and find the ID. AMS SKMS API ListSubnetSummaries or CLI: Note The AMS CLI must be installed for these commands to work. To install the AMS API or CLI, go to the AMS console Developers Resources page. For reference material on the AMS CM API or AMS SKMS API, see the AMS Information Resources section in the User Guide. You may need to add a --profile option for authentication; for example, aws amsskms ams-cli-command --profile SAML. You may also need to add the --region option as all AMS commands run out of us-east-1; for example aws amscm ams-cli-command -- region=us-east-1. Find subnet IDs Version May 08, 2025 524 AMS Advanced User Guide AMS Advanced Concepts and Procedures Note The AMS API/CLI (amscm and amsskms) endpoints are in the AWS N. Virginia Region, us-east-1. Depending on how your authentication is set, and what AWS Region your account and resources are in, you may need to add --region us-east-1 when issuing commands. You may also need to add --profile saml, if that is your authentication method. To find the subnets for your VPC, you can search with the list-subnet-summaries command as shown. Note If you're looking for subnets that are not in an AMS account, you can try aws ec2 describe-subnets --region us-west-2. 1. The SKMS API/CLI ListSubnetSummaries operation: A simple list: aws amsskms list-subnet-summaries Output to a table: aws amsskms list-subnet-summaries --output table 2. The SKMS API ListSubnetSummaries operation has parameters to narrow the results based on visibility. In addition, you can Filter results based on name. If you're using the CLI, you can also use the --query option to narrow the output or search on a portion of a value. For example, to find all of the subnets for a particular VPC, you can use this command: aws amsskms list-subnet-summaries --query "SubnetSummaries.sort_by(@,&Visibility.Name)[].[Visibility.Name,SubnetId,Name]" -- output table Which returns something like this: Find subnet IDs Version May 08, 2025 525 AMS Advanced User Guide AMS Advanced Concepts and Procedures -------------------------------------------------------------------- | ListSubnetSummaries | +---------+------------ -------+---------------------------+ | Private| subnet-01234567890abcdef | Demo Deployment Zone #1 | | Private| subnet-01234567890abcdef | Demo Deployment Zone #1 | | Public | subnet-01234567890abcdef | Demo DMZ #1 | | Public | subnet-01234567890abcdef | Demo DMZ #1 | +---------+---------- ---------+---------------------------+ For information about using CLI queries, see How to Filter the Output with the --query Option and the |
ams-ug-200 | ams-ug.pdf | 200 | a particular VPC, you can use this command: aws amsskms list-subnet-summaries --query "SubnetSummaries.sort_by(@,&Visibility.Name)[].[Visibility.Name,SubnetId,Name]" -- output table Which returns something like this: Find subnet IDs Version May 08, 2025 525 AMS Advanced User Guide AMS Advanced Concepts and Procedures -------------------------------------------------------------------- | ListSubnetSummaries | +---------+------------ -------+---------------------------+ | Private| subnet-01234567890abcdef | Demo Deployment Zone #1 | | Private| subnet-01234567890abcdef | Demo Deployment Zone #1 | | Public | subnet-01234567890abcdef | Demo DMZ #1 | | Public | subnet-01234567890abcdef | Demo DMZ #1 | +---------+---------- ---------+---------------------------+ For information about using CLI queries, see How to Filter the Output with the --query Option and the query language reference, JMESPath Specification. 3. If you have multiple VPCs, include a VPC filter in the command, and then run the command for each VPC. For example: list-subnet-summaries --filter Attribute=VpcId,Value=vpc-xxxxxxxx --query "SubnetSummaries.sort_by(@,&Visibility.Name)[].[Visibility.Name,SubnetId,Name]" -- output table 4. In AWS, use describe-subnets. For information about using CLI queries, see How to Filter the Output with the --query Option and the query language reference, JMESPath Specification.. Subnet names Your AMS subnets are created automatically after input is gathered from you and added to the system. AMS uses a formula to create your subnet names: AACCOUNT_ID-SUBNET-TYPE-AZ- IDENTIFIER. The subnet type would be either dmz, shared-services, or customer- application. Should you have more than one customer-application subnet, an optional identifier may be added to the subnet name, after the account ID, to indicated that the subnet is an "additional" or "reserved" subnet. Find AMI IDs, AMS An Amazon Machine Image, or AMI, is a template for Amazon EC2 instances, created from an Amazon EC2 instance. AWS provides updated AMIs (with patches, for example) every month; however, AWS Managed Services (AMS) requires AMIs that have been modified for AMS use. AMS releases new AMIs that you can use shortly after Patch Tuesday every month. Find AMI IDs Version May 08, 2025 526 AMS Advanced User Guide AMS Advanced Concepts and Procedures Amazon Machine Images (AMIs) are instance configuration templates that are used to create EC2 instances in AWS. AMS requires that specific AMIs be used for AMS-managed resources. The change types for creating EC2 instances and EC2 Auto Scaling groups require that you specify an AMI for AMS to use as the basis for the instances that the change type creates. AMS recommends that you always select the most recent AMI available to you. To learn more about AWS AMIs, see AWS AMI Design. When creating an Amazon EC2 stack or Amazon EC2 Auto Scaling group for your AMS account, you must specify an AMI by AmiId. You're limited to AMIs that begin with "customer-" and we recommend that you always choose the most recent AMI. To find the most recent AMI for your account, you can search with an AMS SKMS CLI command or use the AMS console details page for relevant VPC: • Use the AMS console: Available AMIs are listed on the AMI page in the AMS console. Select from AMIs with names that begin with "customer-". • Use the AMS SKMS API/CLI ListAmis operation. Note The AMS CLI must be installed for these commands to work. To install the AMS API or CLI, go to the AMS console Developers Resources page. For reference material on the AMS CM API or AMS SKMS API, see the AMS Information Resources section in the User Guide. You may need to add a --profile option for authentication; for example, aws amsskms ams-cli-command --profile SAML. You may also need to add the -- region option as all AMS commands run out of us-east-1; for example aws amscm ams-cli-command --region=us-east-1. Here is a CLI example with a query option that restricts the results to customer AMIs: aws amsskms list-amis --vpc-id VPC_ID --query "Amis.sort_by(@,&Name)[? starts_with(Name,'customer')].[Name,AmiId]" --output table This example uses the filter option with the query option to find Windows AMIs that start with "customer": Find AMI IDs Version May 08, 2025 527 AMS Advanced User Guide AMS Advanced Concepts and Procedures aws amsskms list-amis --vpc-id VPC_ID --query "Amis.sort_by(@,&Name)[? starts_with(Name,'customer')].[Name,AmiId]" --filter Attribute=Platform,Value=windows --output table • For information about using CLI queries, see How to Filter the Output with the --query Option and the query language reference, JMESPath Specification. Find security group (SG) IDs, AMS Amazon EC2 create and OpenSearch create domain CTs require a security group ID. This will be in the form sg-02ce123456e7893c7. Your account has at least two default security groups; see Security groups. Additionally, you may have security groups that you created for specific purposes. To discover your security groups: • AWS Console: Use the EC2 or VPC console to view all security groups for the selected VPC. • API/CLI (when logged into your AMS account): List your security groups: aws ec2 describe-security-groups Find IAM entities in AMS Your account has default IAM Roles and Policies; see IAM user role in AMS and default IAM |
ams-ug-201 | ams-ug.pdf | 201 | OpenSearch create domain CTs require a security group ID. This will be in the form sg-02ce123456e7893c7. Your account has at least two default security groups; see Security groups. Additionally, you may have security groups that you created for specific purposes. To discover your security groups: • AWS Console: Use the EC2 or VPC console to view all security groups for the selected VPC. • API/CLI (when logged into your AMS account): List your security groups: aws ec2 describe-security-groups Find IAM entities in AMS Your account has default IAM Roles and Policies; see IAM user role in AMS and default IAM instance profiles; see EC2 IAM instance profile with default policies. To discover your IAM roles and policies: • Console: Use the IAM console to view all IAM policies and roles for your account. • API/CLI (when logged into your AMS account): Note The AMS CLI must be installed for these commands to work. To install the AMS API or CLI, go to the AMS console Developers Resources page. For reference material on the AMS CM API or AMS SKMS API, see the AMS Information Resources section in the User Guide. You may need to add a --profile option for authentication; for example, aws amsskms ams-cli-command --profile SAML. You may also need to add the -- Find security group (SG) IDs Version May 08, 2025 528 AMS Advanced User Guide AMS Advanced Concepts and Procedures region option as all AMS commands run out of us-east-1; for example aws amscm ams-cli-command --region=us-east-1. List your roles: aws --profile saml iam list-roles List your policies: aws --profile saml iam list-role-policies --role-name ROLE_NAME Find stack IDs in AMS To find a Stack ID, you can use either the Amazon EC2 console, AMS console, or the AMS SKMS API/ CLI. AMS Console: • In the navigation pane, select RFCs, and then click the RFC that created the stack. Use the filter option at the top to reduce the list. The RFC details page opens and includes the run output with the stack ID. • Alternatively, you can select Stacks in the navigation pane to open the stacks list page, and then page through the stack list to the stack you're interested in. This method is more useful if you know the subject of the stack you are looking for. Amazon EC2 Console: In the navigation pane, select Instances or Load Balancers or Auto Scaling Groups. AMS SKMS API ListStackSummaries or CLI: Note The AMS CLI must be installed for these commands to work. To install the AMS API or CLI, go to the AMS console Developers Resources page. For reference material on the AMS CM API or AMS SKMS API, see the AMS Information Resources section in the User Guide. Find stack IDs Version May 08, 2025 529 AMS Advanced User Guide AMS Advanced Concepts and Procedures You may need to add a --profile option for authentication; for example, aws amsskms ams-cli-command --profile SAML. You may also need to add the --region option as all AMS commands run out of us-east-1; for example aws amscm ams-cli-command -- region=us-east-1. Note The AMS API/CLI (amscm and amsskms) endpoints are in the AWS N. Virginia Region, us-east-1. Depending on how your authentication is set, and what AWS Region your account and resources are in, you may need to add --region us-east-1 when issuing commands. You may also need to add --profile saml, if that is your authentication method. To view a list of stacks in the current account, run the ListStackSummaries operation of the SKMS API (CLI: list-stack-summaries). To get complete information about a particular stack instance, by StackId, run GetStack. • In the following examples, the first command requests a list of summaries for all stack instances in the account. The second command requests the list of stack instances, with a query filter to list only those of a specific stack template, and output the VpcId, Name, and StackId. aws amsskms list-stack-summaries --output table -------------------------------------------------------------------- | ListStackSummaries | | StackSummaries | +------------+----------------------+---------------------+--------+ | VpcId | StackId | StackTemplateId | Name | +------------+----------------------+---------------------+--------+ |vpc-0123abcd|stack-1fb7fe2212345678|stm-sdhopvbb123456789|Test ELB| |vpc-0123abcd|stack-8323cc0e12345678|stm-s2b72beb123456789|S3 store| |vpc-0123abcd|stack-2309fa0712345678|stm-sdhopvbb123456789|ELB | |vpc-0123abcd|stack-5e61a70512345678|stm-sdpabqbb123456789|PatchSim| |vpc-0123abcd|stack-bd0e080d12345678|stm-s2b72beb123456789|CLI demo| +------------+----------------------+---------------------+--------+ Find stack IDs Version May 08, 2025 530 AMS Advanced User Guide AMS Advanced Concepts and Procedures For information about using CLI queries, see How to Filter the Output with the --query Option and the query language reference, JMESPath Specification.. Find instance IDs or IP addresses in AMS • To request access to an instance, to log in to an instance, or to create an AMI, you must have the instance ID. For an EC2 instance (either a standalone instance or a part of a stack), or a database instance, you can find the ID in a few different ways: • The AMS Console for an instance in an ASG stack: Look on the RFC detail |
ams-ug-202 | ams-ug.pdf | 202 | Procedures For information about using CLI queries, see How to Filter the Output with the --query Option and the query language reference, JMESPath Specification.. Find instance IDs or IP addresses in AMS • To request access to an instance, to log in to an instance, or to create an AMI, you must have the instance ID. For an EC2 instance (either a standalone instance or a part of a stack), or a database instance, you can find the ID in a few different ways: • The AMS Console for an instance in an ASG stack: Look on the RFC detail page for the RFC that created the stack. In the Execution Output section, you will find the stack ID for the ASG stack and you can then go to the EC2 Console Auto Scaling Groups page and search for that stack ID and find instances for it. When you find the instance, select it and an area opens at the bottom of the page with details, including the IP address. • The AMS Console for a standalone EC2 or database (DB) instance: Look on the RFC detail page for the RFC that created the EC2 stack or DB instance. In the Execution Output section, you will find the Instance ID and IP address. • AWS EC2 Console: 1. In the navigation pane, select Instances. The Instances page opens. 2. Click the instance that you want the ID for. The instance details page opens and displays the ID and IP address. • AWS Database Console: 1. On the Home page, select DB Instances. The Instances page opens. 2. Filter for the DB instance that you want the ID for. The instance details page opens and displays the ID. • AMS CLI/API. Note The AMS CLI must be installed for these commands to work. To install the AMS API or CLI, go to the AMS console Developers Resources page. For reference material on the AMS CM API or AMS SKMS API, see the AMS Information Resources section in the User Guide. You may need to add a --profile option for authentication; for example, aws amsskms ams-cli-command --profile SAML. You may also Find instance IDs or IP addresses Version May 08, 2025 531 AMS Advanced User Guide AMS Advanced Concepts and Procedures need to add the --region option as all AMS commands run out of us-east-1; for example aws amscm ams-cli-command --region=us-east-1. Note The AMS API/CLI (amscm and amsskms) endpoints are in the AWS N. Virginia Region, us-east-1. Depending on how your authentication is set, and what AWS Region your account and resources are in, you may need to add --region us-east-1 when issuing commands. You may also need to add --profile saml, if that is your authentication method. Run the following command to get stack execution output details: aws amsskms get-stack --stack-id STACK_ID The output looks similar to this with the InstanceId appearing near the bottom, under Outputs (values shown are examples): { "Stack": { "StackId": "stack-7fa52bd5eb8240123", "Status": { "Id": "CreateCompleted", "Name": "CreateCompleted" }, "VpcId": "vpc-01234567890abcdef", "Description": "Amazon", "Parameters": [ { "Value": "sg-01234567890abcdef,sg-01234567890abcdef", "Key": "SecurityGroups" }, { "Value": "subnet-01234567890abcdef", "Key": "InstanceSubnetId" }, { "Value": "t2.large", Find instance IDs or IP addresses Version May 08, 2025 532 AMS Advanced User Guide AMS Advanced Concepts and Procedures "Key": "InstanceType" }, { "Value": "ami-01234567890abcdef", "Key": "InstanceAmiId" } ], "Tags": [], "Outputs": [ { "Value": "i-0b22a22eec53b9321", "Key": "InstanceId" }, { "Value": "10.0.5.000", "Key": "InstancePrivateIP" } ], "StackTemplateId": "stm-s6xvs000000000000", "CreatedTime": "1486584508416", "Name": "Amazon" } } Find Amazon Resource Names (ARNs) in AMS An Amazon Resource Name (ARN) is a string that uniquely identifies an AWS resource, such as EC2 instances, S3 buckets, accounts, Lambda functions, and so forth. AWS requires an ARN when you want to specify a resource unambiguously across all of AWS, such as in IAM policies, Amazon Relational Database Service (Amazon RDS) tags, and API calls. ARNs are constructed from identifiers that specify the service, Region, account, and other information. There are three ARN formats: arn:aws:service:region:account-id:resource-id arn:aws:service:region:account-id:resource-type/resource-id arn:aws:service:region:account-id:resource-type:resource-id Find ARNs Version May 08, 2025 533 AMS Advanced User Guide AMS Advanced Concepts and Procedures Note The exact format of an ARN depends on the service and resource type. To learn more about ARNs, see Amazon Resource Names (ARNs) and AWS Service Namespaces and ARN Formats. For ARN format examples by resource, see the AWS Service Authorization Reference resource types table. Finding the ARN of an AWS object can be difficult. Here are three ways to try: • AWS service console: Go to the relevant AWS service console, locate the resource and find the ARN in the details for the resource. • AWS API/CLI (you must first install the AWS CLI): Look for the relevant service in the AWS CLI Command Reference, then, depending on the AWS service, look for the relevant operation, such as |
ams-ug-203 | ams-ug.pdf | 203 | Amazon Resource Names (ARNs) and AWS Service Namespaces and ARN Formats. For ARN format examples by resource, see the AWS Service Authorization Reference resource types table. Finding the ARN of an AWS object can be difficult. Here are three ways to try: • AWS service console: Go to the relevant AWS service console, locate the resource and find the ARN in the details for the resource. • AWS API/CLI (you must first install the AWS CLI): Look for the relevant service in the AWS CLI Command Reference, then, depending on the AWS service, look for the relevant operation, such as describe, or get, and so forth. For example, for all IAM roles, policies and users, you can get the ARN in the output from the CLI with: aws iam get-role --role-name EMR_DefaultRole • Construct the ARN based on the relevant format: Find the ARN format for the resource, by looking at the Actions, resources, and condition keys for AWS services page, finding the relevant service, and then the relevant action, and drilling down to the resource ARN format. Once you have the format, replace the variables with the relevant settings. You can construct the ARN yourself by following the appropriate format (the formats change per service and resource type) and filling in the information. Here are some ARN examples: • An AWS account ARN has the following syntax: arn:aws:iam::ACCOUNT-ID:root • An S3 ARN has a flat hierarchy of buckets and associated objects: arn:aws:s3:::ams-bucket • An EC2 ARN has sub resource-types like image, security groups, instance, and so forth. This example includes the instance ID at the end: Find ARNs Version May 08, 2025 534 AMS Advanced User Guide AMS Advanced Concepts and Procedures arn:aws:ec2:us-east-1:123456789012:instance/i-012abcd34efghi56 • A Lambda ARN has the function name for the resource-id part, and you may need to include the version number at the end, as shown in this example: arn:aws:lambda:us-east-1:123456789012:function:api-function:1 The AWS Key Management Service service provides this information: Finding the key ID and key ARN. To find the ARN of a DynamoDB table, use the DynamoDB describe-table CLI. For an outsider's look at finding AWS ARNs, see AWS ARN Explained: Amazon Resource Name Guide. Find resources by ARN in AMS Amazon Resource Names (ARNs) uniquely identify AWS resources. To learn about ARNs and ARN formats, see Amazon Resource Names (ARNs) and AWS Service Namespaces and ARN Formats. Note In order to obtain details about a resource from its ARN, you must have access to the account that created the resource. There is no direct path in AWS to look up all resource details from the resource ARN, because services have multiple resource types with various related information. If you have the ARN for a resource, you can determine: • The related AWS service (the third ARN segment) tells you what AWS console to look at to find the resource • The resource ID (the sixth or seventh ARN segment) confirms that you've found the right resource Or you can look for the AWS CLI commands available for that service in the AWS CLI Command Reference for information about obtaining details about the resource. Find resources by ARN Version May 08, 2025 535 AMS Advanced User Guide AMS Advanced Concepts and Procedures For example, from the following ARN, you can determine that the service is lambda, the account is 123456789012, the resource type is function, and the name of the function is TestFunction. arn:aws:lambda:us-east-1:123456789012:function:TestFunction From this, you can review the AWS CLI documentation for the Lambda service to learn how more details can be retrieved with various commands, such as get-function and get-function- configuration. For example, you can use the following commands to get more information about a Lambda function if you have its name or ARN: aws lambda get-function-configuration --function-name TestFunction aws lambda get-function-configuration --function-name arn:aws:lambda:us- east-1:123456789012:function:TestFunction Find AMS account settings Account settings that are used to create AMS RFCs, set schedules, and determine who receives notifications. Some settings are created during onboarding and require a service request to change. You should make a note of these account details because you will use them when communicating with AMS: • Credentials: If you need to retrieve your AMS user name or password, contact your local IT administrator--AMS uses your corporate Active Directory. • Cloud Service Delivery Manager (CSDM): This person is your liaison with AMS and is available to answer service questions. You are given this person's contact information at onboarding and should keep it available to all in your organization who interact with AMS. You can expect to receive monthly reports on your AMS service from this person. • Console access: You access the AMS console at a URL set up specifically for your account. You can get the URL from your CSDM. • AMS CLI: You can obtain the AMS CLI through the AMS |
ams-ug-204 | ams-ug.pdf | 204 | administrator--AMS uses your corporate Active Directory. • Cloud Service Delivery Manager (CSDM): This person is your liaison with AMS and is available to answer service questions. You are given this person's contact information at onboarding and should keep it available to all in your organization who interact with AMS. You can expect to receive monthly reports on your AMS service from this person. • Console access: You access the AMS console at a URL set up specifically for your account. You can get the URL from your CSDM. • AMS CLI: You can obtain the AMS CLI through the AMS console Developer's resources page, or the distributables package that you get from your CSDM. After you have the distributables package, follow the steps outlined in Installing or upgrading the AMS CLI. Find account settings Version May 08, 2025 536 AMS Advanced User Guide AMS Advanced Concepts and Procedures • Maintenance window: Your maintenance window determines when patching happens for your EC2 instances. The AWS Managed Services Maintenance Window (or Maintenance Window) performs maintenance activities for AWS Managed Services (AMS) and recurs the second Thursday of every month from 3 PM to 4 PM Pacific Time. AMS may change the maintenance window with 48 hours notice. You may have chosen a different window at onboarding--keep a record of your chosen maintenance window. • Monitoring: AMS provides a set of CloudWatch metrics by default, but you can also request additional metrics. If you do, keep record of those. • Logs: By default, your logs are stored at ams-a-ACCOUNT_ID-log-management-REGION where REGION is the region where the log was generated. • Mitigation: At onboarding, AMS records the mitigation action of your choice in case a malware attack against your resources is identified. For example, contact certain people. Keep this information available to all in your organization who interact with AMS. • Region: You can look at the VPC details page in the AMS console. You can also run this command after you have installed the AMS SKMS CLI (this command uses a SAML profile, remove if your authentication method is different): aws --profile saml amsskms get-vpc --vpc-id VPC_ID Important Note The AMS API/CLI (amscm and amsskms) endpoints are in the AWS N. Virginia Region, us-east-1. Depending on how your authentication is set, and what AWS Region your account and resources are in, you may need to add --region us- east-1 when issuing commands. You may also need to add --profile saml, if that is your authentication method. Find account settings Version May 08, 2025 537 AMS Advanced User Guide AMS Advanced Concepts and Procedures Find FQDNs in AMS AWS Managed Services (AMS) access change types (CTs) require the fully qualified domain name, or FQDN, of your AMS-trusted domain, in the form of C844273800838.amazonaws.com. To discover your AWS FQDN, do one of the following: • AWS Console: Look in the AWS Directory Service console in the Directory name column. • CLI: Use these commands while logged into your domain: Windows (returns user and FQDN): whoami /upn or (DC+DC+DC=FQDN) whoami /fqdn Linux: hostname --fqdn Note The AMS API/CLI (amscm and amsskms) endpoints are in the AWS N. Virginia Region, us-east-1. Depending on how your authentication is set, and what AWS Region your account and resources are in, you may need to add --region us-east-1 when issuing commands. You may also need to add --profile saml, if that is your authentication method. Find availability zones (AZs) in AMS Availability Zone: All accounts have at least two availability zones. To accurately find your availability zone names, you must first know the associated subnet ID. Find FQDNs Version May 08, 2025 538 AMS Advanced User Guide AMS Advanced Concepts and Procedures • AMS Console: In the navigation pane click VPCs, and then click the relevant VPC, if necessary. On the VPCs details page, select the relevant subnet in the table of subnets to open the subnet details page with the name of the associated availability zone. • AMS SKMS API/CLI: aws amsskms list-subnet-summaries --output table aws amsskms get-subnet --subnet-id SUBNET_ID Note The AMS API/CLI (amscm and amsskms) endpoints are in the AWS N. Virginia Region, us-east-1. Depending on how your authentication is set, and what AWS Region your account and resources are in, you may need to add --region us-east-1 when issuing commands. You may also need to add --profile saml, if that is your authentication method. Find SNS topics in AMS Your SNS topics determine who is notified under various circumstances. AMS provides SNS topics for AMI notifications (see AMS AMI notifications with SNS), CloudWatch alarms and EC2 resources (see Receiving alerts generated by AMS) and more. To discover your existing SNS topics: • AWS Console: Use the SNS console to view all topics, applications, and subscriptions, and a graph of messages. Also create, delete, subscribe to, and |
ams-ug-205 | ams-ug.pdf | 205 | and resources are in, you may need to add --region us-east-1 when issuing commands. You may also need to add --profile saml, if that is your authentication method. Find SNS topics in AMS Your SNS topics determine who is notified under various circumstances. AMS provides SNS topics for AMI notifications (see AMS AMI notifications with SNS), CloudWatch alarms and EC2 resources (see Receiving alerts generated by AMS) and more. To discover your existing SNS topics: • AWS Console: Use the SNS console to view all topics, applications, and subscriptions, and a graph of messages. Also create, delete, subscribe to, and publish to topics. • API/CLI (when logged into your AMS account, requires the AWS CLI): List your SNS topics: aws sns list-topics List your SNS subscriptions: aws sns list-subscriptions Find SNS topics Version May 08, 2025 539 AMS Advanced User Guide AMS Advanced Concepts and Procedures Note The AMS API/CLI (amscm and amsskms) endpoints are in the AWS N. Virginia Region, us-east-1. Depending on how your authentication is set, and what AWS Region your account and resources are in, you may need to add --region us-east-1 when issuing commands. You may also need to add --profile saml, if that is your authentication method. Find backup settings in AMS Backups and snapshots are managed by AMS through the native AWS Backup service. The configuration is managed through AWS Backup plans. You can have multiple AWS Backup plans that associate tagged resources with backup schedules and retention policies. To find your AMS account AWS Backup settings, use the https://console.aws.amazon.com/backup console, or the AWS CLI Command Reference for backup commands. For more information about AMS and AWS Backup, see Continuity Management. Find backup settings Version May 08, 2025 540 AMS Advanced User Guide AMS Advanced Concepts and Procedures Access management in AMS Learn how to access resources by using SSH, or remote desktop protocol (RDP), and how to use bastions. The AWS Managed Services (AMS) access management system is configured during onboarding. Only users with the AMS IAM user role, federated through AMS, can access AMS resources in the account. In addition to the federated trust, described next, AMS security groups are an important element in private and public application access. For information about AMS security groups and how to change them, see Security groups. Topics • What is Access Management? • How and when to use the root user account in AMS • AMS Advanced console and Amazon EC2 access • Accessing the AWS Management console and the AMS console • Accessing instances using bastions What is Access Management? Access management is how AMS protects your resources by allowing only authorized and authenticated access. AMS uses a default IAM user role and instance profile, as well as multi-factor authentication, security groups, DNS-friendly bastion names, and more to keep your resources protected. AMS focuses on three types of access that require management: • Console access: Leveraging federation, users in the account’s Active Directory can access the console using single sign-on (SSO). If you have multi-factor authentication configured for these accounts, you can continue to require MFA to gain access to the console. • Instance access with RDP or SSH: Leveraging an Active Directory trust, users in the account’s existing Active Directory can request access to an instance, and then successfully authenticate to a bastion and the instance by using their existing corporate credentials. If you have multi-factor What is Access Management? Version May 08, 2025 541 AMS Advanced User Guide AMS Advanced Concepts and Procedures authentication configured for those accounts, you can continue to require MFA to request access to an instance. AMS uses an MFA solution of its own to restrict AMS engineer access to instances. • Application access: Varies by use case. Topics • Why and when AMS accesses your account Why and when AMS accesses your account AWS Managed Services (AMS) manages your AWS infrastructure and sometimes, for specific reasons, AMS operators and administrators access your account. These access events are documented in your AWS CloudTrail (CloudTrail) logs. Why, when, and how AMS accesses your account is explained in the following topics. AMS customer account access triggers AMS customer account access activity is driven by triggers. The triggers today are the AWS tickets created in our issues management system in response to Amazon CloudWatch (CloudWatch) alarms and events, and incident reports or service requests that you submit. Multiple service calls and host-level activities might be performed for each access. Access justification, the triggers, and the initiator of the trigger are listed in the following table. Access Triggers Access Patching Infrastructure deployments Internal problem investigation Alert investigation and remediation AMS Initiator Trigger AMS AMS AMS Patch issue Deployment issue Problem issue (an issue that has been identified as systemic) AWS Systems Manager operational work items (SSM OpsItems) Why and when we |
ams-ug-206 | ams-ug.pdf | 206 | the AWS tickets created in our issues management system in response to Amazon CloudWatch (CloudWatch) alarms and events, and incident reports or service requests that you submit. Multiple service calls and host-level activities might be performed for each access. Access justification, the triggers, and the initiator of the trigger are listed in the following table. Access Triggers Access Patching Infrastructure deployments Internal problem investigation Alert investigation and remediation AMS Initiator Trigger AMS AMS AMS Patch issue Deployment issue Problem issue (an issue that has been identified as systemic) AWS Systems Manager operational work items (SSM OpsItems) Why and when we access your account Version May 08, 2025 542 AMS Advanced User Guide AMS Advanced Concepts and Procedures Access Initiator Trigger Manual RFC execution Incident investigation and remediation Inbound service request fulfillment You You You Request for Change (RFC) issue. (Non-automated RFCs may require AMS access to your resources) Inbound support case (an incident or service request you submit) AMS customer account access IAM roles When triggered, AMS accesses customer accounts using AWS Identity and Access Management (IAM) roles. Like all activity in your account, the roles and their usage are logged in CloudTrail. Important Do not modify or delete these roles. IAM roles for AMS access to customer accounts Role Name Description Account Type (SALZ, MALZ Management, MALZ Applicati on, etc.) ams-service-admin SALZ, MALZ ams-application-infra- read-only ams-application-infra- operations SALZ, MALZ Application, MALZ Tools-App lication AMS Service automation access and automated infrastructure deployments e.g Patch, Backup, Automated Remediation. Operator read only access Operator access for incidents/service requests Why and when we access your account Version May 08, 2025 543 AMS Advanced User Guide Role Name Description Account Type (SALZ, MALZ Management, MALZ Applicati on, etc.) AMS Advanced Concepts and Procedures ams-application-infra- admin AD Admin access ams-primary-read-only Operator read only access ams-primary-operations MALZ Management Operator access for incidents/service requests ams-primary-admin AD Admin access ams-logging-read-only Operator read only access ams-logging-operations MALZ Logging Operator access for incidents/service requests ams-logging-admin AD Admin access ams-networking-read-only Operator read only access ams-networking-ope rations MALZ Networkin Operator access for incidents/service requests g ams-networking-admin AD Admin access ams-shared-services-read- only Operator read only access ams-shared-services- operations MALZ Shared Services Operator access for incidents/service requests ams-shared-services- admin AD Admin access ams-security-read-only Operator read only access ams-security-operations Operator access for incidents/service requests MALZ Security Why and when we access your account Version May 08, 2025 544 AMS Advanced Concepts and Procedures AMS Advanced User Guide Role Name Description Account Type (SALZ, MALZ Management, MALZ Applicati on, etc.) ams-security-admin AD Admin access SALZ, MALZ Application, MALZ Tools-App lication, MALZ Core SALZ ams-access-security- analyst ams-access-security- analyst-read-only Sentinel_AdminUser _Role_PXHazRQadu0P VcCDcMbHE Sentinel_PowerUser _Role_wZuPuS0ROOl0 IazDbRI9 Sentinel_ReadOnlyU ser_Role_Pd4L6Rw9R D0lnLkD5JOo ams_admin_role SALZ, MALZ AWSManagedServices _Provisioning_Cust omerStacksRole customer_ssm_autom ation_role ams_ssm_automation_role SALZ, MALZ Application, MALZ Core AMS Security access AMS Security, read only access [BreakGlassRole]Used to breakGlass into the customer accounts Poweruser access to customer accounts for RFC execution ReadOnly access to customer accounts for RFC execution Admin access to customer accounts for RFC execution Used to launch and update CFN stacks on behalf of customers through CloudFormation Ingest Role passed by CT executions to SSM Automation for runbook execution Role passed by AMS services to SSM Automation for runbook execution Why and when we access your account Version May 08, 2025 545 AMS Advanced User Guide Role Name Description Account Type (SALZ, MALZ Management, MALZ Applicati on, etc.) AMS Advanced Concepts and Procedures ams_ssm_iam_deploy ment_role MALZ Applicati on Role used by IAM catalog ams_ssm_shared_svc s_intermediary_role MALZ Shared Services Role used by application ams_ssm_automation _role to execute specific SSM Documents in AmsOpsCenterRole Shared Services account Used to create and update OpsItems in customer accounts AMSOpsItemAutoExec utionRole SALZ, MALZ Used to get SSM Documents, describe resource tags, update OpsItems, and start automation Default customer EC2 instance profile (role) customer-mc-ec2-in stance-profile Requesting instance access To access a resource, you must first submit a request for change (RFC) for that access. There are two types of access that you can request: admin (read/write permissions) and read-only (standard user access). Access lasts for eight hours, by default. This information is required: • Stack ID, or set of stack IDs, for the instance or instances you want to access. • The fully qualified domain name of your AMS-trusted domain. • The Active Directory username of the person who wants access. • The ID of the VPC where the stacks are that you want access to. Once you've been granted access, you can update the request as needed. Why and when we access your account Version May 08, 2025 546 AMS Advanced User Guide AMS Advanced Concepts and Procedures For examples of how to request access, see Stack Admin Access | Grant or Stack Read-only Access | Grant. How and when to use the root user account in AMS The root user is the superuser within your AWS |
ams-ug-207 | ams-ug.pdf | 207 | AMS-trusted domain. • The Active Directory username of the person who wants access. • The ID of the VPC where the stacks are that you want access to. Once you've been granted access, you can update the request as needed. Why and when we access your account Version May 08, 2025 546 AMS Advanced User Guide AMS Advanced Concepts and Procedures For examples of how to request access, see Stack Admin Access | Grant or Stack Read-only Access | Grant. How and when to use the root user account in AMS The root user is the superuser within your AWS account. AMS monitors root usage. We recommend that you use root only for the few tasks that require it, for example: changing your account settings, activating AWS Identity and Access Management (IAM) access to billing and cost management, changing your root password, and enabling multi-factor authentication (MFA). See Tasks that require root user credentials in the AWS Identity and Access Management User Guide. Note MFA is enabled during AMS Advanced onboarding to specifically disallow root user access. Root access in AMS-managed accounts is different from other AWS accounts, and is critical to the security of your entire AMS-managed environment. The MFA configured is a virtual MFA and is performed using an AMS-owned device. After the virtual MFA is configured with AMS' assistance, the virtual token is immediately deleted. This ensures that neither you nor AMS retains the ability to log in to the account as the root user. Root login can only be re- enabled on special requests (explained next) and AMS expects such accesses to be used only when absolutely necessary. For information about MFA, see Secure New Account with Multi-Factor Authentication. Root access always triggers an AMS Security and Operations team response. AMS monitors API calls for root access, and alarms are triggered if such access is detected. Requesting root access is slightly different between AMS account types. Root access with AMS Advanced single-account landing zone: If you have a single-account landing zone, contact your cloud service deliver manager (CSDM) and cloud architects (CAs) to advise them of the root access work that you require. It is best to give twenty-four hours notice before the proposed activity. Root access with AMS Advanced multi-account landing zone: For multi-account landing zone Application, Shared Services, Security, or Networking accounts, use the Management | Other | Other (ct-1e1xtak34nx76) change type. Include the date, time, and How and when to use root Version May 08, 2025 547 AMS Advanced User Guide AMS Advanced Concepts and Procedures the purpose of using the root user credentials and schedule the RFC to be sure to give twenty- four hours notice before the proposed activity. Use your multi-account landing zone Management account to submit the RFC. Additionally, contact your CSDM and CAs twenty-four hours in advance, to advise them of the root access work you require. AMS operations and security response to root usage: AMS receives an alarm when the root user account is used. If the root credentials usage is unscheduled, they contact the AMS Security team, and your account team, to verify if this is expected activity. If it is not expected activity, AMS works with your Security team to investigate the issue. AMS Advanced console and Amazon EC2 access Accessing the AMS Advanced console. Accessing your Amazon EC2 instances. Submit access request: AMS Advanced console and Amazon EC2 access Version May 08, 2025 548 AMS Advanced User Guide AMS Advanced Concepts and Procedures Logging into your AMS Amazon EC2 instances: Accessing the AWS Management console and the AMS console During onboarding, you're provided a login to the AWS Management console (with limited privileges: you can write to the AMS console, and some fields in your customer information page). You can access the AMS console by selecting the Managed Services link in the AWS Management console. Either federated access or shared credentials (user name/password) are prepared as Accessing the AWS Management console and the AMS console Version May 08, 2025 549 AMS Advanced User Guide AMS Advanced Concepts and Procedures agreed with your IT administration team. For further account or group creation, submit a service request to AMS. For information about getting access to the AWS Management console, see Working with the AWS Management console. For some tips on using the AMS console, see Using the AMS console. Temporary AMS console access If you haven't yet set up an identity provider (for instance, SAML) to authenticate to AMS, you can get temporary access to the AMS console. Contact your CSDM to have a Deployment | Advanced stack components | Identity and Access Management (IAM) | Create entity or policy change request (ct-3dpd8mdd9jn1r) submitted on your behalf with these values: • UserName: A name for the IAM user entity that you're creating • AccessType: "Console access" |
ams-ug-208 | ams-ug.pdf | 208 | AWS Management console, see Working with the AWS Management console. For some tips on using the AMS console, see Using the AMS console. Temporary AMS console access If you haven't yet set up an identity provider (for instance, SAML) to authenticate to AMS, you can get temporary access to the AMS console. Contact your CSDM to have a Deployment | Advanced stack components | Identity and Access Management (IAM) | Create entity or policy change request (ct-3dpd8mdd9jn1r) submitted on your behalf with these values: • UserName: A name for the IAM user entity that you're creating • AccessType: "Console access" • UserPermissions: "Temporary AMS console access for USERNAME (the person that you want to have temporary access)" • Email notifications: Your email address, so you can approve the request when AMS requests you to Note This RFC for temporary AMS Console access requires a security review and acceptance by both your internal security team and AMS Global Security. After this request has been completed, and you're able to log in, you're required to approve the RFC that was created, to track the approval and allow the AMS team to close out the work. To approve the RFC, find it in the RFC's list page (there will be a Pending Approval flag next to it), select it to open the RFC details page for that RFC, and then choose Approve. Note that you won't be able to use AMS until the RFC is approved. When the RFC successfully completes, AMS operations provides you with the new IAM user and a password. Then follow these steps: Temporary AMS console access Version May 08, 2025 550 AMS Advanced User Guide AMS Advanced Concepts and Procedures 1. Go to the AWS Management console and log in with provided credentials. You'll be asked to create a new password. You must also, upon login, set up multi-factor authentication (MFA); to learn more about doing that, see Using Multi-Factor Authentication (MFA) in AWS. 2. In the AWS Management console, change to the provided IAM role (customer_CustomerCode_readonly_user_role). 3. Open the AMS Managed Services Console. Note Temporary access defaults to sixty days; however, you can request a thirty-day extension by contacting your CSDM. Accessing instances using bastions All access to resources inside AMS-managed accounts, for both customers and AMS operators, is gated by the use of bastion hosts. We maintain both Linux and Windows RDP bastions for access for both Multi-account landing zone (MALZ) and Single-account landing zone (SALZ) AMS Advanced accounts. Your bastions are accessible only over your private connection (VPN or AWS Direct Connect)DX. In addition to firewalling to prevent inbound traffic, bastions are regularly re-provisioned (with existing credentials) on a fixed schedule. Note For information on moving files to an EC2 instance, see File transfer: Local Windows or MAC PC to Linux Amazon EC2. MALZ You access your account instances by logging in to a bastion instance with your Active Directory (AD) credentials. Amazon uses bastions located in the perimeter network VPC (networking account), and you use your customer bastions, located in your Customer Bastions subnet in the shared services account. Accessing instances using bastions Version May 08, 2025 551 AMS Advanced User Guide AMS Advanced Concepts and Procedures When your AMS environment is initially onboarded, you have two SSH bastions and two RDP bastions depending on your choice. SALZ You access your account instances by logging in to a bastion instance with your Active Directory (AD) credentials. AMS uses bastions located in the perimeter network subnets, and you use bastions located in your private subnets. When your account is initially onboarded, you have two RDP and two SSH bastions, by default. Note As part of the single-account landing zone, AMS provides both RDP (Windows) and SSH (Linux) bastions to access your stacks; however, you can choose whether you want only RDP bastions or only SSH bastions. To request that only RDP, or only SSH bastions are maintained, submit a service request. In order to access an instance, you need: • Access granted to the stack. To get access granted to a stack, see Stack Admin Access | Grant or Stack Read-Only Access | Grant. • The stack ID that you want to access so you can be granted access to the instance. To find a stack ID, see Find stack IDs in AMS. • The instance IP that you want to access. To find an instance IP, see Find instance IDs or IP addresses in AMS. • The DNS friendly bastion name or the bastion IP. How to use DNS friendly bastion names and how to find a bastion IP are described next. DNS friendly bastion names AWS Managed Services (AMS) uses DNS friendly bastion names. MALZ For Multi-account landing zone (MALZ), DNS records are created for the bastions in the FQDN of the AMS-managed |
ams-ug-209 | ams-ug.pdf | 209 | can be granted access to the instance. To find a stack ID, see Find stack IDs in AMS. • The instance IP that you want to access. To find an instance IP, see Find instance IDs or IP addresses in AMS. • The DNS friendly bastion name or the bastion IP. How to use DNS friendly bastion names and how to find a bastion IP are described next. DNS friendly bastion names AWS Managed Services (AMS) uses DNS friendly bastion names. MALZ For Multi-account landing zone (MALZ), DNS records are created for the bastions in the FQDN of the AMS-managed Active Directory. AMS replaces Linux and Windows bastions as required. DNS friendly bastion names Version May 08, 2025 552 AMS Advanced User Guide AMS Advanced Concepts and Procedures For example, if there is a new bastion AMI that must be deployed, the bastion DNS records dynamically update to point to new, valid bastions. 1. To access SSH (Linux) bastions, use DNS records like this: sshbastion(1-4).Your_Domain.com For example, where the domain is Your_Domain: • sshbastion1.Your_Domain.com • sshbastion2.Your_Domain.com • sshbastion3.Your_Domain.com • sshbastion4.Your_Domain.com 2. To access RDP (Windows) bastions, use DNS records like this: rdp-Username.Your_Domain.com. For example, where the user name is alex, test, demo, or bob, and the domain is Your_Domain.com: • rdp-alex.Your_Domain.com • rdp-test.Your_Domain.com • rdp-demo.Your_Domain.com • rdp-bob.Your_Domain.com SALZ Single-account landing zone (SALZ) replaces Linux and Windows bastions as required. For example, if there is a new bastion AMI that must be deployed, the bastion DNS records dynamically update to point to new, valid bastions. 1. To access SSH (Linux) bastions, use DNS records like this: sshbastion(1-4).AAccountNumber.amazonaws.com. For example, where 123456789012 is the account number: • sshbastion1.A123456789012.amazonaws.com • sshbastion2.A123456789012.amazonaws.com • sshbastion3.A123456789012.amazonaws.com DNS friendly bastion names Version May 08, 2025 553 AMS Advanced User Guide AMS Advanced Concepts and Procedures • sshbastion4.A123456789012.amazonaws.com 2. To access RDP (Windows) bastions, use DNS records like this: rdpbastion(1-4).AACCOUNT_NUMBER.amazonaws.com. For example, where 123456789012 is the account number: • rdpbastion1.A123456789012.amazonaws.com • rdpbastion2.A123456789012.amazonaws.com • rdpbastion3.A123456789012.amazonaws.com • rdpbastion4.A123456789012.amazonaws.com Saving costs on Single-account landing zone (SALZ) bastions AMS provides two SSH bastions and two RDP bastions in the default configuration for you to connect to your Amazon EC2 instances, and also deploys two DMZ bastions in the default configuration for service operations. The bastions use m4. large Amazon EC2 instances by default. You have an option to change the Amazon EC2 instances used for bastions to t3.small, and save cost. If you are using on-demand instances, or spot instances, or a savings plan, you should consider this feature, and save costs. If you use Reserved Instances consider if using t3.small instances might lower your costs. To change the instance type, submit an RFC with Management | Advanced stack components | EC2 instance stack | Resize (ct-15mazjj88xc69) CT from your AMS account. Contact your cloud service delivery manager (CSDM) for additional questions, or to check if you can benefit from this feature. Using bastion IP addresses AMS customers can use SSH and RDP bastions, either the DNS friendly bastion names described previously, or bastion IP addresses. To find bastion IP addresses, SSH and RDP, for your account: 1. For multi-account landing zone only: Log in to the Shared Services account. 2. Open the EC2 Console and choose Running Instances. The Instances page opens. Saving costs on Single-account landing zone (SALZ) bastions Version May 08, 2025 554 AMS Advanced User Guide AMS Advanced Concepts and Procedures 3. In the filter box at the top, enter either ssh-bastion or rdp-bastion. In the filter box at the top, enter either customer-ssh or customer-rdp. The SSH and/or RDP bastions for your account display. Note that in addition to your SSH bastions, you may see AMS perimeter network bastions in the list, which are unavailable for this. 4. Select an SSH or RDP bastion. If you're using a Windows computer and want to log in to a Linux instance, you use an SSH bastion. If you want to log in to a Windows instance, you use an RDP bastion. If you're on a Linux OS and want to log in to a Windows instance, you use an SSH bastion through an RDP tunnel (this is so you can access the Windows desktop). To access a Linux instance from a Linux OS, you use an SSH bastion. Instance access examples in AMS These examples show how to log in to an instance in your AMS account by using a bastion after you've been granted access through an RFC. For information about getting access granted, see Requesting instance access. Note For information on moving files to an EC2 instance, see File transfer: Local Windows or MAC PC to Linux Amazon EC2. Required data: • Bastion DNS friendly name or IP address: Use a DNS friendly name as described in DNS friendly bastion names or find bastion IP addresses as |
ams-ug-210 | ams-ug.pdf | 210 | from a Linux OS, you use an SSH bastion. Instance access examples in AMS These examples show how to log in to an instance in your AMS account by using a bastion after you've been granted access through an RFC. For information about getting access granted, see Requesting instance access. Note For information on moving files to an EC2 instance, see File transfer: Local Windows or MAC PC to Linux Amazon EC2. Required data: • Bastion DNS friendly name or IP address: Use a DNS friendly name as described in DNS friendly bastion names or find bastion IP addresses as described in Using bastion IP addresses. Note An Amazon EC2 instance created through an Amazon EC2 Auto Scaling group will have an IP address that cycles in and out and you have to use your Amazon EC2 console to find that IP address. Instance access examples Version May 08, 2025 555 AMS Advanced User Guide AMS Advanced Concepts and Procedures • User name (for example DOMAIN_FQDN\\USERNAME) and Password: Credentials for the account. The USERNAME must be your Active Directory user name. Note that a user name in the format username@customerdomain.com can be used but can cause trouble with your PBIS setup. • Stack IP address: Find this by looking at the run output for the RFC that you submitted to launch the stack, or look up the Amazon EC2 instance IP address in the Amazon EC2 console. For a single Amazon EC2 instance, you can also use the AMS SKMS command ListStackSummaries to find the stack ID and then GetStack to find the stack IP address. For the AMS SKMS API reference, see the Reports tab in the AWS Artifact Console. Access the bastion IP address, either SSH or RDP, as appropriate, and log in using one of the following procedures. Note RDP bastions only allow two simultaneous connections. So, in the best case scenario, only 4 admins are able to connect to windows stacks at the same time. If you require more connections for RDP, see AMS Bastion Options during Application Migrations/Onboarding in the AMS onboarding guide. Linux computer to Linux instance Use SSH to connect to the SSH bastion and then to the Linux instance. MALZ For more information about the friendly bastion names, see DNS bastions. In order to connect to the Linux instance, you must first connect to an SSH bastion. 1. Open a shell window and enter: ssh Domain_FQDN\\Username@SSH_bastion_name or SSH_bastion_IP Instance access examples Version May 08, 2025 556 AMS Advanced User Guide AMS Advanced Concepts and Procedures Which would look like this if your Domain_FQDN is "corp.domain.com", your account number is "123456789123", Your_Domain is "amazonaws.com", you choose bastion "4", and your user name is "JoeSmith": ssh corp.domain.com\\JoeSmith sshbastion4.A123456789123.amazonaws.com 2. Log in with your corporate Active Directory credentials. 3. When presented with a Bash prompt, SSH in to the instance, and then enter: ssh Domain_FQDN\\Username@Instance_IP Or, you can use the Login flag (-l): ssh -l Domain_FQDN\\Username@Instance_IP SALZ For more information about the friendly bastion names, see DNS bastions. In order to connect to the Linux instance, you must first connect to an SSH bastion. 1. Open a shell window and enter: ssh DOMAIN_FQDN\\USERNAME@SSH_BASTION_name or SSH_BASTION_IP Which would look like this if your account number is 123456789123, you choose bastion 4, and your user name is JoeSmith: ssh corp.domain.com\\JoeSmith sshbastion1.A123456789123.amazonaws.com 2. Log in with your corporate Active Directory credentials. 3. When presented with a Bash prompt, SSH in to the instance, and then enter: ssh DOMAIN_FQDN\\USERNAME@INSTANCE_IP Or, you can use the Login flag (-l): Instance access examples Version May 08, 2025 557 AMS Advanced User Guide AMS Advanced Concepts and Procedures ssh -l DOMAIN_FQDN\\USERNAME@INSTANCE_IP Linux computer to Windows instance Use an SSH tunnel and an RDP client to connect to a Windows instance from your Linux computer. MALZ This procedure requires a Remote Desktop Connection client for Linux; the example uses Microsoft Remote Desktop (an open source UNIX client for connecting to Windows Remote Desktop Services). Rdesktop is an alternative. Note How you log in to Windows instances might change based on the remote desktop client being used. First you establish an SSH tunnel, and then log in. For more information about the friendly bastion names, see DNS friendly bastion names. Before you begin: • Request access to the instance that you want to connect to; for information, see Access requests. • Choose a friendly DNS SSH bastion name to connect to; for example: sshbastion(1-4).Your_Domain Which would look like this if your Domain_FQDN is "corp.domain.com", your AMS-managed Your_Domain is "amazonaws.com", you choose bastion "4", and your user name is "JoeSmith": ssh corp.domain.com\\JoeSmith sshbastion4.amazonaws.com • Find the IP address of the instance that you want to connect to; for information, see Finding an instance ID or IP address. Instance access examples Version May 08, 2025 558 AMS |
ams-ug-211 | ams-ug.pdf | 211 | see DNS friendly bastion names. Before you begin: • Request access to the instance that you want to connect to; for information, see Access requests. • Choose a friendly DNS SSH bastion name to connect to; for example: sshbastion(1-4).Your_Domain Which would look like this if your Domain_FQDN is "corp.domain.com", your AMS-managed Your_Domain is "amazonaws.com", you choose bastion "4", and your user name is "JoeSmith": ssh corp.domain.com\\JoeSmith sshbastion4.amazonaws.com • Find the IP address of the instance that you want to connect to; for information, see Finding an instance ID or IP address. Instance access examples Version May 08, 2025 558 AMS Advanced User Guide AMS Advanced Concepts and Procedures 1. Set up RDP over an SSH tunnel from a Linux desktop to a Windows instance. In order to issue the ssh command with the right values, there are a couple of ways to proceed: • In the Linux shell, set the variables, and then enter the SSH connection command: BASTION="sshbastion(1-4).Your_Domain"" WINDOWS="Windows_Instance_Private_IP" AD="AD_Account_Number" USER="AD_Username" ssh -L 3389:$WINDOWS:3389 A$AD\\\\$USER@$BASTION Example, if the following values are used: BASTION="sshbastion4.A123456789123.amazonaws.com" WINDOWS="172.16.3.254" AD="ACORP_example" USER="john.doe" • Add the variable values directly to the ssh command. In either case, this is what the rendered request would be (assuming the same set of variable values): ssh -L 3389:172.16.3.254:3389 ACORP_example\\\\john.doe@myamsadomain.com 2. Either: Open your Remote Desktop Client, enter the loopback address and port, 127.0.0.1:3389, and then open the connection. Or, log in to the Windows instance from a new Linux desktop shell. If you use RDesktop, the command looks like this: rdesktop 127.0.0.1:3389 A remote desktop window for the Windows instance appears on your Linux desktop. Instance access examples Version May 08, 2025 559 AMS Advanced User Guide AMS Advanced Concepts and Procedures Tip If the remote desktop session fails to start, verify that network connectivity to the Windows instance from the SSH bastion is allowed on port 3389 from the shell in step 1 (replace private_ip_address_of_windows_instance appropriately): nc private_ip_address_of_windows_instance 3389 -v –z Success: nc 172.16.0.83 3389 -v -z Connection to 172.16.0.83 3389 port [tcp/ms-wbt-server] succeeded netstat -anvp | grep 3389 tcp 0 0 172.16.0.253:48079 172.16.3.254:3389 ESTABLISHED SALZ This procedure for a single-account landing zone requires a Remote Desktop Connection client for Linux; the example uses Microsoft Remote Desktop (an open source UNIX client for connecting to Windows Remote Desktop Services). Rdesktop is an alternative. Note How you log in to Windows instances might change based on the remote desktop client being used. First you establish an SSH tunnel, and then log in. For more information about the friendly bastion names, see DNS friendly bastion names. Before you begin: • Request access to the instance that you want to connect to; for information, see Access requests. • Choose a friendly DNS SSH bastion name to connect to; for example: Instance access examples Version May 08, 2025 560 AMS Advanced User Guide AMS Advanced Concepts and Procedures sshbastion(1-4).AAMSAccountNumber.amazonaws.com Which would look like this if your account number is 123456789123 and you choose bastion 4: sshbastion4.A123456789123.amazonaws.com • Find the IP address of the instance that you want to connect to; for information, see Finding an instance ID or IP address. 1. Set up RDP over an SSH tunnel from a Linux desktop to a Windows instance. In order to issue the ssh command with the right values, there are a couple of ways to proceed: • In the Linux shell, set the variables, and then enter the SSH connection command: BASTION="sshbastion(1-4).AAMSAccountNumber.amazonaws.com" WINDOWS="WINDOWS_INSTANCE_PRIVATE_IP" AD="AD_ACCOUNT_NUMBER" USER="AD_USERNAME" ssh -L 3389:$WINDOWS:3389 A$AD\\\\$USER@$BASTION Example, if the following values are used: BASTION="sshbastion4.A123456789123.amazonaws.com" WINDOWS="172.16.3.254" AD="ACORP_example" USER="john.doe" • Add the variable values directly to the ssh command. In either case, this is what the rendered request would be (assuming the same set of variable values): ssh -L 3389:172.16.3.254:3389 ACORP_example\\\ \john.doe@sshbastion4.A123456789123.amazonaws.com Instance access examples Version May 08, 2025 561 AMS Advanced User Guide AMS Advanced Concepts and Procedures 2. Either: Open your Remote Desktop Client, enter the loopback address and port, 127.0.0.1:3389, and then open the connection. Or, log in to the Windows instance from a new Linux desktop shell. If you use RDesktop, the command looks like this: rdesktop 127.0.0.1:3389 A remote desktop window for the Windows instance appears on your Linux desktop. Tip If the remote desktop session fails to start, verify that network connectivity to the Windows instance from the SSH bastion is allowed on port 3389 from the shell in step 1 (replace private_ip_address_of_windows_instance appropriately): nc private_ip_address_of_windows_instance 3389 -v –z Success: nc 172.16.0.83 3389 -v -z Connection to 172.16.0.83 3389 port [tcp/ms-wbt-server] succeeded netstat -anvp | grep 3389 tcp 0 0 172.16.0.253:48079 172.16.3.254:3389 ESTABLISHED Windows computer to Windows instance Use Windows Remote Desktop Connection client to connect to a Windows instance from your Windows computer. MALZ For more information about the friendly bastion names, see DNS friendly bastion names. 1. Open the Remote Desktop Connection program, a standard |
ams-ug-212 | ams-ug.pdf | 212 | start, verify that network connectivity to the Windows instance from the SSH bastion is allowed on port 3389 from the shell in step 1 (replace private_ip_address_of_windows_instance appropriately): nc private_ip_address_of_windows_instance 3389 -v –z Success: nc 172.16.0.83 3389 -v -z Connection to 172.16.0.83 3389 port [tcp/ms-wbt-server] succeeded netstat -anvp | grep 3389 tcp 0 0 172.16.0.253:48079 172.16.3.254:3389 ESTABLISHED Windows computer to Windows instance Use Windows Remote Desktop Connection client to connect to a Windows instance from your Windows computer. MALZ For more information about the friendly bastion names, see DNS friendly bastion names. 1. Open the Remote Desktop Connection program, a standard Windows program, and enter the friendly DNS name of the Windows bastion in the hostname field. Instance access examples Version May 08, 2025 562 AMS Advanced User Guide AMS Advanced Concepts and Procedures 2. Choose Connect. The Remote Desktop Connection attempts an RDP connection to the bastion. If successful, a credentials dialog box opens. To gain access, use your corporate Active Directory credentials, as you would with the Windows instance. 3. Open the Remote Desktop Connection program on the bastion and enter the IP address of the Windows instance you would like to connect to (for example, 10.0.0.100), and then choose Connect. Your corporate Active Directory credentials are again required before you connect to the Windows instance. Instance access examples Version May 08, 2025 563 AMS Advanced User Guide SALZ AMS Advanced Concepts and Procedures For more information about the friendly bastion names, see DNS friendly bastion names. 1. Open the Remote Desktop Connection program, a standard Windows program, and enter the friendly DNS name of the Windows bastion in the hostname field; for example, rdpbastion(1-4).AAMSAccountNumber.amazonaws.com, which would look like this if your account number is 123456789123 and you choose bastion 4, rdpbastion4.A123456789123.amazonaws.com. 2. Choose Connect. The Remote Desktop Connection attempts an RDP connection to the bastion. If successful, a credentials dialog box opens. To gain access, use your corporate Active Directory credentials, as you would with the Windows instance. 3. Open the Remote Desktop Connection program on the bastion and enter the IP address of the Windows instance you would like to connect to (for example, 10.0.0.100), and then Instance access examples Version May 08, 2025 564 AMS Advanced User Guide AMS Advanced Concepts and Procedures choose Connect. Your corporate Active Directory credentials are again required before you connect to the Windows instance. Windows computer to Linux instance To RDP to an SSH bastion from a Windows environment, follow these steps. MALZ Before you begin: • Request access to the instance that you want to connect to; for information, see Access requests. • Choose a friendly DNS SSH bastion name to connect to; for example: sshbastion(1-4).YOUR_DOMAIN Which would look like this if YOUR_DOMAIN is myamsaddomain.com" and you choose bastion 4: sshbastion4.myamsaddomain.com • Find the IP address of the instance that you want to connect to; for information, see Finding an instance ID or IP address. In order to connect to the Linux instance from your Windows machine, you must first connect to an SSH bastion. Use the native Windows OpenSSH client or install PuTTY on your local machine. To learn more about OpenSSH, see OpenSSH in Windows. Instance access examples Version May 08, 2025 565 AMS Advanced User Guide AMS Advanced Concepts and Procedures 1. Use the native Windows or open PuTTY and enter the SSH bastion hostname or the IP address of the SSH bastion. For example, 10.65.2.214 (22 is the port used for SSH; it will be set by default). 2. OpenSSH or PuTTY attempts an SSH connection to the bastion and open a shell window. 3. Use your corporate Active Directory credentials as you would with the RDP hosts to gain access. 4. When presented with a Bash prompt, SSH into the instance. Enter: ssh DOMAIN_FQDN\USERNAME@INSTANCE_IP SALZ Before you begin: • Request access to the instance that you want to connect to; for information, see Access requests. • Choose a friendly DNS SSH bastion name to connect to; for example: sshbastion(1-4).AAMSAccountNumber.amazonaws.com Which would look like this if your account number is 123456789123 and you choose bastion 4: sshbastion4.A123456789123.amazonaws.com • Find the IP address of the instance that you want to connect to; for information, see Finding an instance ID or IP address. In order to connect to the Linux instance from your Windows machine, you must first connect to an SSH bastion. Use the native Windows OpenSSH client or install PuTTY on your local machine. To learn more about OpenSSH, see OpenSSH in Windows. 1. Use the native Windows or open PuTTY and enter the SSH bastion hostname or the IP address of the SSH bastion. For example, 10.65.2.214 (22 is the port used for SSH; it will be set by default). Instance access examples Version May 08, 2025 566 AMS Advanced User Guide AMS Advanced |
ams-ug-213 | ams-ug.pdf | 213 | an instance ID or IP address. In order to connect to the Linux instance from your Windows machine, you must first connect to an SSH bastion. Use the native Windows OpenSSH client or install PuTTY on your local machine. To learn more about OpenSSH, see OpenSSH in Windows. 1. Use the native Windows or open PuTTY and enter the SSH bastion hostname or the IP address of the SSH bastion. For example, 10.65.2.214 (22 is the port used for SSH; it will be set by default). Instance access examples Version May 08, 2025 566 AMS Advanced User Guide AMS Advanced Concepts and Procedures 2. OpenSSH or PuTTY attempts an SSH connection to the bastion and open a shell window. 3. Use your corporate Active Directory credentials as you would with the RDP hosts to gain access. 4. When presented with a Bash prompt, SSH into the instance. Enter: ssh DOMAIN_FQDN\USERNAME@INSTANCE_IP Team, or role, based access control in an AMS account Scenario: Two application teams A, and B, use a single AMS account for their apps "AA", and "BB", respectively. Team A wants access only to resources for app "AA", and team B wants access only to resources for app "BB". How do I set that up? Use their ITSM's tools to implement team-based access controls (TBAC). For example, you could use the AMS ServiceNow Connector App for integration with AMS APIs. Contact your CSDM for high level guidance of this implementation. Team, or role, based access control in an AMS account Version May 08, 2025 567 AMS Advanced User Guide AMS Advanced Concepts and Procedures Automated instance configuration in AMS Advanced The AMS Advanced automated instance configuration service runs daily and automatically scans and updates the SSM and CloudWatch agents and configuration files on your managed EC2 instances. The updates apply, as needed to: • SSM and CloudWatch agents • CloudWatch configuration files These updates allow AMS to access your AMS-managed EC2 instances, and to configure your instances to emit appropriate logs and metrics. Topics • Prerequisites for automated instance configuration • SSM Agent automatic installation • Automated changes Prerequisites for automated instance configuration For AMS Advanced customers who deploy instances with Change Management, the following prerequisites must be met: • The SSM Agent is installed, and in a managed state. • The instance is tagged as a managed instance. (The aws:cloudformation:stack-name tag has a value starting with stack- or sc-.) If the SSM Agent is not already installed on your instance, you can install it using the AMS SSM Agent auto installation feature. For more information, see SSM Agent automatic installation. Or, you can install the SSM Agent manually. For more information, see the following: • Linux: Manually install SSM Agent on EC2 instances for Linux - AWS Systems Manager • Windows: Manually install SSM Agent on EC2 instances for Windows Server - AWS Systems Manager Prerequisites for automated instance configuration Version May 08, 2025 568 AMS Advanced User Guide AMS Advanced Concepts and Procedures For more information on SSM agent, see the AWS documentation Working with SSM Agent. SSM Agent automatic installation To have AMS manage your Amazon Elastic Compute Cloud (Amazon EC2) instances, you must install AWS Systems Manager SSM Agent on each instance. If your instances don't have SSM Agent installed, then you can use the AMS SSM Agent auto-installation feature. Note • This feature is only available for EC2 instances that aren't in an Auto Scaling group and that run Linux operating systems supported by AMS. • The AMS SSM Agent auto-installation feature is disabled by default. To enable it, reach out to your CA or CSDM. Prerequisites for SSM Agent use • Make sure the instance profile associated with the target instances has one of the following policies (or equivalent permissions as allowlisted in them): • AmazonSSMManagedEC2InstanceDefaultPolicy • AmazonSSMManagedInstanceCore • Make sure that there isn't a Service Control Policy at the AWS Organizations level that explicitly denies the permissions listed in the preceding policies. For more information, see Configure instance permissions required for Systems Manager. • To block outbound traffic, ensure that the following interface endpoints are enabled on the VPC where the target instances reside, (replace "region" in the URL appropriately): • ssm.<region>.amazonaws.com • ssmmessages.<region>.amazonaws.com • ec2messages.<region>.amazonaws.com For more information, see Improve the security of EC2 instances by using VPC endpoints for Systems Manager. SSM Agent automatic installation Version May 08, 2025 569 AMS Advanced User Guide AMS Advanced Concepts and Procedures For general tips on enabling or troubleshooting managed node availability, see Solution 2: Verify that an IAM instance profile has been specified for the instance (EC2 instances only). Note AMS stops and starts each instance as part of the auto-installation process. When an instance is stopped, data stored in instance store volumes and data stored on the RAM is lost. For |
ams-ug-214 | ams-ug.pdf | 214 | • ssmmessages.<region>.amazonaws.com • ec2messages.<region>.amazonaws.com For more information, see Improve the security of EC2 instances by using VPC endpoints for Systems Manager. SSM Agent automatic installation Version May 08, 2025 569 AMS Advanced User Guide AMS Advanced Concepts and Procedures For general tips on enabling or troubleshooting managed node availability, see Solution 2: Verify that an IAM instance profile has been specified for the instance (EC2 instances only). Note AMS stops and starts each instance as part of the auto-installation process. When an instance is stopped, data stored in instance store volumes and data stored on the RAM is lost. For more information, see What happens when you stop an instance. Request automatic installation of SSM Agent on your instances If your accounts are onboarded to AMS Accelerate Patch Add-On, then configure a patch maintenance window (MW) for the instances. A working SSM Agent is required to complete the patch process. If SSM Agent is missing on an instance, then AMS tries to automatically install it during the patch maintenance window. Note AMS stops and starts each instance as part of the auto-installation process. When an instance is stopped, data stored in instance store volumes and data stored on the RAM is lost. For more information, see What happens when you stop an instance. How SSM Agent automatic installation works AMS uses EC2 user data to run the installation script on your instances. To add the user data script and run it on your instances, AMS must stop and start each instance. If your instance already has an existing user data script, then AMS completes the following steps during the auto installation process: 1. Creates a backup of the existing user data script. 2. Replaces the existing user data script with the SSM Agent installation script. 3. Restarts the instance to install SSM Agent. 4. Stops the instance and restores the original script. 5. Restarts the instance with the original script. Request automatic installation of SSM Agent Version May 08, 2025 570 AMS Advanced User Guide AMS Advanced Concepts and Procedures Automated changes The AMS Advanced automated instance configuration service makes changes, as needed, to your EC2 instances. What Changes: • Automatically update code on Linux instances • Automatically update PBIS on Linux instances • Automatically update the minimum version of SSM and CloudWatch agents • CloudWatch configuration files, update details • Automatically configured logs Automatically update code on Linux instances AMS automatically updates on instance code on Linux instances. This helps to improve operational stability and security of the AMS components and environment altogether. FAQ: What's included in the On Instance Code (OIC) on Linux? OIC includes ams-toolkit package along with some configuration files and cron jobs. AMS require these files and packages for integration (Active Directory, CloudFormation and other dependencies). We pre-bake these files into AMS-provided AMIs or install onto your instance during workload ingestion. When will AMS update OIC? AMS update OIC when we release a new version with bug fixes or other improvements. The workflow to check the OIC version and update runs daily. Automatically update PBIS on Linux instances AMS uses the Power Broker Identity Service (PBIS) module to join Linux instances into AMS- managed Active Directory. AMS automatically updates PBIS on Linux instances. FAQ: Automated changes Version May 08, 2025 571 AMS Advanced User Guide AMS Advanced Concepts and Procedures When will AMS update PBIS? AMS turns on PBIS update at reboot. If there is a new PBIS version available, then %AMS; attempts to install the new version during the next instance reboot. Can PBIS update be turned off? You can turn off PBIS update at the instance or account levels: • Account level: Create a parameter in the SSM parameter store: Name: /ams/skip-pbis- update, Value: true (any case). Note The instance profile must have permissions to read SSM parameters. If the flag is missing, then the default behavior is to run the update. • Instance level: • Tag-based: Add the following tag to the instance: Key: skip_pbis_update, Value: true (any case). • Config file: Add the following flag to the /opt/aws/ams/etc/ams.conf.d/state.ini file: skip_pbis_update = true. Note Tag has a higher priority than the SSM parameter. You can turn off the PBIS update at the account level through the parameter, but turn it it for a single (or multiple) instance(s) by adding a tag Key:skip_pbis_update, Value: false. To configure any of the described options, follow the standard change management process in your AMS environment. Automatically update the minimum version of SSM and CloudWatch agents The AMS Advanced minimum version (of the SSM or CloudWatch agents) is the version that has been tested by AMS service team and pre-approved for your operating system. We try to stay Automatically update the minimum version of SSM and CloudWatch agents Version May 08, 2025 572 AMS Advanced User Guide |
ams-ug-215 | ams-ug.pdf | 215 | account level through the parameter, but turn it it for a single (or multiple) instance(s) by adding a tag Key:skip_pbis_update, Value: false. To configure any of the described options, follow the standard change management process in your AMS environment. Automatically update the minimum version of SSM and CloudWatch agents The AMS Advanced minimum version (of the SSM or CloudWatch agents) is the version that has been tested by AMS service team and pre-approved for your operating system. We try to stay Automatically update the minimum version of SSM and CloudWatch agents Version May 08, 2025 572 AMS Advanced User Guide AMS Advanced Concepts and Procedures proactive and run the latest stable and compatible version, so the version number changes over time. You can find the current minimum version by raising a service request to AMS. • SSM Agent Management The Amazon SSM Agent is responsible for running remote commands on the instance. The instance configuration automation ensures that the SSM Agent is running the minimum version. • Cloudwatch Agent Management The Amazon CloudWatch Agent is responsible for emitting OS logs and metrics. Automated instance configuration performs the following: • If needed, disables the legacy CloudWatch Log agent and migrates the configuration to the new unified CloudWatch agent • If your instance is running the legacy CloudWatch Log Agent, automated instance configuration disables the legacy CloudWatch Log agent service and migrates its configuration to the unified CloudWatch agent. • Customizes your CloudWatch configuration to emit appropriate logs and metrics. Affected files and directories: • Windows • %ProgramData%\Amazon\AmazonCloudWatchAgent\ • %ProgramData%\Amazon\AmazonCloudWatchAgent\Configs\ • Linux • /opt/aws/amazon-cloudwatch-agent/etc/ • /opt/aws/amazon-cloudwatch-agent/etc/amazon-cloudwatch-agent.d/ • /opt/aws/ams/opt/aws/amazon-cloudwatch-agent/etc/amazon-cloudwatch-agent.json CloudWatch configuration files, update details We read your custom CloudWatch configurations (JSON only) from the following CloudWatch directories (see recommended directories), and merge them with the standard AMS CloudWatch configuration: • CloudWatch Files • On the instance: CloudWatch configuration files, update details Version May 08, 2025 573 AMS Advanced User Guide • Windows AMS Advanced Concepts and Procedures • %ProgramData%\Amazon\AmazonCloudWatchAgent\Configs\ • %ProgramFiles%\WindowsPowerShell\Modules\AWSManagedServices.Logging.Utilities \Files\Config.json • Linux • /opt/aws/ams/opt/aws/amazon-cloudwatch-agent/etc/amazon-cloudwatch-agent.json • On Amazon S3: • Windows: • https://ams-configuration-artifacts-REGION_NAME.s3.REGION_NAME.amazonaws.com/ configurations/cloudwatch/latest/windows-cloudwatch-config.json • Linux: • https://ams-configuration-artifacts-REGION_NAME.s3.REGION_NAME.amazonaws.com/ configurations/cloudwatch/latest/linux-cloudwatch-config.json Automatically configured logs We configure your instance to write the following logs. • Windows: • AmazonSSMAgentLog • AmazonCloudWatchAgentLog • AmazonSSMErrorLog • AmazonCloudFormationLog • ApplicationEventLog • EC2ConfigServiceEventLog • MicrosoftWindowsAppLockerEXEAndDLLEventLog • MicrosoftWindowsAppLockerMSIAndScriptEventLog • MicrosoftWindowsGroupPolicyOperationalEventLog • SecurityEventLog • SystemEventLog • Linux: Automatically configured logs • /var/log/amazon/ssm/amazon-ssm-agent.log Version May 08, 2025 574 AMS Advanced User Guide AMS Advanced Concepts and Procedures • /var/log/amazon/ssm/errors.log • /var/log/audit/audit.log • /var/log/cloud-init-output.log • /var/log/cloud-init.log • /var/log/cron • /var/log/dpkg.log • /var/log/maillog • /var/log/messages • /var/log/secure • /var/log/spooler • /var/log/syslog • /var/log/yum.log • /var/log/zypper.log Automatically configured logs Version May 08, 2025 575 AMS Advanced User Guide AMS Advanced Concepts and Procedures Monitoring and event management in AMS Topics • What is monitoring? • What does the AMS monitoring system monitor? • How monitoring works • Viewing the monitoring configuration for an AMS account • Changing the monitoring configuration for an AMS account • Application aware incident notifications in AMS • Using OpsCenter in AMS • Alert notifications from AMS • Creating additional CloudWatch alarms in AMS • Creating custom CloudWatch metrics and alarms in AMS • Using CloudWatch Application Insights for .Net and SQL server in AMS • Using Amazon EventBridge Managed Rules in AMS • Trusted Remediator in AMS The AWS Managed Services (AMS) monitoring system monitors your AMS resources for failures, performance degradation, and security issues. The AMS monitoring system relies on AWS services such as Amazon CloudWatch(CloudWatch), Amazon GuardDuty, Amazon Macie, and AWS Health. In addition to the monitoring system, AMS also deploys TrendMicro DeepSecurity for protection against malware on Amazon Elastic Compute Cloud (Amazon EC2) instances, for information about endpoint security (EPS) defaults, see Endpoint Security (EPS). AMS monitoring provides these benefits: • A monitoring baseline so that you have a default level of protection even if you don’t configure any other monitoring for your managed accounts. For information, see Alerts from baseline monitoring in AMS. • Investigation alerts to determine the appropriate action. For example, if GuardDuty finds activity indicating brute forcing attempts against an Amazon EC2 instance, AMS analyzes VPC flowlogs to understand the origin and context of the activity. Version May 08, 2025 576 AMS Advanced User Guide AMS Advanced Concepts and Procedures • Remediation of alerts, when possible, to prevent or reduce the impact for your applications. For example, if you are using a standalone Amazon EC2 instance and it fails the System health check, AMS attempts to recover the instance by stopping and restarting it. For more information, see AMS automatic remediation of alerts. • Transparency into active, and previously resolved, alerts using OpsCenter. For example, if you have an unexpected high CPU utilization on an Amazon EC2 instance, you can request access to the AWS Systems Manager console (includes access to the OpsCenter console) |
ams-ug-216 | ams-ug.pdf | 216 | Guide AMS Advanced Concepts and Procedures • Remediation of alerts, when possible, to prevent or reduce the impact for your applications. For example, if you are using a standalone Amazon EC2 instance and it fails the System health check, AMS attempts to recover the instance by stopping and restarting it. For more information, see AMS automatic remediation of alerts. • Transparency into active, and previously resolved, alerts using OpsCenter. For example, if you have an unexpected high CPU utilization on an Amazon EC2 instance, you can request access to the AWS Systems Manager console (includes access to the OpsCenter console) and view the OpsItem directly in the OpsCenter console. What is monitoring? The AMS monitoring system monitors your AWS resources for failures, performance degradation, and security issues. As a managed account, AMS configures and deploys alarms for applicable AWS resources, monitors them, and performs remediation when applicable. The AMS monitoring system generates alerts based on the monitoring configuration in your account. The monitoring configuration of an account refers to all the resource parameters in the account that create an alert; for information about the resource parameters, see Alerts from baseline monitoring in AMS. The monitoring configuration of an account includes CloudWatch Alarm definitions, and CloudWatch Event Rules that generate the alert (alarm or event). The baseline monitoring configuration is the set of alarm definitions (Alerts from baseline monitoring in AMS) curated by AMS for monitoring resources in your managed account. The monitoring configuration of an account may differ from the baseline configuration, as a result of changes requested by you. A notification of imminent, on-going, receding, or potential failures, performance degradation, or security issues generated by the baseline monitoring configured in an account, is called an alert. Examples of alerts are an Amazon CloudWatch Alarm, an Amazon CloudWatch Event, an Event, or a Finding from AWS service such as Amazon GuardDuty, and an event, or an alert, from Trend Micro Deep Security. Alerts from security-related AWS services such as Amazon GuardDuty, Amazon Macie, or Trend Micro Deep Security are called security alerts to differentiate them from other types of alerts. AMS monitoring provides these benefits: • The ability to customize the baseline resource alarms to meet your requirements. What is monitoring? Version May 08, 2025 577 AMS Advanced User Guide AMS Advanced Concepts and Procedures • Automatic remediation of alerts, when possible, to prevent or reduce the impact for your applications. For example, if you are using a standalone Amazon EC2 instance and it fails the system health check, AMS attempts to recover the instance by stopping and restarting it. For more information, see AMS automatic remediation of alerts. • Transparency into active, and previously resolved, alerts using OpsCenter. For example, if you have an unexpected high CPU utilization on an Amazon EC2 instance, you can request access to the AWS Systems Manager console (which includes access to the OpsCenter console) and view the OpsItem directly in the OpsCenter console. • Investigating alerts to determine the appropriate actions. • Alerts generated based on the configuration in your account and supported AWS services. The monitoring configuration of an account refers to all the resource parameters in the account that create an alert. The monitoring configuration of an account includes CloudWatch Alarm definitions, and EventBridge (formerly known as CloudWatch Events) that generate the alert (alarm or event). For more information about resource parameters, see Alerts from baseline monitoring in AMS. • Notification of imminent, on-going, receding, or potential failures; performance degradation; or security issues generated by the baseline monitoring configured in an account (known as an alert). Examples of alerts include a CloudWatch Alarm, an Event, or a Finding from an AWS service, such as GuardDuty or AWS Health. What does the AMS monitoring system monitor? In keeping with the AWS Managed Services (AMS) shared services responsibility model, the AMS monitoring system monitors your AWS infrastructure. For details on baseline monitoring in AMS, including AWS resources monitored and the type of alerts for each resource, see Alerts from baseline monitoring in AMS. For Amazon EC2 instances, AMS monitors the operating system and provides baseline monitoring based on OS metrics such as CPU utilization and root volume usage. We recommend supplementing AMS monitoring with additional monitoring using AWS services tailored to your application. For guidance on monitoring for availability see the "Monitoring and Alarming" section in this whitepaper Reliability Pillar. You can configure your own monitoring to suit your operational needs; how to do this is discussed in Creating additional CloudWatch alarms in AMS and Creating custom CloudWatch metrics and alarms in AMS. What does the AMS monitoring system monitor? Version May 08, 2025 578 AMS Advanced User Guide AMS Advanced Concepts and Procedures Single-Account Landing Zone proactive monitoring of Active Directory Trust in AMS AMS single-account landing zone (SALZ) monitors the status |
ams-ug-217 | ams-ug.pdf | 217 | with additional monitoring using AWS services tailored to your application. For guidance on monitoring for availability see the "Monitoring and Alarming" section in this whitepaper Reliability Pillar. You can configure your own monitoring to suit your operational needs; how to do this is discussed in Creating additional CloudWatch alarms in AMS and Creating custom CloudWatch metrics and alarms in AMS. What does the AMS monitoring system monitor? Version May 08, 2025 578 AMS Advanced User Guide AMS Advanced Concepts and Procedures Single-Account Landing Zone proactive monitoring of Active Directory Trust in AMS AMS single-account landing zone (SALZ) monitors the status of the one-way trust(s) between the Managed Active Directory (AD) in your AMS managed account and your company domain. The one- way trust with Managed AD is critical for access requests and instance logon requests. With this new monitoring, AMS now proactively responds to trust related issues, and reduces the mean time to detect access related incidents. This feature is automatically enabled in your AWS Managed Services (AMS) accounts. There is a small cost impact. The feature uses four AWS CloudWatch metrics, and two AWS CloudWatch alarms for one trust. How monitoring works See the following graphics on monitoring architecture in AWS Managed Services (AMS). The following diagram provides a high-level overview of the AMS multi-account landing zone and AMS single-account landing zone monitoring workflow. • Generation: At the time of account onboarding, AMS configures baseline monitoring (a combination of CloudWatch (CW) alarms, and CW event rules) for all your resources created in a managed account. The baseline monitoring configuration generates an alert when a CW alarm is triggered or a CW event is generated. Single-Account Landing Zone proactive monitoring of Active Directory Trust Version May 08, 2025 579 AMS Advanced User Guide • Aggregation: AMS Advanced Concepts and Procedures • Multi-Account Landing Zone: Alerts are generated by your resources within Application and Core Organizational Unit accounts and sent to the AMS monitoring system by directing them through the Security account. • Single-Account Landing Zone: All alerts generated by your resources are sent to the AMS monitoring system by directing them to an SNS topic in the account. • You can also configure how AMS groups EC2 alerts together. AMS either groups all alerts related to the same EC2 instance into a single incident, or creates one incident per alert, depending on your preference. You can change this configuration at any time by working with your Cloud Service Delivery Manager or Cloud Architect. This works the same way whether you are using Multi-Account Landing Zone or Single-Account Landing Zone. • Processing: AMS analyzes the alerts and processes them based on their potential for impact. Alerts are processed as described next. • Alerts with known customer impact: These lead to the creation of a new incident report and AMS follows the incident management process; for information about incident management, see AMS incident response. Example alert: An Amazon EC2 instance fails a system health check, AMS attempts to recover the instance by stopping and restarting it. • Alerts with uncertain customer impact: For these types of alerts, AMS sends an incident report, in many cases asking you to verify the impact before AMS takes action. However, if the infrastructure-related checks are passing, then AMS doesn't send an incident report to you. For example: An alert for >85% CPU utilization for more than 10 minutes on an Amazon EC2 instance can't immediately be categorized as an incident since this behavior might be expected based on usage. In this example, AMS Automation performs infrastructure-related checks on the resource. If those checks pass, then AMS doesn't send an alert notification, even if CPU usage crossed 99%. If Automation detects that infrastructure-related checks are failing on the resource, then AMS sends an alert notification and checks if mitigation is needed. Alert notifications are discussed in detail in this section. AMS offers mitigation options in the notification. When you reply to the notification confirming that the alert is an incident AMS creates a new incident report and the AMS incident management process begins. Service notifications that receive a response of "no customer impact," or no response at all for three days, is marked as resolved and the corresponding alert is marked as resolved. • Alerts with no customer impact: If, after evaluation, AMS determines that the alert doesn't have customer impact, then the alert is closed. How monitoring works Version May 08, 2025 580 AMS Advanced User Guide AMS Advanced Concepts and Procedures For example, AWS Health notifies of an EC2 instance requiring replacement but that instance has since been terminated. EC2 instance grouped notifications You can configure AMS monitoring to group together alerts from the same EC2 instance into a single incident. Your Cloud Service Delivery Manager or Cloud Architect can configure this for you. There |
ams-ug-218 | ams-ug.pdf | 218 | corresponding alert is marked as resolved. • Alerts with no customer impact: If, after evaluation, AMS determines that the alert doesn't have customer impact, then the alert is closed. How monitoring works Version May 08, 2025 580 AMS Advanced User Guide AMS Advanced Concepts and Procedures For example, AWS Health notifies of an EC2 instance requiring replacement but that instance has since been terminated. EC2 instance grouped notifications You can configure AMS monitoring to group together alerts from the same EC2 instance into a single incident. Your Cloud Service Delivery Manager or Cloud Architect can configure this for you. There are four parameters you can configure for each AMS-managed account. 1. Scope: Choose either account-wide or tag-based. • To specify a configuration that applies to every EC2 instance in that account, choose scope = account-wide. • To specify a configuration that applies only to EC2 instances in that account with a specific tag, choose scope = tag-based. 2. Grouping rule: Choose either classic or instance. • To configure instance-level grouping for every resource in your account, choose scope = account-wide and grouping rule = instance. • To configure specific resources in your account to use instance level grouping, tag those instances and then choose scope = tag-based and grouping rule = instance level. • To not use instance grouping for alerts in your account, choose grouping rule = classic. 3. Engagement option: Choose either none, report only, or default. • For AMS to not create incidents or run automations for alarms from those resources while the configuration is active, choose none. • For AMS to not create incidents or run automations for alarms from those resources while the configuration is active, and not run automated healing Systems Manager documents but to include records of these events in your reporting, choose report only. This may be useful if you want to reduce the volume of incident support cases you interact with and if some incidents from some resources do not require immediate attention, for example those in a non-production account. • For AMS to process your alerts, run automations, and create incident cases when needed, choose default. 4. Resolve after: Choose either 24 hours, 48 hours, or 72 hours. Lastly, configure when incident cases are automatically closed. If the time from the last case correspondence reaches the configured Resolve after value, the incident is closed. EC2 instance grouped notifications Version May 08, 2025 581 AMS Advanced User Guide Alert notification AMS Advanced Concepts and Procedures As a part of the alert processing, based on the impact analysis, AWS Managed Services (AMS) creates an incident and initiates the incident management process for remediation, when impact can be determined. If impact can't be determined, then AMS sends an alert notification to the email address associated with your account through a service notification. In some scenarios, this alert notification isn't sent. For example, if the infrastructure-related checks are passing for a high CPU utilization alert, then an alert notification isn't sent to you. For more information, see the diagram on AMS monitoring architecture for alert handling process in How monitoring works. Tag-based alert notification Use tags to send alert notifications for your resources to different email addresses. It's a best practice to use tag-based alert notifications because notifications sent to a single email address might cause confusion when multiple developer teams use the same account. Tag-based alert notifications are not affected by the EC2 instance grouped notifications settings you choose. With tag-based alert notifications you can: • Send alerts to a specific email address: Tag resources that have alerts that must be sent to a specific email address with the key = OwnerTeamEmail, value = EMAIL_ADDRESS. • Send alerts to multiple email addresses: To use multiple email addresses, specify a comma- separated list of values. For example, key = OwnerTeamEmail, value = EMAIL_ADDRESS_1, EMAIL_ADDRESS_2, EMAIL_ADDRESS_3, .... The total number of characters for the value field cannot exceed 260. • Use a custom tag key: To use a custom tag key, provide the custom tag key name to your CSDM in an email that explicitly gives consent to activate automated notifications for the tag-based communication. It's a best practice to use the same tagging strategy for contact tags across all your instances and resources. Note The key value OwnerTeamEmail doesn't have to be in camel case. However, tags are case sensitive and it's best practice to use the recommended format. The email address must be specified in full, with the "at sign" (@) to separate the local part from the domain. Examples of invalid email addresses: Team.AppATabc.xyz or john.doe. For general guidance on your tagging strategy, see Tagging AWS resources. Tag-based alert notification Version May 08, 2025 582 AMS Advanced User Guide AMS Advanced Concepts and Procedures Don't add personally identifiable information (PII) in your |
ams-ug-219 | ams-ug.pdf | 219 | for contact tags across all your instances and resources. Note The key value OwnerTeamEmail doesn't have to be in camel case. However, tags are case sensitive and it's best practice to use the recommended format. The email address must be specified in full, with the "at sign" (@) to separate the local part from the domain. Examples of invalid email addresses: Team.AppATabc.xyz or john.doe. For general guidance on your tagging strategy, see Tagging AWS resources. Tag-based alert notification Version May 08, 2025 582 AMS Advanced User Guide AMS Advanced Concepts and Procedures Don't add personally identifiable information (PII) in your tags. Use distribution lists or aliases wherever possible. Tag-based alert notification is supported for resources from the following Amazon Services: EC2, Elastic Block Store (EBS), Elastic Load Balancing (ELB), Application Load Balancer (ALB), Network Load Balancer, Relational Database Service (RDS), OpenSearch, Elastic File System (EFS), FSx, and Site-to-Site VPN. Viewing the monitoring configuration for an AMS account There are two key parts to the monitoring configuration of an account that you can view: • CloudWatch Alarms: You can view all the CW alarms in the account by going to the CloudWatch console and selecting different services of interest. • CloudWatch Events: • Multi-Account Landing Zone: CloudWatch Events monitored in the account can be found by filtering for all CW event rules with the string "ams-". • Single-Account Landing Zone: CloudWatch Events monitored in the account can be found by filtering for all CW event rules with the string "mc-". Changing the monitoring configuration for an AMS account You can change your baseline monitoring configuration for Amazon EC2 resources. For the alerts that can be configured, see Alerts from baseline monitoring in AMS. You can change the alarm definition, alarm destination, or opt-out of the alarm notification for the baseline monitors so that the alerts meet your application’s operational requirements. You can request any or all of the previously mentioned changes by submitting a Management | Other | Other | Update CT (ct-0xdawir96cy7k) with the following details. • Instance IDs [optional, if not mentioned, all instances in the account are in-scope] • CloudWatch metric name, for example, CPU utilization / swap free / IOwait • Target - email ID / phone number for SMS / SNS topic To learn more about the type of changes you can request in the baseline monitoring configuration, see the Amazon CloudWatch Documentation. Viewing the monitoring configuration for an account Version May 08, 2025 583 AMS Advanced User Guide AMS Advanced Concepts and Procedures Application aware incident notifications in AMS Use application aware automated incident notifications to customize your communication experience for support cases that AMS creates on your behalf. When you use this feature, AMS retrieves custom workload preferences from AWS Service Catalog AppRegistry to enrich your AMS incident communications with metadata about your applications and to customize the severity of support cases created by AMS on your behalf. To use this feature, you must first provision AWS Service Catalog AppRegistry in your AMS account. To learn more about AMS monitoring defaults, see Monitoring and event management in AMS. Provision AppRegistry in your AMS account and create applications The AppRegistry service is available in Self-service Provisioning (SSP) mode for your AMS account. For instructions on how to request access, see Use AMS SSP to provision AWS Service Catalog AppRegistry in your AMS account. After provisioning AppRegistry, use one of the following methods to create applications: 1. AWS console: To learn more about creating an application in AppRegistry through the AWS console, see Creating Applications in the AWS Service Catalog AppRegistry Administrator Guide. 2. CloudFormation: You can define your AppRegistry application just like you define any other resource. For more information, see AWS Service Catalog AppRegistry resource type reference in the AWS CloudFormation User Guide. Create tags to enable case enrichment You must tag your applications before AMS can access application metadata. The following table lists the required tag. Tag key ams-managed Tag value true Customize AMS support case severity for your applications You can customize the severity of AMS created support cases by specifying how critical your application is for your organization. This setting is controlled by an attribute group associated with Application aware incident notifications in AMS Version May 08, 2025 584 AMS Advanced User Guide AMS Advanced Concepts and Procedures your application in AppRegistry. The name of the attribute group name must match the following pattern: AMS.<ApplicationName>.CommunicationOptions In the preceding pattern, the ApplicationName must match the name used in AppRegistry when you created the application. Example content: { "SchemaVersion": "1.0", "Criticality": "low" } SchemaVersion This determines the schema version that you're using and the subset of features available to use. Schema version Feature 1.0 Criticality Customized support case severity based on Criticality value The criticality of this application determines the severity of the |
ams-ug-220 | ams-ug.pdf | 220 | notifications in AMS Version May 08, 2025 584 AMS Advanced User Guide AMS Advanced Concepts and Procedures your application in AppRegistry. The name of the attribute group name must match the following pattern: AMS.<ApplicationName>.CommunicationOptions In the preceding pattern, the ApplicationName must match the name used in AppRegistry when you created the application. Example content: { "SchemaVersion": "1.0", "Criticality": "low" } SchemaVersion This determines the schema version that you're using and the subset of features available to use. Schema version Feature 1.0 Criticality Customized support case severity based on Criticality value The criticality of this application determines the severity of the support cases created by the AMS automated systems. Valid values: low|normal|high|urgent|critical For more information on severity levels, see SeverityLevel in the AWS Support API Reference. Required: Yes Customize AMS support case severity for your applications Version May 08, 2025 585 AMS Advanced User Guide AMS Advanced Concepts and Procedures Review required permissions To use this feature, AMS requires access to the following AWS Identity and Access Management permissions: • iam:ListRoleTags • iam:ListUserTags • resourcegroupstaggingapi:GetResources • servicecatalog-appregistry:GetApplication • servicecatalog-appregistry:ListAssociatedAttributeGroups • servicecatalog-appregistry:GetAttributeGroup Important Make sure that there isn't an IAM policy or service control policy (SCP) that denies the preceding actions. The API calls are made by the ams-access-admin role. The following is an example of what you might see: arn:aws:sts::111122223333:assumed-role/ams-access-admin/AMS-AMSAppMetadataLookup-* Using OpsCenter in AMS The AWS Managed Services (AMS) Operations team uses AWS Systems Manager OpsCenter for diagnosing and remediating many alerts related to your resources. Using OpsCenter reduces mean time to resolution (MTTR), while providing a transparent view into the operational queues of the AMS operations teams. With OpsCenter, AMS provides you with a transparent view of operational work items, also known as OpsItems, actively being worked upon by AMS teams, in addition to automated solutions. To learn more about OpsCenter and OpsItems, see AWS Systems Manager OpsCenter. For information about getting access to the AWS Management Console, see Working with the AWS Management Console. From the AWS Management Console you can navigate to the AWS Review required permissions Version May 08, 2025 586 AMS Advanced User Guide AMS Advanced Concepts and Procedures Systems Manager Console, and OpsCenter; to learn more, see AWS Systems Manager Session Manager. OpsCenter also provides an API that you can use; for information, see Learn More About OpsCenter. OpsCenter is a priced feature with ~1000 OpsItems that cost under $10. For information, see AWS Systems Manager pricing. Alert notifications from AMS As a part of the alert processing, based on the impact analysis, AWS Managed Services (AMS) creates an incident and initiates the incident management process for remediation, when impact can be determined. In case impact cannot be determined, AMS sends an alert notification to the email address associated with your account through a service notification; see the diagram on AMS monitoring architecture for alert handling process in How monitoring works. Receiving alerts generated by AMS AWS Managed Services (AMS) enables you to receive alert notifications for Amazon EC2 resources directly to reduce communication delays. To receive Amazon EC2 alerts directly, subscribe your target (preferred email) to the Amazon SNS topic Direct-Customer-Alerts using the Management | Monitoring and notification | SNS | Subscribe change type (ct-3rcl9u1k017wu). Note Not all baseline alerts are sent to the Direct-Customer-Alerts topic by default. To see all alerts that are generated by the AMS monitoring system, subscribe to the Amazon SNS topic for the AMS monitoring system. In the request, ask for the "AMS Monitoring Topic", specify a subscription channel to receive the alerts (Lambda, Amazon SQS, HTTP/S, email, or SMS), and specify the endpoints (for example, email addresses, if you choose the email protocol) that will receive the alerts. The AMS monitoring topic receives alerts that are used by AMS shared services, so it can be noisy. To learn more, see the Subscribe section in the Amazon Simple Notification Service Subscribe API reference. For a list of baseline alerts AMS provides, see Alerts from baseline monitoring in AMS. Alert notifications Version May 08, 2025 587 AMS Advanced User Guide AMS Advanced Concepts and Procedures Tag-based alert notifications in AMS Use tags to send alert notifications for your resources to different email addresses. It's a best practice to use tag-based alert notifications because notifications sent to a single email address might cause confusion when multiple developer teams use the same account. Important Tag-based alert notifications only work for notifications related to Amazon EC2, Amazon EBS, Elastic Load Balancing, Network Load Balancer, Application Load Balancer, Amazon RDS, Amazon Redshift, and OpenSearch. Don't add personally identifiable information (PII) in your tags. Send alerts to a specific email address Tag resources that have alerts that must be sent to a specific email address with the key = OwnerTeamEmail, value = EMAIL_ADDRESS. Send alerts to multiple email addresses To use multiple email addresses, specify |
ams-ug-221 | ams-ug.pdf | 221 | alert notifications because notifications sent to a single email address might cause confusion when multiple developer teams use the same account. Important Tag-based alert notifications only work for notifications related to Amazon EC2, Amazon EBS, Elastic Load Balancing, Network Load Balancer, Application Load Balancer, Amazon RDS, Amazon Redshift, and OpenSearch. Don't add personally identifiable information (PII) in your tags. Send alerts to a specific email address Tag resources that have alerts that must be sent to a specific email address with the key = OwnerTeamEmail, value = EMAIL_ADDRESS. Send alerts to multiple email addresses To use multiple email addresses, specify a comma-separated list of values. For example, key = OwnerTeamEmail, value = EMAIL_ADDRESS_1, EMAIL_ADDRESS_2, EMAIL_ADDRESS_3, .... The total number of characters for the value field cannot exceed 260. Use a custom tag key To use a custom tag key, provide the custom tag key name to your CSDM in an email providing consent to activate automated notification for the tag-based communication. It's a best practice to use the same tagging strategy for contact tags across all your instances and resources. The email address must be specified in full, with the "at sign" (@) to separate the local part from the domain. Examples of invalid email addresses: Team.AppATabc.xyz or john.doe. For general guidance on your tagging strategy, see Using tags. To tag an existing resource, submit an RFC with the Deployment | Advanced stack components | Tag | Create (auto) (ct-3cx7we852p3af) change type. Tag-based alert notifications Version May 08, 2025 588 AMS Advanced User Guide AMS Advanced Concepts and Procedures Note The key value OwnerTeamEmail does not have to be in camel case. However, tags are case sensitive and it's best practice to use the recommended format. AMS automatic remediation of alerts Some alerts are automatically remediated by AWS Managed Services (AMS). This section describes how this remediation works and the conditions that must be met for the remediation to take place. Alert name Status Check Failed Description Thresholds Action Possible hardware failures or a fault state of The system has detected a failed status at least AMS automatic remediati on first validates if the the instance. once within the last 15 instance is accessible. If minutes. AMSLinuxD iskUsage Trigger when the disk usage of 1 mount point (designated space on a volume) on your EC2 instance is filling up. The threshold is above the defined value 6 times on the last 30 minutes. the instance is inaccessi ble, then the instance is stopped and restarted . The stop and start allows the instance to migrate to new underlyin g hardware. For more information, see the following section "EC2 Status Check Failure Remediation Automatio n." AMS automatic remediation first deletes temporary files. If that does not free up enough disk space, it extends the volume to prevent AMS automatic remediation of alerts Version May 08, 2025 589 AMS Advanced User Guide AMS Advanced Concepts and Procedures Alert name Description Thresholds Action downtime if the volume becomes full. AMSWindow sDiskUsage When the disk usage of 1 mount point (designat The threshold is above the defined value 6 AMS automatic remediation first deletes ed space on a volume) times during the last 30 temporary files. If that on your EC2 instance is minutes. filling up. does not free up enough disk space, it extends the volume to prevent downtime if the volume becomes full. RDS- EVENT -0089 The DB instance has consumed more than 90% of its allocated storage. The storage is more than 90% allocated. AMS automatic remediati on first validates that the DB is in a modifiable and available or storage-full state. It then attempts to increase the allocated storage, IOPS, and storage throughput through a CloudForm ation changeset. If stack drift is already detected, it falls back to the RDS API to prevent downtime. AMS automatic remediation of alerts Version May 08, 2025 590 AMS Advanced User Guide AMS Advanced Concepts and Procedures Alert name RDS- EVENT -0007 Description Thresholds Action Allocated storage for the DB instance has been Storage is 100% allocated. exhausted. To resolve, allocate additional storage. AMS automatic remediati on first validates that the DB is in a modifiable and available or storage-full state. It then attempts to increase the allocated storage, IOPS, and storage throughput through a CloudForm ation changeset. If stack drift is already detected, it falls back to the RDS API to prevent downtime. AMS automatic remediation of alerts Version May 08, 2025 591 AMS Advanced User Guide AMS Advanced Concepts and Procedures Alert name RDS- EVENT -0224 Description Thresholds Action The requested allocated storage reaches or The maximum storage threshold for the DB AMS automatic remediati on first validates that exceeds the configure instance has been the requested amount d maximum storage exhausted or is greater of RDS storage will threshold. than or |
ams-ug-222 | ams-ug.pdf | 222 | to increase the allocated storage, IOPS, and storage throughput through a CloudForm ation changeset. If stack drift is already detected, it falls back to the RDS API to prevent downtime. AMS automatic remediation of alerts Version May 08, 2025 591 AMS Advanced User Guide AMS Advanced Concepts and Procedures Alert name RDS- EVENT -0224 Description Thresholds Action The requested allocated storage reaches or The maximum storage threshold for the DB AMS automatic remediati on first validates that exceeds the configure instance has been the requested amount d maximum storage exhausted or is greater of RDS storage will threshold. than or equal to the breach the max storage requested allocated threshold. If confirmed storage. , AMS attempts to increase the max storage threshold by 30% with a CloudFormation changeset, or direct RDS API if resources are not provisioned through CloudFormation. This feature can be opted out of by adding the following tag to the RDS DB Instance: "Key: ams:rt:ams-rds- max-allocated- storage-policy, Value: ams-opt-o ut". AMS automatic remediation of alerts Version May 08, 2025 592 AMS Advanced User Guide AMS Advanced Concepts and Procedures Alert name Description Thresholds Action RDS-Stora ge-Capaci Less than 1GB is left at the allocated storage for ty the DB instance. Storage is 99% allocated. AMS automatic remediati on first validates that the DB is in a modifiable and available or storage-full state. It then attempts to increase the allocated storage, IOPS, and storage throughput through a CloudForm ation changeset. If stack drift is already detected, it falls back to the RDS API to prevent downtime. EC2 status check failure: Remediation automation notes How AMS auto-remediation works with EC2 status check failure issues: • If your Amazon EC2 instance has become unreachable, the instance must be stopped and started again so it can be migrated to new hardware and recovered. • If the root of the problem is within the OS (missing devices in fstab, kernel corruption, and so on), the automation is not able to recover your instance. • If your instance belongs to an Auto Scaling group, the automation takes no action—the AutoScalingGroup scaling action replaces the instance. • If your instance has EC2 Auto Recovery enabled, the remediation doesn't take action. EC2 volume usage remediation automation How AWS Managed Services (AMS) auto-remediation works with EC2 volume usage issues: AMS automatic remediation of alerts Version May 08, 2025 593 AMS Advanced User Guide AMS Advanced Concepts and Procedures • The automation first validates if the volume expansion is required and if it can be performed. If the expansion is deemed appropriate, the automation can increase the volume capacity. This automated process balances the need for growth with controlled, limited expansion. • Before extending a volume, the automation performs cleanup tasks (Windows: Disk Cleaner, Linux: Logrotate + Simple Service Manager Agent Log removal) on the instance to try to free up space. Note The cleanup tasks are not run on EC2 "T" family instances due to their reliance on CPU credits for continued functionality. • On Linux, the automation only supports extending file systems of type EXT2, EXT3, EXT4 and XFS. • On Windows, the automation only supports New Technology File System (NTFS) and Resilient File System (ReFS). • The automation doesn't extend volumes that are part of Logical Volume Manager (LVM) or a RAID array. • The automation doesn't extend instance store volumes. • The automation doesn't take action if the affected volume is already bigger than 2 TiB. • The expansion through automation is limited to a maximum of three times per week and five times total over the system's lifetime. • The automation doesn't expand the volume if the previous expansion happened within the last six hours. When these rules prevent the automation from taking action, AMS reaches out to you through an outbound service request to determine the next actions to take. Amazon RDS low storage event remediation automation How AWS Managed Services (AMS) auto-remediation works with Amazon RDS low storage event issues: • Before trying to extend the Amazon RDS instance storage, the automation performs several checks to ensure the Amazon RDS instance is in a modifiable and available, or storage-full, state. • Where CloudFormation stack drift is detected, remediation occurs through the Amazon RDS API. AMS automatic remediation of alerts Version May 08, 2025 594 AMS Advanced User Guide AMS Advanced Concepts and Procedures • The remediation action does not run in the following scenarios: • The Amazon RDS instance status is not "available" or "storage-full". • The Amazon RDS instance storage is not currently modifiable (such as when the storage has been modified in the last six hours). • The Amazon RDS instance has auto-scaling storage enabled. • The Amazon RDS instance is not a resource within a CloudFormation stack. • Remediation is limited to one expansion per six hours |
ams-ug-223 | ams-ug.pdf | 223 | the Amazon RDS API. AMS automatic remediation of alerts Version May 08, 2025 594 AMS Advanced User Guide AMS Advanced Concepts and Procedures • The remediation action does not run in the following scenarios: • The Amazon RDS instance status is not "available" or "storage-full". • The Amazon RDS instance storage is not currently modifiable (such as when the storage has been modified in the last six hours). • The Amazon RDS instance has auto-scaling storage enabled. • The Amazon RDS instance is not a resource within a CloudFormation stack. • Remediation is limited to one expansion per six hours and no more than three expansions within a rolling fourteen day period. • When these scenarios occur, AMS reaches out to you with an outbound incident to determine next actions. Creating additional CloudWatch alarms in AMS You can create new CloudWatch alarms using the AWS Managed Services (AMS) Deployment | Monitoring and notification | CloudWatch | Create alarms change type. Important AMS does not monitor CloudWatch alarms created by you. Using custom CloudWatch metrics and alarms for Amazon EC2 instances (works only for mutable deployments that do not rely on updated AMIs deployed to Auto Scaling groups): 1. Produce your application monitoring script and custom metric. For more information and access to example scripts, see Monitoring Memory and Disk Metrics for Amazon EC2 Linux Instances. The Amazon CloudWatch monitoring scripts for Linux Amazon EC2 instances demonstrate how to produce and consume Amazon CloudWatch custom metrics. These sample Perl scripts comprise a fully functional example that reports memory, swap, and disk space utilization metrics for a Linux instance. 2. Upload your monitoring script. To upload the monitoring script to your Auto Scaling group or Amazon EC2 instance configuration, you can use UserData when configuring your Auto Scaling group or Amazon EC2 instance, or, if your application was deployed with CodeDeploy, you can modify the configuration with a Deployment | Applications | CodeDeploy application | Deploy CT (ct-2edc3sd1sqmrb). Creating additional CloudWatch alarms Version May 08, 2025 595 AMS Advanced User Guide AMS Advanced Concepts and Procedures 3. Publish your custom metric to CloudWatch (the first time you publish a data point for a new custom metric, it is created), see Publishing Custom Metrics. 4. Create the CloudWatch alarm, see Create a CloudWatch Alarm for an Instance. Important Monitoring data must be sent to this path [infra/INSTANCE_ID/YOUR_CUSTOM_METRIC] To modify or delete a CloudWatch alarm, submit an RFC with the Management | Other | Other | Create change type (ct-1e1xtak34nx76) with the parameters required to complete the action as described in the Amazon CloudWatch API reference PutMetricAlarm. You can use the CloudWatch event stream. AMS is integrated with CloudWatch and you can request that any AWS API call trigger a CloudWatch event. To do this, submit a Management | Other | Other | Update CT (ct-0xdawir96cy7k) with the API calls that you are interested in. An AMS operator will talk to you to gather requirements. To learn more, see the Amazon CloudWatch Documentation. To get access to the CloudWatch event stream, submit a Management | Other | Other | Update CT (ct-0xdawir96cy7k) to add a party to the SNS notification topic. An AMS operator will talk to you to gather requirements. Creating custom CloudWatch metrics and alarms in AMS You can store your business and application metrics in Amazon CloudWatch. You can view graphs, and set alarms based on these metrics, just as you can for the metrics that CloudWatch already stores for your AWS Managed Services (AMS) resources. To learn more about CloudWatch, see Amazon CloudWatch Concepts. Amazon SNS allows applications to send time-critical messages to multiple subscribers through a "push" mechanism against the AMS Managed Monitoring System or MMS, Amazon SNS (SNS) topic that the alarms are published to; in this case, MMS and your SQS queues. You can use CloudWatch to create custom metrics and, through an SNS topic, have AMS alarm you appropriately. To do this, follow these steps. Creating custom CloudWatch metrics and alarms Version May 08, 2025 596 AMS Advanced User Guide AMS Advanced Concepts and Procedures Note This process doesn't work for immutable deployments that rely on updated AMIs deployed to Auto Scaling groups, it is suitable for mutable application (not ASG) deployments. Setting up a custom metric within the limitations of AMS Advanced, is a complex task. For an example from CloudWatch, see Example: Count occurrences of a term. 1. Produce your application monitoring script and custom metric (such as the count occurrences example). For more information and access to example scripts, see Monitoring Memory and Disk Metrics for Amazon EC2 Linux Instances. 2. Upload your monitoring script. To upload the monitoring script to your Auto Scaling group or Amazon EC2 instance configuration, you can use UserData when configuring your Auto Scaling group or Amazon EC2 |
ams-ug-224 | ams-ug.pdf | 224 | for mutable application (not ASG) deployments. Setting up a custom metric within the limitations of AMS Advanced, is a complex task. For an example from CloudWatch, see Example: Count occurrences of a term. 1. Produce your application monitoring script and custom metric (such as the count occurrences example). For more information and access to example scripts, see Monitoring Memory and Disk Metrics for Amazon EC2 Linux Instances. 2. Upload your monitoring script. To upload the monitoring script to your Auto Scaling group or Amazon EC2 instance configuration, you can use UserData when configuring your Auto Scaling group or Amazon EC2 instance, or, if your application was deployed with CodeDeploy, you can modify the configuration with a Deployment | Applications | CodeDeploy application | Deploy CT (ct-2edc3sd1sqmrb). 3. Publish your custom metric to CloudWatch (the first time you publish a data point for a new custom metric, it is created), see Publish Custom Metrics. 4. To integrate your customer metric to your application monitoring system, request AMS create an SNS topic for the metric by submitting an RFC with the Management | Other | Other | Create CT (ct-1e1xtak34nx76). 5. Create the CloudWatch alarm, see Creating Amazon CloudWatch Alarms. Important Monitoring data must be sent to this path [infra/INSTANCE_ID/YOUR_CUSTOM_METRIC]. Using CloudWatch Application Insights for .Net and SQL server in AMS You can use Amazon CloudWatch Application Insights to set up the monitors for your AWS Managed Services (AMS) application resources to continuously analyze data for signs of problems with your applications and reduce your mean time to repair (MTTR) when troubleshooting Using CloudWatch Application Insights for .Net and SQL server Version May 08, 2025 597 AMS Advanced User Guide AMS Advanced Concepts and Procedures application issues. For details about CloudWatch Application Insights, see CloudWatch Application Insights for .NET and SQL Server. Important AMS does not monitor problems from CloudWatch Application Insights because they are for application code controlled by you. To use CloudWatch Application Insights, submit an RFC with the Management | Other | Other | Create change type (ct-1e1xtak34nx76) with a request to create an IAM role that provides you with permission to configure CloudWatch Application Insights. There are two options to receive the problems identified: through an SNS topic or with a target in CloudWatch Event rules. In the RFC, specify which you want. If you plan to use CloudWatch Event rules, also specify the rule definition in the RFC. After you're set up with CloudWatch Application Insights, you receive notice of potential problems including insights that point to a possible root cause. To learn how you can assume the role, see the AMS Onboarding Guide Federate your Active Directory with the AMS IAM Roles. Using Amazon EventBridge Managed Rules in AMS AMS Advanced uses Amazon EventBridge Managed Rules. A Managed Rule is a unique type of rule that is directly linked to AMS. These rules match incoming events and send them to targets for processing. Managed Rules are predefined by AMS and include event patterns that are required by the service to manage customer accounts, and unless defined otherwise, only the owning service can utilize these Managed Rules. AMS Managed Rules are linked to events.managedservices.amazonaws.com service principal. These Managed Rules are managed through the AWSServiceRoleForManagedServices_Events service-linked role. To delete these rules a special confirmation by the customer is required. For more information see Deleting Managed Rules for AMS. For more information about rules, see Rules in the Amazon EventBridge User Guide. AMS Event Router Version May 08, 2025 598 AMS Advanced User Guide AMS Advanced Concepts and Procedures Amazon EventBridge Managed Rules deployed by AMS Amazon EventBridge Managed Rules Rule Name Description Definition { { "source": ["aws.cloudwatch"], "detail-type": ["CloudWatch Alarm State Change"], } } AMSAdvanc edCoreRule This rule forwards Amazon CloudWatc h Alarms to AMS Monitoring. The Amazon CloudWatc h events monitor CloudWatch Alarms. Creating Managed Rules for AMS You don’t need to manually create Amazon EventBridge Managed Rules. When you onboard to AMS in the AWS Management Console, the AWS CLI, or the AWS API, AMS creates them for you. Editing Managed Rules for AMS AMS doesn't allow you to edit the Managed Rules. Name and event pattern for each Managed Rule are predefined by AMS. Deleting Managed Rules for AMS You don’t need to manually delete the Managed Rules. When you offboard from AMS in the AWS Management Console, the AWS CLI, or the AWS API, AMS cleans up the resources and deletes all Managed Rules owned by AMS for you. Amazon EventBridge Managed Rules deployed by AMS Version May 08, 2025 599 AMS Advanced User Guide AMS Advanced Concepts and Procedures In the event AMS fails to remove the Managed Rules during offboarding, you can also use the Amazon EventBridge console, the AWS CLI or the AWS API to manually delete the Managed Rules. To |
ams-ug-225 | ams-ug.pdf | 225 | Managed Rules for AMS You don’t need to manually delete the Managed Rules. When you offboard from AMS in the AWS Management Console, the AWS CLI, or the AWS API, AMS cleans up the resources and deletes all Managed Rules owned by AMS for you. Amazon EventBridge Managed Rules deployed by AMS Version May 08, 2025 599 AMS Advanced User Guide AMS Advanced Concepts and Procedures In the event AMS fails to remove the Managed Rules during offboarding, you can also use the Amazon EventBridge console, the AWS CLI or the AWS API to manually delete the Managed Rules. To do this, you must first offboard from AMS and conduct a force delete of the Managed Rules. Trusted Remediator in AMS Trusted Remediator is an AWS Managed Services solution that automates the remediation of AWS Trusted Advisor checks. Trusted Remediator creates recommendations when Trusted Advisor checks indicate opportunities for you to reduce costs, improve system availability, optimize performance, or close security gaps for your AWS accounts. With Trusted Remediator, you can address these security, performance, cost optimization, fault tolerance, and service limit recommendations in a safe, standardized way that uses established best practices. Trusted Remediator allows you to configure a remediation solution and runs automatically on a schedule that you create, simplifying the remediation process. This streamlined approach addresses issues consistently, efficiently, and without manual intervention. Topics • Trusted Remediator key benefits • How Trusted Remediator works • Key terms for Trusted Remediator • Get started with Trusted Remediator in AMS • Trusted Advisor checks supported by Trusted Remediator • Configure Trusted Advisor check remediation in Trusted Remediator • Execution mode decision workflow • Configure remediation tutorials • Work with remediations in Trusted Remediator • Remediation logs in Trusted Remediator • Best practices in Trusted Remediator • Trusted Remediator FAQs Trusted Remediator key benefits The following are the key benefits of Trusted Remediator: Trusted Remediator Version May 08, 2025 600 AMS Advanced User Guide AMS Advanced Concepts and Procedures • Improved security, performance, and cost optimization: Trusted Remediator helps you to enhance your accounts' overall security posture, optimize resource utilization, and reduce operational costs. • Self-service setup and configuration: You can configure Trusted Remediator to align with your requirements and preferences. • Automated Trusted Advisor check remediation: After configuration, Trusted Remediator automatically runs the remediation actions for selected Trusted Advisor checks. This automation eliminates the need for manual intervention. • Best practice implementation: Remediation actions are based on established best practices, so issues are addressed in a standardized and effective manner. • Scheduled execution: You can choose the remediation schedule that aligns with your day-to- day operational workflows. Trusted Remediator empowers you to proactively address identified issues in your AWS environments, helping you to adhere to best practices and maintain secure, high-performing, and cost-effective cloud infrastructure. How Trusted Remediator works The following is an illustration of the Trusted Remediator workflow: Trusted Remediator assesses Trusted Advisor recommendations for your AWS accounts and creates AWS Systems Manager OpsItems in OpsCenter. Then, you can use Trusted Remediator automation documents to remediate the OpsItems automatically or manually. The following are details for each type of remediation: • Automated remediation: Trusted Remediator runs the automation document and monitors the run. After the automation document completes, Trusted Remediator resolves the Opsitem. • Manual remediation: Trusted Remediator creates the OpsItem for you to review. After you review, you can create an automated RFC, Trusted Remediator | Finding | Remediate, change type How Trusted Remediator works Version May 08, 2025 601 AMS Advanced User Guide AMS Advanced Concepts and Procedures to remediate the resource. For information on the manual remediation steps, see Run manual remediations in Trusted Remediator. Remediation logs are stored in an Amazon S3 bucket. You can use the data in the S3 bucket to build custom QuickSight dashboards for reporting. AMS also provides on-request reports for Trusted Remediator. To receive these reports, contact your CSDM. Key terms for Trusted Remediator The following are terms that are useful to know when you use Trusted Remediator in AMS: • AWS Trusted Advisor: A cloud optimization service provided by AWS. Trusted Advisor inspects your AWS environment and provides recommendations based on best practices in the following six categories: • Cost optimization • Performance • Security • Fault tolerance • Operational excellence • Service limits For more information, see AWS Trusted Advisor. • Trusted Remediator: An AMS remediation solution for Trusted Advisor checks. Trusted Remediator helps you to safely remediate Trusted Advisor checks with known best practices to improve security, performance, and reduce costs. Trusted Remediator is easy to setup and configure. You configure once, and Trusted Remediator runs remediations on your preferred schedule (daily or weekly). • AWS Systems Manager SSM document: A JSON or YAML file that defines the actions that AWS Systems Manager performs on your |
ams-ug-226 | ams-ug.pdf | 226 | • Cost optimization • Performance • Security • Fault tolerance • Operational excellence • Service limits For more information, see AWS Trusted Advisor. • Trusted Remediator: An AMS remediation solution for Trusted Advisor checks. Trusted Remediator helps you to safely remediate Trusted Advisor checks with known best practices to improve security, performance, and reduce costs. Trusted Remediator is easy to setup and configure. You configure once, and Trusted Remediator runs remediations on your preferred schedule (daily or weekly). • AWS Systems Manager SSM document: A JSON or YAML file that defines the actions that AWS Systems Manager performs on your AWS resources. The SSM document serves as a declarative specification to automate operational tasks across multiple AWS resources and instances. • AWS Systems Manager OpsCenter OpsItem: A cloud operational issue management resource that helps you track and resolve operational issues in your AWS environment. OpsItems provide a centralized view and management system for operational data and issues across AWS services and resources. Each OpsItem represents an operational issue, such as a potential security risk, a performance problem, or an operational incident. Key terms Version May 08, 2025 602 AMS Advanced User Guide AMS Advanced Concepts and Procedures • Configuration: A configuration is a set of attributes stored in AWS AppConfig, a capability of AWS Systems Manager. The Trusted Remediator application in AWS AppConfig helps to configure remediations at the account level. • Execution mode: Execution mode is a configuration attribute that determines how to run the remediation for each Trusted Advisor check result. There are four supported execution modes: Automated, Manual, Conditional, Inactive. • Resource override: This feature uses resource tags to override a configuration for specific resources. • Remediation item log: A log file in the Trusted Remediator remediation S3 log bucket. The remediation item log is created when remediation OpsItems are created. This log file contains manual execution remediation OpsItems and automated execution remediation OpsItems. Use this log file to track all remediation items. • Automated remediation execution log: A log file in the Trusted Remediator remediation S3 log bucket. The automated remediation execution log is created when automated an SSM document run completes. This log contains SSM execution details for automated execution remediation OpsItems. Use this log file to track automated remediations. Get started with Trusted Remediator in AMS Trusted Remediator is available in AMS at no additional charge. Trusted Remediator supports single account and multi-account configurations. Topics • Onboard to Trusted Remediator • AMS configures your AWS accounts in Trusted Remediator • Choose the Trusted Advisor checks to remediate • Track your remediations in Trusted Remediator • Run manual remediations in Trusted Remediator Onboard to Trusted Remediator To onboard your AMS accounts to Trusted Remediator, email your Cloud Architects or Cloud Service Delivery Managers (CSDMs). In the email, include the following information: Get started with Trusted Remediator Version May 08, 2025 603 AMS Advanced User Guide AMS Advanced Concepts and Procedures • AWS accounts: The twelve-digit account identification number. All accounts that you want to onboard to Trusted Remediator must belong to the same AMS Advanced customer. • Delegated administrator account: The account that is used for Trusted Advisor check configuration for single or multiple accounts. • Member accounts: These are the accounts linked to the delegated administrator account. These accounts inherit the configurations from the delegated administrator account. You can have one member account or multiple member accounts. Note Member accounts inherit the configurations from the delegated administrator account. If you need different configurations for specific accounts, then onboard multiple delegated administrator accounts with your preferred configurations. Plan the account structure and the configurations with your Cloud Architects before you onboard. • AWS Region: The AWS Region where your resources are located. For a list of AWS Regions, see AWS services by Region. • Remediation schedule and time: Your preferred remediation schedule (daily or weekly). Trusted Remediator gathers Trusted Advisor checks and initiates remediation at the scheduled time. For example, you can set the remediation schedule for 1:00 AM Sunday every week, Australian Eastern Standard Time. • Notification email: Trusted Remediator uses the notification email to notify you when your scheduled remediations complete. Note Review your applications and resources after every scheduled remediation. For additional support, contact AMS. After you submit your onboard request with the required details to your CA or CSDM, AMS onboards your accounts to Trusted Remediator. Trusted Remediator uses AWS AppConfig, a capability of AWS Systems Manager, to define the configuration for the Trusted Advisor checks. These configurations are a set of attributes that are stored in AWS AppConfig. To prevent unauthorized charges to your resources, all supported Trusted Advisor checks are set to Inactive when accounts are onboarded to Trusted Remediator. These configurations help you to Get started with Trusted Remediator Version May 08, 2025 604 AMS Advanced User Guide |
ams-ug-227 | ams-ug.pdf | 227 | support, contact AMS. After you submit your onboard request with the required details to your CA or CSDM, AMS onboards your accounts to Trusted Remediator. Trusted Remediator uses AWS AppConfig, a capability of AWS Systems Manager, to define the configuration for the Trusted Advisor checks. These configurations are a set of attributes that are stored in AWS AppConfig. To prevent unauthorized charges to your resources, all supported Trusted Advisor checks are set to Inactive when accounts are onboarded to Trusted Remediator. These configurations help you to Get started with Trusted Remediator Version May 08, 2025 604 AMS Advanced User Guide AMS Advanced Concepts and Procedures automatically remediate specific Trusted Advisor checks, or to assess and manually remediate the remaining checks. The configurations are highly customizable, allowing you to apply configurations for each Trusted Advisor check. For more information, see Configure Trusted Advisor check remediation in Trusted Remediator. AMS configures your AWS accounts in Trusted Remediator When onboarding is complete, your CA or CDSM notifies you and the default configurations are created in your delegated administrator AWS account. The configuration is stored in AWS AppConfig under the Trusted Remediator application. You can use the RFC Management | Trusted Remediator | Remediation configuration | Update to request configuration updates. For more information, see Configure Trusted Advisor check remediation in Trusted Remediator. To view the default Trusted Remediator configurations, complete the following steps: 1. Open the AWS Systems Manager console at https://console.aws.amazon.com/systems- manager/. Note Make sure that you're in the delegated administrator account. 2. Choose Application Management, AppConfig. 3. Select Trusted Remediator from the list of applications. The following is an example of the AWS AppConfig console showing Trusted Remediator configurations: Get started with Trusted Remediator Version May 08, 2025 605 AMS Advanced User Guide AMS Advanced Concepts and Procedures Choose the Trusted Advisor checks to remediate By default, remediation execution mode is Inactive for all Trusted Advisor checks in your configuration. This prevents unauthorized remediation and protects resources. AMS provides curated SSM automation documents for Trusted Advisor check remediation. To select the checks that you want to remediate with Trusted Remediator, complete the following steps: 1. Review the list of supported Trusted Advisor checks and the name of the associated SSM automation documents to decide which checks you want to remediate with Trusted Remediator. 2. Submit a Management | Trusted Remediator | Remediation configuration | Update request to update configuration for your selected Trusted Advisor checks. For instructions on how to select checks, see Configure Trusted Advisor check remediation in Trusted Remediator. Get started with Trusted Remediator Version May 08, 2025 606 AMS Advanced User Guide AMS Advanced Concepts and Procedures Track your remediations in Trusted Remediator After you update your account-level configuration, Trusted Remediator creates OpsItems for each remediation. Trusted Remediator runs the SSM document for automated remediation of OpsItems according to your remediation schedule. For instructions on how to view all remediation OpsItems from the Systems Manager OpsCenter console, see Track remediations in Trusted Remediator. Run manual remediations in Trusted Remediator You can manually remediate Trusted Advisor checks using an automated RFC. When you choose manual remediation, Trusted Remediator creates a manual execution OpsItem. For more information, see Run manual remediations in Trusted Remediator. Trusted Advisor checks supported by Trusted Remediator The following table lists the supported Trusted Advisor checks, SSM automation documents, preconfigured parameters, and the expected outcome of the automation documents. Review the expected outcome to help you understand possible risks based on your business requirements before you enable an SSM automation document for check remediation. Make sure that the corresponding config rule for each Trusted Advisor check is present for the supported checks that you want to enable remediation for. For more information, see View AWS Trusted Advisor checks powered by AWS Config. If a check has corresponding AWS Security Hub controls, make sure that the Security Hub control is enabled. For more information, see Enabling controls in Security Hub. For information on managing preconfigured parameters, see Configure Trusted Advisor check remediation in Trusted Remediator. Trusted Advisor cost optimization checks supported by Trusted Remediator Check ID and name SSM document name and expected outcome Supported preconfigured parameters and constraints Z4AUBRNSmz Unassocia ted Elastic IP AWSManagedServices-TrustedR emediatorReleaseElasticIP No preconfigured parameters are allowed. Releases an elastic IP address that is No constraints Addresses not associated with any resource. Supported Trusted Advisor checks Version May 08, 2025 607 AMS Advanced User Guide AMS Advanced Concepts and Procedures Check ID and name SSM document name and expected outcome Supported preconfigured parameters and constraints c18d2gz128 Amazon ECR Repositor y Without AWSManagedServices-TrustedR emediatorPutECRLifecyclePolicy ImageAgeLimit: The maximum age limit in days (1-365) for 'any' image Creates a lifecycle policy for the specified repository if a lifecycle No constraints in the Amazon ECR repository. Lifecycle Policy policy does not already exist. AWSManagedServices-DeleteUn usedEBSVolume • CreateSnapshot: |
ams-ug-228 | ams-ug.pdf | 228 | preconfigured parameters are allowed. Releases an elastic IP address that is No constraints Addresses not associated with any resource. Supported Trusted Advisor checks Version May 08, 2025 607 AMS Advanced User Guide AMS Advanced Concepts and Procedures Check ID and name SSM document name and expected outcome Supported preconfigured parameters and constraints c18d2gz128 Amazon ECR Repositor y Without AWSManagedServices-TrustedR emediatorPutECRLifecyclePolicy ImageAgeLimit: The maximum age limit in days (1-365) for 'any' image Creates a lifecycle policy for the specified repository if a lifecycle No constraints in the Amazon ECR repository. Lifecycle Policy policy does not already exist. AWSManagedServices-DeleteUn usedEBSVolume • CreateSnapshot: If set to true, then the automation creates a Configured DAvU99Dc4C Underutilized Amazon EBS Deletes underutilized Amazon Volumes EBS volumes if the volumes are unattached for the last 7 days. An Amazon EBS snapshot is created by default. snapshot of the Amazon EBS volume before it's deleted. The default setting is true. Valid values are true and false (case- sensitive). • MinimumUnattachedDays: Minimum unattached days of the EBS volume to delete, up to 62 days. If set to 0, then the SSM document doesn't check the unattached period and deletes the volume if the volume is currently unattached. The default is value is 7. No constraints Supported Trusted Advisor checks Version May 08, 2025 608 AMS Advanced User Guide AMS Advanced Concepts and Procedures Check ID and name SSM document name and expected outcome Supported preconfigured parameters and constraints hjLMh88uM8 Idle Load Balancers AWSManagedServices-DeleteId leClassicLoadBalancer IdleLoadBalancerDays: The number of days that the Classic Load Deletes an idle Classic Load Balancer if it's unused and no instances are registered. Balancer has 0 requested connectio ns before considering it idle. The default is seven days. If auto execution is enabled, the automation deletes idle Classic Load Balancers if there are no active back- end instances. For all idle Classic Load Balancers that have active back-end instances, but don't have healthy back-end instances, auto remediation isn't used and OpsItems for manual remediation are created. Ti39halfu8 Amazon AWSManagedServices-StopIdle RDSInstance No preconfigured parameters are allowed. RDS Idle DB Amazon RDS DB instance that has No constraints Instances been in an idle state for the last seven days is stopped. COr6dfpM05 AWS Lambda over-provisioned functions for memory size AWSManagedServices-ResizeLa mbdaMemory AWS Lambda function's memory size is resized to the recommended memory size provided by Trusted Advisor. RecommendedMemorySize: The recommended memory allocatio n for the Lambda function. Value range is between 128 and 10240. If the Lambda function size was modified before the automation runs, then the settings might be overwritten by this automation with the value recommended by Trusted Advisor. Supported Trusted Advisor checks Version May 08, 2025 609 AMS Advanced User Guide AMS Advanced Concepts and Procedures Check ID and name SSM document name and expected outcome Supported preconfigured parameters and constraints Qch7DwouX1 Low Utilization Amazon EC2 Instances AWSManagedServices-StopEC2I nstance (Default SSM document for both auto and manual execution ForceStopWithInstanceStore: Set to true to force stop instances using instance store. Otherwise, set to mode.) Amazon EC2 instances with low utilization are stopped. false. The default value of false prevents instance from stopping. Valid values are true or false (case- sensitive). No constraints Supported Trusted Advisor checks Version May 08, 2025 610 AMS Advanced User Guide AMS Advanced Concepts and Procedures Check ID and name SSM document name and expected outcome Supported preconfigured parameters and constraints Qch7DwouX1 Low Utilization AWSManagedServices-ResizeIn stanceByOneLevel • MinimumDaysSinceLastChange: Minimum number of days since Amazon EC2 Amazon EC2 instance is resized by Instances one instance type down in the same instance family type. The instance is stopped and started during the resize operation and returned to the initial state after the SSM document run completes. This automation doesn't support resizing instances that are in an Auto Scaling Group. the last instance type change. If the instance type was modified within a specified time, then the instance type isn't changed. Use 0 to skip this validation. The default is 7. • CreateAMIBeforeResize: To create the instance AMI as a backup before resizing, choose true. To not create a backup, choose false. The default is false. Valid values are true and false (case- sensitive). • ResizeIfStopped: To proceed with the instance size change, even if the instance is in a stopped state, choose true. To not automatically resize the instance if in a stopped state, choose false. Valid values are true and false (case-sen sitive). No constraints Supported Trusted Advisor checks Version May 08, 2025 611 AMS Advanced User Guide AMS Advanced Concepts and Procedures Check ID and name SSM document name and expected outcome Supported preconfigured parameters and constraints Qch7DwouX1 Low Utilization AWSManagedServices-Terminat eInstance Amazon EC2 Low utilized Amazon EC2 instances Instances are terminated if not part of an Auto Scaling Group and termination protection isn't enabled. An AMI is CreateAMIBeforeTermination: Set this |
ams-ug-229 | ams-ug.pdf | 229 | if the instance is in a stopped state, choose true. To not automatically resize the instance if in a stopped state, choose false. Valid values are true and false (case-sen sitive). No constraints Supported Trusted Advisor checks Version May 08, 2025 611 AMS Advanced User Guide AMS Advanced Concepts and Procedures Check ID and name SSM document name and expected outcome Supported preconfigured parameters and constraints Qch7DwouX1 Low Utilization AWSManagedServices-Terminat eInstance Amazon EC2 Low utilized Amazon EC2 instances Instances are terminated if not part of an Auto Scaling Group and termination protection isn't enabled. An AMI is CreateAMIBeforeTermination: Set this option to true or false to create an instance AMI as a backup before terminating the EC2 instance. The default is true. Valid values are true and false (case-sensitive). created by default. No constraints G31sQ1E9U Underutil AWSManagedServices-PauseRed shiftCluster No preconfigured parameters are allowed. ized Amazon The Amazon Redshift cluster is No constraints Redshift Clusters paused. c1cj39rr6v Amazon S3 Incomplet e Multipart AWSManagedServices-TrustedR emediatorEnableS3AbortIncom DaysAfterInitiation:The number of days after which Amazon S3 stops pleteMultipartUpload an incomplete multipart upload. Amazon S3 bucket is configure Default is set to 7 days. Upload Abort d with a lifecycle rule to abort No constraints Configuration multipart uploads that remain incomplete after certain days. Trusted Advisor security checks supported by Trusted Remediator Check ID and name SSM document name and expected outcome Supported preconfigured parameters and constraints 12Fnkpl8Y5 Exposed Access Keys AWSManagedServices-TrustedR emediatorDeactivateIAMAccessKey No preconfigured parameters are allowed. The exposed IAM access key is deactivated. Supported Trusted Advisor checks Version May 08, 2025 612 AMS Advanced User Guide AMS Advanced Concepts and Procedures Check ID and name SSM document name and expected outcome Supported preconfigured parameters and constraints Hs4Ma3G127 - API Gateway AWSManagedServices-TrustedR emediatorEnableAPIGateWayEx ecutionLogging Execution logging is enabled on the API stage. Applications configured with an exposed IAM access key can't authenticate. LogLevel: Logging level to enable execution logging, ERROR - Logging is enabled for errors only. INFO - Logging is enabled for all events. You must grant API Gateway permission to read and write logs to CloudWatch for your account in order to enable execution log, refer to Set up CloudWatch logging for REST APIs in API Gateway for detail. AWSManagedServices-EnableAp iGateWayXRayTracing No preconfigured parameters are allowed. X-Ray tracing is enabled on the API No constraints stage. REST and WebSocket API execution logging should be enabled Corresponding AWS Security Hub check: APIGateway.1 Hs4Ma3G129 - API Gateway REST API stages should have AWS X-Ray tracing enabled Corresponding AWS Security Hub check: APIGateway.3 Supported Trusted Advisor checks Version May 08, 2025 613 AMS Advanced User Guide AMS Advanced Concepts and Procedures Check ID and name SSM document name and expected outcome Supported preconfigured parameters and constraints Hs4Ma3G202 - API Gateway REST API cache data should be encrypted at rest Corresponding AWS Security Hub check: APIGateway.5 Hs4Ma3G177 - Correspon ding AWS AWSManagedServices-EnableAP IGatewayCacheEncryption No preconfigured parameters are allowed. Enable encryption at rest for API No constraints Gateway REST API cache data if the API Gateway REST API stage has cache enabled. AWSManagedServices-TrustedR emediatorEnableAutoScalingG HealthCheckGracePeriod: The amount of time, in seconds, that roupELBHealthCheck Auto Scaling waits before checking Security Hub Elastic Load Balancing health checks check - Auto are enabled for the Auto Scaling scaling groups Group. associated with a load balancer should use load balancer health checks AutoScali ng.1 the health status of an Amazon Elastic Compute Cloud instance that has come into service. Turning on Elastic Load Balancing health checks might result in replacing a running instance if any of the Elastic Load Balancing load balancers attached to the Auto Scaling group report it as unhealthy. For more information, see Attach an Elastic Load Balancing load balancer to your Auto Scaling group Supported Trusted Advisor checks Version May 08, 2025 614 AMS Advanced User Guide AMS Advanced Concepts and Procedures Check ID and name SSM document name and expected outcome Supported preconfigured parameters and constraints Hs4Ma3G245 - AWS CloudForm AWSManagedServices-EnableCF NStackNotification NotificationARNs: The ARNs of the Amazon SNS topics to be associate Associate a CloudFormation stack with an Amazon SNS topic for stacks. d with selected CloudFormation notification. To enable auto remediation, The NotificationARNs preconfig ured parameter must be provided. ation stacks should be integrated with Amazon Simple Notification Service Corresponding AWS Security Hub check: CloudForm ation.1 Supported Trusted Advisor checks Version May 08, 2025 615 AMS Advanced User Guide AMS Advanced Concepts and Procedures Check ID and name SSM document name and expected outcome Supported preconfigured parameters and constraints AWSManagedServices-EnableCl oudFrontDistributionLogging • BucketName: The name of the Amazon S3 bucket where you Logging is enabled for Amazon CloudFront distributions. want to store access logs. • S3KeyPrefix: The prefix for the location in the S3 bucket for theAmazon CloudFront distribut ion logs. • IncludeCookies: Indicates whether to include cookies in access logs. To enable auto remediation, |
ams-ug-230 | ams-ug.pdf | 230 | Amazon Simple Notification Service Corresponding AWS Security Hub check: CloudForm ation.1 Supported Trusted Advisor checks Version May 08, 2025 615 AMS Advanced User Guide AMS Advanced Concepts and Procedures Check ID and name SSM document name and expected outcome Supported preconfigured parameters and constraints AWSManagedServices-EnableCl oudFrontDistributionLogging • BucketName: The name of the Amazon S3 bucket where you Logging is enabled for Amazon CloudFront distributions. want to store access logs. • S3KeyPrefix: The prefix for the location in the S3 bucket for theAmazon CloudFront distribut ion logs. • IncludeCookies: Indicates whether to include cookies in access logs. To enable auto remediation, the following preconfigured parameters must be provided: • BucketName • S3KeyPrefix • IncludeCookies For this remediations constraints, see How do I turn on logging for my CloudFront distribution? AWSManagedServices-TrustedR emediatorEnableCloudTrailLo No preconfigured parameters are allowed. gValidation Enables CloudTrail trail log validatio n. No constraints Hs4Ma3G21 0 - CloudFron t distributions should have logging enabled Corresponding AWS Security Hub check: CloudFront.2 Hs4Ma3G109 - CloudTrail log file validatio n should be enabled Corresponding AWS Security Hub check: CloudTrail.4 Supported Trusted Advisor checks Version May 08, 2025 616 AMS Advanced User Guide AMS Advanced Concepts and Procedures Check ID and name SSM document name and expected outcome Supported preconfigured parameters and constraints Hs4Ma3G10 8 - CloudTrai l trails should be integrated with Amazon CloudWatch Logs Corresponding AWS Security Hub check: CloudTrail.5 AWSManagedServices-Integrat eCloudTrailWithCloudWatch • CloudWatchLogsLogGroupArn: The Amazon Resource Name AWS CloudTrail is integrated with CloudWatch Logs. (ARN) of an Amazon CloudWatch Logs log group. • CloudWatchLogsRoleArn: The ARN of an IAM role used by AWS CloudTrail to integrate with CloudWatch. To enable auto remediation, the following preconfigured parameters must be provided: • CloudWatchLogsLogGroupArn • CloudWatchLogsRoleArn Hs4Ma3G21 7 - CodeBuild AWSManagedServices-TrustedR emediatorEnableCodeBuildLog No preconfigured parameters are allowed. No constraints project gingConfig Enables the logging for CodeBuild project. environments should have a logging AWS configuration Corresponding AWS Security Hub check: CodeBuild.4 Supported Trusted Advisor checks Version May 08, 2025 617 AMS Advanced User Guide AMS Advanced Concepts and Procedures Check ID and name SSM document name and expected outcome Supported preconfigured parameters and constraints Hs4Ma3G306 - Neptune DB AWSManagedServices-TrustedR emediatorDisablePublicAcces No preconfigured parameters are allowed. No constraints clusters should sOnDocumentDBSnapshot Removes public access from Amazon DocumentDB manual cluster snapshot. have deletion protection enabled Corresponding AWS Security Hub check: DocumentDB.3 Hs4Ma3G30 8 - Amazon AWSManagedServices-TrustedR emediatorEnableDocumentDBCl No preconfigured parameters are allowed. No constraints DocumentDB usterDeletionProtection Enables deletion protection for Amazon DocumentDB cluster. clusters should have deletion protection enabled Corresponding AWS Security Hub check: DocumentDB.5 Supported Trusted Advisor checks Version May 08, 2025 618 AMS Advanced User Guide AMS Advanced Concepts and Procedures Check ID and name SSM document name and expected outcome Supported preconfigured parameters and constraints Hs4Ma3G323 - DynamoDB AWSManagedServices-TrustedR emediatorEnableDynamoDBTabl No preconfigured parameters are allowed. tables should eDeletionProtection No constraints have deletion protection enabled Corresponding AWS Security Hub check: DynamoDB.6 ePs02jT06 w - Amazon EBS Public Snapshots Enables deletion protection for non- AMS DynamoDB tables. AWSManagedServices-TrustedR emediatorDisablePublicAcces No preconfigured parameters are allowed. sOnEBSSnapshot Public access for Amazon EBS snapshot is disabled. No constraints Hs4Ma3G118 - VPC default AWSManagedServices-TrustedR emediatorRemoveAllRulesFrom No preconfigured parameters are allowed. No constraints security groups DefaultSG All ingress and egress rules in the default security group are removed. should not allow inbound or outbound traffic Corresponding AWS Security Hub check: EC2.2 Supported Trusted Advisor checks Version May 08, 2025 619 AMS Advanced User Guide AMS Advanced Concepts and Procedures Check ID and name SSM document name and expected outcome Supported preconfigured parameters and constraints Hs4Ma3G117 - Attached EBS volumes should be encrypted at- rest Corresponding AWS Security Hub check: EC2.3 AWSManagedServices-EncryptI nstanceVolume • KMSKeyId: AWS KMS key ID or ARN to encrypt the volume. The attached Amazon EBS volume on the instance is encrypted. • DeleteStaleNonEncryptedSnap shotBackups: A flag that decides whether the snapshot backup of the old unencrypted volumes should be deleted. The instance is rebooted as a part of the remediation and rollback is possible if DeleteStaleNonEncr is set yptedSnapshotBackups to false which helps with restore. Hs4Ma3G120 - Stopped EC2 AWSManagedServices-Terminat eInstance CreateAMIBeforeTermination:. To create the instance AMI as a backup Amazon EC2 instances stopped for 30 days are terminated. before terminating the EC2 instance, choose true. To not create a backup before terminating, choose false. The default is true. No constraints instances should be removed after a specified time period Corresponding AWS Security Hub check: EC2.4 Supported Trusted Advisor checks Version May 08, 2025 620 AMS Advanced User Guide AMS Advanced Concepts and Procedures Check ID and name SSM document name and expected outcome Supported preconfigured parameters and constraints Hs4Ma3G121 - EBS default AWSManagedServices-EncryptE BSByDefault No preconfigured parameters are allowed. Amazon EBS encryption by default is Encryption by default is a Region- enabled for the specific AWS Region specific setting. If you enable it for encryption should be |
ams-ug-231 | ams-ug.pdf | 231 | create a backup before terminating, choose false. The default is true. No constraints instances should be removed after a specified time period Corresponding AWS Security Hub check: EC2.4 Supported Trusted Advisor checks Version May 08, 2025 620 AMS Advanced User Guide AMS Advanced Concepts and Procedures Check ID and name SSM document name and expected outcome Supported preconfigured parameters and constraints Hs4Ma3G121 - EBS default AWSManagedServices-EncryptE BSByDefault No preconfigured parameters are allowed. Amazon EBS encryption by default is Encryption by default is a Region- enabled for the specific AWS Region specific setting. If you enable it for encryption should be enabled Corresponding AWS Security Hub check: EC2.7 Hs4Ma3G124 - Amazon EC2 AWSManagedServices-TrustedR emediatorEnableEC2InstanceI instances should MDSv2 Amazon EC2 instances use Instance Metadata Service Version 2 (IMDSv2). use Instance Metadata Service Version 2 (IMDSv2) Corresponding AWS Security Hub check: EC2.8 a Region, you can't disable it for individual volumes or snapshots in that Region. • IMDSv1MetricCheckPeriod: The number of days (42-455) to analyze IMDSv1 usage metrics in CloudWatch. If the Amazon EC2 instance was created within the specified time period, then the analysis begins from the instance's creation date. • HttpPutResponseHopLimit: The maximum number of network hops allowed for the instance metadata token. This value can be configured between 1 and 2 hops. A hop limit of 1 restricts token access to processes running directly on the instance, while a hop limit of 2 allows access from containers running on the instance. No constraints Supported Trusted Advisor checks Version May 08, 2025 621 AMS Advanced User Guide AMS Advanced Concepts and Procedures Check ID and name SSM document name and expected outcome Supported preconfigured parameters and constraints AWSManagedServices-UpdateAu toAssignPublicIpv4Addresses No preconfigured parameters are allowed. VPC subnets are configured to No constraints not automatically assign public IP addresses. Hs4Ma3G207 - EC2 subnets should not automatically assign public IP addresses Corresponding AWS Security Hub check: EC2.15 Hs4Ma3G20 9 - Unused AWSManagedServices-DeleteUn usedNACL No preconfigured parameters are allowed. Delete unused network ACL No constraints AWSManagedServices-DeleteSe curityGroups No preconfigured parameters are allowed. Delete unused security groups. No constraints Network Access Control Lists are removed Corresponding AWS Security Hub check: EC2.16 Hs4Ma3G215 - Unused Amazon EC2 security groups should be removed Corresponding AWS Security Hub check: EC2.22 Supported Trusted Advisor checks Version May 08, 2025 622 AMS Advanced User Guide AMS Advanced Concepts and Procedures Check ID and name SSM document name and expected outcome Supported preconfigured parameters and constraints Hs4Ma3G24 7 - Amazon EC2 Transit Gateway should AWSManagedServices-TrustedR emediatorDisableTGWAutoVPCA ttach - Disables the automatic acceptance of VPC attachment not automatic requests for the specified non-AMS ally accept VPC Amazon EC2 Transit Gateway. No preconfigured parameters are allowed. No constraints attachment requests Corresponding AWS Security Hub check: EC2.23 Hs4Ma3G235 - ECR private AWSManagedServices-TrustedR emediatorSetImageTagImmutab No preconfigured parameters are allowed. No constraints repositories ility Sets the image tag mutability settings to IMMUTABLE for the specified repository. should have tag immutability configured Corresponding AWS Security Hub check: ECR.2 Supported Trusted Advisor checks Version May 08, 2025 623 AMS Advanced User Guide AMS Advanced Concepts and Procedures Check ID and name SSM document name and expected outcome Supported preconfigured parameters and constraints AWSManagedServices-PutECRRe positoryLifecyclePolicy LifecyclePolicyText: The JSON repository policy text to apply to the ECR repository has a lifecycle policy configured. repository. To enable auto remediation, the following preconfigured parameters must be provided: LifecyclePolicyText AWSManagedServices-TrustedR emediatorEnableEKSAuditLog No preconfigured parameters are allowed. Audit log is enabled for EKS cluster. No constraints AWSConfigRemediation-DropIn validHeadersForALB No preconfigured parameters are allowed. Application Load Balancer is configured to invalid header fields. No constraints Hs4Ma3G216 - ECR repositor ies should have at least one lifecycle policy configured Corresponding AWS Security Hub check: ECR.3 Hs4Ma3G325 - EKS clusters should have audit logging enabled Corresponding AWS Security Hub check: EKS.8 Hs4Ma3G183 - Application load balancer should be configured to drop HTTP headers Corresponding AWS Security Hub check: ELB.4 Supported Trusted Advisor checks Version May 08, 2025 624 AMS Advanced User Guide AMS Advanced Concepts and Procedures Check ID and name SSM document name and expected outcome Supported preconfigured parameters and constraints AWSManagedServices-EnableEL BLogging Application Load Balancer and Classic Load Balancer logging is enabled. • BucketName: The bucket name (not the ARN). Make sure that the bucket policy is correctly configure d for logging. • S3KeyPrefix: The prefix for the location in the Amazon S3 bucket for the Elastic Load Balancing logs. To enable auto remediation, the following preconfigured parameter s must be provided: BucketName and S3KeyPrefix:. Make sure the Amazon S3 bucket has a bucket policy that grants Elastic Load Balancing permission to write the access logs to the bucket. AWSManagedServices-TrustedR emediatorEnableEMRBlockPubl No preconfigured parameters are allowed. icAccess Amazon EMR block public access settings is turned on for the account. No constraints Hs4Ma3G184 - Application Load Balancers and Classic Load Balancers logging should be enabled Corresponding AWS |
ams-ug-232 | ams-ug.pdf | 232 | is correctly configure d for logging. • S3KeyPrefix: The prefix for the location in the Amazon S3 bucket for the Elastic Load Balancing logs. To enable auto remediation, the following preconfigured parameter s must be provided: BucketName and S3KeyPrefix:. Make sure the Amazon S3 bucket has a bucket policy that grants Elastic Load Balancing permission to write the access logs to the bucket. AWSManagedServices-TrustedR emediatorEnableEMRBlockPubl No preconfigured parameters are allowed. icAccess Amazon EMR block public access settings is turned on for the account. No constraints Hs4Ma3G184 - Application Load Balancers and Classic Load Balancers logging should be enabled Corresponding AWS Security Hub check: ELB.5 Hs4Ma3G32 6 - Amazon EMR block public access setting should be enabled Corresponding AWS Security Hub check: EMR.2 Supported Trusted Advisor checks Version May 08, 2025 625 AMS Advanced User Guide AMS Advanced Concepts and Procedures Check ID and name SSM document name and expected outcome Supported preconfigured parameters and constraints AWSManagedServices-CancelKe yDeletion No preconfigured parameters are allowed. AWS KMS key deletion is canceled. No constraints Hs4Ma3G13 5 - AWS KMS keys should not be deleted unintentionally Corresponding AWS Security Hub check: KMS.3 Hs4Ma3G29 9 - Amazon AWSManagedServices-TrustedR emediatorEnableNeptuneDBClu No preconfigured parameters are allowed. No constraints DocumentDB sterDeletionProtection Enables deletion protection for Amazon Neptune cluster. manual cluster snapshots should not be public Corresponding AWS Security Hub check: Neptune.4 Supported Trusted Advisor checks Version May 08, 2025 626 AMS Advanced User Guide AMS Advanced Concepts and Procedures Check ID and name SSM document name and expected outcome Supported preconfigured parameters and constraints Hs4Ma3G319 - Network Firewall firewalls should have deletion AWSManagedServices-TrustedR emediatorEnableNetworkFirew allDeletionProtection - Enables the delete protection for AWS Network No preconfigured parameters are allowed. No constraints protection enabled Firewall. Corresponding AWS Security Hub check: NetworkFi rewall.9 Hs4Ma3G223 - OpenSearch domains should encrypt data sent between nodes Corresponding AWS Security Hub check: OpenSearch.3 AWSManagedServices-EnableOp enSearchNodeToNodeEncryption No preconfigured parameters are allowed. Node to Node encryption is enabled After node-to-node encryption for the domain. is enabled, you can't disable the setting. Instead, take a manual snapshot of the encrypted domain, create another domain, migrate your data, and then delete the old domain. Supported Trusted Advisor checks Version May 08, 2025 627 AMS Advanced User Guide AMS Advanced Concepts and Procedures Check ID and name SSM document name and expected outcome Supported preconfigured parameters and constraints Hs4Ma3G222 - OpenSearch domain error logging to CloudWatch Logs should be enabled Corresponding AWS Security Hub check: Opensearch.4 Hs4Ma3G221 - OpenSearch domains should have audit logging enabled Corresponding AWS Security Hub check: Opensearch.5 AWSManagedServices-EnableOp enSearchLogging CloudWatchLogGroupArn: The ARN of anAmazon CloudWatch Logs log Error logging is enabled for the group. OpenSearch domain. To enable auto remediation, the following preconfigured parameter must be provided: CloudWatc hLogGroupArn. Amazon CloudWatch resource policy must be configured with permissions. For more informati on, see Enabling audit logs in the Amazon OpenSearch Service User Guide AWSManagedServices-EnableOp enSearchLogging CloudWatchLogGroupArn: The ARN of the CloudWatch Logs group to OpenSearch domains are configured publish logs to. with audit logging enabled. To enable auto remediation, the following preconfigured parameter must be provided: CloudWatc hLogGroupArn Amazon CloudWatch resource policy must be configured with permissions. For more informati on, see Enabling audit logs in the Amazon OpenSearch Service User Guide Supported Trusted Advisor checks Version May 08, 2025 628 AMS Advanced User Guide AMS Advanced Concepts and Procedures Check ID and name SSM document name and expected outcome Supported preconfigured parameters and constraints Hs4Ma3G220 - Connections AWSManagedServices-EnableOp enSearchEndpointEncryptionT No preconfigured parameters are allowed. to OpenSearch LS1.2 domains should be encrypted using TLS 1.2 TLS policy is set to `Policy-M domains are required to use TLS 1.2. in-TLS-1-2-2019-07` and only Encrypting data in transit can affect encrypted connections over HTTPS performance. Test your applications Connections to OpenSearch Corresponding (TLS) are allowed. AWS Security Hub check: Opensearch.8 with this feature to understand the performance profile and the impact of TLS. Hs4Ma3G194 - Amazon RDS AWSManagedServices-DisableP ublicAccessOnRDSSnapshotV2 No preconfigured parameters are allowed. Public access for Amazon RDS No constraints snapshot is disabled. snapshot should be private Corresponding AWS Security Hub check: RDS.1 Supported Trusted Advisor checks Version May 08, 2025 629 AMS Advanced User Guide AMS Advanced Concepts and Procedures Check ID and name SSM document name and expected outcome Supported preconfigured parameters and constraints Hs4Ma3G19 2 - RDS DB AWSManagedServices-TrustedR emediatorDisablePublicAcces No preconfigured parameters are allowed. No constraints Instances should sOnRDSInstance Disable public access on RDS DB instance. prohibit public access, as determined by the PubliclyA ccessible AWS Configuration Corresponding AWS Security Hub check: RDS.2 Supported Trusted Advisor checks Version May 08, 2025 630 AMS Advanced User Guide AMS Advanced Concepts and Procedures Check ID and name SSM document name and expected outcome Supported preconfigured parameters and constraints Hs4Ma3G18 9 - Enhanced AWSManagedServices-TrustedR emediatorEnableRDSEnhancedM • MonitoringInterval: The interval, in seconds, between points when monitoring are onitoring Enable |
ams-ug-233 | ams-ug.pdf | 233 | expected outcome Supported preconfigured parameters and constraints Hs4Ma3G19 2 - RDS DB AWSManagedServices-TrustedR emediatorDisablePublicAcces No preconfigured parameters are allowed. No constraints Instances should sOnRDSInstance Disable public access on RDS DB instance. prohibit public access, as determined by the PubliclyA ccessible AWS Configuration Corresponding AWS Security Hub check: RDS.2 Supported Trusted Advisor checks Version May 08, 2025 630 AMS Advanced User Guide AMS Advanced Concepts and Procedures Check ID and name SSM document name and expected outcome Supported preconfigured parameters and constraints Hs4Ma3G18 9 - Enhanced AWSManagedServices-TrustedR emediatorEnableRDSEnhancedM • MonitoringInterval: The interval, in seconds, between points when monitoring are onitoring Enable enhanced monitoring for Amazon RDS DB instances configured for Amazon RDS DB instances Corresponding AWS Security Hub check: RDS.6 Enhanced Monitoring metrics are collected for the DB instance. Valid intervals are 0, 1, 5, 10, 15, 30 and 60. To disable collectin g Enhanced Monitoring metrics, specify 0. • MonitoringRoleName: The name of the IAM role that permits Amazon RDS to send enhanced monitoring metrics to Amazon CloudWatch Logs. If a role isn't specified, then the default role rds-monitoring-role is used or created, if it doesn't exist. If enhanced monitoring is enabled before the automation execution, then the settings might be overwritt en by this automation with the MonitoringInterval and Monitorin gRoleName values configured in the preconfigured parameters. Supported Trusted Advisor checks Version May 08, 2025 631 AMS Advanced User Guide AMS Advanced Concepts and Procedures Check ID and name SSM document name and expected outcome Supported preconfigured parameters and constraints Hs4Ma3G190 - Amazon RDS AWSManagedServices-TrustedR emediatorEnableRDSDeletionP No preconfigured parameters are allowed. No constraints clusters should rotection Deletion protection is enabled for Amazon RDS clusters. have deletion protection enabled Corresponding AWS Security Hub check: RDS.7 Hs4Ma3G198 - Amazon RDS DB AWSManagedServices-TrustedR emediatorEnableRDSDeletionP No preconfigured parameters are allowed. instances should rotection No constraints Deletion protection is enabled for Amazon RDS instances. AWSManagedServices-TrustedR emediatorEnableRDSLogExports No preconfigured parameters are allowed. RDS log exports is enabled for the RDS DB instance or RDS DB cluster. Service-linked role AWSServic eRoleForRDS is required. have deletion protection enabled Corresponding AWS Security Hub check: RDS.8 Hs4Ma3G19 9 - RDS DB instances should publish logs to CloudWatch Logs Corresponding AWS Security Hub check: RDS.9 Supported Trusted Advisor checks Version May 08, 2025 632 AMS Advanced User Guide AMS Advanced Concepts and Procedures Check ID and name SSM document name and expected outcome Supported preconfigured parameters and constraints AWSManagedServices-UpdateRD SIAMDatabaseAuthentication ApplyImmediately: Indicates if the modifications in this request AWS Identity and Access Management authentication is enabled for the RDS instance. and any pending modifications are asynchronously applied as soon as possible, To apply the change immediately, choose true. To schedule the change for the next maintenance window, choose false. No constraints AWSManagedServices-UpdateRD SIAMDatabaseAuthentication ApplyImmediately: Indicates if the modifications in this request IAM authentication is enabled for the RDS cluster. and any pending modifications are asynchronously applied as soon as possible, To apply the change immediately, choose true. To schedule the change for the next maintenance window, choose false. No constraints AWSManagedServices-UpdateRD SInstanceMinorVersionUpgrade No preconfigured parameters are allowed. Automatic minor version upgrade configuration for Amazon RDS is enabled. The Amazon RDS instance must be in the available state for this remediation to happen. Hs4Ma3G160 - IAM authentic ation should be configured for RDS instances Corresponding AWS Security Hub check: RDS.10 Hs4Ma3G161 - IAM authentic ation should be configured for RDS clusters Corresponding AWS Security Hub check: RDS.12 Hs4Ma3G162 - RDS automatic minor version upgrades should be enabled Corresponding AWS Security Hub check: RDS.13 Supported Trusted Advisor checks Version May 08, 2025 633 AMS Advanced User Guide AMS Advanced Concepts and Procedures Check ID and name SSM document name and expected outcome Supported preconfigured parameters and constraints AWSManagedServices-UpdateRD SCopyTagsToSnapshots No preconfigured parameters are allowed. CopyTagtosnapshot setting for Amazon RDS clusters is enabled. Amazon RDS instances must be in available state for this remediation to happen. Hs4Ma3G16 3 - RDS DB clusters should be configured to copy tags to snapshots Corresponding AWS Security Hub check: RDS.16 Hs4Ma3G16 4 - RDS DB AWSManagedServices-UpdateRD SCopyTagsToSnapshots No preconfigured parameters are allowed. instances should be configured to copy tags to snapshots Corresponding AWS Security Hub check: RDS.17 rSs93HQwa1 Amazon RDS Public Snapshots CopyTagsToSnapshot for Amazon RDS is enabled. setting Amazon RDS instances must be in available state for this remediation to happen. AWSManagedServices-DisableP ublicAccessOnRDSSnapshotV2 No preconfigured parameters are allowed. Public access for Amazon RDS snapshot is disabled. No constraints Supported Trusted Advisor checks Version May 08, 2025 634 AMS Advanced User Guide AMS Advanced Concepts and Procedures Check ID and name SSM document name and expected outcome Supported preconfigured parameters and constraints Hs4Ma3G10 3 - Amazon AWSManagedServices-DisableP ublicAccessOnRedshiftCluster No preconfigured parameters are allowed. Redshift clusters should prohibit public access Corresponding AWS Security Hub check: Redshift.1 Public access on Amazon Redshift Disabling public access blocks all cluster is |
ams-ug-234 | ams-ug.pdf | 234 | enabled. setting Amazon RDS instances must be in available state for this remediation to happen. AWSManagedServices-DisableP ublicAccessOnRDSSnapshotV2 No preconfigured parameters are allowed. Public access for Amazon RDS snapshot is disabled. No constraints Supported Trusted Advisor checks Version May 08, 2025 634 AMS Advanced User Guide AMS Advanced Concepts and Procedures Check ID and name SSM document name and expected outcome Supported preconfigured parameters and constraints Hs4Ma3G10 3 - Amazon AWSManagedServices-DisableP ublicAccessOnRedshiftCluster No preconfigured parameters are allowed. Redshift clusters should prohibit public access Corresponding AWS Security Hub check: Redshift.1 Public access on Amazon Redshift Disabling public access blocks all cluster is disabled. clients coming from the internet. And the Amazon Redshift cluster is in the modifying state for a few minutes while the remediation disables public access on the cluster. Hs4Ma3G10 6 - Amazon AWSManagedServices-TrustedR emediatorEnableRedshiftClus No preconfigured parameters are allowed. Redshift clusters terAuditLogging should have audit logging enabled Corresponding AWS Security Hub check: Redshift.4 To enable auto remediation, the Audit logging is enabled to your following preconfigured parameters Amazon Redshift cluster during the must be provided. maintenance window. BucketName: The bucket must be in the same AWS Region. The cluster must have read bucket and put object permissions. If Redshift cluster logging is enabled before the automation execution , then the logging settings might be overwritten by this automatio n with the BucketName and S3KeyPrefix values configured in the preconfigured parameters. Supported Trusted Advisor checks Version May 08, 2025 635 AMS Advanced User Guide AMS Advanced Concepts and Procedures Check ID and name SSM document name and expected outcome Supported preconfigured parameters and constraints No preconfigured parameters are allowed. No constraints Hs4Ma3G10 5 - Amazon Redshiftshould AWSManagedServices-EnableRe dshiftClusterVersionAutoUpgrade - Major version upgrades are applied have automatic automatically to the cluster during upgrades to the maintenance window. There is major versions no immediate downtime for the enabled Amazon Redshift cluster, but your Corresponding AWS Security Hub check: Redshift.6 Amazon Redshift cluster might have downtime during its maintenance window if it upgrades to a major version. Hs4Ma3G10 4 - Amazon AWSManagedServices-TrustedR emediatorEnableRedshiftClus No preconfigured parameters are allowed. Redshift clusters terEnhancedVPCRouting No constraints should use enhanced VPC routing Corresponding AWS Security Hub check: Redshift.7 Hs4Ma3G17 3 - S3 Block Public Access setting should be enabled at the bucket-level Corresponding AWS Security Hub check: S3.8 Enhanced VPC routing is enabled for Amazon Redshift clusters. AWSManagedServices-TrustedR emediatorBlockS3BucketPubli No preconfigured parameters are allowed. cAccess Bucket-level public access blocks are applied for the Amazon S3 bucket. This remediation might affect S3 object availability. For information on how Amazon S3 evaluates access, see Blocking public access to your Amazon S3 storage. Supported Trusted Advisor checks Version May 08, 2025 636 AMS Advanced User Guide AMS Advanced Concepts and Procedures Check ID and name SSM document name and expected outcome Supported preconfigured parameters and constraints Hs4Ma3G23 0 - S3 bucket server access logging should be enabled Corresponding AWS Security Hub check: S3.9 AWSManagedServices-EnableBu cketAccessLogging • TargetBucket: The name of S3 bucket to store server access logs. Amazon S3 server access logging is enabled. • TargetObjectKeyFormat: Amazon S3 key format for log objects, to use the simple format for S3 keys for log objects, chooseSimplePre fix . To use Partitioned S3 key for log objects and use EventTime for the partitioned prefix, choose PartitionedPrefixE ventTime . To use Partitioned S3 key for log objects and use DeliveryTime for the partition ed prefix, choose Partition . edPrefixDeliveryTime Valid values are SimplePre fix , PartitionedPrefixE ventTime and Partition edPrefixDeliveryTime (case-sensitive). To enable auto remediation, the following preconfigured parameter must be provided: TargetBucket. The destination bucket must be in the same AWS Region and AWS account as the source bucket, with correct permissions for log delivery. For more information, see Enabling Amazon S3 server access logging. Supported Trusted Advisor checks Version May 08, 2025 637 AMS Advanced User Guide AMS Advanced Concepts and Procedures Check ID and name SSM document name and expected outcome Supported preconfigured parameters and constraints AWSManagedServices-TrustedR emediatorBlockS3BucketPubli No preconfigured parameters are allowed. Pfx0RwqBli Amazon S3 Bucket Permissio cAccess ns Block public access This check consists of multiple alert criteria. This automation remediates public access issues. Remediation for other configuration issues flagged by Trusted Advisor isn't supported . This remediation does support remediating AWS service created S3 buckets (for example, cf-templa tes-000000000000). Hs4Ma3G272 - Users should not AWSManagedServices-TrustedR emediatorDisableSageMakerNo No preconfigured parameters are allowed. have root access tebookInstanceRootAccess Root access for users is disabled for the SageMaker notebook instance is SageMaker notebook instance. in the InService state. This remediation causes outage if to SageMaker notebook instances Corresponding AWS Security Hub check: SageMaker.3 Supported Trusted Advisor checks Version May 08, 2025 638 AMS Advanced User Guide AMS Advanced Concepts and Procedures Check ID and name SSM document name and expected outcome Supported preconfigured parameters and constraints AWSManagedServices-EnableSN SEncryptionAtRest KmsKeyId: The ID |
ams-ug-235 | ams-ug.pdf | 235 | does support remediating AWS service created S3 buckets (for example, cf-templa tes-000000000000). Hs4Ma3G272 - Users should not AWSManagedServices-TrustedR emediatorDisableSageMakerNo No preconfigured parameters are allowed. have root access tebookInstanceRootAccess Root access for users is disabled for the SageMaker notebook instance is SageMaker notebook instance. in the InService state. This remediation causes outage if to SageMaker notebook instances Corresponding AWS Security Hub check: SageMaker.3 Supported Trusted Advisor checks Version May 08, 2025 638 AMS Advanced User Guide AMS Advanced Concepts and Procedures Check ID and name SSM document name and expected outcome Supported preconfigured parameters and constraints AWSManagedServices-EnableSN SEncryptionAtRest KmsKeyId: The ID of an AWS managed customer master key SNS topic is configured with server- side encryption. Hs4Ma3G17 9 - SNS topics should be encrypted at- rest using AWS KMS Corresponding AWS Security Hub check: SNS.1 (CMK) for Amazon SNS or a custom CMK to be used for server-side encryption (SSE). Default is set to alias/aws/sns . If a custom AWS KMS key is used, it must be configured with the correct permissions. For more information, see Enabling server-side encryption (SSE) for an Amazon SNS topic No preconfigured parameters are allowed. No constraints Hs4Ma3G158 - SSM documents should not be public AWSManagedServices-TrustedR emediatorDisableSSMDocPubli cSharing - Disables the public sharing of SSM document. Corresponding AWS Security Hub check: SSM.4 Supported Trusted Advisor checks Version May 08, 2025 639 AMS Advanced User Guide AMS Advanced Concepts and Procedures Check ID and name SSM document name and expected outcome Supported preconfigured parameters and constraints AWSManagedServices-EnableSQ SEncryptionAtRest Messages in Amazon SQS are encrypted. Hs4Ma3G136 - Amazon SQS queues should be encrypted at rest Corresponding AWS Security Hub check: SQS.1 • SqsManagedSseEnabled: Set to true to enable server-side queue encryption using Amazon SQS owned encryption keys, set to false to enable server-side queue encryption using an AWS KMS key. • KMSKeyId: The ID or alias of an AWS managed customer master key (CMK) for Amazon SQS or a custom CMK to be used for server- side encryption for the queue. If not provided, alias/aws/sqs is used. • KmsDataKeyReusePeriodSecond s: The length of time, in seconds, for which Amazon SQS can reuse a data key to encrypt or decrypt messages before calling AWS KMS again. An integer representing seconds, between 60 seconds (1 minute) and 86,400 seconds (24 hours). This setting is ignored if SqsManagedSseEnabled is set to true. Anonymous SendMessage and ReceiveMessage requests to the encrypted queue are rejected. All requests to queues with SSE enabled must use HTTPS and Signature Version 4. Supported Trusted Advisor checks Version May 08, 2025 640 AMS Advanced User Guide AMS Advanced Concepts and Procedures Trusted Advisor fault tolerance checks supported by Trusted Remediator Check ID and name SSM document name and expected outcome Supported preconfigured parameters and constraints c18d2gz138 Amazon AWSManagedServices-TrustedR emediatorEnableDDBPITR No preconfigured parameters are allowed. DynamoDB Enables point-in-time recovery for No constraints Point-in-time DynamoDB tables. Recovery R365s2Qddf Amazon S3 AWSManagedServices-TrustedR emediatorEnableBucketVersioning No preconfigured parameters are allowed. Bucket Versionin Amazon S3 bucket versioning is This remediation doesn't support g enabled. remediating AWS service created S3 buckets (for example cf-templa tes-000000000000). BueAdJ7NrP Amazon S3 AWSManagedServices-EnableBu cketAccessLogging • TargetBucket: The name of the S3 bucket to store server access logs. Bucket Logging Amazon S3 bucket logging is enabled. • TargetObjectKeyFormat: Amazon S3 key format for log objects, to use the simple format for S3 keys for log objects, chooseSimplePre fix . To use Partitioned S3 key for log objects and use EventTime for the partitioned prefix, choose PartitionedPrefixE ventTime . To use Partitioned S3 key for log objects and use DeliveryTime for the partition ed prefix, choose Partition edPrefixDeliveryTi me . The default is Partition edPrefixEventTime . Supported Trusted Advisor checks Version May 08, 2025 641 AMS Advanced User Guide AMS Advanced Concepts and Procedures Check ID and name SSM document name and expected outcome Supported preconfigured parameters and constraints Valid values are SimplePre fix , PartitionedPrefixE ventTime and Partition edPrefixDeliveryTime (case-sensitive). To enable auto remediation, the following preconfigured parameters must be provided: • TargetBucket The destination bucket must be in the same AWS Region and AWS account as the source bucket, with correct permissions for log delivery. For more information, see Enabling Amazon S3 server access logging. f2iK5R6Dep Amazon RDS AWSManagedServices-TrustedR emediatorEnableRDSMultiAZ No preconfigured parameters are allowed. Multi-AZ Multi-Availability Zone deployment There is a possible performance is enabled. degradation during this change. H7IgTzjTYb Amazon EBS Snapshots AWSManagedServices-TrustedR emediatorCreateEBSSnapshot No preconfigured parameters are allowed. Amazon EBSsnapshots are created. No constraints Supported Trusted Advisor checks Version May 08, 2025 642 AMS Advanced User Guide AMS Advanced Concepts and Procedures Check ID and name SSM document name and expected outcome Supported preconfigured parameters and constraints opQPADkZvH RDS Backups AWSManagedServices-EnableRD SBackupRetention • BackupRetentionPeriod: The number of days (1-35) to retain Amazon RDS backup retention is enabled for the DB. automated backups. • ApplyImmediately: Indicates |
ams-ug-236 | ams-ug.pdf | 236 | AWSManagedServices-TrustedR emediatorEnableRDSMultiAZ No preconfigured parameters are allowed. Multi-AZ Multi-Availability Zone deployment There is a possible performance is enabled. degradation during this change. H7IgTzjTYb Amazon EBS Snapshots AWSManagedServices-TrustedR emediatorCreateEBSSnapshot No preconfigured parameters are allowed. Amazon EBSsnapshots are created. No constraints Supported Trusted Advisor checks Version May 08, 2025 642 AMS Advanced User Guide AMS Advanced Concepts and Procedures Check ID and name SSM document name and expected outcome Supported preconfigured parameters and constraints opQPADkZvH RDS Backups AWSManagedServices-EnableRD SBackupRetention • BackupRetentionPeriod: The number of days (1-35) to retain Amazon RDS backup retention is enabled for the DB. automated backups. • ApplyImmediately: Indicates if the RDS backup retention change and any pending modifications are asynchronously applied as soon as possible. Choose true to apply the change immediately, or false to schedule the change for the next maintenance window. If the ApplyImmediately parameter is set to true, the pending changes on the db are applied along with RDSBackup retention setting. Supported Trusted Advisor checks Version May 08, 2025 643 AMS Advanced User Guide AMS Advanced Concepts and Procedures Check ID and name SSM document name and expected outcome Supported preconfigured parameters and constraints c1qf5bt013 Amazon RDS DB instances have storage autoscali ng turned off AWSManagedServices-TrustedR emediatorEnableRDSInstanceS torageAutoScaling - Storage autoscaling is enabled for Amazon • MaxAllocatedStorageIncrease Percentage: The increase percentage of the current AllocatedStorage, to set the RDS DB instance. MaxAllocatedStorage. Default is set to 26. You must set the maximumst orage threshold to at least 10% more than the current allocated storage. It's a best practice to set the maximumstorage threshold to at least 26% more. For details, check Managing capacity automatically with Amazon Relational Database Service storage autoscaling. No constraints 7qGXsKIUw Classic Load Balancer Connection Draining AWSManagedServices-TrustedR emediatorEnableCLBConnectio ConnectionDrainingTimeout: The maximum time, in seconds, to nDraining Connection draining is enabled for Classic Load Balancer. keep the existing connections open before deregistering the instances. Default is set to 300 seconds. No constraints Supported Trusted Advisor checks Version May 08, 2025 644 AMS Advanced User Guide AMS Advanced Concepts and Procedures Check ID and name SSM document name and expected outcome Supported preconfigured parameters and constraints c18d2gz106 Amazon EBS Not Included in AWS AWSManagedServices-TrustedR emediatorAddVolumeToBackupP Remediation tags the Amazon EBS volume with the following tag pair. lan The tag pair must match the tag- based resource selection criteria for Backup Plan Amazon EBS is included in AWS Backup Plan. AWS Backup. • TagKey • TagValue No constraints AWSManagedServices-TrustedR emediatorAddDynamoDBToBacku Remediation tags the Amazon DynamoDB with the following tag c18d2gz107 Amazon DynamoDB Table Not pPlan Amazon DynamoDB Table is Included in AWS included in AWS Backup Plan. Backup Plan pair. The tag pair must match the tag-based resource selection criteria for AWS Backup. • TagKey • TagValue No constraints c18d2gz117 Amazon EFS Not Included in AWS Backup Plan AWSManagedServices-TrustedR emediatorAddEFSToBackupPlan Remediation tags the Amazon EFS with the following tag pair. The Amazon EFS is included in AWS Backup Plan. tag pair must match the tag-based resource selection criteria for AWS Backup. • TagKey • TagValue No constraints Supported Trusted Advisor checks Version May 08, 2025 645 AMS Advanced User Guide AMS Advanced Concepts and Procedures Check ID and name SSM document name and expected outcome Supported preconfigured parameters and constraints c18d2gz105 Network Load Balancers Cross AWSManagedServices-TrustedR emediatorEnableNLBCrossZone No preconfigured parameters are allowed. LoadBalancing No constraints Load Balancing Cross-zone load balancing is enabled on Network Load Balancer. c1qf5bt026 Amazon RDS synchrono us_commit parameter is turned off c1qf5bt030 Amazon RDS innodb_fl ush_log_a t_trx_com mit parameter is not 1 c1qf5bt031 Amazon RDS sync_binlog parameter is turned off AWSManagedServices-TrustedR emediatorRemediateRDSParame No preconfigured parameters are allowed. terGroupParameter Parameter synchronous_commit is turned on for Amazon RDS. No constraints AWSManagedServices-TrustedR emediatorRemediateRDSParame No preconfigured parameters are allowed. terGroupParameter Parameter innodb_flush_log_a t_trx_commit Amazon RDS. is set to 1 for No constraints AWSManagedServices-TrustedR emediatorRemediateRDSParame No preconfigured parameters are allowed. terGroupParameter Parameter sync_binlog is turned on for Amazon RDS. No constraints Supported Trusted Advisor checks Version May 08, 2025 646 AMS Advanced User Guide AMS Advanced Concepts and Procedures Check ID and name SSM document name and expected outcome Supported preconfigured parameters and constraints c1qf5bt036 Amazon RDS innodb_de fault_row _format parameter setting is unsafe c18d2gz144 Amazon EC2 Detailed AWSManagedServices-TrustedR emediatorRemediateRDSParame No preconfigured parameters are allowed. terGroupParameter Parameter innodb_default_row _format is set to DYNAMIC for Amazon RDS. No constraints AWSManagedServices-TrustedR emediatorEnableEC2InstanceD etailedMonitoring No preconfigured parameters are allowed. No constraints Monitoring Not Detailed Monitoring is enabled for Enabled Amazon EC2. Trusted Advisor performance checks supported by Trusted Remediator Check ID and name SSM document name and expected outcome Supported preconfigured parameters and constraints COr6dfpM06 AWS Lambda under-pro visioned functions for memory size AWSManagedServices-ResizeLa mbdaMemory RecommendedMemorySize: The recommended memory allocatio Lambda functionss memory size are resized to the recommended memory size provided by Trusted Advisor. n for the Lambda function. Value range is between 128 and 10240. If Lambda |
ams-ug-237 | ams-ug.pdf | 237 | Parameter innodb_default_row _format is set to DYNAMIC for Amazon RDS. No constraints AWSManagedServices-TrustedR emediatorEnableEC2InstanceD etailedMonitoring No preconfigured parameters are allowed. No constraints Monitoring Not Detailed Monitoring is enabled for Enabled Amazon EC2. Trusted Advisor performance checks supported by Trusted Remediator Check ID and name SSM document name and expected outcome Supported preconfigured parameters and constraints COr6dfpM06 AWS Lambda under-pro visioned functions for memory size AWSManagedServices-ResizeLa mbdaMemory RecommendedMemorySize: The recommended memory allocatio Lambda functionss memory size are resized to the recommended memory size provided by Trusted Advisor. n for the Lambda function. Value range is between 128 and 10240. If Lambda function size is modified before the automation execution , then this automation might overwrite the settings with the value recommended by Trusted Advisor. ZRxQlPsb6c AWSManagedServices-ResizeIn stanceByOneLevel • MinimumDaysSinceLastChange: The minimum number of days Supported Trusted Advisor checks Version May 08, 2025 647 AMS Advanced User Guide AMS Advanced Concepts and Procedures Check ID and name SSM document name and expected outcome Supported preconfigured parameters and constraints High Utilizati Amazon EC2 instances are resized since the last instance type on Amazon EC2 Instances by one instance type up in the same instance family type. The instances change. If the instance type was modified within the specified are stopped and started during the time, the instance type isn't resize operation and returned to the initial state after the execution is complete. This automation doesn't support resizing instances that are in an Auto Scaling Group. changed. Use 0 to skip this validation. The default is 7. • CreateAMIBeforeResize: To create the instance AMI as a backup before resizing, choose true. To not create a backup, choose false. The default is false. Valid values are true and false (case- sensitive). • ResizeIfStopped: To proceed with the instance size change, even if the instance is in a stopped state, choose true. To not automatically resize the instance if in a stopped state, choose false. Valid values are true and false (case-sen sitive). No constraints c1qf5bt021 Amazon RDS innodb_ch ange_buff ering parameter using less than optimum value AWSManagedServices-TrustedR emediatorRemediateRDSParame No preconfigured parameters are allowed. terGroupParameter The value of innodb_ch ange_buffering parameter is set to NONE for Amazon RDS. No constraints Supported Trusted Advisor checks Version May 08, 2025 648 AMS Advanced User Guide AMS Advanced Concepts and Procedures Check ID and name SSM document name and expected outcome Supported preconfigured parameters and constraints c1qf5bt025 Amazon RDS autovacuum parameter is turned off c1qf5bt028 Amazon RDS enable_in dexonlysc an parameter is turned off c1qf5bt029 Amazon RDS enable_in dexscan parameter is turned off c1qf5bt032 Amazon RDS innodb_st ats_persi stent parameter is turned off AWSManagedServices-TrustedR emediatorRemediateRDSParame No preconfigured parameters are allowed. terGroupParameter Parameter autovacuum is turned on for Amazon RDS. No constraints AWSManagedServices-TrustedR emediatorRemediateRDSParame No preconfigured parameters are allowed. terGroupParameter Parameter enable_indexonlysc an is turned on for Amazon RDS. No constraints AWSManagedServices-TrustedR emediatorRemediateRDSParame No preconfigured parameters are allowed. terGroupParameter Parameter enable_indexscan is turned on for Amazon RDS. No constraints AWSManagedServices-TrustedR emediatorRemediateRDSParame No preconfigured parameters are allowed. terGroupParameter Parameter innodb_stats_persi stent is turned on for Amazon RDS. No constraints Supported Trusted Advisor checks Version May 08, 2025 649 AMS Advanced User Guide AMS Advanced Concepts and Procedures Check ID and name SSM document name and expected outcome Supported preconfigured parameters and constraints c1qf5bt037 Amazon RDS general_l ogging parameter is turned on AWSManagedServices-TrustedR emediatorRemediateRDSParame No preconfigured parameters are allowed. terGroupParameter Parameter general_logging is turned off for Amazon RDS. No constraints Trusted Advisor service limits checks supported by Trusted Remediator Check ID and name SSM document name and expected outcome Supported preconfigured parameters and constraints lN7RR0l7J9 EC2-VPC Elastic AWSManagedServices-UpdateVp cElasticIPQuota Increment: The number to increase the current quota. The default is 3. IP Address A new limit for EC2-VPC elastic IP If this automation is run multiple addresses are requested. By default, times before the Trusted Advisor the limit is be increased by 3. kM7QQ0l7J9 VPC Internet Gateways AWSManagedServices-Increase ServiceQuota - A new limit for VPC internet gateways are requested. By default, the limit is increased by three. check is updated with the OK status, then there might be a higher limit increase. Increment: The number to increase the current quota. The default is 3. If this automation is run multiple times before the Trusted Advisor check is updated with the OK status, then there might be a higher limit increase. jL7PP0l7J9 VPC AWSManagedServices-Increase ServiceQuota Increment: The number to increase the current quota. The default is 3. Supported Trusted Advisor checks Version May 08, 2025 650 AMS Advanced User Guide AMS Advanced Concepts and Procedures Check ID and name SSM document name and expected outcome Supported preconfigured parameters and constraints A new limit for VPC is requested. By If this automation is run multiple default, the limit is increased by 3. times before the Trusted Advisor check is updated with the OK status, |
ams-ug-238 | ams-ug.pdf | 238 | the Trusted Advisor check is updated with the OK status, then there might be a higher limit increase. jL7PP0l7J9 VPC AWSManagedServices-Increase ServiceQuota Increment: The number to increase the current quota. The default is 3. Supported Trusted Advisor checks Version May 08, 2025 650 AMS Advanced User Guide AMS Advanced Concepts and Procedures Check ID and name SSM document name and expected outcome Supported preconfigured parameters and constraints A new limit for VPC is requested. By If this automation is run multiple default, the limit is increased by 3. times before the Trusted Advisor check is updated with the OK status, then there might be a higher limit increase. fW7HH0l7J9 Auto Scaling Groups 3Njm0DJQO9 RDS Option Groups AWSManagedServices-Increase ServiceQuota Increment: The number to increase the current quota. The default is 3. A new limit for Auto Scaling Groups If this automation is run multiple is requested. By default, the limit is times before the Trusted Advisor increased by 3. check is updated with the OK status, then there might be a higher limit increase. AWSManagedServices-Increase ServiceQuota Increment: The number to increase the current quota. The default is 3. A new limit for Amazon RDS option If this automation is run multiple groups is requested. By default, the times before the Trusted Advisor limit is increased by 3. check is updated with the OK status, then there might be a higher limit increase. EM8b3yLRTr ELB Application Load Balancers AWSManagedServices-Increase ServiceQuota Increment: The number to increase the current quota. The default is 3. A new limit for ELB Application Load Balancers is requested. By default, the limit is increased by 3. If this automation is run multiple times before the Trusted Advisor check is updated with the OK status, then there might be a higher limit increase. Supported Trusted Advisor checks Version May 08, 2025 651 AMS Advanced User Guide AMS Advanced Concepts and Procedures Check ID and name SSM document name and expected outcome Supported preconfigured parameters and constraints 8wIqYSt25K ELB Network AWSManagedServices-Increase ServiceQuota Increment: The number to increase the current quota. The default is 3. Load Balancers A new limit for ELB Network Load If this automation is run multiple Balancers is requested. By default, times before the Trusted Advisor the limit is increased by 3. check is updated with the OK status, then there might be a higher limit increase. Trusted Advisor operational excellence checks supported by Trusted Remediator Check ID and name SSM document name and expected outcome Supported preconfigured parameters and constraints c18d2gz125 Amazon API Gateway AWSManagedServices-TrustedR emediatorEnableAPIGateWayEx No preconfigured parameters are allowed. ecutionLogging You must grant API Gateway Not Logging Execution logging is enabled on the permission to read and write logs Execution Logs API stage. AWSManagedServices-TrustedR emediatorEnableELBDeletionP rotection - Deletion protection is turned on for the Elastic Load Balancer. c18d2gz168 Elastic Load Balancing Deletion Protection Not Enabled for Load Balancers to CloudWatch for your account in order to enable execution log, refer to Set up CloudWatch logging for REST APIs in API Gateway for detail. No preconfigured parameters are allowed. No constraints Supported Trusted Advisor checks Version May 08, 2025 652 AMS Advanced User Guide AMS Advanced Concepts and Procedures Check ID and name SSM document name and expected outcome Supported preconfigured parameters and constraints c1qf5bt012 Amazon RDS Performan AWSManagedServices-TrustedR emediatorEnableRDSPerforman ceInsights • PerformanceInsightsRetentio nPeriod: The number of days to retain Performance Insights ce Insights is Performance Insights is turned on turned off for Amazon RDS. data. Valid Values: 7 or month * 31, where month is a number of months from 1-23. Examples: 93 (3 months * 31), 341 (11 months * 31), 589 (19 months * 31) or 731. • PerformanceInsightsKMSKeyId: The AWS KMS key id for encryptio n of Performance Insights data. If you don’t specify a value for PerformanceInsightsKMSKeyId , then Amazon RDS uses your default AWS KMS key. No constraints Configure Trusted Advisor check remediation in Trusted Remediator Configurations are stored in AWS AppConfig as part of the Trusted Remediator application. Each Trusted Advisor check category has a separate configuration profile. For more information on Trusted Advisor categories, see View check categories. You can request to configure remediations on a per-resource basis or per Trusted Advisor check basis. You can apply exceptions using resource tags. Note The remediation of Trusted Advisor findings is currently configured using AWS AppConfig, and this feature is fully supported today. AMS anticipates that this will change in the future. It's a best practice to avoid building automations that depend on AWS AppConfig, as this method is subject to change. Be aware that you might need to update or modify Configure check remediation Version May 08, 2025 653 AMS Advanced User Guide AMS Advanced Concepts and Procedures automations built around the current AWS AppConfig implementation in the future for compatibility. Default remediation configurations The configurations for individual |
ams-ug-239 | ams-ug.pdf | 239 | exceptions using resource tags. Note The remediation of Trusted Advisor findings is currently configured using AWS AppConfig, and this feature is fully supported today. AMS anticipates that this will change in the future. It's a best practice to avoid building automations that depend on AWS AppConfig, as this method is subject to change. Be aware that you might need to update or modify Configure check remediation Version May 08, 2025 653 AMS Advanced User Guide AMS Advanced Concepts and Procedures automations built around the current AWS AppConfig implementation in the future for compatibility. Default remediation configurations The configurations for individual Trusted Advisor checks are stored as AWS AppConfig flags. The flag name matches the check name. Each check configuration contains the following attributes: • execution-mode: Determines how Trusted Remediator performs default remediation: • Automated: Trusted Remediator automatically remediates resources by creating an OpsItem, running the SSM document, and then resolving the OpsItem after successful execution. • Manual: An OpsItem is created, but the SSM document isn't executed automatically. You review the OpsItem and run remediation using the automated RFC. For more information, see Work with remediations in Trusted Remediator. • Conditional: Remediation is disabled by default. You can enable it for specific resources using tags. For more information, see the following sections Customize remediation with resource tags and Customize remediation with resource override tags. • Inactive: Remediation doesn't occur and no OpsItem are created. You can't override the execution mode for the Trusted Advisor check that's set to inactive. • preconfigured-parameters: Enter values for SSM document parameters that are required for automated remediation. • alternative-automation-document: This attribute helps override the existing automation document with another supported document (if available for the specific check). By default, this attribute isn't selected. For information on supported checks and the automation documents, see Trusted Advisor checks supported by Trusted Remediator Note The alternative-automation-document attribute doesn't support custom automation documents. You can use existing supported Trusted Remediator automation documents. Configure check remediation Version May 08, 2025 654 AMS Advanced User Guide AMS Advanced Concepts and Procedures Tip Before you apply the default configurations for your Trusted Advisor checks, it's a best practice to consider using the Resource tagging and Resource override features described in the following sections. The default configurations apply to all resources within the account, which might not be desirable in all cases. The following is an example console screenshot with the execution-mode set to Manual. Customize remediation with resource tags The automated-for-tagged-only and manual-for-tagged-only attributes in the check configuration allow you to specify resource tags for how you want to remediate individual checks. Configure check remediation Version May 08, 2025 655 AMS Advanced User Guide AMS Advanced Concepts and Procedures It's a best practice to use this method when you need to apply a consistent remediation behavior to a group of resources that share the same tag or tags. The following are descriptions for these tags: • automated-for-tagged-only: Specify resource tags for checks to remediate automatically, regardless of the default execution mode. • manual-for-tagged-only: Specify resource tags for remediations that should be executed manually, regardless of the default execution mode. For example, if you want to enable automated remediation for all non-production resources and enforce manual remediation for production resources, you might set your configuration as follows: "execution-mode": "Conditional", "automated-for-tagged-only": "Environment=Non-Production", "manual-for-tagged-only": "Environment=Production", With the preceding configurations set on your resources, check remediation behavior is as follows: • Resources tagged with `Environment=Non-Production` are remediated automatically. • Resources tagged with `Environment=Production` require manual intervention for remediation. • Resources without the `Environment` tag follow the default execution mode (`Conditional`, in this case. So, no actions is taken on the remaining resources). For additional support with your configurations, contact your Cloud Architect. Customize remediation with resource override tags Resource override tags allow you to customize the remediation behavior for individual resources, regardless of their tags. By adding a specific tag to a resource, you override the default execution mode for that resource and the Trusted Advisor check. The resource override tag takes precedence over the default configuration and the resource tagging settings. So, if you set the default execution mode to Automated, Manual, or Conditional for a resource using the resource override tag, it overrides the default execution mode and any resource tagging configurations. To override the execution mode for a resource, complete the following steps: 1. Identify the resources for which you want to override the remediation configuration. Configure check remediation Version May 08, 2025 656 AMS Advanced User Guide AMS Advanced Concepts and Procedures 2. Determine the Trusted Advisor check ID for the check that you want to override. You can find the check IDs for supported Trusted Advisor checks in Trusted Advisor checks supported by Trusted Remediator. 3. Add a tag to the resources with the following key and value using the |
ams-ug-240 | ams-ug.pdf | 240 | the default execution mode and any resource tagging configurations. To override the execution mode for a resource, complete the following steps: 1. Identify the resources for which you want to override the remediation configuration. Configure check remediation Version May 08, 2025 656 AMS Advanced User Guide AMS Advanced Concepts and Procedures 2. Determine the Trusted Advisor check ID for the check that you want to override. You can find the check IDs for supported Trusted Advisor checks in Trusted Advisor checks supported by Trusted Remediator. 3. Add a tag to the resources with the following key and value using the Tag | Update or Tag | Bulk Update change type: • Tag key: TR-Trusted Advisor check ID-Execution-Mode (case-sensitive) In the preceding tag key example, replace Trusted Advisor check ID with the unique identified of the Trusted Advisor check that you want to override. • Tag value: Use one of the following values for the tag value: • Automated: Trusted Remediator automatically remediates the resource for this Trusted Advisor check. • Manual: An OpsItem is created for the resource, but remediation isn't performed automatically. You review and run the remediation using the automated. For more information, see Work with remediations in Trusted Remediator. • Inactive: Remediation and OpsItem creation isn't performed for this resource and the specified Trusted Advisor check. For example, to automatically remediate an Amazon EBS volume with the Trusted Advisor check ID DAvU99Dc4C add a tag to the EBS volume. The tag key is TR-DAvU99Dc4C-Execution-Mode and the tag value is Automated. The following is an example of the console showing the Tags section: Configure check remediation Version May 08, 2025 657 AMS Advanced User Guide AMS Advanced Concepts and Procedures Execution mode decision workflow There are multiple levels to configure execution mode for your resources and each Trusted Advisor check. The following diagram shows how Trusted Remediator decides which execution mode to use based on your configurations: Execution mode decision workflow Version May 08, 2025 658 AMS Advanced User Guide AMS Advanced Concepts and Procedures Execution mode decision workflow Version May 08, 2025 659 AMS Advanced User Guide AMS Advanced Concepts and Procedures Configure remediation tutorials The following tutorials provide examples of creating common remediations in Trusted Remediator Topics • Remediate all resources manually • Remediate all resources automatically, except for selected resources • Remediate tagged resources automatically • Reset configuration to default Remediate all resources manually This example configures manual remediation for all Amazon EBS volumes with the Trusted Advisor check ID DAvU99Dc4C (Underutilized Amazon EBS Volumes). Configure manual remediation for Amazon EBS volumes with check ID DAvU99Dc4C 1. Use the Remediation Configuration|Update, change type to request the configuration update. 2. Enter the following parameters: • CheckIds: DAvU99Dc4C • ExecutionMode: Manual Note Multiple checks can be configured in a single request. For checks that require the same configuration, include multiple check IDs in the CheckIds parameter. For checks that require a different configuration, create a new RemediationConfiguration object. 3. Submit the RFC. Remediate all resources automatically, except for selected resources This example configures automatic remediation for all Amazon EBS volumes with the Trusted Advisor check ID DAvU99Dc4C (Underutilized Amazon EBS Volumes), with the exception of specified volumes that won't be remediated (designated Inactive. Configure remediation tutorials Version May 08, 2025 660 AMS Advanced User Guide AMS Advanced Concepts and Procedures Configure automatic remediation for Amazon EBS volumes with check ID DAvU99Dc4C, with the exception of selected inactive resources 1. Override automated remediation for selected Amazon EBS volumes: Use Tag | Update or Tag | Bulk Update change type to apply the following tag for volumes to be excluded from automated remediation: • Key: TR-DAvU99Dc4C-Execution-Mode • Value: Inactive 2. Use the Remediation Configuration|Update change type to request the configuration update. 3. Enter the following parameters: • CheckIds: DAvU99Dc4C • ExecutionMode: Automated 4. Submit the RFC. Remediate tagged resources automatically This example configures automatic remediation for all Amazon EBS volumes with the tag Stage=NonProd with the Trusted Advisor check ID DAvU99Dc4C (Underutilized Amazon EBS Volumes). All other resources without this tag aren't remediated. Configure automatic remediation for Amazon EBS volumes with the tag Stage=NonProd for check ID DAvU99Dc4C 1. Use the Remediation Configuration | Update, change type to request the configuration update. 2. Enter the following parameters: • CheckIds: DAvU99Dc4C • ExecutionMode: Conditional • AutomatedForTaggedOnly: {"Stage":"NonProd"} Configure remediation tutorials Version May 08, 2025 661 AMS Advanced User Guide AMS Advanced Concepts and Procedures Note The value specified for the AutomatedForTaggedOnly parameter overrides the previously configured value. To retain existing tags, include them in the new value. 3. Submit the RFC. Reset configuration to default This example removes existing automated-for-tagged-only configuration for the check Hs4Ma3G104. To remove previously applied tag configuration, set the AutomatedForTaggedOnly parameter value to {}. Reset configuration to default for check Hs4Ma3G104 1. Use the Remediation Configuration |
ams-ug-241 | ams-ug.pdf | 241 | the configuration update. 2. Enter the following parameters: • CheckIds: DAvU99Dc4C • ExecutionMode: Conditional • AutomatedForTaggedOnly: {"Stage":"NonProd"} Configure remediation tutorials Version May 08, 2025 661 AMS Advanced User Guide AMS Advanced Concepts and Procedures Note The value specified for the AutomatedForTaggedOnly parameter overrides the previously configured value. To retain existing tags, include them in the new value. 3. Submit the RFC. Reset configuration to default This example removes existing automated-for-tagged-only configuration for the check Hs4Ma3G104. To remove previously applied tag configuration, set the AutomatedForTaggedOnly parameter value to {}. Reset configuration to default for check Hs4Ma3G104 1. Use the Remediation Configuration | Update change type to request the configuration update. 2. Enter the following parameters: • CheckIds: Hs4Ma3G104 • ExecutionMode: Enter the currently used value • AutomatedForTaggedOnly: {} 3. Submit the RFC. Work with remediations in Trusted Remediator Topics • Track remediations in Trusted Remediator • Run manual remediations in Trusted Remediator • Troubleshoot remediations in Trusted Remediator Track remediations in Trusted Remediator To track OpsItems remediations, complete the following steps: Work with remediations Version May 08, 2025 662 AMS Advanced User Guide AMS Advanced Concepts and Procedures 1. Open the AWS Systems Manager console at https://console.aws.amazon.com/systems- manager/. 2. Choose Operations Management, OpsCenter. 3. (Optional) Filter the list by Source=Trusted Remediator to include only Trusted Remediator OpsItems in the list. The following is an example of the OpsCenter screen filtered by Source=Trusted Remediator: Note In addition to viewing OpsItems from the OpsCenter, you can view remediation logs in the AMS S3 bucket. For more information, see Remediation logs in Trusted Remediator. Run manual remediations in Trusted Remediator Trusted Remediator creates OpsItems for checks configured for manual remediation. You must review these checks and begin the remediation process manually. To manually remediate the OpsItem, complete the following steps: 1. Open the AWS Systems Manager console at https://console.aws.amazon.com/systems- manager/. 2. Choose Operations Management, OpsCenter. 3. (Optional) Filter the list by Source=Trusted Remediator to include only Trusted Remediator OpsItems in the list. 4. Choose the OpsItem that you want to review. Work with remediations Version May 08, 2025 663 AMS Advanced User Guide AMS Advanced Concepts and Procedures 5. Review the operational data of the OpsItem. The operational data includes the following items: • trustedAdvisorCheckCategory: The category of the Trusted Advisor check ID. For example, Fault tolerance • trustedAdvisorCheckId: The unique Trusted Advisor check ID. • trustedAdvisorCheckMetadata: The resource metadata, including the resource ID. • trustedAdvisorCheckName: The name of the Trusted Advisor check. • trustedAdvisorCheckStatus: The status of the Trusted Advisor check detected for the resource. • trustedAdvisorCheckManualRemediation: The custom data that provides reference details for manual remediation. • ManualExecutionInput: An object that defines parameters that you can modify values for when executing manual remediation. • DocumentName: The name of the runbook (SSM document). • CustomizableParameters: Parameter names that you can modify. • DefaultInput: An object that defines parameter names and values to be used for manual remediation. The values populate based on preconfigured-parameters. 6. To manually remediate the OpsItem, complete the following steps: a. Use Trusted Remediator | Finding | Remediate ct-1c7ch8z5phrjp change type b. Enter values for the following parameters: • DocumentName: Must be AWSManagedServices- RemediateTrustedRemediatorFinding. • Region: The AWS Region, in the form us-east-1. • Parameters: Enter the manual remediation parameters: • OpsItemId: The ID of the Ops Item. • RemediationDocumentName: The name of the SSM automation document to use. The document must be associated with the Ops Item. If multiple documents are associated with the Ops Item, then the DocumentName must be specified. • RemediationParameters: A key/value map of parameters for the automation execution, in the form: {\"ParameterName1\":[\"ParameterValue1\"], \"ParameterName2\":[\"ParameterValue2\"]}. You can only use parameters Version May 08, 2025 664 Work with remediations AMS Advanced User Guide AMS Advanced Concepts and Procedures that are present in the Ops Item trustedAdvisorCheckManualRemediation CustomizableParameters. If not specified, parameters and values are retrieved from the Ops Item. c. Choose Run. If there are no errors, then the RFC successfully created page displays with the submitted RFC details, and the initial Run output. d. Monitor the RFC execution's progress. e. After the execution completes, the OpsItem is resolved. If the RFC failed, then follow the steps in Troubleshoot remediations in Trusted Remediator. For additional troubleshooting support, contact AMS. Troubleshoot remediations in Trusted Remediator For assistance with manual remediations and remediation failures, contact AMS. To view remediation status and results, complete the following steps: 1. Open the AWS Systems Manager console at https://console.aws.amazon.com/systems- manager/. 2. Choose Operations Management, OpsCenter. 3. (Optional) Filter the list by Source=Trusted Remediator to include only Trusted Remediator OpsItems in the list. 4. Choose the OpsItem that you want to review. 5. In the Automation Executions section review the Document Name and Status and results. 6. Review the following common automation failures. If your issues isn't listed here, then contact your CSDM for |
ams-ug-242 | ams-ug.pdf | 242 | contact AMS. Troubleshoot remediations in Trusted Remediator For assistance with manual remediations and remediation failures, contact AMS. To view remediation status and results, complete the following steps: 1. Open the AWS Systems Manager console at https://console.aws.amazon.com/systems- manager/. 2. Choose Operations Management, OpsCenter. 3. (Optional) Filter the list by Source=Trusted Remediator to include only Trusted Remediator OpsItems in the list. 4. Choose the OpsItem that you want to review. 5. In the Automation Executions section review the Document Name and Status and results. 6. Review the following common automation failures. If your issues isn't listed here, then contact your CSDM for assistance. Common remediation errors No executions are listed in Automation Executions No executions associated with the OpsItem might indicate that the execution failed to start due to incorrect parameter values. Troubleshooting steps 1. In the Operational data, review the trustedAdvisorCheckAutoRemediation property value. Work with remediations Version May 08, 2025 665 AMS Advanced User Guide AMS Advanced Concepts and Procedures 2. Verify that the DocumentName and Parameters values are correct. For the correct values, review Configure Trusted Advisor check remediation in Trusted Remediator for details on how to configure SSM parameters. To review supported check parameters, see Trusted Advisor checks supported by Trusted Remediator 3. Verify that values in the SSM document match allowed patterns. To view parameters details in the document content, select the document name in the Runbooks section. 4. After you review and correct the parameters, manually remediate the OpsItem. For the remediation steps, see Run manual remediations in Trusted Remediator. 5. To prevent this error from reoccurring, make sure that you configure the remediation with the correct parameter values in your configuration. For more information, see Configure Trusted Advisor check remediation in Trusted Remediator Failed executions in Automation Executions Remediation documents contain multiple steps that interact with AWS services performing various actions through APIs. To identify a specific cause for the failure, complete the following steps: Troubleshooting steps 1. To view the individual execution steps, choose the Execution ID, link in the Automation Executions section. The following is an example of the Systems Manager console showing the Exection steps for a selected automation: Work with remediations Version May 08, 2025 666 AMS Advanced User Guide AMS Advanced Concepts and Procedures 2. Choose the step with the Failed status. The following are example error messages: • NoSuchBucket - An error occurred (NoSuchBucket) when calling the GetPublicAccessBlock operation: The specified bucket does not exist This error indicates that the incorrect bucket name was specified in the remediation configuration's preconfigured-parameters. To resolve this error, manually run the automation using the correct bucket name. To prevent this issue from reoccurring, update the remediation configuration with the correct bucket name. • DB instance my-db-instance-1 is not in available status for modification. This error indicates that the automation couldn't make the expected changes because the DB instance was in an invalid state. Work with remediations Version May 08, 2025 667 AMS Advanced User Guide AMS Advanced Concepts and Procedures To resolve this error, manually run the automation. Remediation logs in Trusted Remediator Trusted Remediator creates logs in JSON format and uploads them to Amazon Simple Storage Service The log files are uploaded to an S3 bucket created by AMS and named ams-trusted- remediator-{your-account-id}-logs. AMS creates the S3 bucket in the Delegated Administrator account. You can import the log files into QuickSight to generate customized remediation reports. Topics • Remediation item log • Automated remediation execution log Remediation item log Trusted Remediator creates the Remediation item log when a remediation OpsItem is created. This log contains manual remediation OpsItem and automated remediation OpsItem. You can use the Remediation item log to track the overview of all remediations. Remediation item log location s3://ams-trusted-remediator-delegated-administrator-account-id-logs/ remediation_items/remediation creation time in yyyy-mm-dd format/10 digits epoch time or unix timestamp-Trusted Advisor check ID-Resource ID.json Remediation item log sample file URL s3:///ams-trusted-remediator-111122223333-logs/ remediation_items/2023-02-06/1675660464-DAvU99Dc4C- vol-00bd8965660b4c16d.json Remediation item log format { "TrustedAdvisorCheckID": Trusted Advisor check ID, "TrustedAdvisorCheckName": Trusted Advisor check name, Remediation logs Version May 08, 2025 668 AMS Advanced User Guide AMS Advanced Concepts and Procedures "TrustedAdvisorCheckResultTime": 10 digits epoch time or unix timestamp, "ResourceID": Resource ID, "RemediationTime": Remediation creation time, "ExecutionMode": Automated or Manual, "OpsItemID": OpsItem ID, } Remediation item log format sample content { "TrustedAdvisorCheckID": "DAvU99Dc4C", "TrustedAdvisorCheckName": "Underutilized Amazon EBS Volumes", "TrustedAdvisorCheckResultTime": 1675614749, "ResourceID": "vol-00bd8965660b4c16d", "RemediationTime": 1675660464, "OpsItemID": "oi-cca5df7af718" } Automated remediation execution log Trusted Remediator creates the Automated remediation execution log when an automated SSM document run is completed. This log contains SSM run details for automated remediation OpsItem only. You can use this log file to track automated remediations. Automated remediation log location s3://ams-trusted-remediator-delegated-administrator-account-id-logs// remediation_executions/remediation creation time in yyyy-mm-dd format/10 digits epoch time or unix timestamp-Trusted Advisor check ID-Resource ID.json Automated remediation log location example s3://ams-trusted-remediator-111122223333-logs/ remediation_executions/2023-02-06/1675660573-DAvU99Dc4C- vol-00bd8965660b4c16d.json Automated remediation log format { Remediation logs Version May 08, |
ams-ug-243 | ams-ug.pdf | 243 | format sample content { "TrustedAdvisorCheckID": "DAvU99Dc4C", "TrustedAdvisorCheckName": "Underutilized Amazon EBS Volumes", "TrustedAdvisorCheckResultTime": 1675614749, "ResourceID": "vol-00bd8965660b4c16d", "RemediationTime": 1675660464, "OpsItemID": "oi-cca5df7af718" } Automated remediation execution log Trusted Remediator creates the Automated remediation execution log when an automated SSM document run is completed. This log contains SSM run details for automated remediation OpsItem only. You can use this log file to track automated remediations. Automated remediation log location s3://ams-trusted-remediator-delegated-administrator-account-id-logs// remediation_executions/remediation creation time in yyyy-mm-dd format/10 digits epoch time or unix timestamp-Trusted Advisor check ID-Resource ID.json Automated remediation log location example s3://ams-trusted-remediator-111122223333-logs/ remediation_executions/2023-02-06/1675660573-DAvU99Dc4C- vol-00bd8965660b4c16d.json Automated remediation log format { Remediation logs Version May 08, 2025 669 AMS Advanced User Guide AMS Advanced Concepts and Procedures "OpsItemID": OpsItem ID, "SSMExecutionID": SSM Execution ID, "SSMExecutionStatus": Success/Failed, } Automated remediation log format sample content { "OpsItemID": "oi-767c77e05301", "SSMExecutionID": "93d091b2-778a-4cbc-b672-006954d76b86", "SSMExecutionStatus": "Success" } Best practices in Trusted Remediator The following are best practices to help you use Trusted Remediator: • If you're unsure about the remedation results, start with manual execution mode. Sometimes, applying automated execution for remediations from the start might cause unexpected results. • Conduct a weekly review of the remediations and OpsItems to gain insights in the Trusted Remediator results. • Member accounts inherit the configurations from the delegated administrator account. So, it’s important to structure the accounts in a way that helps you manage multiple accounts with the same configurations. You can exempt resources from the default configuration using tags. Trusted Remediator FAQs The following are frequently asked questions about Trusted Remediator: What is Trusted Remediator and how does it benefit me? When a non-compliance is identified by Trusted Advisor, Trusted Remediator responds according to your specified preferences, either by applying remediation, seeking approval through manual remediations, or reporting the remediations during your upcoming Monthly Business Review (MBR). The remediation happen at your preferred remediation time or schedule. Trusted Remediator provides you with the ability to self-service and act on Trusted Advisor checks with the flexibility Best practices Version May 08, 2025 670 AMS Advanced User Guide AMS Advanced Concepts and Procedures to configure and remediate checks individually or in bulk. With a library of tested remediation documents, AMS constantly bar raises your accounts by applying safety checks and following AWS best practices. You are only notified if you specify to do so in your configuration. AMS users can opt-in to Trusted Remediator at no additional charge. How does Trusted Remediator relate to and work with other AWS services? You have access to Trusted Advisor checks as part of your existing Enterprise Support plan. Trusted Remediator integrates with Trusted Advisor leverage existing AMS automation capabilities. Specifically, AMS uses AWS Systems Manager automation documents (runbooks) for automated remediations. AWS AppConfig is used to configure the remediation workflows. You can view all the current and past remediations through the Systems Manager OpsCenter. The remediation logs are stored in an Amazon S3 bucket. You can use the logs to import and build custom reporting dashboards in QuickSight. Who configures the remediations? You own the configurations in your account. Managing your configurations is your responsibility. You can also reach out to AMS for configuration changes, support, and manual remediations, and troubleshooting remediation failures. How do I install SSM automation documents? SSM automation documents are automatically shared to onboarded AMS accounts. Will AMS owned resources be remediated too? AMS owned resources aren't flagged by Trusted Remediator. Trusted Remediator focuses only on your resources. What AWS Regions is Trusted Remediator available in and who can use it? Trusted Remediator is available for AMS Advanced customers. For a current list of support Regions, see AWS services by Region. Will Trusted Remediator cause resource drift? Since SSM automation documents directly update resources through the AWS API, resource drift might occur. You can use tags to segregate resources created through your existing CI/ CD packages. You can configure Trusted Remediator to ignore the tagged resources while still remediating your other resources. FAQs Version May 08, 2025 671 AMS Advanced User Guide AMS Advanced Concepts and Procedures How do I pause or stop Trusted Remediator? Use the Management | Trusted Remediator | State | Enable or disable change type to stop the Trusted Remediator service. Use the same change type to re-enable Trusted Remediator. How can I remediate checks that aren't supported by Trusted Remediator? You can continue to reach out to AMS through Operations On Demand (OOD) for unsupported checks. AMS assists you with remediating these checks. For more information, see Operations On Demand. What resources does Trusted Remediator deploy to your accounts? Trusted Remediator deploys the following resources in the Trusted Remediator delegated administrator account: • An Amazon S3 bucket named ams-trusted-remediator-{your-account-id}-logs. Trusted Remediator creates the Remediation item log in JSON format when a remediation OpsItem is created, and uploads the log files to this bucket. • An AWS AppConfig application to |
ams-ug-244 | ams-ug.pdf | 244 | How can I remediate checks that aren't supported by Trusted Remediator? You can continue to reach out to AMS through Operations On Demand (OOD) for unsupported checks. AMS assists you with remediating these checks. For more information, see Operations On Demand. What resources does Trusted Remediator deploy to your accounts? Trusted Remediator deploys the following resources in the Trusted Remediator delegated administrator account: • An Amazon S3 bucket named ams-trusted-remediator-{your-account-id}-logs. Trusted Remediator creates the Remediation item log in JSON format when a remediation OpsItem is created, and uploads the log files to this bucket. • An AWS AppConfig application to hold the remediation configurations for supported Trusted Advisor checks. Trusted Remediator doesn't deploy resources in the Trusted Remediator member account. FAQs Version May 08, 2025 672 AMS Advanced User Guide AMS Advanced Concepts and Procedures Log management Topics • What is log management? • How AMS logging works • Accessing your logs • Customizing your log configuration AMS log management collects, aggregates, and controls retention of the logs from the managed account. AWS log management aggregates logs from Amazon EC2 instances and AWS resources deployed within your account into CloudWatch Logs. The full list of services from which logs are currently aggregated can be found in AMS aggregated service logs. What is log management? Log management is the process of dealing with log events generated by instances, applications, and AWS services. This feature defines how AMS processes, stores, and rotates the log events generated in your managed AWS account. Infrastructure logs are used during incident resolution and to support system audits. How AMS logging works AMS single-account landing zone (SALZ) log management uses a variety of pre-installed agents and tools that are implemented when instances and applications are onboarded or provisioned. Logging is configured during the account onboarding process and when a stack is launched. AMS multi-account landing zone (MALZ) logs produced by instances and AWS services are available in CloudWatch Logs or Amazon Simple Storage Service (Amazon S3), within each account managed by AMS. AMS multi-account landing zone provides a central Logging Account that acts as a central aggregation location for some logs produced by individual application accounts. The tables in the Accessing your logs subsections describe which logs are available in individual accounts, and which are available in the central Logging Account. What is log management? Version May 08, 2025 673 AMS Advanced User Guide AMS Advanced Concepts and Procedures Accessing your logs To access your logs, ensure that you have one of the required IAM roles and are in your AMS account. Then navigate to the directory shown. Multi-Account Landing Zone (MALZ) Provides five default IAM roles, each of which allow access to all logs within your account (all are prefaced with AWSManagedServices): • AdminRole • CaseRole • ChangeManagementRole • ReadOnlyRole • SecurityOpsRole Access to these roles is configured via federation, with each role being mapped to a group within your Active Directory domain. To learn more about these roles, see IAM user role in AMS . Single-Account Landing Zone (SALZ) The default Customer_ReadOnly_Role for AMS single-account landing zone allows your access to all logs within your account. Access to the logs is controlled using AWS Identity and Access Management (IAM) roles mapped to Active Directory groups. AMS aggregated service logs Each AWS service logs to either CloudWatch Logs or a specific location in an Amazon S3 bucket. Note Unless specifically stated, all log locations are local to the account that generated the logs, and are not aggregated into the central Logging account. To find the default AMS CloudTrail trail names in SALZ and MALZ accounts, go to the AWS Console for CloudTrail and then to the Trails page and search for AMS. Because AMS resources have tags, you can find the trails this way. Example AMS CloudTrail tag: Accessing your logs Version May 08, 2025 674 AMS Advanced User Guide AMS Advanced Concepts and Procedures Environment AMSInfrastructure To access your logs, ensure that you have one of the required IAM roles and are in your AMS account. Then navigate to the directory shown. Multi-Account Landing Zone AMS multi-account landing zone Aggregated Service Logs Service name Log details Log location 1 Amazon Aurora General, slow query, and error CloudWatch LogGroup: /aws/ logs. 2 AWS API call logging only. CloudForm ation (CFN) rds/cluster/{database_name }/ {log_name} AWS CloudFormation API calls are documented via CloudTrail, which sends its logs to the CloudWatc h LogGroup and then syncs the logs into an S3 bucket. Logs are retained for 14 days by default in the CloudWatch LogGroup, and are retained indefinitely in the S3 bucket. CloudWatch LogGroup: /CloudTra il/Landing-Zone-Logs S3 bucket [in the central Logging Account]: aws-landing-zone-logs- ams-a{account_ID }-log-man agement-{region} Path: /AWSLogs/{account_I D }/CloudTrail/ AMS aggregated service logs Version May 08, 2025 675 AMS Advanced User Guide AMS Advanced Concepts and Procedures |
ams-ug-245 | ams-ug.pdf | 245 | error CloudWatch LogGroup: /aws/ logs. 2 AWS API call logging only. CloudForm ation (CFN) rds/cluster/{database_name }/ {log_name} AWS CloudFormation API calls are documented via CloudTrail, which sends its logs to the CloudWatc h LogGroup and then syncs the logs into an S3 bucket. Logs are retained for 14 days by default in the CloudWatch LogGroup, and are retained indefinitely in the S3 bucket. CloudWatch LogGroup: /CloudTra il/Landing-Zone-Logs S3 bucket [in the central Logging Account]: aws-landing-zone-logs- ams-a{account_ID }-log-man agement-{region} Path: /AWSLogs/{account_I D }/CloudTrail/ AMS aggregated service logs Version May 08, 2025 675 AMS Advanced User Guide AMS Advanced Concepts and Procedures Service name Log details Log location 3 Amazon CloudFront User request logging. CloudFron t logging must be explicitly S3 bucket: ams-a{account_I D }-log-management-{region} (CloudFront) enabled. For information, see Enabling logging for supported services. Path: AWS/RedShift/{CloudFron t distribution ID } 4 Amazon API call logging only. CloudWatch (CloudWatch) CloudWatch LogGroup: /CloudTra il/Landing-Zone-Logs S3 bucket [in the central Logging Account]: aws-landing-zone-logs- {account_ID }-{region} Path: /AWSLogs/{account_I D }/CloudTrail/ 5 Amazon Elastic Block Store No logs are produced by the EBS service. Not applicable (Amazon EBS) 6 Amazon Elastic Compute Cloud (Amazon EC2) 7 Amazon Elastic File System (Amazon EFS) System and application logs. For information, see the Amazon Elastic Compute Cloud (Amazon EC2) - system level logs. API call logging only. CloudWatch Logs: /{instance ID} CloudWatch LogGroup: /CloudTra il/Landing-Zone-Logs S3 bucket [in the central Logging Account]: aws-landing-zone-logs- {account_ID }-{region} Path: /AWSLogs/{account_I D }/CloudTrail/ AMS aggregated service logs Version May 08, 2025 676 AMS Advanced User Guide AMS Advanced Concepts and Procedures Service name Log details Log location 8 Elastic Load Access and error log entries. API call logs: Balancing (ELB) Elastic load balancers log all CloudWatch LogGroup: /CloudTra requests sent to them, including il/Landing-Zone-Logs requests that aren't routed to back-end instances. For example, if a client sends a malformed request, or there are no healthy instances to respond, the request is still logged. S3 bucket [in the central Logging Account]: aws-landing-zone-logs- {account_ID }-{region} Path: /AWSLogs/{account_I D }/CloudTrail/ For more information about Elastic Load Balancing log entries, Access logs: see • Classic Load Balancers: Access S3 bucket: mc-a{account_ID }- logs{region} log entries. Path: aws/elbaccess • Application Load Balancers: Access log entries. • Network Load Balancers: Access log entries. 9 Amazon Service error logs. OpenSearc h Service (OpenSearch Service) CloudWatch LogGroup: /CloudTra il/Landing-Zone-Logs You must explicitly enable OpenSearch logging. For S3 bucket [in the central Logging information, see Enabling logging for supported services Account]: aws-landing-zone-logs- {account_ID }-{region} Path: /AWSLogs/{account_I D }/CloudTrail/ AMS aggregated service logs Version May 08, 2025 677 AMS Advanced User Guide AMS Advanced Concepts and Procedures Service name Log details Log location 10 Amazon API call logging only. ElastiCache 11 Amazon GuardDuty 12 Amazon Inspector 13 Amazon Macie CloudWatch LogGroup: //CloudTr ail/Landing-Zone-Logs S3 bucket [in the central Logging Account]: aws-landing-zone-logs- {account_ID }-{region} Path: /AWSLogs/{account_I D }/CloudTrail/ 14 Amazon Redshift Connection, user, and activity logs. S3 bucket: ams-a{account_I D }-log-management-{region} Logging is enabled by default Path: /AWS/RedShift/ {CloudFront Distribution ID} when you create your Redshift cluster by invoking the Create Redshift cluster CT (ct-1malj 7snzxrkr). For information, see Database Audit Logging. 15 Amazon Logs specific to database type. CloudWatch LogGroup: Relationa l Database Service (RDS) You must explicitly enable RDS logging. For information, see Enabling logging for supported services You can only access MSSQL logs through a stored procedure; for information, see Archiving Log Files. /aws/rds/(instance or cluster)/{database_name }/ {log_name} AMS aggregated service logs Version May 08, 2025 678 AMS Advanced User Guide AMS Advanced Concepts and Procedures Service name Log details Log location 16 Amazon S3 (S3) Bucket access logs. Each access log record provides details about S3 bucket: mc-a{account_ID }- log-management-{region} a single access request such as the requester, bucket name, request time, request action, response status, and error code (if any). Access log information can be useful in security and access audits. It can also help you learn about your customer base and Path: /aws/s3access/{bucket_na me } S3 bucket [in the central Logging Account]: aws-landing-zone-s 3-access-logs-{account_ID }- {region} understand your Amazon S3 bill. Path: / For more information about S3 Access Log entries, see S3 Server Access Log Format. 17 Amazon SES API service calls. Simple Email Service (SES) CloudWatch LogGroup: /CloudTra il/Landing-Zone-Logs S3 bucket [in the central Logging Account]: aws-landing-zone-logs- {account_ID }-{region} Path: /AWSLogs/{account_I D }/CloudTrail/ 18 Amazon Virtual Private Cloud (VPC) VPC flow data (information about the IP traffic going to and from your VPC's network interfaces). CloudWatch LogGroup: /aws/vpcflow/{VPC_ID} AMS aggregated service logs Version May 08, 2025 679 AMS Advanced User Guide AMS Advanced Concepts and Procedures Service name Log details Log location 19 Auto Scaling API call logging only. 20 AWS Certificate Manager CloudWatch LogGroup: /CloudTra il/Landing-Zone-Logs S3 bucket [in the central Logging Account]: aws-landing-zone-logs- {account_ID }-{region} Path: /AWSLogs/{account_I D }/CloudTrail/ 21 AWS CodeDeploy Instance-specific deployment |
ams-ug-246 | ams-ug.pdf | 246 | LogGroup: /CloudTra il/Landing-Zone-Logs S3 bucket [in the central Logging Account]: aws-landing-zone-logs- {account_ID }-{region} Path: /AWSLogs/{account_I D }/CloudTrail/ 18 Amazon Virtual Private Cloud (VPC) VPC flow data (information about the IP traffic going to and from your VPC's network interfaces). CloudWatch LogGroup: /aws/vpcflow/{VPC_ID} AMS aggregated service logs Version May 08, 2025 679 AMS Advanced User Guide AMS Advanced Concepts and Procedures Service name Log details Log location 19 Auto Scaling API call logging only. 20 AWS Certificate Manager CloudWatch LogGroup: /CloudTra il/Landing-Zone-Logs S3 bucket [in the central Logging Account]: aws-landing-zone-logs- {account_ID }-{region} Path: /AWSLogs/{account_I D }/CloudTrail/ 21 AWS CodeDeploy Instance-specific deployment logs. On Instance 22 AWS Config AWS Config API service calls. CloudWatch LogGroup: /CloudTra il/Landing-Zone-Logs S3 bucket [in the central Logging Account]: aws-landing-zone-logs- {account_ID }-{region} Path: /AWSLogs/{account_I D }/CloudTrail/ Resource configuration changes, as tracked by AWS Config. S3 bucket [in the central Logging Account]: aws-landing-zone-logs- {account_ID }-{region} Path: /AWSLogs/{account_I D }/Config/ 23 AWS Database Migration Service Database migration logs. Database migration console For information, see Introduci ng log management in AWS Database Migration Service. AMS aggregated service logs Version May 08, 2025 680 AMS Advanced User Guide AMS Advanced Concepts and Procedures Service name Log details Log location CloudWatch LogGroup: /CloudTra il/Landing-Zone-Logs S3 bucket [in the central Logging Account]: aws-landing-zone-logs- {account_ID }-{region} Path: /AWSLogs/{account_I D }/CloudTrail/ 24 AWS Direct API call logging only. Connect (DX) 25 AWS Glacier 26 AWS IAM (IAM) 27 AWS Key Management Service 28 AWS Managemen t Console (console or AWS Console) 29 AWS Simple Notification Service (SNS) 30 AWS Simple Queueing Service (SQS) Single-Account Landing Zone AMS single-account landing zone Aggregated Service Logs Service name Log details Log location 1 Amazon Aurora General, slow query, and error CloudWatch LogGroup: /aws/ logs. rds/cluster/{database_name }/ {log_name} 2 Amazon API call logging only. CloudForm CloudFormation API calls are documented via CloudTrail, which AMS aggregated service logs Version May 08, 2025 681 AMS Advanced User Guide AMS Advanced Concepts and Procedures Service name Log details Log location ation (CloudFor mation or CFN) 3 Amazon User request logging. CloudFront (CloudFront) You must explicitly enable CloudFront logging. For informati sends its logs to the CloudWatch LogGroup and then syncs the logs into an S3 bucket. CloudWatch LogGroup: /aws/ ams/cloudtrail S3 bucket: ams-a{account_I D }-log-management-{region} S3 bucket: ams-a{account_I D }-log-management-{region} Path: AWS/RedShift/{CloudFron on, see Enabling logging for t_distribution_ID } supported services 4 Amazon API call logging only. CloudWatch (CloudWatch) CloudWatch LogGroup: /aws/ ams/cloudtrail 5 Amazon Elastic Block Store No logs are produced by the EBS service. Not applicable (EBS) 6 Amazon Elastic Compute Cloud (EC2) 7 Amazon Elastic File System (Amazon EFS) System and application logs. For information, see the Amazon Elastic Compute Cloud (Amazon EC2) - system level logs. API call logging only. CloudWatch Logs: /{instance_ ID } CloudWatch LogGroup: /aws/ ams/cloudtrail AMS aggregated service logs Version May 08, 2025 682 AMS Advanced User Guide AMS Advanced Concepts and Procedures Service name Log details Log location 8 Elastic Load Access and error log entries. Balancing (ELB) Elastic load balancers log all CloudWatch LogGroup: /aws/ ams/cloudtrail requests sent to them, including requests that aren't routed to S3 bucket: mc-a{account_ID }- logs-{region} Path: aws/elbaccess back-end instances. For example, if a client sends a malformed request, or there are no healthy instances to respond, the request is still logged. For more information about elastic load balancer log entries, see • Classic Load Balancers: Access log entries. • Application Load Balancers: Access log entries. • Network Load Balancers: Access log entries. 9 Amazon Service error logs. OpenSearc h Service (OpenSearch Service) You must explicitly enable OpenSearch logging. For information, see Enabling logging for supported services 10 Amazon API call logging only. ElastiCache 11 Amazon GuardDuty CloudWatch LogGroup: /aws/ ams/cloudtrail CloudWatch LogGroup: /aws/ ams/cloudtrail AMS aggregated service logs Version May 08, 2025 683 AMS Advanced User Guide AMS Advanced Concepts and Procedures Service name Log details Log location 12 Amazon Inspector 13 Amazon Macie 14 Amazon Redshift Connection, user, and activity logs. S3 bucket: ams-a{account_I D }-log-management-{region} Logging is enabled by default Path: /AWS/RedShift/ {CloudFront_Distrib ution_ID } when you create your Redshift cluster by invoking the Create Redshift cluster CT (ct-1malj 7snzxrkr). For information, see Database Audit Logging. CloudWatch LogGroup: /aws/ rds/(instance|cluster)/{database name}/{log name} 15 Amazon Logs specific to database type. Relationa l Database Service (RDS) RDS logging must be explicitl y enabled. For information, see Enabling logging for supported services You can only access MSSQL logs through a stored procedure; for information, see Archiving Log Files. AMS aggregated service logs Version May 08, 2025 684 AMS Advanced User Guide AMS Advanced Concepts and Procedures Service name Log details Log location 16 Amazon S3 (S3) Bucket access logs. Each access log record provides details about S3 bucket: mc-a{account_ID }- log-management-{region} Path: /aws/s3access/{bucket_na me } a single access request, such as: requester, bucket name, request time, request |
ams-ug-247 | ams-ug.pdf | 247 | Logs specific to database type. Relationa l Database Service (RDS) RDS logging must be explicitl y enabled. For information, see Enabling logging for supported services You can only access MSSQL logs through a stored procedure; for information, see Archiving Log Files. AMS aggregated service logs Version May 08, 2025 684 AMS Advanced User Guide AMS Advanced Concepts and Procedures Service name Log details Log location 16 Amazon S3 (S3) Bucket access logs. Each access log record provides details about S3 bucket: mc-a{account_ID }- log-management-{region} Path: /aws/s3access/{bucket_na me } a single access request, such as: requester, bucket name, request time, request action, response status, and error code (if any). Access log information can be useful in security and access audits; it can also help you learn about your customer base and understand your Amazon S3 bill. For more information on S3 Access Log entries, see S3 Server Access Log Format. 17 Amazon SES API service calls. Simple Email Service (SES) CloudWatch LogGroup: /aws/ ams/cloudtrail S3 bucket: ams-a{account_I D }-log-management-{region} Path: AWS/CloudTrail/AWSLogs/ {account_ID }/CloudTrail/ {region} 18 Amazon Virtual Private Cloud (VPC) VPC flow data (information about the IP traffic going to and from your VPC's network interfaces). CloudWatch LogGroup: /aws/vpcf low/{vpc_id} 19 Auto Scaling API call logging only. CloudWatch LogGroup: /aws/ ams/cloudtrail 20 AWS Certificate Manager 21 AWS CodeDeploy Instance specific deployment logs. On instance AMS aggregated service logs Version May 08, 2025 685 AMS Advanced User Guide AMS Advanced Concepts and Procedures Service name Log details Log location 22 AWS Config AWS Config API service calls. CloudWatch LogGroup: /aws/ ams/cloudtrail S3 bucket: ams-a{account_I D }-log-management-{region} Path: AWS/CloudTrail/AWSLogs/ {account_ID }/CloudTrail/ {region} 23 AWS Database Migration Service Database migration logs. Database migration console For information, see Introduci ng log management in AWS Database Migration Service. CloudWatch LogGroup: /aws/ ams/cloudtrail 24 AWS Direct API call logging only. Connect (DX) 25 AWS Glacier 26 AWS IAM (IAM) 27 AWS Key Management Service 28 AWS Managemen t Console (console or AWS Console) 29 AWS Simple Notification Service (SNS) AMS aggregated service logs Version May 08, 2025 686 AMS Advanced User Guide AMS Advanced Concepts and Procedures Service name Log details Log location 30 AWS Simple Queueing Service (SQS) AMS shared services logs The following table describes the logs, and log location, for the AMS Shared Services in your account. To access your logs, ensure that you have one of the required IAM roles and are in your AMS account. Then navigate to the directory shown. AMS single-account landing zone Shared Services Logging Shared service name 1 Bastion Hosts Log details Log location Information regarding users accessing the bastion host. Linux Bastions: CloudWatch Logs: /{instance id}/ var/log/secure CloudWatch Logs: /{instance id}/ var/log/audit/audit.log Windows Bastions: CloudWatch Logs: /{instance id}/ SecurityEventLog CloudWatch Logs: /{instance id}/ ApplicationEventLog 2 Management Hosts Output of scripts, which assist in automated access management actions within the account. 4 EPS Hosts (DSM) Information regarding the enrollment of instances CloudWatch Logs: /{instance id}/ var/log/DSM.log AMS shared services logs Version May 08, 2025 687 AMS Advanced User Guide AMS Advanced Concepts and Procedures Shared service name Log details Log location onto the Deep Security Management platform. 5 Directory Services Information regarding account login, account CloudWatch Logs: /aws/dire ctoryservice/{directory id}-{dire management, detailed ctory dns name} tracking, object access, policy change, and privilege use within the account’s directory. You must explicitly enable Directory Services logging. For information, see Enabling logging for supported services. 6 Lambdas Output of various lambdas, which assist in automated CloudWatch Logs: /aws/lambda/ {lambda name} operational actions within the account. AMS multi-account landing zone Shared Services Logging Shared service name 1 Bastions Log details Log location Output of instance logins and authentication failures. Linux Bastions CloudWatch Logs: / {instance_ID }/var/log/secure.l og Windows Bastions CloudWatch Logs: /{instance_ID }/Securit yEventLog AMS shared services logs Version May 08, 2025 688 AMS Advanced User Guide AMS Advanced Concepts and Procedures Shared service name Log details Log location 2 Management Hosts Output of scriptsy, which assist in automated access CloudWatch Logs: /{instance_ ID }/ApplicationEventLog management actions within the account. 3 EPS Hosts (DSM) Information regarding the enrollment of instances CloudWatch Logs: /{instance_ ID }/var/log/DSM.log 4 Directory Services 5 Lambdas onto the Deep Security Management platform. Information regarding account login, account management, detailed tracking, object access, policy change, and privilege use within the account’s directory. You must explicitly enable Directory Services logging. For information, see Enabling logging for supported services. Output of various lambdas, which assist in automated operational actions within the account. CloudWatch Logs: /aws/dire ctoryservice/{directory_ID }- {directory_DNS_name } CloudWatch Logs: /aws/lambda/ {Lambda_name } Amazon Elastic Compute Cloud (Amazon EC2) - system level logs Instance logs are collected by a CloudWatch Logs agent running on the instance and can be accessed through a CloudWatch Log group of the same name as the instance. For example, if the Amazon Elastic Compute Cloud |
ams-ug-248 | ams-ug.pdf | 248 | detailed tracking, object access, policy change, and privilege use within the account’s directory. You must explicitly enable Directory Services logging. For information, see Enabling logging for supported services. Output of various lambdas, which assist in automated operational actions within the account. CloudWatch Logs: /aws/dire ctoryservice/{directory_ID }- {directory_DNS_name } CloudWatch Logs: /aws/lambda/ {Lambda_name } Amazon Elastic Compute Cloud (Amazon EC2) - system level logs Instance logs are collected by a CloudWatch Logs agent running on the instance and can be accessed through a CloudWatch Log group of the same name as the instance. For example, if the Amazon Elastic Compute Cloud (Amazon EC2) - system level logs Version May 08, 2025 689 AMS Advanced User Guide AMS Advanced Concepts and Procedures instance ID is i-0123456789abcdef0 and the log file name is /var/log/messages, the Log Group would be i-0123456789abcdef0 and the Log Stream /var/log/messages. See also AMS aggregated service logs. To access your logs, ensure that you have one of the required IAM roles and are in your AMS account. Then navigate to the directory shown. Note The following logs are collected by default. Amazon Linux / Red Hat Linux / Centos Linux / Ubuntu / SUSE Linux Log file / Log stream /var/log/amazon/ssm/amazon-ssm-agent.log /var/log/amazon/ssm/errors.log /var/log/audit/audit.log /var/log/cloud-init-output.log /var/log/cfn-init.log /var/log/cfn-init-cmd.log /var/log/cloud-init.log (Amazon Linux 1 / Amazon Linux 2 only) /var/log/cron /var/log/dnf.log /var/log/maillog /var/log/messages /var/log/secure /var/log/spooler /var/log/yum.log /var/log/aws/ams/bootstrap.log /var/log/aws/ams/build.log /var/log/syslog /var/log/dpkg.log /var/log/auth.log /var/log/zypper.log Amazon Elastic Compute Cloud (Amazon EC2) - system level logs Version May 08, 2025 690 AMS Advanced User Guide AMS Advanced Concepts and Procedures Note For information on accessing logs for Amazon Linux 2023, see Why is the /var/log directory missing logs in my EC2 Amazon Linux 2023 instance? Windows Log file / Log stream SecurityEventLog SystemEventLog AmazonSSMAgentLog MicrosoftWindowsAppLockerMSIAndScriptEventLog MicrosoftWindowsAppLockerEXEAndDLLEventLog AmazonCloudWatchAgentLog EC2ConfigServiceEventLog (Windows Server 2012 R2 Only) ApplicationEventLog AmazonCloudFormationLog MicrosoftWindowsGroupPolicyOperationalEventLog AmazonSSMErrorLog Integrating with Splunk AMS supports AWS Lambda-based push to customer log analytics services, such as Splunk. AMS leverages the Splunk Add-on for Amazon Web services, which allows AWS data to be streamed to Splunk. See Hardware and software requirements. Refer to this Splunk blog post How to stream AWS CloudWatch Logs to Splunk (Hint: it’s easier than you think). Because CloudWatch log streaming is enabled by default for AMS customers, and AMS configures the AWS Lambda function for you, though you need to configure the Splunk HTTP Event Collector (HEC) input and submit a request to AMS for the added functionality. Here’s how the data input settings might look: Integrating with Splunk Version May 08, 2025 691 AMS Advanced User Guide AMS Advanced Concepts and Procedures Customizing your log configuration You can alter log data retention for CloudWatch logs, and you can enable logging for additional AWS services. Altering CloudWatch log retention You can change the log data retention setting for CloudWatch logs. By default, logs are kept indefinitely and never expire. You can adjust the retention policy for each log group, keeping the indefinite retention, or choosing a retention period between 10 years and one day. To view the allowed minimum retention period in AMS, see the AMS Technical Standards document available through AWS Artifact. To access AWS Artifact, contact your CSDM for instructions or go to Getting Started with AWS Artifact. The CloudWatch Logs log retention feature deletes the log events in a stream based on retention policy. It doesn't delete log streams or log groups. For general information, see the Amazon CloudWatch Logs User Guide What is Amazon CloudWatch Logs?. For information on customizing a log retention period, and to learn more, see Change Log Data Retention in CloudWatch Logs. Customizing your log configuration Version May 08, 2025 692 AMS Advanced User Guide AMS Advanced Concepts and Procedures Enabling logging for supported services Some services do not have logging enabled by default and require explicit enablement. To enable logging for CloudFront, OpenSearch, Amazon RDS and Route53, submit an RFC with the Management | Other | Other | Create change type (ct-1e1xtak34nx76) with the following values, replacing variables as appropriate: Subject: Enable logging for SERVICE_NAME Description: Service ARN: SERVICE_ARN Enabling logging for supported services Version May 08, 2025 693 AMS Advanced User Guide AMS Advanced Concepts and Procedures Security management AWS Managed Services (AMS) security management is the process by which AMS identifies an organization's assets and implements policies and procedures to protect those assets. Note AMS now has a change type (CT), Deployment | Advanced stack components | ACM certificate with additional SANs | Create (ct-3l14e139i5p50), that you can use to submit a request for an AWS Certificate Manager certificate. For information, see AWS::CertificateManager::Certificate. This CT provides for the creation of additional subject alternative name (SAN). To better understand general AWS security, see Best Practices for Security, Identity, & Compliance. AMS categorizes security risks as follows: • Known risks detected by anti-malware, which the malware mitigation process |
ams-ug-249 | ams-ug.pdf | 249 | process by which AMS identifies an organization's assets and implements policies and procedures to protect those assets. Note AMS now has a change type (CT), Deployment | Advanced stack components | ACM certificate with additional SANs | Create (ct-3l14e139i5p50), that you can use to submit a request for an AWS Certificate Manager certificate. For information, see AWS::CertificateManager::Certificate. This CT provides for the creation of additional subject alternative name (SAN). To better understand general AWS security, see Best Practices for Security, Identity, & Compliance. AMS categorizes security risks as follows: • Known risks detected by anti-malware, which the malware mitigation process handles. • Security events including access breaches, which the security event management process handles. Topics • Data protection in AMS • Identity and access management • Security Incident Response in AMS • Change request security reviews in AMS Advanced Data protection in AMS AMS continuously monitors your managed accounts by leveraging native AWS services such as Amazon GuardDuty, Amazon Macie (optionally), and other internal proprietary tools and processes. After an alarm is triggered, AMS assumes responsibility for the initial triage and response to the alarm. Our response processes are based on NIST standards. AMS regularly tests its response processes using Security Incident Response Simulation with you to align your workflow with existing customer security response programs. Data protection in AMS Version May 08, 2025 694 AMS Advanced User Guide AMS Advanced Concepts and Procedures When AMS detects any violation, or imminent threat of violation, of AWS or your security policies, we gather information, including impacted resources and any configuration-related changes. AMS provides 24/7/365 follow-the-sun support with dedicated operators actively reviewing and investigating monitoring dashboards, incident queue, and service requests across all of your managed accounts. AMS investigates the findings with our security experts to analyze the activity and notify you through the security escalation contacts listed in your account. Based on our findings, AMS engages with you proactively. If you believe the activity is unauthorized or suspicious, AMS works with you to investigate and remediate or contain the issue. There are certain finding types generated by GuardDuty that require you to confirm the impact before AMS is able to take any action. For example, the GuardDuty finding type UnauthorizedAccess:IAMUser/ ConsoleLogin, indicates that one of your users has logged in from an unusual location; AMS notifies you and asks that you review the finding to confirm if this behavior is legitimate. Amazon Macie AWS Managed Services recommends that you use Macie to detect a large and comprehensive list of sensitive data, such as personal health information (PHI), personally identifiable information (PII), and financial data. Macie can be configured to run periodically on any Amazon S3 bucket, automating the evaluation of any new or modified objects within a bucket over time. As security findings are generated, AMS will notify you and work with you to remediate as needed. For more information, see Analyzing Amazon Macie findings. Amazon Macie security Macie is an artificial intelligence/AI powered security service that helps you prevent data loss by automatically discovering, classifying, and protecting sensitive data stored in AWS. Macie uses machine learning to recognize sensitive data such as personally identifiable information (PII) or intellectual property, assigns a business value, and provides visibility into where this data is stored and how it is being used in your organization. Macie continuously monitors data access activity for anomalies, and delivers alerts when it detects risk of unauthorized access or inadvertent data leaks. Macie service supports Amazon S3 and AWS CloudTrail data sources. AMS continuously monitors for alerts from Macie and, if alerted, takes quick actions to protect your resources and account. With the addition of Macie to the list of services AMS supports, we are also now responsible for enabling and configuring Macie in all of your accounts, per your instructions. You can view Macie alerts and our actions as they unfold in the AWS console or Amazon Macie Version May 08, 2025 695 AMS Advanced User Guide AMS Advanced Concepts and Procedures supported integrations. During account onboarding, you can indicate accounts that you use to store PII. For all new accounts with PII, we recommend using Macie. For existing accounts with PII, contact us and we will turn it on in your account. As a result, you can have an added layer of protection available and enjoy all the benefits of Macie in your AWS environment managed by AMS. AMS Macie FAQs • Why do I need Macie when all AMS accounts have Trend Micro and GuardDuty enabled? Macie helps you protect your data in Amazon S3 by helping you classify what data you have, the value that data has to the business, and the behavior associated with access to that data. Amazon GuardDuty provides broad protection of your AWS accounts, workloads, and data by helping to identify |
ams-ug-250 | ams-ug.pdf | 250 | it on in your account. As a result, you can have an added layer of protection available and enjoy all the benefits of Macie in your AWS environment managed by AMS. AMS Macie FAQs • Why do I need Macie when all AMS accounts have Trend Micro and GuardDuty enabled? Macie helps you protect your data in Amazon S3 by helping you classify what data you have, the value that data has to the business, and the behavior associated with access to that data. Amazon GuardDuty provides broad protection of your AWS accounts, workloads, and data by helping to identify threats such as threat actor reconnaissance, instance issue, and problematic account activity. Both services incorporate user behavior analysis, machine learning, and anomaly detection to detect threats in their respective categories. Trend Micro does not focus on identifying PII and threats from them. • How do I turn Macie on in my AMS account? If you have PII/PHI stored in your accounts or are planning to store it, contact your CSDM or raise a service request to enable Macie for your new or existing accounts managed by AMS. • What are the cost implications of enabling Macie in my AMS account? Macie pricing works for AMS similar to other services such as Amazon Elastic Compute Cloud (Amazon EC2). You pay for Amazon Macie based on usage and an AMS uplift based on your SLAs. Macie fees are based on usage, see Amazon Macie Pricing, measured based on AWS CloudTrail events and Amazon S3 storage. Please note that Macie charges tend to flatten out from the second month after it's enabled because it charges based on incremental data added to Amazon S3 buckets. To learn more about Macie, see Amazon Macie. GuardDuty GuardDuty is a continuous security monitoring service that uses threat intelligence feeds, such as lists of malicious IP addresses and domains, and machine learning to identify unexpected and potentially unauthorized and malicious activity within your AWS environment. This can include issues like escalations of privileges, uses of exposed credentials, or communication with malicious GuardDuty Version May 08, 2025 696 AMS Advanced User Guide AMS Advanced Concepts and Procedures IP addresses, or domains. GuardDuty also monitors Amazon Web Services account access behavior for signs of compromise, such as unauthorized infrastructure deployments, like instances deployed in a Region that has never been used, or unusual API calls, like a password policy change to reduce password strength. For more information, refer to the GuardDuty User Guide. To view and analyze your GuardDuty findings, use the following procedure. 1. Open the GuardDuty console. 2. Choose Findings, and then choose a specific finding to view details. The details for each finding differ depending on the finding type, resources involved, and nature of the activity. For more information on available finding fields, see GuardDuty finding details. GuardDuty security Amazon GuardDuty offers threat detection that enables you to continuously monitor and protect your AWS accounts and workloads. Amazon GuardDuty analyzes continuous streams of meta-data generated from your account and network activity found in AWS CloudTrail Events, Amazon VPC flow logs, and Domain Name System (DNS) logs. It also uses integrated threat intelligence such as known malicious IP addresses, anomaly detection, and machine learning to identify threats more accurately. GuardDuty is a monitored AMS service. To learn more about Amazon GuardDuty monitoring, see GuardDuty monitoring. To learn more about GuardDuty, see Amazon GuardDuty. All new AMS accounts have GuardDuty enabled by default. AMS configures GuardDuty during account onboardings. You can submit change requests to modify the settings at any time. GuardDuty pricing works for AMS similarly to other services such as Amazon Elastic Compute Cloud (Amazon EC2). You pay for GuardDuty based on usage and an AMS uplift based on your SLAs. GuardDuty fees are based on usage (Amazon GuardDuty Pricing), measured based on AWS CloudTrail events and volume of your Amazon VPC Flow log. For GuardDuty in AMS, the following primary detection categories are enabled: • Reconnaissance -- Activity suggesting reconnaissance by a threat actor, such as unusual API activity, intra-VPC port scanning, unusual patterns of failed login requests, or unblocked port probing from a known bad IP. • Instance issue -- Problematic instance activity, such as cryptocurrency mining, malware using domain generation algorithms (DGA), outbound denial of service activity, unusually high volume of network traffic, unusual network protocols, outbound instance communication with a known GuardDuty Version May 08, 2025 697 AMS Advanced User Guide AMS Advanced Concepts and Procedures malicious IP, temporary Amazon EC2 credentials used by an external IP address, and data exfiltration using DNS. • Account activity -- Common patterns indicative of account activity include API calls from an unusual geolocation or anonymizing proxy, attempts to disable AWS CloudTrail logging, unusual instance or infrastructure launches, infrastructure deployments in an unusual AWS Region, and API |
ams-ug-251 | ams-ug.pdf | 251 | cryptocurrency mining, malware using domain generation algorithms (DGA), outbound denial of service activity, unusually high volume of network traffic, unusual network protocols, outbound instance communication with a known GuardDuty Version May 08, 2025 697 AMS Advanced User Guide AMS Advanced Concepts and Procedures malicious IP, temporary Amazon EC2 credentials used by an external IP address, and data exfiltration using DNS. • Account activity -- Common patterns indicative of account activity include API calls from an unusual geolocation or anonymizing proxy, attempts to disable AWS CloudTrail logging, unusual instance or infrastructure launches, infrastructure deployments in an unusual AWS Region, and API calls from known malicious IP addresses. AMS uses GuardDuty in your managed accounts to continuously monitor for findings and alerts from GuardDuty and, if alerted, AMS operations takes proactive actions to protect your resources and account. You can view GuardDuty findings and our actions as they unfold in the AWS console or supported integrations. GuardDuty works with Trend Micro Deep Security Manager in your account. Trend Micro Deep Security Manager provides host-based Intrusion Detection / Intrusion Prevention services. Trend Micro Web Reputation services have some overlap with GuardDuty in the ability to detect when a host is attempting to communicate with a host or web service known to be a threat. However, GuardDuty provides additional threat detection categories and accomplishes this by monitoring network traffic, a method which is complementary to Trend Micro's host-based detection. Network- based threat detection allows for increased security by not allowing controls to fail if the host has been exhibiting problematic behavior. AMS recommends using GuardDuty in all your AMS accounts. To learn more about Trend Micro, see Trend Micro Deep Security Help Center; note that non- Amazon links may change without notice to us. GuardDuty monitoring GuardDuty informs you of the status of your AWS environment by producing security findings that AMS captures and can alert on. Amazon GuardDuty monitors the security of your AWS environment by analyzing and processing VPC flow logs, AWS CloudTrail event logs, and Domain Name System logs. You can expand this monitoring scope by configuring GuardDuty to also use your own custom, trusted IP lists, and threat lists. • Trusted IP lists consist of IP addresses that you have allowed for secure communication with your AWS infrastructure and applications. GuardDuty does not generate findings for IP addresses on trusted IP lists. At any given time, you can have only one uploaded trusted IP list per AWS account per region. GuardDuty Version May 08, 2025 698 AMS Advanced User Guide AMS Advanced Concepts and Procedures • Threat lists consist of known malicious IP addresses. GuardDuty generates findings based on threat lists. At any given time, you can have up to six uploaded threat lists per AWS account per region. To implement GuardDuty, use the AMS CT Deployment | Monitoring and notification | GuardDuty IP set | Create (ct-08avsj2e9mc7g) to create a set of approved IP addresses. You can also use the AMS CT Deployment | Monitoring and notification | GuardDuty threat intel set | Create (ct-25v6r7t8gvkq5) to create a set of denied IP addresses. For a list of the services that AMS monitors, see What does the AMS monitoring system monitor?. Amazon Route 53 Resolver DNS Firewall Amazon Route 53 Resolver responds recursively to DNS queries from AWS resources for public records, Amazon VPC-specific DNS names, and Amazon Route 53 private hosted zones, and is available by default in all VPCs. With Route 53 Resolver DNS Firewall, you can filter and regulate outbound DNS traffic for your virtual private cloud (VPC). To do this, you create reusable collections of filtering rules in DNS Firewall rule groups, associate the rule groups to your VPC, and then monitor activity in DNS Firewall logs and metrics. Based on the activity, you can adjust the behavior of DNS Firewall accordingly. For more information, see Using DNS Firewall to filter outbound DNS traffic. To view and manage your Route 53 Resolver DNS Firewall configuration, use the following procedure: 1. Sign in to the AWS Management Console and open the Amazon VPC console at https:// console.aws.amazon.com/vpc/. 2. Under DNS Firewall, choose Rule groups. 3. Review, edit, or delete your existing configuration, or create a new rule group. For more information, see How Route 53 Resolver DNS Firewall works. Amazon Route 53 Resolver DNS Firewall monitoring and security Amazon Route 53 DNS Firewall uses the concepts of rule associations, rule action, and rule evaluation priority. A domain list is a reusable set of domain specifications that you use in a DNS Firewall rule, inside a rule group. When you associate a rule group with a VPC, DNS Firewall compares your DNS queries against the domain lists that are used in the rules. If DNS Firewall Amazon Route 53 Resolver DNS Firewall Version May 08, 2025 699 AMS |
ams-ug-252 | ams-ug.pdf | 252 | group. For more information, see How Route 53 Resolver DNS Firewall works. Amazon Route 53 Resolver DNS Firewall monitoring and security Amazon Route 53 DNS Firewall uses the concepts of rule associations, rule action, and rule evaluation priority. A domain list is a reusable set of domain specifications that you use in a DNS Firewall rule, inside a rule group. When you associate a rule group with a VPC, DNS Firewall compares your DNS queries against the domain lists that are used in the rules. If DNS Firewall Amazon Route 53 Resolver DNS Firewall Version May 08, 2025 699 AMS Advanced User Guide AMS Advanced Concepts and Procedures finds a match, then it handles the DNS query according to the matching rule's action. For more information about rule groups and rules, see DNS Firewall rule groups and rules. Domain lists fall into two main categories: • Managed domain lists, that AWS creates and maintains for you. • Your own domain lists, that you create and maintain. Rule groups are evaluated based on their association priority index. By default, AMS deploys a baseline configuration that consists of the following rule and rule group: • One rule group named DefaultSecurityMonitoringRule. The rule group has the highest association priority that's available at the time of creation for each existing VPC in each enabled AWS Region. • One rule named DefaultSecurityMonitoringRule with priority 1 within the DefaultSecurityMonitoringRule rule group, using the AWSManagedDomainsAggregateThreatList Managed Domain list with action ALERT. If you have an existing configuration, the baseline configuration is deployed with lower priority than your existing configuration. Your existing configuration is the default. You use the AMS baseline configuration as a catch-all if your existing configuration doesn't provide a higher priority instruction on how to handle query resolution. To alter or remove the baseline configuration, do one of the following: • Contact your Cloud Service Delivery Manager (CSDM) or Cloud Architect (CA). • Create a Request For Change (RFC) using Management | Other | Other | Create CT (ct-1e1xtak34nx76). • Create a service request. If your account is operated in Developer mode or Direct Change mode, you can perform the changes yourself. AWS Certificate Manager (ACM) certificate AMS has a CT, Deployment | Advanced stack components | ACM certificate with additional SANs | Create (ct-3l14e139i5p50), that you can use to submit a request for an AWS Certificate Manager AWS Certificate Manager (ACM) certificate Version May 08, 2025 700 AMS Advanced User Guide AMS Advanced Concepts and Procedures certificate, with up to five additional Subject alternative names (SAN) (such as example.com, example.net, and example.org). For details, see What Is AWS Certificate Manager? and ACM Certificate Characteristic. Note This timeout setting isn't just about the run, but also your validation of the ACM certificate through email validation. Without your validation, the RFC fails. Data encryption in AMS AMS uses several AWS services for data encryption, notably Amazon Simple Storage Service, AWS Key Management Service (AWS KMS), Amazon Elastic Block Store, Amazon Relational Database Service, Amazon Redshift, Amazon ElastiCache, AWS Lambda, and Amazon OpenSearch Service. Amazon S3 Amazon S3 offers several object encryption options that protect data in transit and at rest. Server- side encryption encrypts your object before saving it on disks in its data centers and then decrypts it when you download the objects. As long as you authenticate your request and you have access permissions, there is no difference in the way you access encrypted or unencrypted objects. For more information, see Data protection in Amazon S3. Amazon EBS With Amazon EBS encryption, you don't need to build, maintain, and secure your own key management infrastructure. Amazon EBS encryption uses AWS KMS keys when creating encrypted volumes and snapshots. Encryption operations occur on the servers that host Amazon EC2 instances. This is done to make sure that both data-at-rest and data-in-transit between an instance and its attached Amazon EBS storage is secure. You can attach both encrypted and unencrypted volumes to an instance simultaneously. For more information, see Amazon EBS Encryption. Amazon RDS Amazon RDS can encrypt your Amazon RDS DB instances. Data that's encrypted at rest includes the underlying storage for DB instances, its automated backups, read replicas, and snapshots. Amazon RDS-encrypted DB instances use the industry standard AES-256 encryption algorithm to encrypt your data on the server that hosts your Amazon RDS DB instances. After your data is encrypted, Amazon RDS handles authentication of access and decryption of your data transparently with a Data encryption in AMS Version May 08, 2025 701 AMS Advanced User Guide AMS Advanced Concepts and Procedures minimal impact on performance. You don't need to modify your database client applications to use encryption. For more information, see Encrypting Amazon RDS resources. Amazon Simple Queue Service In addition to the default Amazon SQS managed server-side encryption (SSE) option, Amazon SQS-managed |
ams-ug-253 | ams-ug.pdf | 253 | use the industry standard AES-256 encryption algorithm to encrypt your data on the server that hosts your Amazon RDS DB instances. After your data is encrypted, Amazon RDS handles authentication of access and decryption of your data transparently with a Data encryption in AMS Version May 08, 2025 701 AMS Advanced User Guide AMS Advanced Concepts and Procedures minimal impact on performance. You don't need to modify your database client applications to use encryption. For more information, see Encrypting Amazon RDS resources. Amazon Simple Queue Service In addition to the default Amazon SQS managed server-side encryption (SSE) option, Amazon SQS-managed SSE (SSE-SQS) allows you to create custom managed server-side encryption that uses Amazon SQS-managed encryption keys to protect sensitive data that's sent over message queues. Server-side encryption (SSE) allows you to transmit sensitive data in encrypted queues. SSE protects the content of messages in queues using Amazon SQS-managed encryption keys (SSE-SQS) or keys that are managed in AWS KMS (SSE-KMS). For information about managing SSE using the AWS Management Console, see Encryption at rest. Data encryption at rest OpenSearch Service domains offer encryption of data at rest, a security feature that helps prevent unauthorized access to your data. The feature uses AWS Key Management Service (AWS KMS) to store and manage your encryption keys and the Advanced Encryption Standard algorithm with 256-bit keys(AES-256) to perform the encryption. For more information, see Encryption of Data at Rest for Amazon OpenSearch Service. Key management AWS KMS is a managed service that makes it easy for you to create and control customer master keys (CMKs), the encryption keys used to encrypt your data. AWS KMS CMKs are protected by hardware security modules (HSMs) that are validated by the FIPS 140-2 Cryptographic Module Validation Program except in the China (Beijing) and China (Ningxia) Regions. For more information, see What is AWS Key Management Service? Identity and access management AWS Identity and Access Management (IAM) is a web service that helps you securely control access to AWS resources. You use IAM to control who is authenticated (signed in) and authorized (has permissions) to use resources. During AMS onboarding, you are responsible for creating cross- account IAM Admin roles within each of your managed accounts. Multi-Account Landing Zone (MALZ) IAM safeguards AMS multi-account landing zone (MALZ) requires an Active Directory (AD) trust as a primary design goal of AMS access management to allow each organization (both AMS, and customer) Identity and access management Version May 08, 2025 702 AMS Advanced User Guide AMS Advanced Concepts and Procedures management of their own identities' life cycles. This avoids the need to have credentials in one another's directory. The one-way trust is configured, so that the Managed Active Directory within the AWS account trusts the customer owned or managed AD to authenticate users. Because the trust is only one way, it doesn't mean that the Managed AD is trusted by the Customer Active Directory. In this configuration, the customer directory that manages user identities is known as the User Forest, and the Managed AD to which Amazon EC2 instances are attached is known as the Resource Forest. This is a commonly-leveraged Microsoft design pattern for Windows authentication; for more information, see Forest Design Models. This model allows both organizations to automate their respective lifecycles and allows both AMS and you to rapidly revoke access if an employee leaves the organization. Without this model, if both organizations used a common directory (or created users/groups in one another's directories), then both organizations would have to put in additional workflows, and user syncs, to account for employees starting and leaving. This introduces risk as that process has latency and can be error- prone. MALZ access pre-requisites MALZ Identity Provider Integration for access to the AWS/AMS console, CLI, SDK. Multi-Account Landing Zone (MALZ) IAM safeguards Version May 08, 2025 703 AMS Advanced User Guide AMS Advanced Concepts and Procedures One-way trust for Amazon EC2 instances in your AMS account. Authenticating with identities AMS uses IAM roles, which is a type of IAM identity. An IAM role is very similar to a user, in that it is an identity with permission policies that determine what the identity can and cannot do in AWS. However, a role doesn't have credentials associated with it and, instead of being uniquely Authenticating with identities Version May 08, 2025 704 AMS Advanced User Guide AMS Advanced Concepts and Procedures associated with one person, a role is intended to be assumable by anyone who needs it. An IAM user can assume a role to temporarily take on different permissions for a specific task. Access roles are controlled by internal group membership, which is administered and periodically reviewed by Operations Management. IAM user role in AMS An IAM role is similar to an IAM user, in that it is an AWS |
ams-ug-254 | ams-ug.pdf | 254 | a role doesn't have credentials associated with it and, instead of being uniquely Authenticating with identities Version May 08, 2025 704 AMS Advanced User Guide AMS Advanced Concepts and Procedures associated with one person, a role is intended to be assumable by anyone who needs it. An IAM user can assume a role to temporarily take on different permissions for a specific task. Access roles are controlled by internal group membership, which is administered and periodically reviewed by Operations Management. IAM user role in AMS An IAM role is similar to an IAM user, in that it is an AWS identity with permission policies that determine what the identity can and can't do in AWS. However, instead of being uniquely associated with one person, a role is intended to be assumable by anyone who needs it. Currently there is one AMS default user role, Customer_ReadOnly_Role, for standard AMS accounts and an additional role, customer_managed_ad_user_role for AMS accounts with Managed Active Directory. The role policies set permissions for CloudWatch and Amazon S3 log actions, AMS console access, read-only restrictions on most AWS services, restricted access to account S3 console, and AMS change-type access. Additionally, the Customer_ReadOnly_Role has mutative, reserved-instances permissions that allow you to reserve instances. It has some cost-saving values, so, if you know that you're going to need a certain number of Amazon EC2 instances for a long period of time, you can call those APIs. To learn more, see Amazon EC2 Reserved Instances. Note The AMS service level objective (SLO) for creating custom IAM policies for IAM users is four business days, unless an existing policy is going to be reused. If you want to modify the existing IAM user role, or add a new one, submit an IAM: Update Entity or IAM: Create Entity RFC, respectively. If you're unfamiliar with Amazon IAM roles, see IAM Roles for important information. Multi-Account Landing Zone (MALZ): To see the AMS multi-account landing zone default, un- customized, user role policies, see MALZ: Default IAM User Roles, next. MALZ: Default IAM User Roles JSON policy statements for the default multi-account AMS multi-account landing zone user roles. Authenticating with identities Version May 08, 2025 705 AMS Advanced User Guide AMS Advanced Concepts and Procedures Note The user roles are customizable and may differ on a per-account basis. Instructions on finding your role are provided. These are examples of the default MALZ user roles. To make sure that you have the policies set that you need, run the AWS command get-role or sign in to the AWS Management -> IAM console and choose Roles in the navigation pane. Core OU account roles A core account is an MALZ-managed infrastructure account. AMS multi-account landing zone Core accounts include a management account and a networking account. Core OU account: Common roles and policies Role Policy or policies AWSManagedServicesReadOnlyRole ReadOnlyAccess (Public AWS Managed Policy). AWSManagedServicesCaseRole ReadOnlyAccess AWSSupportAccess (Public AWS Managed Policy). AWSManagedServicesChangeManagementRo le (Core account version) ReadOnlyAccess AWSSupportAccess AMSChangeManagementReadOnlyPolicy AMSChangeManagementInfrastructurePolicy Core OU account: Management account roles and policies Role Policy or policies AWSManagedServicesBillingRole AMSBillingPolicy (AMSBillingPolicy). Authenticating with identities Version May 08, 2025 706 AMS Advanced User Guide AMS Advanced Concepts and Procedures Role Policy or policies AWSManagedServicesReadOnlyRole ReadOnlyAccess (Public AWS Managed Policy). AWSManagedServicesCaseRole ReadOnlyAccess AWSSupportAccess (Public AWS Managed Policy). AWSManagedServicesChangeManagementRo le (Management account version) ReadOnlyAccess AWSSupportAccess AMSChangeManagementReadOnlyPolicy AMSChangeManagementInfrastructurePolicy AMSMasterAccountSpecificCha ngeManagementInfrastructure Policy Core OU Account: Networking account roles and policies Role Policy or policies AWSManagedServicesReadOnlyRole ReadOnlyAccess (Public AWS Managed Policy). AWSManagedServicesCaseRole ReadOnlyAccess AWSSupportAccess (Public AWS Managed Policy). AWSManagedServicesChangeManagementRo le (Networking account version) ReadOnlyAccess AWSSupportAccess AMSChangeManagementReadOnlyPolicy AMSChangeManagementInfrastructurePolicy Authenticating with identities Version May 08, 2025 707 AMS Advanced User Guide AMS Advanced Concepts and Procedures Role Policy or policies AMSNetworkingAccountSpecificChangeMa nagementInfrastructurePolicy Application Account Roles Application account roles are applied to your application-specific accounts. Application account: Roles and policies Role Policy or policies AWSManagedServicesReadOnlyRole ReadOnlyAccess (Public AWS Managed Policy). AWSManagedServicesCaseRole ReadOnlyAccess AWSSupportAccess (Public AWS Managed Policy). This policy provides access to all support operations and resources. For information, see Getting Started with AWS Support. AWSManagedServicesSecurityOpsRole ReadOnlyAccess AWSSupportAccess Example This policy provides access to all support operations and resources. AWSCertificateManagerFullAccess information, (Public AWS Managed Policy) AWSWAFFullAccess information, (Public AWS Managed policy). This policy grants full access to AWS WAF resources. AMSSecretsManagerSharedPolicy Authenticating with identities Version May 08, 2025 708 AMS Advanced User Guide AMS Advanced Concepts and Procedures Role AWSManagedServicesChangeManagementRo le (Application account version) Policy or policies ReadOnlyAccess AWSSupportAccess (Public AWS Managed Policy). This policy provides access to all support operations and resources. For information, see Getting Started with AWS Support. AMSSecretsManagerSharedPolicy AMSChangeManagementPolicy AMSReservedInstancesPolicy AMSS3Policy AWSManagedServicesAdminRole ReadOnlyAccess AWSSupportAccess AMSChangeManagementInfrastructurePolicy AWSMarketplaceManageSubscriptions AMSSecretsManagerSharedPolicy AMSChangeManagementPolicy AWSCertificateManagerFullAccess AWSWAFFullAccess AMSS3Policy AMSReservedInstancesPolicy Authenticating with identities Version May 08, 2025 709 AMS Advanced User Guide Policy Examples AMS Advanced Concepts and Procedures Examples are provided for most policies used. To view the ReadOnlyAccess policy (which is pages long as |
ams-ug-255 | ams-ug.pdf | 255 | with identities Version May 08, 2025 708 AMS Advanced User Guide AMS Advanced Concepts and Procedures Role AWSManagedServicesChangeManagementRo le (Application account version) Policy or policies ReadOnlyAccess AWSSupportAccess (Public AWS Managed Policy). This policy provides access to all support operations and resources. For information, see Getting Started with AWS Support. AMSSecretsManagerSharedPolicy AMSChangeManagementPolicy AMSReservedInstancesPolicy AMSS3Policy AWSManagedServicesAdminRole ReadOnlyAccess AWSSupportAccess AMSChangeManagementInfrastructurePolicy AWSMarketplaceManageSubscriptions AMSSecretsManagerSharedPolicy AMSChangeManagementPolicy AWSCertificateManagerFullAccess AWSWAFFullAccess AMSS3Policy AMSReservedInstancesPolicy Authenticating with identities Version May 08, 2025 709 AMS Advanced User Guide Policy Examples AMS Advanced Concepts and Procedures Examples are provided for most policies used. To view the ReadOnlyAccess policy (which is pages long as it provides read-only access to all AWS services), you can use this link, if you have an active AWS account: ReadOnlyAccess. Also, a condensed version is included here. AMSBillingPolicy AMSBillingPolicy The new Billing role can be used by your accounting department to view and change billing information or account settings in the Management account. To access information such as Alternate Contacts, view the account resources usage, or keep a tab of your billing or even modify your payment methods, you use this role. This new role comprises of all the permissions listed in the AWS Billing IAM actions web page. { "Version": "2012-10-17", "Statement": [ { "Action": [ "aws-portal:ViewBilling", "aws-portal:ModifyBilling" ], "Resource": "*", "Effect": "Allow", "Sid": "AllowAccessToBilling" }, { "Action": [ "aws-portal:ViewAccount", "aws-portal:ModifyAccount" ], "Resource": "*", "Effect": "Allow", "Sid": "AllowAccessToAccountSettings" }, { "Action": [ "budgets:ViewBudget", "budgets:ModifyBudget" ], "Resource": "*", Authenticating with identities Version May 08, 2025 710 AMS Advanced User Guide AMS Advanced Concepts and Procedures "Effect": "Allow", "Sid": "AllowAccessToAccountBudget" }, { "Action": [ "aws-portal:ViewPaymentMethods", "aws-portal:ModifyPaymentMethods" ], "Resource": "*", "Effect": "Allow", "Sid": "AllowAccessToPaymentMethods" }, { "Action": [ "aws-portal:ViewUsage" ], "Resource": "*", "Effect": "Allow", "Sid": "AllowAccessToUsage" }, { "Action": [ "cur:DescribeReportDefinitions", "cur:PutReportDefinition", "cur:DeleteReportDefinition", "cur:ModifyReportDefinition" ], "Resource": "*", "Effect": "Allow", "Sid": "AllowAccessToCostAndUsageReport" }, { "Action": [ "pricing:DescribeServices", "pricing:GetAttributeValues", "pricing:GetProducts" ], "Resource": "*", "Effect": "Allow", "Sid": "AllowAccessToPricing" }, { "Action": [ "ce:*", Authenticating with identities Version May 08, 2025 711 AMS Advanced User Guide AMS Advanced Concepts and Procedures "compute-optimizer:*" ], "Resource": "*", "Effect": "Allow", "Sid": "AllowAccessToCostExplorerComputeOptimizer" }, { "Action": [ "purchase-orders:ViewPurchaseOrders", "purchase-orders:ModifyPurchaseOrders" ], "Resource": "*", "Effect": "Allow", "Sid": "AllowAccessToPurchaseOrders" }, { "Action": [ "redshift:AcceptReservedNodeExchange", "redshift:PurchaseReservedNodeOffering" ], "Resource": "*", "Effect": "Allow", "Sid": "AllowAccessToRedshiftAction" }, { "Action": "savingsplans:*", "Resource": "*", "Effect": "Allow", "Sid": "AWSSavingsPlansFullAccess" } ] } AMSChangeManagementReadOnlyPolicy AMSChangeManagementReadOnlyPolicy Permissions to see all AMS change types, and the history of requested change types. { "Version": "2012-10-17", "Statement": [{ "Sid": "AMSCoreAccountsCMAndSKMSReadOnlyAccess", "Effect": "Allow", Authenticating with identities Version May 08, 2025 712 AMS Advanced Concepts and Procedures AMS Advanced User Guide "Action": [ "amscm:GetChangeTypeVersion", "amscm:GetRfc", "amscm:ListChangeTypeCategories", "amscm:ListChangeTypeClassificationSummaries", "amscm:ListChangeTypeItems", "amscm:ListChangeTypeOperations", "amscm:ListChangeTypeSubcategories", "amscm:ListChangeTypeVersionSummaries", "amscm:ListRestrictedExecutionTimes", "amscm:ListRfcSummaries", "amsskms:GetStack", "amsskms:GetSubnet", "amsskms:GetVpc", "amsskms:ListAmis", "amsskms:ListStackSummaries", "amsskms:ListSubnetSummaries", "amsskms:ListVpcSummaries" ], "Resource": "*" }] } AMSMasterAccountSpecificChangeManagementInfrastructurePolicy AMSMasterAccountSpecificChangeManagementInfrastructurePolicy Permissions to request the Deployment | Managed landing zone | Management account | Create application account (with VPC) change type. { "Version": "2012-10-17", "Statement": [{ "Sid": "AMSMasterAccountAccess", "Effect": "Allow", "Action": [ "amscm:ApproveRfc", "amscm:CancelRfc", "amscm:CreateRfc", "amscm:RejectRfc", "amscm:SubmitRfc", "amscm:UpdateRfc", "amscm:UpdateRfcActionState", Authenticating with identities Version May 08, 2025 713 AMS Advanced User Guide AMS Advanced Concepts and Procedures "amscm:UpdateRestrictedExecutionTimes" ], "Resource": [ "arn:aws:amscm:global:*:changetype/ct-1zdasmc2ewzrs:*" ] }] } AMSNetworkingAccountSpecificChangeManagementInfrastructurePolicy AMSNetworkingAccountSpecificChangeManagementInfrastructurePolicy Permissions to request the Deployment | Managed landing zone | Networking account | Create application route table change type. { "Version": "2012-10-17", "Statement": [{ "Sid": "AMSNetworkingAccountAccess", "Effect": "Allow", "Action": [ "amscm:ApproveRfc", "amscm:CancelRfc", "amscm:CreateRfc", "amscm:RejectRfc", "amscm:SubmitRfc", "amscm:UpdateRfc", "amscm:UpdateRfcActionState", "amscm:UpdateRestrictedExecutionTimes" ], "Resource": [ "arn:aws:amscm:global:*:changetype/ct-1urj94c3hdfu5:*" ] }] } AMSChangeManagementInfrastructurePolicy AMSChangeManagementInfrastructurePolicy (for Management | Other | Other CTs) Permissions to request the Management | Other | Other | Create, and Management | Other | Other | Update change types. Authenticating with identities Version May 08, 2025 714 AMS Advanced User Guide AMS Advanced Concepts and Procedures { "Version": "2012-10-17", "Statement": [{ "Sid": "AMSCoreAccountsAccess", "Effect": "Allow", "Action": [ "amscm:CancelRfc", "amscm:CreateRfc", "amscm:SubmitRfc", "amscm:UpdateRfc", "amscm:UpdateRfcActionState", "amscm:UpdateRestrictedExecutionTimes", ], "Resource": [ "arn:aws:amscm:global:*:changetype/ct-1e1xtak34nx76:*", "arn:aws:amscm:global:*:changetype/ct-0xdawir96cy7k:*", ] }] } AMSSecretsManagerSharedPolicy AMSSecretsManagerSharedPolicy Permissions to view secret passwords/hashes shared by AMS through AWS Secrets Manager (e.g. passwords to infrastructure for auditing). Permissions to create secret password/hashes to share with AMS. (for example, license keys for products that need to be deployed). { "Version": "2012-10-17", "Statement": [{ "Sid": "AllowAccessToSharedNameSpaces", "Effect": "Allow", "Action": "secretsmanager:*", "Resource": [ "arn:aws:secretsmanager:*:*:secret:ams-shared/*", "arn:aws:secretsmanager:*:*:secret:customer-shared/*" ] }, { Authenticating with identities Version May 08, 2025 715 AMS Advanced User Guide AMS Advanced Concepts and Procedures "Sid": "DenyGetSecretOnCustomerNamespace", "Effect": "Deny", "Action": "secretsmanager:GetSecretValue", "Resource": "arn:aws:secretsmanager:*:*:secret:customer-shared/*" }, { "Sid": "AllowReadAccessToAMSNameSpace", "Effect": "Deny", "NotAction": [ "secretsmanager:Describe*", "secretsmanager:Get*", "secretsmanager:List*" ], "Resource": "arn:aws:secretsmanager:*:*:secret:ams-shared/*" } ] } AMSChangeManagementPolicy AMSChangeManagementPolicy Permissions to request and view all AMS change types, and the history of requested change types. { "Version": "2012-10-17", "Statement": [{ "Sid": "AMSFullAccess", "Effect": "Allow", "Action": [ "amscm:*", "amsskms:*" ], "Resource": [ "*" ] }] } AMSReservedInstancesPolicy AMSReservedInstancesPolicy Authenticating with identities Version May 08, 2025 716 AMS Advanced User Guide AMS Advanced Concepts and Procedures Permissions to manage Amazon EC2 reserved instances; for pricing information, |
ams-ug-256 | ams-ug.pdf | 256 | Advanced User Guide AMS Advanced Concepts and Procedures "Sid": "DenyGetSecretOnCustomerNamespace", "Effect": "Deny", "Action": "secretsmanager:GetSecretValue", "Resource": "arn:aws:secretsmanager:*:*:secret:customer-shared/*" }, { "Sid": "AllowReadAccessToAMSNameSpace", "Effect": "Deny", "NotAction": [ "secretsmanager:Describe*", "secretsmanager:Get*", "secretsmanager:List*" ], "Resource": "arn:aws:secretsmanager:*:*:secret:ams-shared/*" } ] } AMSChangeManagementPolicy AMSChangeManagementPolicy Permissions to request and view all AMS change types, and the history of requested change types. { "Version": "2012-10-17", "Statement": [{ "Sid": "AMSFullAccess", "Effect": "Allow", "Action": [ "amscm:*", "amsskms:*" ], "Resource": [ "*" ] }] } AMSReservedInstancesPolicy AMSReservedInstancesPolicy Authenticating with identities Version May 08, 2025 716 AMS Advanced User Guide AMS Advanced Concepts and Procedures Permissions to manage Amazon EC2 reserved instances; for pricing information, see Amazon EC2 Reserved Instances. { "Version": "2012-10-17", "Statement": [{ "Sid": "AllowReservedInstancesManagement", "Effect": "Allow", "Action": [ "ec2:ModifyReservedInstances", "ec2:PurchaseReservedInstancesOffering" ], "Resource": [ "*" ] }] } AMSS3Policy AMSS3Policy Permissions to create and delete files from existing Amazon S3 buckets. Note These permissions do not grant the ability to create S3 buckets; that must be done with the Deployment | Advanced stack components | S3 storage | Create change type. { "Version": "2012-10-17", "Statement": [{ "Effect": "Allow", "Action": [ "s3:AbortMultipartUpload", "s3:DeleteObject", "s3:PutObject", ], "Resource": "*" }] } Authenticating with identities Version May 08, 2025 717 AMS Advanced User Guide AWSSupportAccess AWSSupportAccess AMS Advanced Concepts and Procedures Full access to Support. For information, see Getting Started with Support. For Premium Support information, see Support. { "Version": "2012-10-17", "Statement": [{ "Effect": "Allow", "Action": [ "support:*" ], "Resource": "*" }] } AWSMarketplaceManageSubscriptions AWSMarketplaceManageSubscriptions (Public AWSManaged Policy) Permissions to subscribe, unsubscribe, and view AWS Marketplace subscriptions. { "Version": "2012-10-17", "Statement": [{ "Action": [ "aws-marketplace:ViewSubscriptions", "aws-marketplace:Subscribe", "aws-marketplace:Unsubscribe" ], "Effect": "Allow", "Resource": "*" }] } AWSCertificateManagerFullAccess AWSCertificateManagerFullAccess Full access to AWS Certificate Manager. For more information, see AWS Certificate Manager. Authenticating with identities Version May 08, 2025 718 AMS Advanced User Guide AMS Advanced Concepts and Procedures AWSCertificateManagerFullAccess information, (Public AWS Managed Policy). { "Version": "2012-10-17", "Statement": [{ "Effect": "Allow", "Action": [ "acm:*" ], "Resource": "*" }] } AWSWAFFullAccess AWSWAFFullAccess Full access to AWS WAF. For more information, see AWS WAF - Web Application Firewall. AWSWAFFullAccess information, (Public AWS Managed policy). This policy grants full access to AWS WAF resources. { "Version": "2012-10-17", "Statement": [{ "Action": [ "waf:*", "waf-regional:*", "elasticloadbalancing:SetWebACL" ], "Effect": "Allow", "Resource": "*" }] } ReadOnlyAccess ReadOnlyAccess Read-only access to all AWS services and resources on the AWS console. When AWS launches a new service, AMS updates the ReadOnlyAccess policy to add read-only permissions for the new service. The updated permissions are applied to all principal entities that the policy is attached to. Authenticating with identities Version May 08, 2025 719 AMS Advanced User Guide AMS Advanced Concepts and Procedures This doesn't grant the ability to log into EC2 hosts or database hosts. If you have an active AWS account, then you can use this link ReadOnlyAccess to view the entire ReadOnlyAccess policy. The whole ReadOnlyAccess policy is very long as it provides read-only access to all AWS services. The following is a partial excerpt of the ReadOnlyAccess policy. {{ "Version": "2012-10-17", "Statement": [ { "Sid": "ReadOnlyActions", "Effect": "Allow", "Action": [ "a4b:Get*", "a4b:List*", "a4b:Search*", "access-analyzer:GetAccessPreview", "access-analyzer:GetAnalyzedResource", ...{truncated} } Single-Account Landing Zone (SALZ): To see the AMS single-account landing zone default, uncustomized, user role policies, see SALZ: Default IAM User Role, next. SALZ: Default IAM User Role JSON policy statements for the default AMS single-account landing zone user role. Note The SALZ default user role is customizable and may differ on a per-account basis. Instructions on finding your role are provided. This is an example of the default SALZ user role, but to make sure that you have the policies set for you, run the AWS command get-role or sign in to the AWS Management -> IAM console at https://console.aws.amazon.com/iam/. In the IAM console, in the navigation pane, choose Roles. The customer read-only role is a combination of multiple policies. A breakdown of the role (JSON) follows. Authenticating with identities Version May 08, 2025 720 AMS Advanced User Guide AMS Advanced Concepts and Procedures Managed Services Audit Policy: {"Version": "2012-10-17", "Statement": [ { "Sid": "BasicConsoleAccess", "Effect": "Allow", "Action": [ "aws-portal:View*", "ec2-reports:View*", "support:*" ], "Resource": [ "*" ] }, { "Sid": "AuditAccessToAWSServices", "Effect": "Allow", "Action": [ "acm:Describe*", "acm:List*", "appstream:Get*", "autoscaling:Describe*", "cloudformation:Describe*", "cloudformation:Get*", "cloudformation:List*", "cloudformation:ValidateTemplate", "cloudfront:Get*", "cloudfront:List*", "cloudsearch:Describe*", "cloudsearch:List*", "cloudtrail:DescribeTrails", "cloudtrail:GetTrailStatus", "cloudtrail:LookupEvents", "cloudwatch:Describe*", "cloudwatch:Get*", "cloudwatch:List*", "codecommit:Get*", "codecommit:List*", "codedeploy:BatchGet*", "codedeploy:Get*", "codedeploy:List*", "codepipeline:Get*", Authenticating with identities Version May 08, 2025 721 AMS Advanced User Guide AMS Advanced Concepts and Procedures "codepipeline:List*", "config:Describe*", "config:Get*", "datapipeline:Describe*", "datapipeline:EvaluateExpression", "datapipeline:GetPipelineDefinition", "datapipeline:ListPipelines", "datapipeline:ValidatePipelineDefinition", "directconnect:Describe*", "ds:Describe*", "dynamodb:Describe*", "dynamodb:List*", "ec2:Describe*", "ec2:Get*", "ecs:Describe*", "ecs:List*", "elasticache:Describe*", "elasticache:List*", "elasticbeanstalk:Check*", "elasticbeanstalk:Describe*", "elasticbeanstalk:List*", "elasticbeanstalk:RequestEnvironmentInfo", "elasticbeanstalk:RetrieveEnvironmentInfo", "elasticfilesystem:Describe*", "elasticloadbalancing:Describe*", "elasticmapreduce:Describe*", "elasticmapreduce:List*", "elastictranscoder:List*", "events:Describe*", "events:Get*", "events:List*", "guardduty:Get*", "guardduty:List*", "kinesis:Describe*", "kinesis:List*", "kms:List*", "lambda:Get*", "lambda:List*", "macie:Describe*", "macie:Get*", "macie:List*", "opsworks:Describe*", "opsworks:Get*", "rds:Describe*", Authenticating with identities Version May 08, 2025 722 AMS Advanced User Guide AMS Advanced Concepts and Procedures "rds:Download*", "rds:List*", "redshift:Describe*", "redshift:View*", "route53:Get*", "route53:List*", "route53domains:CheckDomainAvailability", "route53domains:Get*", "route53domains:List*", "sdb:Get*", |
ams-ug-257 | ams-ug.pdf | 257 | "cloudtrail:DescribeTrails", "cloudtrail:GetTrailStatus", "cloudtrail:LookupEvents", "cloudwatch:Describe*", "cloudwatch:Get*", "cloudwatch:List*", "codecommit:Get*", "codecommit:List*", "codedeploy:BatchGet*", "codedeploy:Get*", "codedeploy:List*", "codepipeline:Get*", Authenticating with identities Version May 08, 2025 721 AMS Advanced User Guide AMS Advanced Concepts and Procedures "codepipeline:List*", "config:Describe*", "config:Get*", "datapipeline:Describe*", "datapipeline:EvaluateExpression", "datapipeline:GetPipelineDefinition", "datapipeline:ListPipelines", "datapipeline:ValidatePipelineDefinition", "directconnect:Describe*", "ds:Describe*", "dynamodb:Describe*", "dynamodb:List*", "ec2:Describe*", "ec2:Get*", "ecs:Describe*", "ecs:List*", "elasticache:Describe*", "elasticache:List*", "elasticbeanstalk:Check*", "elasticbeanstalk:Describe*", "elasticbeanstalk:List*", "elasticbeanstalk:RequestEnvironmentInfo", "elasticbeanstalk:RetrieveEnvironmentInfo", "elasticfilesystem:Describe*", "elasticloadbalancing:Describe*", "elasticmapreduce:Describe*", "elasticmapreduce:List*", "elastictranscoder:List*", "events:Describe*", "events:Get*", "events:List*", "guardduty:Get*", "guardduty:List*", "kinesis:Describe*", "kinesis:List*", "kms:List*", "lambda:Get*", "lambda:List*", "macie:Describe*", "macie:Get*", "macie:List*", "opsworks:Describe*", "opsworks:Get*", "rds:Describe*", Authenticating with identities Version May 08, 2025 722 AMS Advanced User Guide AMS Advanced Concepts and Procedures "rds:Download*", "rds:List*", "redshift:Describe*", "redshift:View*", "route53:Get*", "route53:List*", "route53domains:CheckDomainAvailability", "route53domains:Get*", "route53domains:List*", "sdb:Get*", "sdb:List*", "ses:Get*", "ses:List*", "sns:Get*", "sns:List*", "sqs:Get*", "sqs:List*", "ssm:ListCommands", "ssm:ListCommandInvocations", "storagegateway:Describe*", "storagegateway:List*", "swf:Count*", "swf:Describe*", "swf:Get*", "swf:List*", "tag:get*", "trustedadvisor:Describe*", "waf:Get*", "waf:List*", "waf-regional:Get*", "waf-regional:List*" ], "Resource": [ "*" ] }, { "Sid": "AWSManagedServicesFullAccess", "Effect": "Allow", "Action": [ "amscm:*", "amsskms:*" ], "Resource": [ Authenticating with identities Version May 08, 2025 723 AMS Advanced User Guide AMS Advanced Concepts and Procedures "*" ] } ] } Managed Services IAM ReadOnly Policy { "Statement": [ { "Action": [ "iam:GenerateCredentialReport", "iam:GetAccountAuthorizationDetails", "iam:GetAccountPasswordPolicy", "iam:GetAccountSummary", "iam:GetCredentialReport", "iam:GetGroup", "iam:GetGroupPolicy", "iam:GetInstanceProfile", "iam:GetPolicy", "iam:GetPolicyVersion", "iam:GetRole", "iam:GetRolePolicy", "iam:GetUser", "iam:GetUserPolicy", "iam:ListAccountAliases", "iam:ListAttachedRolePolicies", "iam:ListEntitiesForPolicy", "iam:ListGroupPolicies", "iam:ListGroups", "iam:ListGroupsForUser", "iam:ListInstanceProfiles", "iam:ListInstanceProfilesForRole", "iam:ListMFADevices", "iam:ListPolicies", "iam:ListPolicyVersions", "iam:ListRolePolicies", "iam:ListRoles", "iam:ListSAMLProviders", "iam:ListUsers", "iam:ListVirtualMFADevices" ], Authenticating with identities Version May 08, 2025 724 AMS Advanced User Guide AMS Advanced Concepts and Procedures "Effect": "Allow", "Resource": [ "*" ], "Sid": "IAMReadOnlyAccess" }, { "Action": [ "iam:*" ], "Effect": "Deny", "Resource": [ "arn:aws:iam::*:group/mc-*", "arn:aws:iam::*:group/mc_*", "arn:aws:iam::*:policy/mc-*", "arn:aws:iam::*:policy/mc_*", "arn:aws:iam::*:role/mc-*", "arn:aws:iam::*:role/mc_*", "arn:aws:iam::*:role/Sentinel-*", "arn:aws:iam::*:role/Sentinel_*", "arn:aws:iam::*:user/mc-*", "arn:aws:iam::*:user/mc_*" ], "Sid": "DenyAccessToIamRolesStartingWithMC" } ], Managed Services User Policy "Version": "2012-10-17" } { "Version": "2012-10-17", "Statement": [ { "Sid": "AllowCustomerToListTheLogBucketLogs", "Effect": "Allow", "Action": [ "s3:ListBucket" ], "Resource": [ "arn:aws:s3:::mc-a*-logs-*" ], Authenticating with identities Version May 08, 2025 725 AMS Advanced User Guide AMS Advanced Concepts and Procedures "Condition": { "StringLike": { "s3:prefix": [ "aws/*", "app/*", "encrypted", "encrypted/", "encrypted/app/*" ] } } }, { "Sid": "BasicAccessRequiredByS3Console", "Effect": "Allow", "Action": [ "s3:ListAllMyBuckets", "s3:GetBucketLocation" ], "Resource": [ "arn:aws:s3:::*" ] }, { "Sid": "AllowCustomerToGetLogs", "Effect": "Allow", "Action": [ "s3:GetObject*" ], "Resource": [ "arn:aws:s3:::mc-a*-logs-*/aws/*", "arn:aws:s3:::mc-a*-logs-*/encrypted/app/*" ] }, { "Sid": "AllowAccessToOtherObjects", "Effect": "Allow", "Action": [ "s3:DeleteObject*", "s3:Get*", "s3:List*", "s3:PutObject*" ], "Resource": [ Authenticating with identities Version May 08, 2025 726 AMS Advanced User Guide AMS Advanced Concepts and Procedures "*" ] }, { "Sid": "AllowCustomerToListTheLogBucketRoot", "Effect": "Allow", "Action": [ "s3:ListBucket" ], "Resource": [ "arn:aws:s3:::mc-a*-logs-*" ], "Condition": { "StringEquals": { "s3:prefix": [ "", "/" ] } } }, { "Sid": "AllowCustomerCWLConsole", "Effect": "Allow", "Action": [ "logs:DescribeLogStreams", "logs:DescribeLogGroups" ], "Resource": [ "arn:aws:logs:*:*:log-group:*" ] }, { "Sid": "AllowCustomerCWLAccessLogs", "Effect": "Allow", "Action": [ "logs:FilterLogEvents", "logs:GetLogEvents" ], "Resource": [ "arn:aws:logs:*:*:log-group:/aws/*", "arn:aws:logs:*:*:log-group:/infra/*", "arn:aws:logs:*:*:log-group:/app/*", "arn:aws:logs:*:*:log-group:RDSOSMetrics:*:*" Authenticating with identities Version May 08, 2025 727 AMS Advanced User Guide AMS Advanced Concepts and Procedures ] }, { "Sid": "AWSManagedServicesFullAccess", "Effect": "Allow", "Action": [ "amscm:*", "amsskms:*" ], "Resource": [ "*" ] }, { "Sid": "ModifyAWSBillingPortal", "Effect": "Allow", "Action": [ "aws-portal:Modify*" ], "Resource": [ "*" ] }, { "Sid": "DenyDeleteCWL", "Effect": "Deny", "Action": [ "logs:DeleteLogGroup", "logs:DeleteLogStream" ], "Resource": [ "arn:aws:logs:*:*:log-group:*" ] }, { "Sid": "DenyMCCWL", "Effect": "Deny", "Action": [ "logs:CreateLogGroup", "logs:CreateLogStream", "logs:DescribeLogStreams", "logs:FilterLogEvents", "logs:GetLogEvents", "logs:PutLogEvents" Authenticating with identities Version May 08, 2025 728 AMS Advanced Concepts and Procedures AMS Advanced User Guide ], "Resource": [ "arn:aws:logs:*:*:log-group:/mc/*" ] }, { "Sid": "DenyS3MCNamespace", "Effect": "Deny", "Action": [ "s3:*" ], "Resource": [ "arn:aws:s3:::mc-a*-logs-*/encrypted/mc/*", "arn:aws:s3:::mc-a*-logs-*/mc/*", "arn:aws:s3:::mc-a*-logs-*-audit/*", "arn:aws:s3:::mc-a*-internal-*/*", "arn:aws:s3:::mc-a*-internal-*" ] }, { "Sid": "ExplicitDenyS3CfnBucket", "Effect": "Deny", "Action": [ "s3:*" ], "Resource": [ "arn:aws:s3:::cf-templates-*" ] }, { "Sid": "DenyListBucketS3LogsMC", "Action": [ "s3:ListBucket" ], "Effect": "Deny", "Resource": [ "arn:aws:s3:::mc-a*-logs-*" ], "Condition": { "StringLike": { "s3:prefix": [ "auditlog/*", "encrypted/mc/*", "mc/*" Authenticating with identities Version May 08, 2025 729 AMS Advanced User Guide AMS Advanced Concepts and Procedures ] } } }, { "Sid": "DenyS3LogsDelete", "Effect": "Deny", "Action": [ "s3:Delete*", "s3:Put*" ], "Resource": [ "arn:aws:s3:::mc-a*-logs-*/*" ] }, { "Sid": "DenyAccessToKmsKeysStartingWithMC", "Effect": "Deny", "Action": [ "kms:*" ], "Resource": [ "arn:aws:kms::*:key/mc-*", "arn:aws:kms::*:alias/mc-*" ] }, { "Sid": "DenyListingOfStacksStartingWithMC", "Effect": "Deny", "Action": [ "cloudformation:*" ], "Resource": [ "arn:aws:cloudformation:*:*:stack/mc-*" ] }, { "Sid": "AllowCreateCWMetricsAndManageDashboards", "Effect": "Allow", "Action": [ "cloudwatch:PutMetricData" ], "Resource": [ "*" Authenticating with identities Version May 08, 2025 730 AMS Advanced User Guide AMS Advanced Concepts and Procedures ] }, { "Sid": "AllowCreateandDeleteCWDashboards", "Effect": "Allow", "Action": [ "cloudwatch:DeleteDashboards", "cloudwatch:PutDashboard" ], "Resource": [ "*" ] } ] } Customer Secrets Manager Shared Policy { "Version": "2012-10-17", "Statement": [ { "Sid": "AllowSecretsManagerListSecrets", "Effect": "Allow", "Action": "secretsmanager:listSecrets", "Resource": "*" }, { "Sid": "AllowCustomerAdminAccessToSharedNameSpaces", "Effect": "Allow", "Action": "secretsmanager:*", "Resource": [ "arn:aws:secretsmanager:*:*:secret:ams-shared/*", "arn:aws:secretsmanager:*:*:secret:customer-shared/*" ] }, { "Sid": "DenyCustomerGetSecretCustomerNamespace", "Effect": "Deny", "Action": "secretsmanager:GetSecretValue", "Resource": "arn:aws:secretsmanager:*:*:secret:customer-shared/*" }, { Authenticating with identities Version May 08, 2025 731 AMS Advanced User Guide AMS Advanced Concepts and Procedures "Sid": "AllowCustomerReadOnlyAccessToAMSNameSpace", "Effect": "Deny", "NotAction": [ "secretsmanager:Describe*", "secretsmanager:Get*", "secretsmanager:List*" ], "Resource": "arn:aws:secretsmanager:*:*:secret:ams-shared/*" } ] } Customer Marketplace Subscribe Policy { "Version": "2012-10-17", "Statement": [ { "Sid": "AllowMarketPlaceSubscriptions", "Effect": "Allow", "Action": [ "aws-marketplace:ViewSubscriptions", "aws-marketplace:Subscribe" ], "Resource": [ "*" ] } ] } Security event |
ams-ug-258 | ams-ug.pdf | 258 | Policy { "Version": "2012-10-17", "Statement": [ { "Sid": "AllowSecretsManagerListSecrets", "Effect": "Allow", "Action": "secretsmanager:listSecrets", "Resource": "*" }, { "Sid": "AllowCustomerAdminAccessToSharedNameSpaces", "Effect": "Allow", "Action": "secretsmanager:*", "Resource": [ "arn:aws:secretsmanager:*:*:secret:ams-shared/*", "arn:aws:secretsmanager:*:*:secret:customer-shared/*" ] }, { "Sid": "DenyCustomerGetSecretCustomerNamespace", "Effect": "Deny", "Action": "secretsmanager:GetSecretValue", "Resource": "arn:aws:secretsmanager:*:*:secret:customer-shared/*" }, { Authenticating with identities Version May 08, 2025 731 AMS Advanced User Guide AMS Advanced Concepts and Procedures "Sid": "AllowCustomerReadOnlyAccessToAMSNameSpace", "Effect": "Deny", "NotAction": [ "secretsmanager:Describe*", "secretsmanager:Get*", "secretsmanager:List*" ], "Resource": "arn:aws:secretsmanager:*:*:secret:ams-shared/*" } ] } Customer Marketplace Subscribe Policy { "Version": "2012-10-17", "Statement": [ { "Sid": "AllowMarketPlaceSubscriptions", "Effect": "Allow", "Action": [ "aws-marketplace:ViewSubscriptions", "aws-marketplace:Subscribe" ], "Resource": [ "*" ] } ] } Security event logging and monitoring AMS continuously monitors the managed environment for security threats. Security events might be detected by AMS or by you. AMS regularly updates its automation process—based on the Computer Security Incident Handling Guide by the National Institute of Standards and Technology (NIST)—to better detect security threats. Endpoint Security (EPS) Resources that you provision in your AMS Advanced environment automatically include the installation of an endpoint security (EPS) monitoring client. This process ensures that the AMS Security event logging and monitoring Version May 08, 2025 732 AMS Advanced User Guide AMS Advanced Concepts and Procedures Advanced-managed resources are monitored and supported 24x7. In addition, AMS Advanced monitors all agent activity, and an incident is created if any security event is detected. Note Security incidents are handled as incidents; for more information, see Incident response. Endpoint security provides anti-malware protection, specifically, the following actions are supported: • EC2 instances register with EPS • EC2 instances deregister from EPS • EC2 instances real-time anti-malware protection • EPS agent-initiated heartbeat • EPS restore quarantined file • EPS event notification • EPS reporting AMS Advanced uses Trend Micro for endpoint security (EPS). These are the default EPS settings. To learn more about Trend Micro, see the Trend Micro Deep Security Help Center; note that non- Amazon links may change without notice to us. AMS Advanced Multi-Account Landing Zone (MALZ) default settings are described in the following sections; for non-default AMS multi-account landing zone EPS settings, see AMS Advanced Multi- Account Landing Zone EPS non-default settings. Note You can bring your own EPS, see AMS bring your own EPS. General EPS settings Endpoint security general network settings. Endpoint Security (EPS) Version May 08, 2025 733 AMS Advanced User Guide EPS defaults Setting Firewall Ports (Instances’ Security Group) AMS Advanced Concepts and Procedures Default EPS Deep Security Manager agents (DSMs) must have port 4120 open for the Agent/Rel ay to Manager communication, and port 4119 for the Manager Console. EPS Relays must have port 4122 open for the Manager/Agent to Relay communication. No specific ports should be open for customer instance inbound communication because agents initiate all requests. Communication Direction Agent/Appliance Initiated Heartbeat Interval Ten minutes Number of missed heartbeats before an alert Two Maximum allowed drift (difference) between server times Unlimited Raise offline errors for inactive (registered, but not online) virtual machines No Default policy Base policy (described next) Activation of multiple computers with the same host name Is allowed Alerts for pending updates are raised After seven days Update schedule AMS targets a monthly release cycle for Trend Micro Deep Security Manager (DSM) / Deep Security Agent (DSA) software updates. However, AMS doesn't maintain an SLA for updates. Updates are performed fleet-wide by AMS developer teams during a deployment. Endpoint Security (EPS) Version May 08, 2025 734 AMS Advanced User Guide AMS Advanced Concepts and Procedures Setting Default DSA/DSA updates are logged in Trend Micro DSM system events that AMS retains locally by default for 13 weeks. For vendor documenta tion, see System events in the Trend Micro Deep Security Help Center. Logs are also exported to log group /aws/ams/eps/var/log/ DSM.log in Amazon CloudWatch. Trend Micro Update Server (https://ipv6-iaus .trendmicro.com/iau_server.dll/) Events and logs are deleted from the DSM database after seven days. Update source Event or log data deletion Agent software versions are held Most recent rule updates are held Up to five Up to ten Logs storage By default, log files are stored securely in Amazon S3, but you can also archive them to Amazon Glacier to help meet audit and compliance requirements. Base policy Endpoint security base policy default settings. EPS base policy Setting Enabled Modules Disabled Modules Default Anti-Malware Web Reputation Firewall Intrusion Protection Endpoint Security (EPS) Version May 08, 2025 735 AMS Advanced User Guide AMS Advanced Concepts and Procedures Setting Default Integrity Monitoring Log Inspection Application Control Anti-malware Endpoint security anti-malware settings. EPS anti-malware defaults Setting Default Notes Real-Time Scan Scan everything Every Day/All Day (24 hours) Manual Scan Scan everything Scheduled Scan Scan everything Quarantine all suspected viruses. Enable IntelliTrap and spyware/grayware protection. Spyware and Grayware trigger Anti-Malware and result in a quarantine of the item. Must be requested, then follows default real-time scan configuration. Set for |
ams-ug-259 | ams-ug.pdf | 259 | base policy Setting Enabled Modules Disabled Modules Default Anti-Malware Web Reputation Firewall Intrusion Protection Endpoint Security (EPS) Version May 08, 2025 735 AMS Advanced User Guide AMS Advanced Concepts and Procedures Setting Default Integrity Monitoring Log Inspection Application Control Anti-malware Endpoint security anti-malware settings. EPS anti-malware defaults Setting Default Notes Real-Time Scan Scan everything Every Day/All Day (24 hours) Manual Scan Scan everything Scheduled Scan Scan everything Quarantine all suspected viruses. Enable IntelliTrap and spyware/grayware protection. Spyware and Grayware trigger Anti-Malware and result in a quarantine of the item. Must be requested, then follows default real-time scan configuration. Set for the last Sunday of every month, 6am. Smart Protection Disabled N/A Endpoint Security (EPS) Version May 08, 2025 736 AMS Advanced User Guide AMS Advanced Concepts and Procedures Setting Default Notes Quarantined Files Trend Micro Deep Security Manager (DSM) Appx 1GB of disk reserved for quarantine. Scan Limitation Trend Micro DSM Scan files of all sizes. Allowed Spyware or Grayware None Local Event Notification Yes N/A N/A Malware mitigation process AMS uses Trend Micro’s Deep Security Platform (anti-malware system) to detect and respond to malware on your AMS-managed instances. By default, the Trend Micro detection agent runs on all Amazon EC2 instances, including those in the shared services and private subnets, for both Windows and Linux operating systems. The anti-malware system is connected to AMS monitoring so that an event is generated whenever malware is detected. If there is customer impact, the event is escalated to the incident management process (for details, see AMS incident response). While AMS assesses the impact, you are notified, and attempts are made to mitigate the impact. Trend Micro anti-malware definitions are updated automatically when Trend Micro publishes updates. During application onboarding, you indicate the action you want AMS to take when malware is found on an instance: • Make sure the quarantined file is on the allow list, removing it from the quarantine and releasing it back to the file system. • Delete the quarantined file, removing it from the instance. • Suspend the instance and replace it. The suspended instance is then available to you to mount for forensic research. After application onboarding: • When the anti-malware system discovers malware on an instance, AMS automatically quarantines the malware. This triggers an event and a follow-up investigation. Malware mitigation process Version May 08, 2025 737 AMS Advanced User Guide AMS Advanced Concepts and Procedures • AMS notifies you of the event through a service notification and starts following the default mitigation action that you selected. • If you haven't chosen a default action, AMS asks you which action to take. After receiving your instructions, AMS runs the selected action and notifies you. AMS notifies you again after the action is complete, including details needed for forensic analysis, if applicable. Enable IDS and IPS in Trend Micro Deep Security You can request that AMS enable Trend Micro Intrusion Detection System (IDS) and Intrusion Protection Systems (IPS), non-default features, for your account. To do this, submit an update request (Management | Other | Other | Update) and include a list of email addresses to receive IDS and IPS notifications. These addresses are added to an SNS topic in your account, which AMS creates for you. Note AMS cannot add any Trend Micro service that might interfere with our ability to provide other AMS services. Full system malware scans The Payment Card Industry Data Security Standard (PCI DSS) requires full system malware scans, which are enabled on your AMS-managed VPC by default. Full system scans are set to occur at 2AM (on the time zone set on the server) because they use a lot of CPU. Full system scans are in addition to regular malware scans that do not use a lot of CPU. There is a new Management change type (CT), Disable malware scans, that allows you to disable full system malware scans. You can find the CT in the Management | Host security | Full system scan | Disable classification, change ID ct-1pybwg08h8qsz. To re-enable scans, use the Management | Other | Other | Update CT. Disabling full system scans does not disable your regular malware scans. Amazon Inspector security The Amazon Inspector service monitors the security of your AMS-managed stacks. Amazon Inspector is an automated security assessment service that helps identify gaps in the security and compliance of infrastructure deployed on AWS. Amazon Inspector security assessments enable you Amazon Inspector security Version May 08, 2025 738 AMS Advanced User Guide AMS Advanced Concepts and Procedures to automatically assess stacks for exposure, vulnerabilities, and deviations from best practices by checking for unintended network accessibility and vulnerabilities in your Amazon EC2 instances. After performing an assessment, Amazon Inspector produces a detailed list of security findings prioritized by level of severity. Amazon Inspector assessments are offered as |
ams-ug-260 | ams-ug.pdf | 260 | the security of your AMS-managed stacks. Amazon Inspector is an automated security assessment service that helps identify gaps in the security and compliance of infrastructure deployed on AWS. Amazon Inspector security assessments enable you Amazon Inspector security Version May 08, 2025 738 AMS Advanced User Guide AMS Advanced Concepts and Procedures to automatically assess stacks for exposure, vulnerabilities, and deviations from best practices by checking for unintended network accessibility and vulnerabilities in your Amazon EC2 instances. After performing an assessment, Amazon Inspector produces a detailed list of security findings prioritized by level of severity. Amazon Inspector assessments are offered as pre-defined rules packages mapped to common security best practices and definitions. These rules are regularly updated by AWS security researchers. For more information about Amazon Inspector go to Amazon Inspector. AMS Amazon Inspector FAQs • Is Amazon Inspector installed to my AMS accounts by default? No. Amazon Inspector is not part of the default AMI build or workload ingestion. • How do I access and install Amazon Inspector? Submit an RFC (Management | Other | Other | Create) to request account access and installation to Inspector and the AMS operations team will modify the Customer_ReadOnly_Role to provide Amazon Inspector console access (without SSM access). • Does the Amazon Inspector Agent have to be installed on all of the Amazon EC2 instances I want to assess? No, Amazon Inspector assessments with the network reachability rules package can be run without an agent for any Amazon EC2 instances. The agent is required for host assessment rules packages. For more information about agent installation, see Installing Amazon Inspector Agents. • Is there an additional cost for this service? Yes. Amazon Inspector pricing can be found on the Amazon Inspector pricing site. • What are Amazon Inspector findings? Findings are potential security issues discovered during the Amazon Inspector assessment of the selected assessment target. Findings are displayed in the Amazon Inspector console or the API, and contain both a detailed description of the security issues and recommendations for resolving them. • Are reports of the Amazon Inspector assessment available? Yes. An assessment report is a document that details what is tested in the assessment run, and the results of the assessment. The results of your assessment are formatted into standard Amazon Inspector security Version May 08, 2025 739 AMS Advanced User Guide AMS Advanced Concepts and Procedures reports, which can be generated to share results within your team for remediation actions, to enrich compliance audit data, or to store for future reference. An Amazon Inspector assessment report can be generated for an assessment run once it has been successfully completed. • Can I use tags to identify the stacks I want to run Amazon Inspector reports against? Yes. • Will AMS Operations teams have access to the Amazon Inspector assessment results? Yes. Anyone with access to the Amazon Inspector console in AWS is able to view findings and assessment reports. • Will AMS Operations teams recommend or take action based on the findings of the Amazon Inspector reports? No. If you want changes made based on the findings of the Amazon Inspector report, you must request changes through an RFC (Management | Other | Other | Update). • Will AMS be notified when I run an Amazon Inspector report? When you request Amazon Inspector access, the AMS Operator running the RFC notifies your CSDM of the request. For more information, see Amazon Inspector FAQs. AMS incident response AMS uses traditional IT service management (ITSM) incident management best practices to restore service, when needed, as quickly as possible. We provide 24/7/365 follow-the-sun support through multiple operations centers around the world with dedicated operators actively monitoring dashboards and incident queues. Our operations engineers use internal incident tracking tools to identify, log, categorize, prioritize, diagnose, resolve, and close incidents and provide updates on all of these activities to you through the AMS console or through the Support API. Our operators, many of whom have spent time in AWS Premium Support in various technology profiles and roles, leverage a variety of internal Support tools to help with all of those activities. These operators are deeply familiar with AMS supported infrastructures and have expert level technical skills to address all identified support issues. In the rare case where our operators need assistance, the Premium Support and AWS Service teams are available to assist as needed. AMS incident response Version May 08, 2025 740 AMS Advanced User Guide AMS Advanced Concepts and Procedures In cases where High priority incidents are impacting your critical workloads, AMS will recommend an infrastructure restore. There is often a tradeoff between troubleshooting an issue or restoring from a known good backup, and customer risks and impacts from service downtime are the deciding factors. If you have time to devote to troubleshooting issues, AMS will assist |
ams-ug-261 | ams-ug.pdf | 261 | all identified support issues. In the rare case where our operators need assistance, the Premium Support and AWS Service teams are available to assist as needed. AMS incident response Version May 08, 2025 740 AMS Advanced User Guide AMS Advanced Concepts and Procedures In cases where High priority incidents are impacting your critical workloads, AMS will recommend an infrastructure restore. There is often a tradeoff between troubleshooting an issue or restoring from a known good backup, and customer risks and impacts from service downtime are the deciding factors. If you have time to devote to troubleshooting issues, AMS will assist you, but if the urgency to restore is high, we can initiate a restore right away. Note Ephemeral data that is not part of the stack template or data restore is lost. AMS uses reasonable efforts to perform infrastructure restore while AWS service offerings are unavailable. Infrastructure restore is completed once AWS service offerings are available. If you don't authorize an infrastructure restore as recommended by AMS, you won't be eligible for a service credit for the AMS service commitment for incident resolution time. Compliance validation AMS deploys and manages a library of AWS Config rules and remediation actions, to protect against misconfigurations that could reduce the security and operational integrity of your accounts. As an example, when an Amazon S3 bucket is created, AWS Config can evaluate the Amazon S3 bucket against a rule that requires Amazon S3 buckets to deny public read access. If the Amazon S3 bucket policy or bucket access control list (ACL), allows public read access, AWS Config flags both the bucket and the rule as noncompliant. These AWS Config Rules mark resources as either Compliant, Noncompliant, or Not Applicable, based on the result of their evaluation. For more information about AWS Config service, see the AWS Config Developer Guide. You can use the AWS Config console, AWS CLI, or AWS Config API to view the rules deployed in your account and the compliance state of your rules and resources. For more information, see the AWS Config documentation: Viewing Configuration Compliance. Note Additional information on this topic is available by accessing AWS Artifact reports. For more information, see Downloading reports in AWS Artifact. To access AWS Artifact, you can contact your CSDM for instructions or go to Getting Started with AWS Artifact. This information is not included in this user guide because it contains sensitive security content. Compliance validation Version May 08, 2025 741 AMS Advanced User Guide AMS Advanced Concepts and Procedures Multi-Account Landing Zone viewing the compliance status of your AWS Config Rules AMS multi-account landing zone utilizes the AWS Config aggregator service to create a centralized view of compliance across all your accounts. This means you can see the compliance status of all AWS Config Rules across your AMS multi-account landing zone environment under the AWS Config aggregator in your security account. The following is a sample of the AWS Config aggregator showcasing central compliance status of AWS Config Rules across accounts. For more information, see the AWS documentation for Config Aggregator. • How does AMS use AWS Config rules? AMS creates AWS Config Rules to give visibility into the configuration of your AWS resources against conditions specified in the rules. If a rule is non-compliant, you can request a change and the AMS Ops team will work with you to take corrective action. • In that case, you see the following changes appear in your AMS accounts: • AWS Config Rules under AWS Config > Rules • Custom Config rules with their Lambda functions exist in your account Multi-Account Landing Zone viewing the compliance status of your AWS Config Rules Version May 08, 2025 742 AMS Advanced User Guide AMS Advanced Concepts and Procedures • Config Aggregator in Security account and Config Authorization in all accounts (Multi-Account Landing Zone only) The following is a sample of AWS Config Rules and their compliance evaluation results is shown below: To learn more about AWS Config, see: • AWS Config: What Is Config? • AWS Config Rules: Evaluating Resources with Rules • AWS Config Rules: Dynamic Compliance Checking: AWS Config Rules – Dynamic Compliance Checking for Cloud Resources • AWS Config Aggregator: Multi-Account Multi-Region Data Aggregation AMS multi-account landing zone service control policy restrictions This section has been redacted because it contains sensitive AMS security-related information. This information is available through the AMS console Documentation. To access AWS Artifact, you can contact your CSDM for instructions or go to Getting Started with AWS Artifact. AMS multi-account landing zone service control policy restrictions Version May 08, 2025 743 AMS Advanced User Guide Resilience AMS Advanced Concepts and Procedures The AWS global infrastructure is built around AWS Regions and Availability Zones. AWS Regions provide multiple physically separated and isolated Availability Zones, which are connected with low-latency, |
ams-ug-262 | ams-ug.pdf | 262 | Data Aggregation AMS multi-account landing zone service control policy restrictions This section has been redacted because it contains sensitive AMS security-related information. This information is available through the AMS console Documentation. To access AWS Artifact, you can contact your CSDM for instructions or go to Getting Started with AWS Artifact. AMS multi-account landing zone service control policy restrictions Version May 08, 2025 743 AMS Advanced User Guide Resilience AMS Advanced Concepts and Procedures The AWS global infrastructure is built around AWS Regions and Availability Zones. AWS Regions provide multiple physically separated and isolated Availability Zones, which are connected with low-latency, high-throughput, and highly redundant networking. With Availability Zones, you can design and operate applications and databases that automatically fail over between zones without interruption. Availability Zones are more highly available, fault tolerant, and scalable than traditional single or multiple data center infrastructures. For more information about AWS Regions and Availability Zones, see AWS global infrastructure. Infrastructure security Note Additional information on this topic is available by accessing AWS Artifact reports. For more information, see Downloading reports in AWS Artifact. To access AWS Artifact, you can contact your CSDM for instructions or go to Getting Started with AWS Artifact. This information is not included in this user guide because it contains sensitive security content. Security control for end-of-support operating systems Operating systems that are outside of the general support period of the operating system manufacturer's "end-of-support" or EOS, and do not receive security updates, have an increased security risk. AWS offers some services to help with handling operation system end-of-support. For information about Windows end-of-support, see End-of-Support Migration Program for Windows Server. Note Additional information on this topic is available by accessing AWS Artifact reports. For more information, see Downloading reports in AWS Artifact. To access AWS Artifact, you can contact your CSDM for instructions or go to Getting Started with AWS Artifact. This information is not included in this user guide because it contains sensitive security content. Resilience Version May 08, 2025 744 AMS Advanced User Guide Using security groups AMS Advanced Concepts and Procedures A security group acts as a virtual firewall that controls the traffic for one or more instances. AMS security groups allow you to set inbound traffic rules and outbound traffic rules on an instance- level basis. You can create a security group and specify resources in your AMS account, Amazon EC2 instances, Amazon RDS DB instances, Load Balancers, Deep Security Manager (DSM) replication instances, EFS mount targets, and ElastiCache clusters, to associate with the security group. Once associated, traffic to or from those instances is constrained by the rules set in the security group. To better understand general AWS security, see Best Practices for Security, Identity, & Compliance and Amazon EC2 Security Groups for Linux Instances. AMS now has a set of change types for creating and managing security groups: • Deployment | Advanced stack components | Security group | Create (ct-1oxx2g2d7hc90) • Management | Advanced stack components | Security group | Delete (ct-3cp96z7r065e4) • Management | Advanced stack components | Security group | Update (ct-3memthlcmvc1b) For examples, see Security groups. Security groups In AWS VPCs, AWS Security Groups act as virtual firewalls, controlling the traffic for one or more stacks (an instance or a set of instances). When a stack is launched, it's associated with one or more security groups, which determine what traffic is allowed to reach it: • For stacks in your public subnets, the default security groups accept traffic from HTTP (80) and HTTPS (443) from all locations (the internet). The stacks also accept internal SSH and RDP traffic from your corporate network, and AWS bastions. Those stacks can then egress through any port to the Internet. They can also egress to your private subnets and other stacks in your public subnet. • Stacks in your private subnets can egress to any other stack in your private subnet, and instances within a stack can fully communicate over any protocol with each other. Important The default security group for stacks on private subnets allows all stacks in your private subnet to communicate with other stacks in that private subnet. If you want to restrict Infrastructure security Version May 08, 2025 745 AMS Advanced User Guide AMS Advanced Concepts and Procedures communications between stacks within a private subnet, you must create new security groups that describe the restriction. For example, if you want to restrict communications to a database server so that the stacks in that private subnet can only communicate from a specific application server over a specific port, request a special security group. How to do so is described in this section. Default Security Groups MALZ The following table describes the default inbound security group (SG) settings for your stacks. The SG is named "SentinelDefaultSecurityGroupPrivateOnly-vpc-ID" where ID is a VPC ID |
ams-ug-263 | ams-ug.pdf | 263 | Advanced User Guide AMS Advanced Concepts and Procedures communications between stacks within a private subnet, you must create new security groups that describe the restriction. For example, if you want to restrict communications to a database server so that the stacks in that private subnet can only communicate from a specific application server over a specific port, request a special security group. How to do so is described in this section. Default Security Groups MALZ The following table describes the default inbound security group (SG) settings for your stacks. The SG is named "SentinelDefaultSecurityGroupPrivateOnly-vpc-ID" where ID is a VPC ID in your AMS multi-account landing zone account. All traffic is allowed outbound to "mc-initial- garden-SentinelDefaultSecurityGroupPrivateOnly" via this security group (all local traffic within stack subnets is allowed). All traffic is allowed outbound to 0.0.0.0/0 by a second security group "SentinelDefaultSecurityGroupPrivateOnly". Tip If you're choosing a security group for an AMS change type, such as EC2 create, or OpenSearch create domain, you would use one of the default security groups described here, or a security group that you created. You can find the list of security groups, per VPC, in either the AWS EC2 console or VPC console. There are additional default security groups that are used for internal AMS purposes. AMS default security groups (inbound traffic) Type Protocol Port range Source All traffic All traffic All All All All SentinelDefaultSecurityGroupPrivateOnly (restrict s outbound traffic to members of the same security group) SentinelDefaultSecurityGroupPrivateOnlyEgress All (does not restrict outbound traffic) Infrastructure security Version May 08, 2025 746 AMS Advanced User Guide AMS Advanced Concepts and Procedures Type Protocol Port range Source HTTP, HTTPS, SSH, RDP TCP 80 / 443 (Source 0.0.0.0/0) SentinelDefaultSecurityGroupPublic (does not restrict outbound traffic) SSH and RDP access is allowed from bastions MALZ bastions: SSH SSH RDP RDP TCP TCP TCP TCP SALZ bastions: SSH SSH RDP RDP TCP TCP TCP TCP 22 22 3389 3389 22 22 3389 3389 SALZ SharedServices VPC CIDR and DMZ VPC CIDR, plus Customer-provided on-prem CIDRs mc-initial-garden-LinuxBastionSG mc-initial-garden-LinuxBastionDMZSG mc-initial-garden-WindowsBastionSG mc-initial-garden-WindowsBastionDMZSG The following table describes the default inbound security group (SG) settings for your stacks. The SG is named "mc-initial-garden-SentinelDefaultSecurityGroupPrivateOnly-ID" where ID is a unique identifier. All traffic is allowed outbound to "mc-initial-garden- SentinelDefaultSecurityGroupPrivateOnly" via this security group (all local traffic within stack subnets is allowed). All traffic is allowed outbound to 0.0.0.0/0 by a second security group "mc-initial-garden- SentinelDefaultSecurityGroupPrivateOnlyEgressAll-ID". Infrastructure security Version May 08, 2025 747 AMS Advanced User Guide AMS Advanced Concepts and Procedures Tip If you're choosing a security group for an AMS change type, such as EC2 create, or OpenSearch create domain, you would use one of the default security groups described here, or a security group that you created. You can find the list of security groups, per VPC, in either the AWS EC2 console or VPC console. There are additional default security groups that are used for internal AMS purposes. AMS default security groups (inbound traffic) Type Protocol Port range Source All traffic All traffic HTTP, HTTPS, SSH, RDP All All All All SentinelDefaultSecurityGroupPrivateOnly (restrict s outbound traffic to members of the same security group) SentinelDefaultSecurityGroupPrivateOnlyEgress All (does not restrict outbound traffic) TCP 80 / 443 (Source 0.0.0.0/0) SentinelDefaultSecurityGroupPublic (does not restrict outbound traffic) SSH and RDP access is allowed from bastions MALZ bastions: SSH SSH RDP RDP TCP TCP TCP TCP SALZ bastions: 22 22 3389 3389 SharedServices VPC CIDR and DMZ VPC CIDR, plus Customer-provided on-prem CIDRs Infrastructure security Version May 08, 2025 748 AMS Advanced User Guide AMS Advanced Concepts and Procedures Type Protocol Port range Source SSH SSH RDP RDP TCP TCP TCP TCP 22 22 3389 3389 mc-initial-garden-LinuxBastionSG mc-initial-garden-LinuxBastionDMZSG mc-initial-garden-WindowsBastionSG mc-initial-garden-WindowsBastionDMZSG Create, Change, or Delete Security Groups You can request custom security groups. In cases where the default security groups do not meet the needs of your applications or your organization, you can modify or create new security groups. Such a request would be considered approval-required and would be reviewed by the AMS operations team. To create a security group outside of stacks and VPCs, submit an RFC using the Management | Other | Other | Create CT (ct-1e1xtak34nx76). To add or remove a user from an Active Directory (AD) security group, submit a request for change (RFC) using the Management | Other | Other | Update CT (ct-0xdawir96cy7k). Note When using "review required" CTs, AMS recommends that you use the ASAP Scheduling option (choose ASAP in the console, leave start and end time blank in the API/CLI) as these CTs require an AMS operator to examine the RFC, and possibly communicate with you before it can be approved and run. If you schedule these RFCs, be sure to allow at least 24 hours. If approval does not happen before the scheduled start time, the RFC is rejected automatically. Find Security Groups To |
ams-ug-264 | ams-ug.pdf | 264 | a request for change (RFC) using the Management | Other | Other | Update CT (ct-0xdawir96cy7k). Note When using "review required" CTs, AMS recommends that you use the ASAP Scheduling option (choose ASAP in the console, leave start and end time blank in the API/CLI) as these CTs require an AMS operator to examine the RFC, and possibly communicate with you before it can be approved and run. If you schedule these RFCs, be sure to allow at least 24 hours. If approval does not happen before the scheduled start time, the RFC is rejected automatically. Find Security Groups To find the security groups attached to a stack or instance, use the EC2 console. After finding the stack or instance, you can see all security groups attached to it. For ways to find security groups at the command line and filter the output, see describe- security-groups. Infrastructure security Version May 08, 2025 749 AMS Advanced User Guide AMS Advanced Concepts and Procedures AMS preventative and detective controls library AWS Managed Services (AMS) provides you with a curated library/catalog of proven service control policies (SCPs) and ConfigRules that can be leveraged to improve your security posture and mitigate compliance gaps in your AMS accounts. Topics • Curated SCPs and Config Rules • Custom notification for Config rules Curated SCPs and Config Rules Curated SCPs and Config Rules for AMS Advanced. • Service control policies (SCPs): The provided SCPs are in addition to default AMS ones. You can use these library controls in tandem with the default ones to meet specific security requirements. • Config Rules: As a baseline measure, AMS recommends applying Conformance Packs (see Conformance Packs in the AWS Config guide) in addition to the default AMS config rules (see AMS Artifacts for default rules). The Conformance Packs cover a majority of compliance requirements and AWS regularly updates them. The rules listed here can be used to cover use-case specific gaps that aren’t covered by Conformance Packs Note As AMS default rules and conformance packs get updated over time, you might see duplicates of these rules. AMS recommends doing periodic clean-up of duplicate Config Rules in general. For AMS Advanced, Config Rules should not use auto-remediations (see Remediating Noncompliant AWS Resources by AWS Config Rules) in order to avoid out-of-band changes. SCP-AMS-001: Restrict EBS creation Prevent the creation of EBS volumes if you don’t have encryption enabled. Infrastructure security Version May 08, 2025 750 AMS Advanced User Guide AMS Advanced Concepts and Procedures { "Condition": { "Bool": { "ec2:Encrypted": "false" } }, "Action": "ec2:CreateVolume", "Resource": "*", "Effect": "Deny" } SCP-AMS-002: Restrict EC2 launch Prevent the launch of an EC2 instance if the EBS volume is unencrypted. This includes denying an EC2 launch from unencrypted AMIs because this SCP also applies to root volumes. { "Condition": { "Bool": { "ec2:Encrypted": "false" } }, "Action": "ec2:RunInstances", "Resource": "arn:aws:ec2:*:*:volume/*", "Effect": "Deny" } SCP-ADV-001: Restrict RFC submissions Restrict default AMS roles from submitting specific automated RFCs like Create VPC or Delete VPC. This is helpful if you want to apply more granular permissions to your federated roles. For example, you might want the default AWSManagedServicesChangeManagement Role to be able to submit most of the available RFCs except the ones that allow for the creation and deletion of a VPC, creation of additional subnets, offboarding of an application account, updating or deleting SAML identity providers: { "Version": "2012-10-17", "Statement": [ { Infrastructure security Version May 08, 2025 751 AMS Advanced User Guide AMS Advanced Concepts and Procedures "Condition": { "ArnLike": { "aws:PrincipalARN": [ "arn:aws:iam::*:role/AWSManagedServicesChangeManagement Role", "arn:aws:iam::*:role/AWSManagedServicesAdminRole" ] } }, "Action": [ "amscm:ApproveRfc", "amscm:CancelRfc", "amscm:CreateRfc", "amscm:CreateRfcAttachment", "amscm:CreateRfcCorrespondence", "amscm:GetRfcAttachment", "amscm:ListRfcAttachmentSummaries", "amscm:ListRfcCorrespondences", "amscm:RejectRfc", "amscm:SubmitRfc", "amscm:UpdateRestrictedExecutionTimes", "amscm:UpdateRfc" ], "Resource": [ "arn:aws:amscm:global:*:changetype/ct-1j3503fres5a5:*", "arn:aws:amscm:global:*:changetype/ct-2paw0y79kvr3l:*" "arn:aws:amscm:global:*:changetype/ct-2ha68tpd7nr3y:*" "arn:aws:amscm:global:*:changetype/ct-2wlfo2jxj2rkj:*" "arn:aws:amscm:global:*:changetype/ct-3hox8uwjgze1f:*" "arn:aws:amscm:global:*:changetype/ct-01zl37gmuk4q2:*" "arn:aws:amscm:global:*:changetype/ct-379uwo67vbvng:*" ], "Effect": "Deny", "Sid": "RestrictAppAccountRFCs" } ] } SCP-AMS-003: Restrict EC2 or RDS creation in AMS Prevent creation of Amazon EC2 and RDS instances that don't have specific tags, while allowing the AMS default AMS Backup IAM role to do so. This is needed for disaster recover or DR. { Infrastructure security Version May 08, 2025 752 AMS Advanced User Guide AMS Advanced Concepts and Procedures "Sid": "DenyRunInstanceWithNoOrganizationTag", "Effect": "Deny", "Action": [ "ec2:RunInstances", "rds:CreateDBInstance" ], "Resource": [ "arn:aws:ec2:*:*:instance/*", "arn:aws:ec2:*:*:volume/*", "arn:aws:rds:*:*:db:*" ], "Condition": { "Null": { "aws:RequestTag/organization": "true" }, "StringNotLike": { "aws:PrincipalArn": [ "arn:aws:iam::<Account_Number>:role/ams-backup-iam-role" ] } } } SCP-AMS-004: Restrict S3 uploads Prevent uploads of unencrypted S3 objects. { "Sid": "DenyUnencryptedS3Uploads", "Effect": "Deny", "Action": "s3:PutObject", "Resource": "*", "Condition": { "StringNotLike": { "s3:x-amz-server-side-encryption": ["aws:kms", "AES256"] }, "Null": { "s3:x-amz-server-side-encryption": "false" } } } ] } Infrastructure security Version May 08, 2025 753 AMS Advanced User Guide AMS Advanced Concepts and Procedures SCP-AMS-005: Restrict API and console access Prevent AWS Console and API access for requests coming from known bad IP addresses as determined customer InfoSec. { "Version": "2012-10-17", "Statement": [ { "Condition": { "IpAddressIfExists": |
ams-ug-265 | ams-ug.pdf | 265 | { "Null": { "aws:RequestTag/organization": "true" }, "StringNotLike": { "aws:PrincipalArn": [ "arn:aws:iam::<Account_Number>:role/ams-backup-iam-role" ] } } } SCP-AMS-004: Restrict S3 uploads Prevent uploads of unencrypted S3 objects. { "Sid": "DenyUnencryptedS3Uploads", "Effect": "Deny", "Action": "s3:PutObject", "Resource": "*", "Condition": { "StringNotLike": { "s3:x-amz-server-side-encryption": ["aws:kms", "AES256"] }, "Null": { "s3:x-amz-server-side-encryption": "false" } } } ] } Infrastructure security Version May 08, 2025 753 AMS Advanced User Guide AMS Advanced Concepts and Procedures SCP-AMS-005: Restrict API and console access Prevent AWS Console and API access for requests coming from known bad IP addresses as determined customer InfoSec. { "Version": "2012-10-17", "Statement": [ { "Condition": { "IpAddressIfExists": { "aws:SourceIp": [ "<ip address 1>", "<ip address 2>", "<ip address n>" ] } }, "Action": [ "*" ], "Resource": [ "*" ], "Effect": "Deny", "Sid": "IPDeny" } ] } SCP-AMS-006: Prevent IAM entity from removing member account from the organization Prevent an AWS Identity and Access Management entity from removing member accounts from the organization. { "Effect": "Deny", "Action": ["organizations:LeaveOrganization"], "Resource": ["*"] } Infrastructure security Version May 08, 2025 754 AMS Advanced User Guide AMS Advanced Concepts and Procedures SCP-AMS-007: Prevent sharing resources to accounts outside your organization Prevent sharing resources with external accounts outside your AWS organization { "Effect": "Deny", "Action": [ "ram:*" ], "Resource": [ "*" ], "Condition": { "Bool": { "ram:AllowsExternalPrincipals": "true" } } }, { "Effect": "Deny", "Action": [ "ram:CreateResourceShare", "ram:UpdateResourceShare" ], "Resource": "*", "Condition": { "Bool": { "ram:RequestedAllowsExternalPrincipals": "true" } } } SCP-AMS-008: Prevent sharing with organizations or organizational units (OUs) Prevent sharing resources with an account and/or OU that's in an organization. { "Effect": "Deny", "Action": [ "ram:CreateResourceShare", "ram:AssociateResourceShare" ], Infrastructure security Version May 08, 2025 755 AMS Advanced User Guide AMS Advanced Concepts and Procedures "Resource": "*", "Condition": { "ForAnyValue:StringLike": { "ram:Principal": [ "arn:aws:organizations::*:account/o-${OrganizationId}/${AccountId}", "arn:aws:organizations::*:ou/o-${OrganizationId}/ou-${OrganizationalUnitId}" ] } } } SCP-AMS-009: Prevent users from accepting resource share invitations Prevent member accounts from accepting invitations from AWS RAM to join resource shares. This API doesn't support any conditions and prevents shares only from external accounts. { "Effect": "Deny", "Action": ["ram:AcceptResourceShareInvitation"], "Resource": ["*"] } SCP-AMS-010: Prevent account Region enable and disable actions Prevent enabling or disabling any new AWS Regions for your AWS accounts. { "Effect": "Deny", "Action": [ "account:EnableRegion", "account:DisableRegion" ], "Resource": "*" } SCP-AMS-011: Prevent billing modification actions Prevent modifications to billing and payment configuration. { "Effect": "Deny", "Action": [ "aws-portal:ModifyBilling", Infrastructure security Version May 08, 2025 756 AMS Advanced User Guide AMS Advanced Concepts and Procedures "aws-portal:ModifyAccount", "aws-portal:ModifyPaymentMethods" ], "Resource": "*" } SCP-AMS-012: Prevent deletion or modification to specific CloudTrails Prevent modifications to specific AWS CloudTrail trails. { "Effect": "Deny", "Action": [ "cloudtrail:DeleteEventDataStore", "cloudtrail:DeleteTrail", "cloudtrail:PutEventSelectors", "cloudtrail:PutInsightSelectors", "cloudtrail:UpdateEventDataStore", "cloudtrail:UpdateTrail", "cloudtrail:StopLogging" ], "Resource": [ "arn:${Partition}:cloudtrail:${Region}:${Account}:trail/${TrailName}" ] } SCP-AMS-013: Prevent disabling default EBS encryption Prevent disabling of default Amazon EBS encryption. { "Effect": "Deny", "Action": [ "ec2:DisableEbsEncryptionByDefault" ], "Resource": "*" } SCP-AMS-014: Prevent creating default VPC and subnet Prevent the creation of a default Amazon VPC and subnets. { Infrastructure security Version May 08, 2025 757 AMS Advanced User Guide AMS Advanced Concepts and Procedures "Effect": "Deny", "Action": [ "ec2:CreateDefaultSubnet", "ec2:CreateDefaultVpc" ], "Resource": "*" } SCP-AMS-015: Prevent disabling and modifying GuardDuty Prevent Amazon GuardDuty from being modified or disabled. { "Effect": "Deny", "Action": [ "guardduty:AcceptInvitation", "guardduty:ArchiveFindings", "guardduty:CreateDetector", "guardduty:CreateFilter", "guardduty:CreateIPSet", "guardduty:CreateMembers", "guardduty:CreatePublishingDestination", "guardduty:CreateSampleFindings", "guardduty:CreateThreatIntelSet", "guardduty:DeclineInvitations", "guardduty:DeleteDetector", "guardduty:DeleteFilter", "guardduty:DeleteInvitations", "guardduty:DeleteIPSet", "guardduty:DeleteMembers", "guardduty:DeletePublishingDestination", "guardduty:DeleteThreatIntelSet", "guardduty:DisableOrganizationAdminAccount", "guardduty:DisassociateFromMasterAccount", "guardduty:DisassociateMembers", "guardduty:InviteMembers", "guardduty:StartMonitoringMembers", "guardduty:StopMonitoringMembers", "guardduty:TagResource", "guardduty:UnarchiveFindings", "guardduty:UntagResource", "guardduty:UpdateDetector", "guardduty:UpdateFilter", "guardduty:UpdateFindingsFeedback", Infrastructure security Version May 08, 2025 758 AMS Advanced User Guide AMS Advanced Concepts and Procedures "guardduty:UpdateIPSet", "guardduty:UpdateMalwareScanSettings", "guardduty:UpdateMemberDetectors", "guardduty:UpdateOrganizationConfiguration", "guardduty:UpdatePublishingDestination", "guardduty:UpdateThreatIntelSet" ], "Resource": "*" } SCP-AMS-016: Prevent root user activity Prevent the root user from performing any action. { "Action": "*", "Resource": "*", "Effect": "Deny", "Condition": { "StringLike": { "aws:PrincipalArn": [ "arn:aws:iam::*:root" ] } } } SCP-AMS-017: Prevent creating access keys for the root user Prevent the creation of access keys for the root user. { "Effect": "Deny", "Action": "iam:CreateAccessKey", "Resource": "arn:aws:iam::*:root" } SCP-AMS-018: Prevent disabling S3 account public access block Prevent disabling an Amazon S3 account public access block. This prevents any bucket in the account from becoming public. { Infrastructure security Version May 08, 2025 759 AMS Advanced User Guide "Effect": "Deny", "Action": "s3:PutAccountPublicAccessBlock", "Resource": "*" } AMS Advanced Concepts and Procedures SCP-AMS-019: Prevent disabling AWS Config or modifying Config rules Prevent disabling or modifying AWS Config rules. { "Effect": "Deny", "Action": [ "config:DeleteConfigRule", "config:DeleteConfigurationRecorder", "config:DeleteDeliveryChannel", "config:DeleteEvaluationResults", "config:StopConfigurationRecorder" ], "Resource": "*" } SCP-AMS-020: Prevent all IAM actions Prevent all IAM actions. { "Effect": "Deny", "Action": [ "iam:*" ], "Resource": "*" } SCP-AMS-021: Prevent deleting CloudWatch Logs groups and streams Prevent deleting Amazon CloudWatch Logs groups and streams. { "Effect": "Deny", "Action": [ "logs:DeleteLogGroup", "logs:DeleteLogStream" Infrastructure security Version May 08, 2025 760 AMS Advanced Concepts and Procedures AMS Advanced User Guide ], "Resource": "*" } SCP-AMS-022: Prevent Glacier deletion Prevent Amazon S3 Glacier deletion. { "Effect": "Deny", "Action": [ "glacier:DeleteArchive", |
ams-ug-266 | ams-ug.pdf | 266 | Config rules Prevent disabling or modifying AWS Config rules. { "Effect": "Deny", "Action": [ "config:DeleteConfigRule", "config:DeleteConfigurationRecorder", "config:DeleteDeliveryChannel", "config:DeleteEvaluationResults", "config:StopConfigurationRecorder" ], "Resource": "*" } SCP-AMS-020: Prevent all IAM actions Prevent all IAM actions. { "Effect": "Deny", "Action": [ "iam:*" ], "Resource": "*" } SCP-AMS-021: Prevent deleting CloudWatch Logs groups and streams Prevent deleting Amazon CloudWatch Logs groups and streams. { "Effect": "Deny", "Action": [ "logs:DeleteLogGroup", "logs:DeleteLogStream" Infrastructure security Version May 08, 2025 760 AMS Advanced Concepts and Procedures AMS Advanced User Guide ], "Resource": "*" } SCP-AMS-022: Prevent Glacier deletion Prevent Amazon S3 Glacier deletion. { "Effect": "Deny", "Action": [ "glacier:DeleteArchive", "glacier:DeleteVault" ], "Resource": "*" } SCP-AMS-023: Prevent deletion of IAM Access Analyzer Prevent the deletion of IAM Access Analyzer. { "Action": [ "access-analyzer:DeleteAnalyzer" ], "Resource": "*", "Effect": "Deny" } SCP-AMS-024: Prevent modifications to Security Hub Prevent the deletion of AWS Security Hub. { "Action": [ "securityhub:DeleteInvitations", "securityhub:DisableSecurityHub", "securityhub:DisassociateFromMasterAccount", "securityhub:DeleteMembers", "securityhub:DisassociateMembers" ], "Resource": "*", "Effect": "Deny" Infrastructure security Version May 08, 2025 761 AMS Advanced User Guide } AMS Advanced Concepts and Procedures SCP-AMS-025: Prevent deletion under Directory Service Prevent the deletion of resources under AWS Directory Service. { "Action": [ "ds:DeleteDirectory", "ds:DeleteLogSubscription", "ds:DeleteSnapshot", "ds:DeleteTrust", "ds:DeregisterCertificate", "ds:DeregisterEventTopic", "ds:DisableLDAPS", "ds:DisableRadius", "ds:DisableSso", "ds:UnshareDirectory" ], "Resource": "*", "Effect": "Deny" } SCP-AMS-026: Prevent use of denylisted service Prevent the use of denylisted services. Note Replace service1 and service2 with your service names. Example access-analyzer or IAM. { "Effect": "Deny", "Resource": "*", "Action": ["service1:*", "service2:*"] } SCP-AMS-027: Prevent use of denylisted service in specific Regions Prevent the use of denylisted services in specific AWS Regions. Infrastructure security Version May 08, 2025 762 AMS Advanced User Guide AMS Advanced Concepts and Procedures Note Replace service1 and service2 with your service names. Example access-analyzer or IAM. Replace region1 and region2 with your service names. Example us-west-2 or use- east-1. { "Effect": "Deny", "Resource": "*", "Action": ["service1:*", "service2:*"], "Condition": { "StringEquals": { "aws:RequestedRegion": [ "region1", "region2" ] } } } SCP-AMS-028: Prevent tags from being modified except by authorized principals Prevent tag modifications by any user except the authorized principals. Use authorization tags to authorize principals. Authorization tags must be associated with resources and with principals. A user/role is only considered authorized if the tag on both the resource and the principal match. For more information, see the following resources: • Securing resource tags used for authorization using a service control policy in AWS Organizations • Prevent tags from being modified except by authorized principals { "Effect": "Deny", "Action": [ "ec2:CreateTags", "ec2:DeleteTags" ], "Resource": [ Infrastructure security Version May 08, 2025 763 AMS Advanced User Guide "*" ], "Condition": { "StringNotEquals": { AMS Advanced Concepts and Procedures "ec2:ResourceTag/access-project": "${aws:PrincipalTag/access-project}", "aws:PrincipalArn": "arn:aws:iam::{ACCOUNT_ID}:{RESOURCE_TYPE}/{RESOURCE_NAME}" }, "Null": { "ec2:ResourceTag/access-project": false } } }, { "Effect": "Deny", "Action": [ "ec2:CreateTags", "ec2:DeleteTags" ], "Resource": [ "*" ], "Condition": { "StringNotEquals": { "aws:RequestTag/access-project": "${aws:PrincipalTag/access-project}", "aws:PrincipalArn": "arn:aws:iam::{ACCOUNT_ID}:{RESOURCE_TYPE}/{RESOURCE_NAME}" }, "ForAnyValue:StringEquals": { "aws:TagKeys": [ "access-project" ] } } }, { "Effect": "Deny", "Action": [ "ec2:CreateTags", "ec2:DeleteTags" ], "Resource": [ "*" ], "Condition": { "StringNotEquals": { Infrastructure security Version May 08, 2025 764 AMS Advanced User Guide AMS Advanced Concepts and Procedures "aws:PrincipalArn": "arn:aws:iam::{ACCOUNT_ID}:{RESOURCE_TYPE}/{RESOURCE_NAME}" }, "Null": { "aws:PrincipalTag/access-project": true } } } SCP-AMS-029: Prevent users from deleting Amazon VPC Flow Logs Prevent the deletion of Amazon VPC Flow Logs. { "Action": [ "ec2:DeleteFlowLogs", "logs:DeleteLogGroup", "logs:DeleteLogStream", "s3:DeleteBucket", "s3:DeleteObject", "s3:DeleteObjectVersion", "s3:PutLifecycleConfiguration", "firehose:DeleteDeliveryStream" ], "Resource": "*", "Effect": "Deny" } SCP-AMS-030: Prevent sharing VPC subnet with account other than network account Prevent sharing Amazon VPC subnets with accounts other than the network account. Note Replace NETWORK_ACCOUNT_ID with your network account ID. { "Effect": "Deny", "Action": [ "ram:AssociateResourceShare", "ram:CreateResourceShare" ], Infrastructure security Version May 08, 2025 765 AMS Advanced User Guide AMS Advanced Concepts and Procedures "Resource": "*", "Condition": { "StringNotEquals": { "ram:Principal": "NETWORK_ACCOUNT_ID" }, "StringEquals": { "ram:RequestedResourceType": "ec2:Subnet" } } } SCP-AMS-031: Prevent launching instances with prohibited instance types Prevent launcing prohibited Amazon EC2 instance types. Note Replace instance_type1 and instance_type2 with the instance types that you want to restrict, such as t2.micro or a wildcard string such as *.nano. { "Effect": "Deny", "Action": "ec2:RunInstances", "Resource": [ "arn:aws:ec2:*:*:instance/*" ], "Condition": { "ForAnyValue:StringLike": { "ec2:InstanceType": [ "instance_type1", "instance_type2" ] } } } SCP-AMS-032: Prevent launching instances without IMDSv2 Prevent Amazon EC2 instances without IMDSv2. [ Infrastructure security Version May 08, 2025 766 AMS Advanced Concepts and Procedures AMS Advanced User Guide { "Effect": "Deny", "Action": "ec2:RunInstances", "Resource": "arn:aws:ec2:*:*:instance/*", "Condition": { "StringNotEquals": { "ec2:MetadataHttpTokens": "required" } } }, { "Effect": "Deny", "Action": "ec2:RunInstances", "Resource": "arn:aws:ec2:*:*:instance/*", "Condition": { "NumericGreaterThan": { "ec2:MetadataHttpPutResponseHopLimit": "3" } } }, { "Effect": "Deny", "Action": "*", "Resource": "*", "Condition": { "NumericLessThan": { "ec2:RoleDelivery": "2.0" } } }, { "Effect": "Deny", "Action": "ec2:ModifyInstanceMetadataOptions", "Resource": "*" } ] SCP-AMS-033: Prevent modifications to specific IAM role Prevent modifications to specified IAM roles. { "Action": [ "iam:AttachRolePolicy", Infrastructure security Version May 08, 2025 767 AMS Advanced Concepts |
ams-ug-267 | ams-ug.pdf | 267 | Infrastructure security Version May 08, 2025 766 AMS Advanced Concepts and Procedures AMS Advanced User Guide { "Effect": "Deny", "Action": "ec2:RunInstances", "Resource": "arn:aws:ec2:*:*:instance/*", "Condition": { "StringNotEquals": { "ec2:MetadataHttpTokens": "required" } } }, { "Effect": "Deny", "Action": "ec2:RunInstances", "Resource": "arn:aws:ec2:*:*:instance/*", "Condition": { "NumericGreaterThan": { "ec2:MetadataHttpPutResponseHopLimit": "3" } } }, { "Effect": "Deny", "Action": "*", "Resource": "*", "Condition": { "NumericLessThan": { "ec2:RoleDelivery": "2.0" } } }, { "Effect": "Deny", "Action": "ec2:ModifyInstanceMetadataOptions", "Resource": "*" } ] SCP-AMS-033: Prevent modifications to specific IAM role Prevent modifications to specified IAM roles. { "Action": [ "iam:AttachRolePolicy", Infrastructure security Version May 08, 2025 767 AMS Advanced Concepts and Procedures AMS Advanced User Guide "iam:DeleteRole", "iam:DeleteRolePermissionsBoundary", "iam:DeleteRolePolicy", "iam:DetachRolePolicy", "iam:PutRolePermissionsBoundary", "iam:PutRolePolicy", "iam:TagRole", "iam:UntagRole", "iam:UpdateAssumeRolePolicy", "iam:UpdateRole", "iam:UpdateRoleDescription" ], "Resource": [ "arn:aws:iam::{ACCOUNT_ID}:role/{RESOURCE_NAME}" ], "Effect": "Deny" } SCP-AMS-034: Prevent AssumeRolePolicy modification on specific IAM roles Prevent modifications to the AssumeRolePolicy for specified IAM roles. { "Action": [ "iam:UpdateAssumeRolePolicy" ], "Resource": [ "arn:aws:iam::{ACCOUNT_ID}:role/{RESOURCE_NAME}" ], "Effect": "Deny" } ConfigRule: Required tags Check whether EC2 instances have custom tags that you have required. In addition to InfoSec, this is also useful for your Cost Management ConfigRuleName: required-tags Description: >- A Config rule that checks whether EC2 instances have the required tags. Scope: ComplianceResourceTypes: - 'AWS::EC2::Instance' Infrastructure security Version May 08, 2025 768 AMS Advanced User Guide AMS Advanced Concepts and Procedures InputParameters: tag1Key: COST_CENTER tag2Key: APP_ID Source: Owner: AWS SourceIdentifier: REQUIRED_TAGS ConfigRule: Access key rotated Check that access keys are being rotated within the specified time period. This is usually set to be 90 days per typical compliance requirements. ConfigRuleName: access-keys-rotated Description: >- A config rule that checks whether the active access keys are rotated within the number of days specified in maxAccessKeyAge. The rule is NON_COMPLIANT if the access keys have not been rotated for more than maxAccessKeyAge number of days. InputParameters: maxAccessKeyAge: '90' Source: Owner: AWS SourceIdentifier: ACCESS_KEYS_ROTATED MaximumExecutionFrequency: TwentyFour_Hours ConfigRule: IAM root access key in AMS Check that a root access key is not present on an account. For AMS Advanced accounts, this is expected to be compliant out-of-the-box. ConfigRuleName: iam-root-access-key-check Description: >- A config rule that checks whether the root user access key is available. The rule is COMPLIANT if the user access key does not exist. Source: Owner: AWS SourceIdentifier: IAM_ROOT_ACCESS_KEY_CHECK MaximumExecutionFrequency: TwentyFour_Hours ConfigRule: SSM managed EC2 Check that your EC2s are being managed by SSM Systems Manager. Infrastructure security Version May 08, 2025 769 AMS Advanced User Guide AMS Advanced Concepts and Procedures ConfigRuleName: ec2-instance-managed-by-systems-manager Description: >- A Config rule that checks whether the EC2 instances in the account are managed by AWS Systems Manager. Scope: ComplianceResourceTypes: - 'AWS::EC2::Instance' - 'AWS::SSM::ManagedInstanceInventory' Source: Owner: AWS SourceIdentifier: EC2_INSTANCE_MANAGED_BY_SSM ConfigRule: Unused IAM user in AMS Check for IAM user credentials that have not been used for a specified duration. Like the key- rotation check, this usually defaults to 90 days per typical compliance requirements. ConfigRuleName: iam-user-unused-credentials-check Description: >- A config rule that checks whether IAM users have passwords or active access keys that have not been used within the specified number of days provided. InputParameters: maxCredentialUsageAge: '90' Source: Owner: AWS SourceIdentifier: IAM_USER_UNUSED_CREDENTIALS_CHECK MaximumExecutionFrequency: TwentyFour_Hours ConfigRule: S3 bucket logging Check that logging has been enabled for S3 buckets in the account. ConfigRuleName: s3-bucket-logging-enabled Description: >- A Config rule that checks whether logging is enabled for S3 buckets. Scope: ComplianceResourceTypes: - 'AWS::S3::Bucket' Source: Owner: AWS SourceIdentifier: S3_BUCKET_LOGGING_ENABLED Infrastructure security Version May 08, 2025 770 AMS Advanced User Guide AMS Advanced Concepts and Procedures ConfigRule: S3 bucket versioning Check that versioning and MFA-delete (optional) is enabled on all S3 buckets ConfigRuleName: s3-bucket-versioning-enabled Description: >- A Config rule that checks whether versioning is enabled for S3 buckets. Optionally, the rule checks if MFA delete is enabled for S3 buckets. Scope: ComplianceResourceTypes: - 'AWS::S3::Bucket' Source: Owner: AWS SourceIdentifier: S3_BUCKET_VERSIONING_ENABLED ConfigRule: S3 public access Check that public access settings (Public ACL, Public Policy, Public Buckets) are restricted across the account ConfigRuleName: s3-account-level-public-access-blocks Description: >- A Config rule that checks whether the required public access block settings are configured from account level. The rule is only NON_COMPLIANT when the fields set below do not match the corresponding fields in the configuration item. Scope: ComplianceResourceTypes: - 'AWS::S3::AccountPublicAccessBlock' InputParameters: IgnorePublicAcls: 'True' BlockPublicPolicy: 'True' BlockPublicAcls: 'True' RestrictPublicBuckets: 'True' Source: Owner: AWS SourceIdentifier: S3_ACCOUNT_LEVEL_PUBLIC_ACCESS_BLOCKS ConfigRule: Non-archived GuardDuty findings Check for any non-archived GuardDuty findings that are older than the specified duration. The default duration is 30 days for low-sev, 7 days for medium-sev and 1 day for high-sev findings. Infrastructure security Version May 08, 2025 771 AMS Advanced User Guide AMS Advanced Concepts and Procedures ConfigRuleName: guardduty-non-archived-findings Description: >- A Config rule that checks whether the Amazon GuardDuty has findings that are non archived. The rule is NON_COMPLIANT if GuardDuty has non archived low/medium/high severity findings older than the specified number. InputParameters: daysLowSev: '30' daysMediumSev: '7' daysHighSev: '1' Source: Owner: AWS SourceIdentifier: GUARDDUTY_NON_ARCHIVED_FINDINGS |
ams-ug-268 | ams-ug.pdf | 268 | S3_ACCOUNT_LEVEL_PUBLIC_ACCESS_BLOCKS ConfigRule: Non-archived GuardDuty findings Check for any non-archived GuardDuty findings that are older than the specified duration. The default duration is 30 days for low-sev, 7 days for medium-sev and 1 day for high-sev findings. Infrastructure security Version May 08, 2025 771 AMS Advanced User Guide AMS Advanced Concepts and Procedures ConfigRuleName: guardduty-non-archived-findings Description: >- A Config rule that checks whether the Amazon GuardDuty has findings that are non archived. The rule is NON_COMPLIANT if GuardDuty has non archived low/medium/high severity findings older than the specified number. InputParameters: daysLowSev: '30' daysMediumSev: '7' daysHighSev: '1' Source: Owner: AWS SourceIdentifier: GUARDDUTY_NON_ARCHIVED_FINDINGS MaximumExecutionFrequency: TwentyFour_Hours ConfigRule: CMK deletion Check for any AWS Key Management Service custom master keys (CMKs) that are scheduled (aka pending) for deletion. This is crucial as unawareness around CMK deletion can lead to data being unrecoverable ConfigRuleName: kms-cmk-not-scheduled-for-deletion Description: >- A config rule that checks whether customer master keys (CMKs) are not scheduled for deletion in AWS Key Management Service (AWS KMS). The rule is NON_COMPLIANT if CMKs are scheduled for deletion. Source: Owner: AWS SourceIdentifier: KMS_CMK_NOT_SCHEDULED_FOR_DELETION MaximumExecutionFrequency: TwentyFour_Hours ConfigRule: CMK rotation Check that auto-rotation is enabled for every CMK in the account ConfigRuleName: cmk-backing-key-rotation-enabled Description: >- A config rule that checks that key rotation is enabled for each customer master key (CMK). The rule is COMPLIANT, if the key rotation is enabled for specific key object. The rule is not applicable to CMKs that have imported key material. Source: Owner: AWS Infrastructure security Version May 08, 2025 772 AMS Advanced User Guide AMS Advanced Concepts and Procedures SourceIdentifier: CMK_BACKING_KEY_ROTATION_ENABLED MaximumExecutionFrequency: TwentyFour_Hours Custom notification for Config rules There can be occurrences of critical non-compliant Config Rules that require raising escalated awareness directly with the your InfoSec and Leadership teams. For such scenarios, AMS recommends that you configure a non-compliance event-driven custom notification. For example: ConfigRuleName: required-tags Description: >- A Config rule that checks whether EC2 instances have the mandated tags. Scope: ComplianceResourceTypes: - 'AWS::EC2::Instance' InputParameters: tag1Key: COST_CENTER tag2Key: APP_ID Source: Owner: AWS SourceIdentifier: REQUIRED_TAGS NotificationEventRule: Type: 'AWS::Events::Rule' Properties: Name: CWEventForrequired-tags Description: >- SNS Notification for Non-Compliant Events of Config Rule: required-tags State: ENABLED EventPattern: detail-type: - Config Rules Compliance Change source: - aws.config detail: newEvaluationResult: complianceType: - NON_COMPLIANT configRuleARN: - 'Fn::GetAtt': - RequiredEC2Tags Infrastructure security Version May 08, 2025 773 AMS Advanced User Guide AMS Advanced Concepts and Procedures - Arn Targets: - Id: RemediationNotification Arn: Ref: SnsTopic InputTransformer: InputTemplate: >- "EC2 Instance <Instance_ID> is non-compliant. Please add required tags: COST_CENTER, APP_ID, Name, and Backup." InputPathsMap: instance_id: $.detail.resourceId SnsTopic: Type: 'AWS::SNS::Topic' Properties: Subscription: - Endpoint: Cloud_Ops_Leaders@customer.com Protocol: email TopicName: noncompliant-instance-notification SnsTopicPolicy: Type: 'AWS::SNS::TopicPolicy' Properties: PolicyDocument: Statement: - Sid: __default_statement_ID Effect: Allow Principal: AWS: '*' Action: - 'SNS:GetTopicAttributes' - 'SNS:SetTopicAttributes' - 'SNS:AddPermission' - 'SNS:RemovePermission' - 'SNS:DeleteTopic' - 'SNS:Subscribe' - 'SNS:ListSubscriptionsByTopic' - 'SNS:Publish' - 'SNS:Receive' Resource: Ref: SnsTopic Condition: StringEquals: 'AWS:SourceOwner': Ref: 'AWS::AccountId' - Sid: TrustCWEToPublishEventsToMyTopic Infrastructure security Version May 08, 2025 774 AMS Advanced User Guide AMS Advanced Concepts and Procedures Effect: Allow Principal: Service: events.amazonaws.com Action: 'sns:Publish' Resource: Ref: SnsTopic Topics: - Ref: SnsTopic Amazon EventBridge rule service-linked role for AMS Advanced AMS Advanced uses the service-linked role (SLR) named AWSServiceRoleForManagedServices_Events – This role trusts one of the AWS Managed Services service principals (events.managedservices.amazonaws.com) to assume the role for you. The service uses the role to create EventBridge managed rule. This rule is the infrastructure required in your AWS account to deliver alarm state change information from your account to AWS Managed Services. Permissions for EventBridge SLR for AMS Advanced The AWSServiceRoleForManagedServices_Events service-linked role trusts the following services to assume the role: • events.managedservices.amazonaws.com Attached to this role is the AWSManagedServices_EventsServiceRolePolicy AWS managed policy (see AWS managed policy: AWSManagedServices_EventsServiceRolePolicy). The service uses the role to deliver alarm state change information from your account to AWS Managed Services. You must configure permissions to allow an IAM entity (such as a user, group, or role) to create, edit, or delete a service-linked role. For more information, see Service-Linked Role Permissions in the AWS Identity and Access Management User Guide. You can download the JSON AWSManagedServices_EventsServiceRolePolicy in this ZIP: EventsServiceRolePolicy.zip. Creating an EventBridge SLR for AMS Advanced You don't need to manually create a service-linked role. When you Onboard to AMS in the AWS Management Console, the AWS CLI, or the AWS API, then AMS Advanced creates the service-linked role for you. Infrastructure security Version May 08, 2025 775 AMS Advanced User Guide AMS Advanced Concepts and Procedures Important This service-linked role can appear in your account if you were using the AMS Advanced service before February 7, 2023, when it began supporting service-linked roles then AMS Accelerate created the AWSServiceRoleForManagedServices_Events role in your account. To learn more, see A new role appeared in my IAM account. If you delete this service-linked role, and then need to create it again, you can |
ams-ug-269 | ams-ug.pdf | 269 | the AWS Management Console, the AWS CLI, or the AWS API, then AMS Advanced creates the service-linked role for you. Infrastructure security Version May 08, 2025 775 AMS Advanced User Guide AMS Advanced Concepts and Procedures Important This service-linked role can appear in your account if you were using the AMS Advanced service before February 7, 2023, when it began supporting service-linked roles then AMS Accelerate created the AWSServiceRoleForManagedServices_Events role in your account. To learn more, see A new role appeared in my IAM account. If you delete this service-linked role, and then need to create it again, you can use the same process to recreate the role in your account. When you Onboard to AMS, AMS Advanced creates the service-linked role for you again. Editing an EventBridge SLR for AMS Advanced AMS Advanced does not allow you to edit the AWSServiceRoleForManagedServices_Events service- linked role. After you create a service-linked role, you cannot change the name of the role because various entities might reference the role. However, you can edit the description of the role using IAM. For more information, see Editing a service-linked role in the IAM User Guide. Deleting an EventBridge SLR for AMS Advanced You don't need to manually delete the AWSServiceRoleForManagedServices_Events role. When you Offboard from AMS in the AWS Management Console, the AWS CLI or the AWS API, AMS Advanced cleans up the resources and deletes the service-linked role for you. You can also use the IAM console, the AWS CLI or the AWS API to manually delete the service- linked role. To do this, you must first manually clean up the resources for your service-linked role and then you can manually delete it. Note If the AMS Advanced service is using the role when you try to delete the resources, then the deletion might fail. If that happens, wait for a few minutes and try the operation again. To delete AMS Advanced resources used by the AWSServiceRoleForManagedServices_Events service-linked role To manually delete the service-linked role using IAM Infrastructure security Version May 08, 2025 776 AMS Advanced User Guide AMS Advanced Concepts and Procedures Use the IAM console, the AWS CLI, or the AWS API to delete the AWSServiceRoleForManagedServices_Events service-linked role. For more information, see Deleting a service-linked role in the IAM User Guide. Security best practices This section has been redacted because it contains sensitive AMS security-related information. This information is available through the AMS console Documentation. To access AWS Artifact, you can contact your CSDM for instructions or go to Getting Started with AWS Artifact. AMS multi-account landing zone EPS non-default settings This section has been redacted because it contains sensitive AMS security-related information. This information is available through the AMS console Documentation. To access AWS Artifact, you can contact your CSDM for instructions or go to Getting Started with AWS Artifact. AMS Guardrails A guardrail is a high-level rule that provides ongoing governance for your overall AMS environment. This section has been redacted because it contains sensitive AMS security-related information. This information is available through the AMS console Documentation. To access AWS Artifact, you can contact your CSDM for instructions or go to Getting Started with AWS Artifact. MALZ Service control policies This section has been redacted because it contains sensitive AMS security-related information. This information is available through the AMS console Documentation. To access AWS Artifact, you can contact your CSDM for instructions or go to Getting Started with AWS Artifact. Security Incident Response in AMS Security is the top priority at AWS Managed Services (AMS). AMS deploys resources and controls in your accounts to manage them. AWS has a shared responsibility model: AWS manages the security of the cloud, and you are responsible for security in the cloud. AMS protects your data and assets and helps keep your AWS infrastructure secure by using security controls and active monitoring for security issues. These capabilities help you establish a security baseline for applications running in Security best practices Version May 08, 2025 777 AMS Advanced User Guide AMS Advanced Concepts and Procedures the AWS Cloud. AMS collaborates with you through Security Incident Response to assess the effect, and then carry out containment and remediations based on best practice recommendations. When a deviation from the baseline occurs, such as by a misconfiguration or a change in external factors, you need to respond and investigate. To successfully do so, you need to understand the basic concepts of Security Incident Response within your AMS environment. You must also understand the requirements to prepare, educate, and train cloud teams before security issues occur. It is important to know the controls and capabilities that you can use, prepare response plans for common security issues such as a user account compromise or a misuse of privileged accounts, and identify remediation methods that use automation to improve response speed |
ams-ug-270 | ams-ug.pdf | 270 | from the baseline occurs, such as by a misconfiguration or a change in external factors, you need to respond and investigate. To successfully do so, you need to understand the basic concepts of Security Incident Response within your AMS environment. You must also understand the requirements to prepare, educate, and train cloud teams before security issues occur. It is important to know the controls and capabilities that you can use, prepare response plans for common security issues such as a user account compromise or a misuse of privileged accounts, and identify remediation methods that use automation to improve response speed and consistency. Additionally, you need to understand your compliance and regulatory requirements as they relate to building a Security Incident Response program to fulfill those requirements. Security Incident Response can be complex, but by implementing an iterative approach you can simplify the process and allow the incident response team to keep asset stakeholders satisfied by providing early and continuous detection and response. In this guide, we provide you with the methodology that AMS uses for incident response, the AMS responsibility matrix (RACI), how you can be prepared for a security event, how to engage AMS during security incidents, and some of the incident response runbooks that AMS uses. How AMS Security Incident Response works AWS Managed Services aligns to the NIST 800-61 Computer Security Incident Handling Guide for Security Incident Response. By aligning to this industry standard, we provide a consistent approach to security event management and adhere to best practices in securing and responding to security incidents in your cloud. Incident response lifecycle When detection identifies and generates a security alert, or you request security assistance, the AWS Managed Services Operations team makes sure that there is a timely investigation, executes automations to perform data collection, triages and analyzes, informs you of the analysis, performs investigation and any containment activities, and then posts event analysis. How it works Version May 08, 2025 778 AMS Advanced User Guide AMS Advanced Concepts and Procedures The data collection, triage, analysis, and containment activities performed during the incident response vary depending on the type of security event being investigated. Example Security Incident Response workflows for select scenarios are at the end of this document. During incidents, AMS determines the correct course of action dynamically, which might result in documented steps being re-ordered or bypassed as appropriate to make sure that the right outcome occurs. Prepare As the threat landscape evolves, AMS continues to expand detection and response capabilities. As new detections are added, AMS incorporates the alerts from these new detections into the detection and response platform. AMS security responders are trained to investigate and partner with you throughout the Security Incident Response lifecycle. Because of this partnership approach, it's important that your security and application teams are prepared to engage with AMS to handle security events as these events occur. This documentation explains what to expect during a security event and helps you prepare for rapid response when a security incident occurs. This documentation uses the NIST 800-61 definition of an event as any observable occurrence in a system or network and an incident as a violation or imminent threat of violation of policies, acceptable use policies, or standard security practices. Preparation checklist Work through the following checklist with your AMS cloud solution delivery manager (CSDM) and AMS cloud architect (CA): • Understand what workloads are running in which accounts. • Understand what internal teams are responsible for the various workloads and tag them appropriately in the workloads. • Maintain contact details internally for other teams who might be required during a security event investigation and for containment decisions. • Confirm that security contacts are up to date and added to all managed AWS accounts. The contacts are managed on a per account basis. • Know how to raise security incident to AMS, and be familiar with the severity and expected response times. Prepare Version May 08, 2025 779 AMS Advanced User Guide AMS Advanced Concepts and Procedures • Make sure that when security notifications are received, they are routed to the appropriate people and systems such as pagers or your security operations center. • Understand what log sources are available to you, where these are stored in your accounts and who has access to them. • Understand how to use CloudWatch Insights to Query Logs during investigations. • Understand the containment options available to you by resource (EC2, IAM, S3, and son on) and the consequences on your workload availability when in containment. Detect During the management of your AWS accounts, AMS monitors for anomalies in user behavior, account activities and potential security events using data collected from detection sources and controls including but not limited to Amazon CloudWatch, Amazon GuardDuty, VPC Flow Logs, Amazon Macie, AWS Config and Amazon internal |
ams-ug-271 | ams-ug.pdf | 271 | you, where these are stored in your accounts and who has access to them. • Understand how to use CloudWatch Insights to Query Logs during investigations. • Understand the containment options available to you by resource (EC2, IAM, S3, and son on) and the consequences on your workload availability when in containment. Detect During the management of your AWS accounts, AMS monitors for anomalies in user behavior, account activities and potential security events using data collected from detection sources and controls including but not limited to Amazon CloudWatch, Amazon GuardDuty, VPC Flow Logs, Amazon Macie, AWS Config and Amazon internal Threat Intelligence feeds. AMS uses both native AWS services and other detection technologies to respond to security events created by: • Config Conformance Finding Types • GuardDuty Finding Types • Macie Finding Types • Amazon Route 53 Resolver DNS Firewall Events • AMS Security events (cloud watch alarms) Additional findings are added as services, products and threat ecosystems evolves. Report security events to AMS Raise an incident through the AMS Support Portal or Support Center to notify AMS of a security incident or to request investigations. Analyze After a security event is identified and reported, the next step is to analyze whether the reported event is a false positive or a real incident. AMS uses automation and manual investigative techniques to handle security events. The analysis includes investigation of logs from different Detect Version May 08, 2025 780 AMS Advanced User Guide AMS Advanced Concepts and Procedures detection sources such as network traffic logs, host logs,CloudTrail events, AWS service logs and so on. The analysis also looks for patterns that show an anomalous behavior by correlation. Your partnership is required to understand context specific to the account environment and to establish what is normal for your account and workloads. This helps AMS identify an anomaly faster and to an accelerated incident response. Handle communications from AMS about security events AMS keeps you informed during the investigation by engaging your security contacts through an incident ticket. Your AMS cloud service delivery manager (CSDM) and AMS cloud architect (CA) are the point of contacts to reach out to for any communication during an active security investigation. Communication includes automated notification when a security alert is generated, communication after event analysis, establishing call bridges and the ongoing delivery of artifacts such as log files, snapshot of infected resources, and getting investigation results to you during the security event. Standard fields included in AMS security alert notifications are listed below. These fields provide you with information so that you can route events to the appropriate teams within your organization for remediation. • Finding Type • Finding Identifier (Where relevant) • Finding Severity • Finding Description • Finding created Date & Time • AWS Account Id • Region (Where relevant) • AWS Resources (IAM user/role/policy, EC2, S3, EKS) Additional fields are provided depending on the Finding Type, for example EKS Findings include Pod, Container, and Cluster details. Contain AMS's approach to containment is partnership with you. You understand your business and the workload impacts that might occur from containment activities, such as network isolation, IAM user or role de-provisioning, instance re-building, and so forth. Contain Version May 08, 2025 781 AMS Advanced User Guide AMS Advanced Concepts and Procedures An essential part of containment is decision-making. For example, shut down a system, isolate a resource from the network, or turn off access or end sessions. These decisions are easier to make if there are predetermined strategies and procedures to contain the incident. AMS provides the containment strategy and then implements the solution after you have considered the risk involved with implementing the containment actions. There are different containment options depending on the resources under analysis. AMS expects multiple types of containment to be simultaneously deployed during an incident investigation. Some of these examples include: • Apply protection rules to block unauthorized traffic (Security group, NACL, WAF Rules, SCP rules, Deny listing, setting signature action to quarantine or block) • Resource Isolation • Network Isolation • Disabling IAM users, roles and policies • Modifying/Reducing IAM user, role privilege • Terminating / Suspending / Deleting compute resources • Restricting public access from affected resource • Rotating access keys, API keys, and passwords • Scrubbing disclosed credentials and sensitive information AMS encourages you to consider the type of containment strategies for each major incident type that is within their risk appetite, with criteria clearly documented to help with decision making in the event of an incident. Criteria to determine the appropriate strategy include: • Potential damage to resources • Preservation of evidence • Service unavailability (for example, network connectivity, services provided to external parties) • Time and resources needed to implement the strategy • Effectiveness of the strategy (For example, partial containment, full containment) • Permanence of the |
ams-ug-272 | ams-ug.pdf | 272 | keys, API keys, and passwords • Scrubbing disclosed credentials and sensitive information AMS encourages you to consider the type of containment strategies for each major incident type that is within their risk appetite, with criteria clearly documented to help with decision making in the event of an incident. Criteria to determine the appropriate strategy include: • Potential damage to resources • Preservation of evidence • Service unavailability (for example, network connectivity, services provided to external parties) • Time and resources needed to implement the strategy • Effectiveness of the strategy (For example, partial containment, full containment) • Permanence of the solution (For example, one-way door vs two-way door decisions) • Duration of the solution (For example, emergency workaround to be removed in four hours, temporary workaround to be removed in two weeks, permanent solution). Contain Version May 08, 2025 782 AMS Advanced User Guide AMS Advanced Concepts and Procedures • Apply security controls that you can turn on to lower the risk and allow time to define and implement a more effective containment. The speed of containment is critical, AMS advises a staged approach to achieve efficient and effective containment by strategizing short-term and long-term approaches. Use this guide to consider your containment strategy that involves different techniques based on the resource type. • Containment Strategy • Can AMS identify the scope of the security incident? • If yes, identify all the resources (users, systems, resources). • If no, investigate in parallel with executing the next step on identified resources. • Can the resource be isolated? • If yes, then proceed to isolate the affected resources. • If no, then work with system owners and managers to determine further actions necessary to contain the problem. • Are all affected resources isolated from non-affected resources? • If yes, then continue to the next step. • If no, then continue to isolate affected resources until short-term containment is accomplished to prevent the incident from escalating further. • System Backup • Were backup copies of affected systems created for further analysis? • Are the forensic copies encrypted and stored in a secure location? • If yes, then continue to the next step. • If no, encrypt the forensic images, then store them in a secure location to prevent accidental usage, damage, and tampering. Eradicate After an incident is contained, eradication might be necessary to eliminate sources of threat altogether to secure the system before you proceed to the next recovery stage. Eradication steps might include deleting malware and removing compromised user accounts, as well as identifying and mitigating all vulnerabilities that were exploited. During eradication, it's important Eradicate Version May 08, 2025 783 AMS Advanced User Guide AMS Advanced Concepts and Procedures to identify all affected accounts, resources, and instances within the environment so that they can be remediated. It's a best practice that eradication and recovery is done in a phased approach so that remediation steps are prioritized. For large-scale incidents, recovery might take months. The intent of the early phases must be to increase the overall security with relatively quick (days to weeks) high value changes to prevent future incidents. The later phases must focus on longer-term changes (for example, infrastructure changes) and ongoing work to keep the enterprise as secure as possible. For some incidents, eradication is either not necessary or is performed during recovery. Consider the following: • Can the system be re-imaged and then hardened with patches or other countermeasures to prevent or reduce the risk of attacks? • Are all malware and other artifacts left behind by the attackers removed and the affected systems hardened against further attacks? Recover AMS partners with you to restore systems to normal operation, confirm that the systems are functioning normally, and (as applicable) remediate vulnerabilities to prevent similar incidents. Consider the following: • Are the affected system(s) patched and hardened against the recent attack and possible future attacks? • What day and time is feasible to restore the affected systems back into production? • What tools will you use to test, monitor, and verify that the systems that you restore to production aren't vulnerable to the initial attack techniques? Post Incident Report Post event, AMS runs an investigation review process for all security incidents. And, AMS initiates a correction of error (COE) process to address security incidents caused by a system or a procedural miss that plausibly has room for improvement. AMS partners with you to continuously-improve security investigation experience. The COE process helps AMS identify the contributing factors Recover Version May 08, 2025 784 AMS Advanced User Guide AMS Advanced Concepts and Procedures of customer-impacting events and connects those causes to next actions items that can prevent similar events from recurring, or helps mitigate the duration or level of impact. The investigation review process for security incidents addresses the following |
ams-ug-273 | ams-ug.pdf | 273 | all security incidents. And, AMS initiates a correction of error (COE) process to address security incidents caused by a system or a procedural miss that plausibly has room for improvement. AMS partners with you to continuously-improve security investigation experience. The COE process helps AMS identify the contributing factors Recover Version May 08, 2025 784 AMS Advanced User Guide AMS Advanced Concepts and Procedures of customer-impacting events and connects those causes to next actions items that can prevent similar events from recurring, or helps mitigate the duration or level of impact. The investigation review process for security incidents addresses the following items to identify opportunities for improvement: • What was the elapsed time from the beginning of the incident to incident discovery, to the initial impact assessment, and to each stage of the incident handling process (for example, containment, recovery)? • How long did it take the incident response team to respond to the initial report of the incident? • How long did it take to do an initial impact analysis? • Was this preventable and how? Is there a tool or process that could have prevented this? • Could we have detected this sooner and how? • What could have made the investigation go faster? • Were the documented Incident Response Procedures followed? Were they adequate? • Was the information sharing with other stakeholders done in a timely manner How could it be improved? • Was the collaboration with other teams (AWS Security, account teams, AWS Development team and customer security team's) effective? If not, what could be improved? • What preparation steps were missing that might have helped, escalation matrices, RACI’s, shared responsibility models, and so on? Is there a need to update any Runbooks? • What was the difference between the initial impact assessment and the final impact assessment? What can we do to improve accuracy of assessments earlier in the incident response? • What are the Action Items from the Lessons Learned? Security Incident Response Runbooks in AMS This section contains two runbooks: • Response to root user activity • Response to malware events Security Incident Response Runbooks Version May 08, 2025 785 AMS Advanced User Guide AMS Advanced Concepts and Procedures Response to root user activity The root user is the superuser within your AWS account. Note that AMS monitors root usage. It's a best practice to use the root user only for the few tasks that require it, such as to change your account settings, activate AWS Identity and Access Management (IAM) access to billing and cost management, change your root password, and turn on multi-factor authentication (MFA). For more information, see Tasks that require root user credentials. For more information on how to inform AMS of planned root usage, see When and how to use the root account in AMS. When root user activity is detected, either failed attempts to login that might indicate a brute force attack or activity in the account after a successful login, an event generates and an incident sent to your defined security contacts. AWS Managed Services Operations investigates unplanned root user activity, perform data collection, triage and analysis, and perform containment activities at your direction, followed by post event analysis. If you have the AMS Advanced operating model, you receive additional communications from AMS CSDM and AMS Ops engineers that confirm unplanned root user activity due AMS's responsibility to secure root user credentials. AMS investigates root user activity until you confirm a path forward. Prepare Advise AMS of any planned use of root user by submitting an AMS service request with data and times of planned event to prevent unnecessary incident response activities. Periodically conduct GameDays with AMS to validate AMS's customer incident response processes, people and systems are current, and build muscle memory with responsible individuals to achieve faster incident response. Phase A: Detect AMS monitors for root activity in the accounts through detection sources including GuardDuty and AMS monitoring. If you have AMS Accelerate, the operating model responds to the incident requesting investigation for unexpected root user activity. When this occurs, AMS Operations initiates the Compromised Account runbook. Security Incident Response Runbooks Version May 08, 2025 786 AMS Advanced User Guide AMS Advanced Concepts and Procedures If you have AMS Advanced, the operating model responds to the incident, or informs the CSDM of any planned root user activity to terminate an active Account Compromise investigation. Phase B: Analyze AMS performs a thorough investigation of the root user events when it's determined that the activity isn't authorized. Using both automations and AMS security response team, logs and events are analyzed for anomalies and unexpected behavior for root users. Logs are provided to you to help determine if the activity is unknown, or if it's an authorized root user event, or if it requires further investigation. Some examples |
ams-ug-274 | ams-ug.pdf | 274 | If you have AMS Advanced, the operating model responds to the incident, or informs the CSDM of any planned root user activity to terminate an active Account Compromise investigation. Phase B: Analyze AMS performs a thorough investigation of the root user events when it's determined that the activity isn't authorized. Using both automations and AMS security response team, logs and events are analyzed for anomalies and unexpected behavior for root users. Logs are provided to you to help determine if the activity is unknown, or if it's an authorized root user event, or if it requires further investigation. Some examples of the information provided during the investigation to support internal checks includes: • Account information: What account was the root account used on? • E-mail address for root user: Each root user is associated with an e-mail address from your organization • Authentication details: Where and when did the root user access your environment from? • Activity records: What did the user do when logged in as root? These records are in the form of CloudWatch events. Understanding how to read these logs aids in investigation. It's a best practice that you are prepared to receive the analysis information and have a plan for how to reach authorized points of contact for accounts within your organization. Because root users aren't named as individuals, determining who has access to the root e-mail address used for the account within your organization helps to quickly route questions internally. Phase C: Contain and Eradicate AMS partners with your security teams to perform containment at the direction of your authorized Customer Security contacts. Containment options include: • Rotating appropriate credentials and keys. • Terminating active sessions to accounts and resources. • Eradicating resources created. During the containment activities AMS works closely with your security team to ensure any disruption to your workloads are minimized and the root credentials are appropriately secured. Security Incident Response Runbooks Version May 08, 2025 787 AMS Advanced User Guide AMS Advanced Concepts and Procedures After the containment plan is completed, you work with AMS Operations team for any recovery actions as required. Post Incident Report As required, AMS initiates the investigation review process to identify any lessons learned. As part of completing a COE, AMS communicates any relevant findings to affected customers to help them improve their incident response process. AMS documents all final details of the investigation, collects appropriate metrics, and then reports the incident to any AMS internal teams that require information, including your assigned CSDM and CA. Response to malware events Amazon EC2 instances are used to host a variety of workloads including third-party software and custom-developed software deployed by application teams within organizations. AMS provides and encourages you to deploy your workloads on images that are patched and maintained on an ongoing basis by AMS. During the operation of instances, AMS monitors for anomalies in behavior or activity through a variety of security detection controls, including Amazon GuardDuty, Endpoint Protection, Network Traffic, and Amazon internal Threat Intelligence feeds. AMS customers with the AMS Advanced operating model automatically have the endpoint security (EPS) monitoring client installed on provisioned resources. This makes sure that the resources are monitored and supported 24x7, including the creation of a security incident when an event is detected. AMS also monitors GuardDuty Malware Findings. These are available on both AMS Advanced and AMS Accelerate, if enabled. See Malware Protection in Amazon GuardDuty for more information. Note If you opted for Bring Your Own EPS, then the process for incident response differs from what's outlined on this page. For more information, see the referenced documentation. When malware is detected, an incident is created and you are notified of the event. This notification is followed by any remediation activities that occurred. AMS Operations investigates, Security Incident Response Runbooks Version May 08, 2025 788 AMS Advanced User Guide AMS Advanced Concepts and Procedures performs data collection, triage and analysis, and then performs containment activities at your direction, followed by post event analysis. Phase A: Detect AMS monitors for events on instances with GuardDuty and end point security solution monitoring. AMS determines the appropriate enrichment and triage activities to help you make containment or risk acceptance decisions based on the finding or alert type. Data collection is performed based on the finding type. Data collection involves querying multiple data sources both inside and outside of the affected account to build a picture of the activity observed or the configurations of concern. AMS performs correlation of the finding with any other alarms and alerts or telemetry from any impacted accounts or AMS threat intelligence platforms. Phase B: Analyze After data is collected, it's analyzed to identify any activity or indicators of concern. During this phase of the investigation, AMS partners with you to integrate business and domain knowledge |
ams-ug-275 | ams-ug.pdf | 275 | based on the finding or alert type. Data collection is performed based on the finding type. Data collection involves querying multiple data sources both inside and outside of the affected account to build a picture of the activity observed or the configurations of concern. AMS performs correlation of the finding with any other alarms and alerts or telemetry from any impacted accounts or AMS threat intelligence platforms. Phase B: Analyze After data is collected, it's analyzed to identify any activity or indicators of concern. During this phase of the investigation, AMS partners with you to integrate business and domain knowledge of the instances and workloads to help understand what's expected and what's out of the ordinary. Some examples of the information provided during the investigation to support internal checks includes: • Account Information: What account was the malware activity observed on? • Instance Details: What instance(s) are implicated with the malware events? • Event timestamp: When did the alert trigger? • Workload Information: What is running on the instance? • Malware details, if relevant: Families of malware and Open Source information about the malware. • Users or Role Details: What users or roles are affected by and involved in the activity? • Activity Records: What activities are recorded on the instance? These are in the form of CloudWatch events, and system events from the instance. Understanding how to read these logs will aid you in investigation • Network Activity: What endpoints are connecting to the instance, what the instance is connecting to, and what is the traffics analysis? Security Incident Response Runbooks Version May 08, 2025 789 AMS Advanced User Guide AMS Advanced Concepts and Procedures It's a best practice to be prepared to receive investigation information, and have a plan about how to contact the appropriate points of contact for accounts, instances and workloads within your organization. Understanding your network topology and expected connection can help accelerate impact analysis. Knowledge of planned penetration testing in the environment and recent deployments performed by application owners can also speed up the investigation. If you determine that the activity is planned and authorized, then the incident is updated and the investigation ends. If compromise is confirmed, then you and AMS determine the appropriate containment plan. Phace C: Contain and Eradicate AMS partners with you to determine appropriate containment activities based on the data collected and information known. Containment options include but are not limited to: • Preserving data through snapshots • Modifying network rules to limit traffic in or out of instances • Modifying SCP, IAM user and role policies to limit access • Terminating, Suspending or Turning off Instances • Terminating any persistent connections • Rotating appropriate credentials/keys If you opt to perform eradication activity against the instance, then AMS supports you in achieving this. Options include, but are not limited to: • Removing any unwanted software • Rebuilding the instance from a clean fully patched image and redeploying applications and configuration • Restoring the instance from a previous backup • Deploying applications and services on to another instance within your account that might be suitable to host the workloads. It's important to determine how the malware was delivered and run on the instance before restoration of service to make sure that any additional controls are applied to prevent reoccurrence of the malware on the instance. AMS provides additional insights or information to your forensics partners or teams as necessary to support forensics. Security Incident Response Runbooks Version May 08, 2025 790 AMS Advanced User Guide AMS Advanced Concepts and Procedures At this point, you work with AMS Operations for the recovery activities. AMS works closely with you to minimize disruption to the workloads and secure the instances. Post Incident Report As required, AMS initiates the investigation review process to identify lessons learned. As part of completing a COE, AMS communicates relevant findings to you to help you improve your incident response process. AMS documents the final details of the investigation, collects appropriate metrics, and reports the incident to AMS internal teams that require information, including your assigned CSDM and CA. Change request security reviews in AMS Advanced The AWS Managed Services change request review process ensures that AMS performs a security review of the requested changes as they are implemented on your behalf in your account. AMS Advanced technical standards define the minimum security criteria, configurations, and processes to establish the baseline security of your accounts. When AMS implements the requested changes, we follow these standards. AMS evaluates all change requests against the AMS technical standards. Any change that might lower your account's security posture by deviating from the technical standards goes through a security review process. During this process, relevant risk is highlighted by AMS and reviewed and approved by your authorized risk approver to balance security and business |
ams-ug-276 | ams-ug.pdf | 276 | security review of the requested changes as they are implemented on your behalf in your account. AMS Advanced technical standards define the minimum security criteria, configurations, and processes to establish the baseline security of your accounts. When AMS implements the requested changes, we follow these standards. AMS evaluates all change requests against the AMS technical standards. Any change that might lower your account's security posture by deviating from the technical standards goes through a security review process. During this process, relevant risk is highlighted by AMS and reviewed and approved by your authorized risk approver to balance security and business needs. Customer Security Risk Management process The AMS Advanced Customer Security Risk Management (CSRM) process helps to clearly identify and communicate risks to the right owners. This process minimizes the security risks in your environment and reduces ongoing operational overhead for identified risks. By default, when someone from your organization requests that AMS implement a change to your managed environment, AMS reviews the change to determine if the request falls outside of the technical standards, which might alter the security posture of your account. If there is a high or very high security risk, then the change review is accepted or rejected by your authorized security personnel. Requested changes are also evaluated for adverse effects on AMS's ability to operate the account. If the review finds possible adverse impacts, then additional reviews and approvals are required within AMS. Change request security reviews in AMS Advanced Version May 08, 2025 791 AMS Advanced User Guide AMS Advanced Concepts and Procedures You can opt-out from the approval based workflow in the CSRM process for high or very high risks. To change the CSRM option for specific accounts from Standard CSRM to Notification Only, work with your Cloud Service Delivery Managers to create a one-time risk acceptance. If you choose to proceed with the Notification Only option, then AMS implements the requested changes regardless of the risk category. And, AMS sends a risk notification to your authorized risk approvers instead of seeking approval prior to the change implementation. Speak with your Cloud Architects or Cloud Service Delivery Managers for more information about the AMS CSRM process, how to change the default CSRM option when onboarding new AMS accounts, or how to update existing accounts. Note AMS strongly recommends that you use the default option of Standard CSRM in all of your accounts. AMS Advanced technical standards The following are AMS Advanced technical standards categories: ID AMS-STD-001 AMS-STD-002 AMS-STD-003 AMS-STD-004 AMS-STD-005 AMS-STD-006 AMS-STD-007 AMS-STD-008 AMS-STD-009 Category Tagging Configuration AWS Identity and Access Management Network Security Penetration Testing Amazon GuardDuty Host Security Logging AMS-MAD Miscellaneous AMS Advanced technical standards Version May 08, 2025 792 AMS Advanced User Guide AMS Advanced Concepts and Procedures Standard controls in AMS Advanced The following are the standard controls in AMS: AMS-STD-001 - Tagging Configuration The following is the standard control for 001 - Tagging Configuration. 1. All AWS resources required by the AMS team for operational and management purposes must have the following key-value pair. • AppId= AMSInfrastructure • Environment= AMSInfrastructure • AppName = AMSInfrastructure • AMSResource=True 2. All tags required by the AMS team other than those listed previously must have prefixes as mentioned in the list of AMS prefixes (see Note). 3. Tag values required by the AMS team (AppId, Environment and AppName) can be changed on any of the resources created by you based on your change requests. 4. Any tag on stacks required by AMS must not be deleted based on your change requests. 5. You can't use AMS tag naming convention for your infrastructure, as mentioned in point 2. 6. You can have custom tags created in the resources required by AMS (typically for billing and cost reporting use-cases). Custom tags are retained if resources are updated by stack update and not by updating template. Note List of AMS Prefixes 1. ams-* 2. AWSManagedServices* 3. /ams/* 4. ams* 5. AMS* 6. Ams* 7. mc* Standard controls in AMS Advanced Version May 08, 2025 793 AMS Advanced User Guide AMS Advanced Concepts and Procedures 8. MC* 9. Mc* 10.sentinel* 11.Sentinel* 12.Managed_Services* 13.NewAMS* 14.AWS_* 15.aws* 16.VPC_* 17.CloudTrail* 18.Cloudtrail* 19./aws_reserved/ 20.INGEST* 21.EPSDB* 22.MMS* 23.TemplateId* 24.StackSet-ams* 25.StackSet-AWS-Landing-Zone 26.IAMPolicy* 27.customer-mc-* 28.Root* 29.LandingZone* 30.StateMachine* 31.codedeploy_service_role 32.managementhost 33.sentinel.int. 34.eps 35.UnhealthyInServiceBastion 36.ms- Standard controls in AMS Advanced Version May 08, 2025 794 AMS Advanced User Guide AMS Advanced Concepts and Procedures AMS-STD-002 - AWS Identity and Access Management (IAM) ID 1.0 1.1 1.2 1.3 2.0 2.1 2.2 2.3 Technical standard Timeout Duration A federated user default timeout session is one hour and may be increased to up to four hours. RDP session timeout for Microsoft Windows Server is set to 15 minutes and can be extended based on use case. Default Stack Access Time is 12 hours. AWS Root Account Usage If |
ams-ug-277 | ams-ug.pdf | 277 | 27.customer-mc-* 28.Root* 29.LandingZone* 30.StateMachine* 31.codedeploy_service_role 32.managementhost 33.sentinel.int. 34.eps 35.UnhealthyInServiceBastion 36.ms- Standard controls in AMS Advanced Version May 08, 2025 794 AMS Advanced User Guide AMS Advanced Concepts and Procedures AMS-STD-002 - AWS Identity and Access Management (IAM) ID 1.0 1.1 1.2 1.3 2.0 2.1 2.2 2.3 Technical standard Timeout Duration A federated user default timeout session is one hour and may be increased to up to four hours. RDP session timeout for Microsoft Windows Server is set to 15 minutes and can be extended based on use case. Default Stack Access Time is 12 hours. AWS Root Account Usage If there is a root account usage for any reason, Amazon GuardDuty must be configured to generate relevant findings. For single-account landing zone (SALZ) accounts and multi-account landing zone (MALZ) management account (previously known as Master/Billing account), the Root user account must have virtual MFA enabled and the MFA soft token is discarded during the account on-boarding, so that neither AMS nor customers can log in as root. The standard AWS root password lost process must be followed in conjunction with your AMS Cloud Service Delivery Manager (CSDM). This configuration must remain during the life cycle of the AMS managed accounts. You must not create access keys for the root account. Standard controls in AMS Advanced Version May 08, 2025 795 AMS Advanced User Guide AMS Advanced Concepts and Procedures ID 3.0 3.1 3.1.1 3.2 3.3 Technical standard Users Creation and Modification IAM users/roles with programmatic access and with read only permissions can be created without any time-limited policy. However, the permission to allow the reading of objects (for example, S3:GetObject) in all the Amazon Simple Storage Service buckets in the account are not permitted. IAM human users for console access and with read only permissions can be created with the time bound policy (up to 180 days) while the removal/renewal/extension of the time bound policy will result in the risk notificat ion. However, the permission to allow the reading of objects (for example, S3:GetObject) in all the S3 buckets in the account are not permitted. IAM users and roles for console and programmatic access with any infrastructure- mutating permissions (write, permission management, or tagging) in the customer account must not be created without risk acceptance. However, S3 object-level write permissions are allowed without risk acceptance as long as the specific buckets are in the scope. On Microsoft Windows Servers, only Microsoft group Managed Service Account (gMSA) must be created. Standard controls in AMS Advanced Version May 08, 2025 796 AMS Advanced User Guide AMS Advanced Concepts and Procedures ID 3.4 3.5 4.0 4.1 4.2 Technical standard IAM users with programmatic access, named customer_servicenow_user and customer_servicenow_logging_user required for ServiceNow integration in SALZ or MALZ application account and *core accounts* can be created without any time-limited policy. IAM users with programmatic access, using customer_cloud_endure_policy and customer_cloud_endure_deny_ policy (with read-only access) required for CloudEndure integration in SALZ and MALZ accounts can be created but need a time-limited policy for the period of the planned migration. The time-limit can be for a maximum period of 180 days without any RA. The SCP is also authorized for change for MALZ accounts to allow these policies to function for the required period. You define appropriate migration windows for your needs and adjust as required. Policies, Actions, and APIs All your IAM users and roles in SALZ accounts must have the default Customer Deny Policy (CDP) attached to protect AMS infrastructure from accidental or intentional damage. AMS SCPs must be enabled in all the AMS managed accounts in MALZ. Standard controls in AMS Advanced Version May 08, 2025 797 AMS Advanced User Guide AMS Advanced Concepts and Procedures ID 4.3 4.4 4.5 4.6 4.7 4.8 4.9 Technical standard Identities capable of performing administr ative actions on KMS keys, such as PutKeyPol icy , and ScheduleKeyDeletion must be constrained to AMS operators and , automation principals only. A policy must not provide administrator access with a statement that is equivalent to "Effect": "Allow" with "Action": "*" over "Resource": "*" without risk acceptance. The IAM policy must not include any action that includes action Allow S3:*** on any bucket without risk acceptance. API calls against KMS key policies for AMS infrastructure keys in the customer IAM policies must not be permitted. Actions that bypass the change management process (RFC) must not be permitted, such as starting or stopping of the instance, creation of S3 bucket or RDS instance, and so on. Actions that makes changes to the AMS infrastructure DNS records in Amazon Route 53 must not be permitted. IAM human users with console access created after following the due process, must not have any policies attached directly except trust policy, assume role, and time limited policy. Standard controls in AMS Advanced Version May 08, 2025 798 AMS Advanced |
ams-ug-278 | ams-ug.pdf | 278 | AMS infrastructure keys in the customer IAM policies must not be permitted. Actions that bypass the change management process (RFC) must not be permitted, such as starting or stopping of the instance, creation of S3 bucket or RDS instance, and so on. Actions that makes changes to the AMS infrastructure DNS records in Amazon Route 53 must not be permitted. IAM human users with console access created after following the due process, must not have any policies attached directly except trust policy, assume role, and time limited policy. Standard controls in AMS Advanced Version May 08, 2025 798 AMS Advanced User Guide AMS Advanced Concepts and Procedures ID 4.10 4.11 4.12 4.13 4.14 4.15 4.15.1 4.16 Technical standard Amazon EC2 instance profiles with read access to a specific secret or namespace in AWS Secrets Manager within the same account can be created. AWS Managed Services Change Managemen t (AMSCM) or AWS Managed Services Service Knowledge Management System (AMSSKMS) permissions can be added to any role (ability to open SR/Incident/RFC's). IAM policy must not include any action which includes action Allow logs:DeleteLogGrou p and logs:DeleteLogStream on any AMS Amazon CloudWatch log group. Permissions to create multi-Region keys must not be permitted. To provide access to S3 bucket ARNs that aren't yet created in the your accounts, use the service-specific S3 condition key s3:Resour ceAccount to specify the account number. You can have view, create, list, and delete access to your custom dashboard, but only view and list access on Amazon CloudWatch dashboards. You can have view, create, list, and delete access to your S3 storage lens custom dashboard. SQL Workbench related full permissions can be granted to roles/users to work on Amazon Redshift databases. Standard controls in AMS Advanced Version May 08, 2025 799 AMS Advanced User Guide AMS Advanced Concepts and Procedures ID 4.17 4.18 4.19 4.20 4.21 4.22 4.23 Technical standard Any AWS CloudShell permissions can be granted to customer roles as an alternative of CLI. An IAM role with an AWS service as a trusted principal also must be in compliance with the IAM technical standards. Service Linked Roles (SLRs) are not subject to AMS IAM technical standards, as they are built and maintained by IAM Service Team. IAM policies must not allow reading of objects (for example, S3:GetObject) in all the S3 buckets in the account. All the IAM permissions for resource type "savingsplan" can be granted to customers. AMS engineers aren't permitted to copy or move customer data (files, S3 objects, databases) manually in any of the data storage services, such as Amazon S3, Amazon Relational Database Service, Amazon DynamoDB, and so on, or in the OS file system. The SCP policy must not be modified to allow any additional access in any of the AMS managed account. Standard controls in AMS Advanced Version May 08, 2025 800 AMS Advanced User Guide AMS Advanced Concepts and Procedures ID 4.24 4.25 4.26 5.0 5.1 5.2 5.3 6.0 Technical standard Any changes in SCP policy that might break AMS infrastructure or management capabilit ies must not be permitted. (Note: AMS resources have the tag AppId= AMSInfras tructure and follow the AMS Protected Namespace). The AMS Automated IAM Provisioning feature must be enabled in your accounts as an opt-in feature. AMS human-assumed roles or users must not have access to customer content in S3, RDS, DynamoDB, Redshift, Elasticache, EFS and FSx. Also, any access to a known, new APIs released by other AWS services that grant access to customer content must be explicitly denied in the operator roles. Federation Authentication must be configured using federation in AMS managed account. There must be only one-way outgoing trust from AMS AD to your active directory (AMS AD trusts on-prem AD). Your identity stores used to authenticate to AMS must not exist in AMS managed applicati on accounts. Cross Account Policies Standard controls in AMS Advanced Version May 08, 2025 801 AMS Advanced User Guide AMS Advanced Concepts and Procedures ID 6.1 6.2 6.3 6.4 6.5 6.6 6.6.1 Technical standard IAM roles trust policies between AMS accounts that belong to the same customer as per customer records, can be configured. IAM roles trust policies between AMS and non-AMS accounts must be configured only if the non-AMS account is owned by the same AMS customer (by confirming that they are under the same AWS Organizations account or by matching the email domain with the customer's company name). IAM roles trust policies between AMS accounts and third-party accounts must not be configured without risk acceptance. Cross-account policies to access any customer- managed CMKs between AMS accounts of the same customer can be configured. Cross-account policies to access any KMS key within a non-AMS account by an AMS account can be configured. Cross-account policies to access any KMS key within an AMS account by a |
ams-ug-279 | ams-ug.pdf | 279 | only if the non-AMS account is owned by the same AMS customer (by confirming that they are under the same AWS Organizations account or by matching the email domain with the customer's company name). IAM roles trust policies between AMS accounts and third-party accounts must not be configured without risk acceptance. Cross-account policies to access any customer- managed CMKs between AMS accounts of the same customer can be configured. Cross-account policies to access any KMS key within a non-AMS account by an AMS account can be configured. Cross-account policies to access any KMS key within an AMS account by a third-party account must not be permitted without risk acceptance. Cross-account policies to access any KMS key within an AMS account by a non-AMS account can be configured only if the non- AMS account is owned by the same AMS customer. Standard controls in AMS Advanced Version May 08, 2025 802 AMS Advanced User Guide AMS Advanced Concepts and Procedures ID 6.7 6.8 6.9 6.10 Technical standard Cross-account policies to access any S3 bucket data or resources where data can be stored (such as Amazon RDS, Amazon DynamoDB, or Amazon Redshift) between AMS accounts of the same customer can be configured. Cross-account policies to access any S3 bucket data or resources where data can be stored (such as Amazon RDS, Amazon DynamoDB, or Amazon Redshift) in a non-AMS account from an AMS account with read-only access can be configured. Cross-account policies to access any S3 bucket data or resources where data can be stored (such as Amazon RDS, Amazon DynamoDB, or Amazon Redshift) with write permissions from AMS to a non-AMS account (or a non- AMS to AMS account) must be configured only if the non-AMS account is owned by t he same AMS customer (by confirming that they are under the same AWS Organizations account or by matching the email domain with the customer's company name). Cross-account policies to access any S3 bucket data or resources where data can be stored (such as Amazon RDS, Amazon DynamoDB, or Amazon Redshift) in a third-party account from an AMS account with read only access can be configured. Standard controls in AMS Advanced Version May 08, 2025 803 AMS Advanced User Guide AMS Advanced Concepts and Procedures ID 6.11 6.12 7.0 7.1 8.0 8.1 8.2 9.0 Technical standard Cross-account policies to access any S3 bucket data or resources where data can be stored (such as Amazon RDS, Amazon DynamoDB, or Amazon Redshift) in a third-party account from an AMS account with write access must not be configured. Cross-account policies from third-party accounts to access an AMS customer S3 bucket or resources where data can be stored (such asAmazon RDS, Amazon DynamoDB, or Amazon Redshift) must not be configured without risk acceptance. User Groups IAM groups with readonly and non mutative permissions are permitted. Resource-based policies AMS infrastructure resources must be protected from management by unauthorized identities by the attachment of resource based policies. Your resources must be configured with least- privilege resource-based policies, unless you explicitly specify a different policy. Self-service provisioned services (SSPS) Standard controls in AMS Advanced Version May 08, 2025 804 AMS Advanced User Guide AMS Advanced Concepts and Procedures ID 9.1 9.2 9.3 Technical standard AMS default IAM role or policy (including instance profile, SSPS, pattern) must not be modified with or without any risk acceptance. Exceptions are allowed (without risk acceptanc e) for trust policies. Tagging of the role, policy, or user changes, is also permitted in the default SSP roles. Developer mode, DCM role or AMS provided high privileged roles cloning or assignment of policy set from these roles to an existing role will result in risk notification. In general, cloning AMS Role/Policy and modifying them as needed is permitted, inline with the IAM technical standards. SSPS policy for Systems Manager Automation console role cannot be attached to any custom roles aside from the default role. Other SSPS policies must only be attached to custom IAM roles after ensuring the attachment of the policy to a custom role are not providing additional permissions outside the intended design for the default SSPS service. AMS-STD-003 - Network Security The following is the standard control for 003 - Network Security: ID 1.0 Technical standard Networking All EC2 instances must be accessed over SSH or RDP only via Bastion hosts, bastion host Standard controls in AMS Advanced Version May 08, 2025 805 AMS Advanced User Guide AMS Advanced Concepts and Procedures ID 2.0 3.0 4.0 5.0 6.0 7.0 8.0 8.1 Technical standard VPC CIDR range or from the same instance VPC CIDR range. Elastic IP on EC2 instances is permitted AMS control plane and by extension in data plane TLS 1.2+ must be used. All egress traffic must pass using account IGW or TGW. A security group must not have source |
ams-ug-280 | ams-ug.pdf | 280 | ID 1.0 Technical standard Networking All EC2 instances must be accessed over SSH or RDP only via Bastion hosts, bastion host Standard controls in AMS Advanced Version May 08, 2025 805 AMS Advanced User Guide AMS Advanced Concepts and Procedures ID 2.0 3.0 4.0 5.0 6.0 7.0 8.0 8.1 Technical standard VPC CIDR range or from the same instance VPC CIDR range. Elastic IP on EC2 instances is permitted AMS control plane and by extension in data plane TLS 1.2+ must be used. All egress traffic must pass using account IGW or TGW. A security group must not have source as 0.0.0.0/0 in the inbound rule if it is not attached to a load balancer as per 9.0 S3 bucket or objects must not be made public without risk acceptance. Servers management access on ports SSH/22 or SSH/2222 (Not SFTP/2222), TELNET/23, RDP/3389, WinRM/5985-5986, VNC/ 5900-5901 TS/CITRIX/1494 or 1604, LDAP/389 or 636 and RPC/135, NETBIOS/1 37-139 must not be permitted from outside the VPC through security groups. Database management access on ports (MySQL/3306, PostgreSQL/5432, Oracle/15 21, MSSQL/1433) or on custom port must not be permitted from public IPs not routed to VPC over DX, VPC-peer, or VPN through a security group. Any resource where customer data can be stored should not be exposed to public internet directly. Standard controls in AMS Advanced Version May 08, 2025 806 AMS Advanced User Guide AMS Advanced Concepts and Procedures ID 9.0 10.0 11.0 12.0 13.0 14.0 Technical standard Direct applications access over port HTTP/80, HTTPS/8443 and HTTPS/443 from the Internet is permitted only to load balancers , but not to any compute resources directly, for example, EC2 instances, ECS/EKS/Fargate containers, etc. Applications access over port HTTP/80 and HTTPS/443 from customer private IP range can be permitted. Any changes to the security groups which controls the access to the AMS infrastructure must not be permitted without risk acceptanc e. AMS Security refers to the standards every time a security group is requested to be attached to an instance. Customer bastion access on port 3389 and 22 must be permitted only from Private IP ranges that are routed into the VPC over DX, VPC- peer, or VPN. Cross account association of private hosted zones with VPCs from AMS to non-AMS account (or non-AMS to AMS account) must be configured only if non-AMS account is owned by the same AMS customer (by confirming that they are under the same AWS Organizat ion account or by matching the email domain with the customer's company name) using internal tools. Standard controls in AMS Advanced Version May 08, 2025 807 AMS Advanced User Guide AMS Advanced Concepts and Procedures ID 15.0 16.0 17.0 18.0 19.0 20.0 21.0 22.0 23.0 Technical standard VPC peering connections between accounts that belong to the same customer can be permitted. AMS base AMIs can be shared with non-AMS account as long as both accounts are owned by the same customer (by confirming that they are under the same AWS Organizations account or by matching the email domain with the customer's company name) using internal tools. FTP port 21 must not be configured in any of the security group without a risk acceptance. Cross account network connectivity via transit gateway is permitted as long as all the accounts are owned by the customer. Making a private subnet to public is not permitted VPC peering connections with a third party accounts (not owned by the customer) must not be permitted. Transit Gateway attachment with a third party account (not owned by the customer) must not be permitted. Any network traffic required for AMS to provide the services to customers must not be blocked at the customer network egress point. Sharing of resolver rules with AWS account owned by the same customer is allowed with a risk notification Standard controls in AMS Advanced Version May 08, 2025 808 AMS Advanced User Guide AMS Advanced Concepts and Procedures ID 19.0 19.1 19.2 19.3 19.4 20.0 20.1 20.2 Technical standard ICMP Inbound ICMP request to Amazon EC2 from the customer infra will require risk notificat ion. Inbound request from public IPs routed to Amazon VPC over DX, VPC-peer, or VPN via security group is allowed. Inbound request from public IPs not routed to Amazon VPC over DX, VPC-peer, or VPN via security group would require a risk acceptance. Outbound ICMP request from Amazon EC2 to any destination is allowed. Security group sharing If a security group meets this security standard, then it can be shared between VPCs in the same account and between accounts in the same organization. If a security group does not meet this standard and a risk acceptance was previously required for this security group, then the use of the security group sharing feature between VPCs in the same account, or between accounts in the same organization, |
ams-ug-281 | ams-ug.pdf | 281 | not routed to Amazon VPC over DX, VPC-peer, or VPN via security group would require a risk acceptance. Outbound ICMP request from Amazon EC2 to any destination is allowed. Security group sharing If a security group meets this security standard, then it can be shared between VPCs in the same account and between accounts in the same organization. If a security group does not meet this standard and a risk acceptance was previously required for this security group, then the use of the security group sharing feature between VPCs in the same account, or between accounts in the same organization, is not permitted without risk acceptance for that new that VPC or account. AMS-STD-004 - Penetration Testing The following is the standard control for 004 - Penetration Testing Standard controls in AMS Advanced Version May 08, 2025 809 AMS Advanced User Guide AMS Advanced Concepts and Procedures 1. AMS doesn't support pentest infrastructure. It's the customer's responsibility. For example, Kali is not a AMS supported distribution of Linux. 2. Customers need to adhere to Penetration Testing. 3. AMS to be pre-notified 24hrs in advance in the case when the customer would like to perform infrastructure penetration testing within accounts. 4. AMS will provision customer pentesting infrastructure per customer requirements explicitly stated in the change request or service request by the customer. 5. Identity management for customer pentesting infrastructure is the responsibility of the customer. AMS-STD-005 - GuardDuty The following is the standard control for 005 - GuardDuty 1. GuardDuty must be enabled in all the customer accounts at all times. 2. GuardDuty Findings from Customer Managed application Account (CMA) in MALZ will not result in alarms for ops team. 3. GuardDuty alerts must be stored within the same account or any other managed account under the same organization. 4. Trusted IP list feature of GuardDuty must not be used. Instead auto-archiving can be used as an alternative, which is useful for audit purposes. 5. GuardDuty administrator delegation must not be enabled in MALZ as delegated administrator would be able to perform high privilege actions like disabling the GuardDuty in the other accounts without risk acceptance. 6. GuardDuty Auto Archive Filters should use the minimal scope for the maximum return. For example, if AMS will see multiple unpredictable IPs in different CIDR blocks, and there's a corporate ASN that is appropriate to use, use the ASN. However, if you can scope down to specific ranges or /32 addresses, then scope to those. AMS-STD-006 - Host Security The following is the standard control for 006 - Host Security • An anti-virus agent must be running on all EC2 instances at all times.(for example, Trend Micro DSM). Standard controls in AMS Advanced Version May 08, 2025 810 AMS Advanced User Guide AMS Advanced Concepts and Procedures • Anti-malware module must be enabled. • EPS agent must include all directories and files for scanning. • Files quarantined by the anti-virus solution can be shared with the you on-demand. • A third party endpoint security solution should not be installed. • Anti-virus signature update frequency must be set to at least once in a day. • Scheduled scan frequency must be set to at least once in a month. • Real-time (on-access) scan must be enabled and running at all times. • AMS must not execute any custom script that isn't owned or authored by AMS on your instances. (Note: You can do so by using the stack Admin access through the Stack Admin access CT or by using AWS Systems Manager Automation (AMS SSPS). • Network Level Authentication (NLA) must not be disabled on the windows host. • Host operating system must be up to date with the latest security patches as per the configured patch cycle. • An AMS managed account must not have an unmanaged instance in the account. • Creation of local administrator accounts on your instance by AMS must not be permitted. • Key pair on EC2 must not be created. • You must not use operating systems declared as End of Life (EOL) and that there is no further security support provided by the vendor or third party. AMS-STD-007 - Logging The following is the standard control for 007 - Logging ID 1.0 1.1 Technical standard Log types OS Logs: All the hosts must log at minimum host authentication events, access events for all uses of elevated privileges and access events for all changes to access and privilege configuration including success and failure both. Standard controls in AMS Advanced Version May 08, 2025 811 AMS Advanced User Guide AMS Advanced Concepts and Procedures ID 1.2 1.3 1.4 1.5 1.6 1.7 1.8 1.9 Technical standard AWS CloudTrail: CloudTrail management event logging must be enabled and configured to deliver logs to an S3 bucket. VPC Flow Logs: All the network traffic |
ams-ug-282 | ams-ug.pdf | 282 | - Logging ID 1.0 1.1 Technical standard Log types OS Logs: All the hosts must log at minimum host authentication events, access events for all uses of elevated privileges and access events for all changes to access and privilege configuration including success and failure both. Standard controls in AMS Advanced Version May 08, 2025 811 AMS Advanced User Guide AMS Advanced Concepts and Procedures ID 1.2 1.3 1.4 1.5 1.6 1.7 1.8 1.9 Technical standard AWS CloudTrail: CloudTrail management event logging must be enabled and configured to deliver logs to an S3 bucket. VPC Flow Logs: All the network traffic logs must be logged via VPC Flow Logs. Amazon S3 Server Access Logging: AMS mandated S3 buckets that store logs must have server access logging enabled. AWS Config Snapshots: AWS Config must record configuration changes for all supported resources in all the regions and deliver the configuration snapshot files to S3 buckets at least once per day. Endpoint Protection System (EPS) logs: EPS solution logging must be enabled and configured to deliver the logs to an CloudWatc h Logs log group. Application Logs: Customers are empowered to enable logging in their applications and store in CloudWatch Logs log group or an S3 bucket. S3 Object level logging: Customers are empowered to enable object level logging in their S3 buckets. Service Logging: Customers are empowered to enable and forward logs for SSPS services like any core services. Standard controls in AMS Advanced Version May 08, 2025 812 AMS Advanced User Guide AMS Advanced Concepts and Procedures ID 1.10 2.0 2.1 2.2 2.3 2.4 3.0 3.1 3.2 3.3 4.0 Technical standard Elastic Load Balancing(Classic/Application Load Balancer/Network Load Balancer) Logs: Access and error log entries must be stored in the AMS 2.0-managed S3 buckets. Access control You must not have write or delete access in S3 buckets required by AMS that store logs and CloudWatch Logs; log groups. You must have read-only access to all the logs in your accounts. AMS-mandated S3 buckets that store logs must not allow third party accounts users as principles in the bucket policies. Logs from CloudWatch Logs log groups must not be deleted without explicit approval from your authorized security contact. Logs retention AMS-mandated CloudWatch Logs log groups must have a minimum retention period of 90 days on the logs. AMS-mandated S3 buckets that stores the logs must have a minimum retention period of 18 months on the logs. AWS Backup snapshots should be available with minimum retention of 31 days on the supported resources. Encryption Standard controls in AMS Advanced Version May 08, 2025 813 AMS Advanced User Guide AMS Advanced Concepts and Procedures ID 4.1 4.2 5.0 5.1 6.0 6.1 6.2 6.3 Technical standard Encryption must be enabled in all S3 buckets required by AMS Teams that stores logs. Any log forwarding from customer accounts to any other account must be encrypted. Integrity The log file integrity mechanism must be enabled. "Log file validation" must be configured in the AWS CloudTrail trails required by AMS teams. Logs forwarding Any log can be forwarded from one AMS account to another AMS account of the same customer. Any log can be forwarded from AMS to non- AMS account only if non-AMS account is owned by the same AMS customer. Any logs from a customer account must not be forwarded to a third party account (that is not owned by the customer). AMS-STD-008 - AMS-MAD The following is the standard control for 008 - AMS-MAD ID 1.0 1.1 Technical standard Access Management Only AMS privileged users with interactive logins and automation tasks must be allowed Standard controls in AMS Advanced Version May 08, 2025 814 AMS Advanced User Guide AMS Advanced Concepts and Procedures ID 1.2 1.3 1.4 1.5 1.6 2.0 2.1 2.2 2.3 Technical standard to log in to management host for administr ation of managed AD in customer accounts. AD Admins must only have delegated administrator privileges (AMS Delegated Administrator Group). Engineers logging into customer AD environments (management host or instances) must have time-bound access. Customers have read only access to the AD objects using Remote Server Administrator Tools in a EC2 instance. Administrative rights to the active directory user or group must not be permitted. AWS Directory sharing with the AWS account owned by the same customer is allowed with a risk notification. Service accounts Group Managed Service Accounts (gMSA) must be used wherever supported by applications instead of standard service account. All other service accounts must be created after the risk acceptance process. AD Security Groups must not be reused unless explicitly requested by the customer. New AD groups should be created. Computer objects requesting access to the service account must be added to the new security group. Standard controls in AMS Advanced Version May 08, 2025 815 AMS Advanced User Guide AMS Advanced |
ams-ug-283 | ams-ug.pdf | 283 | AWS Directory sharing with the AWS account owned by the same customer is allowed with a risk notification. Service accounts Group Managed Service Accounts (gMSA) must be used wherever supported by applications instead of standard service account. All other service accounts must be created after the risk acceptance process. AD Security Groups must not be reused unless explicitly requested by the customer. New AD groups should be created. Computer objects requesting access to the service account must be added to the new security group. Standard controls in AMS Advanced Version May 08, 2025 815 AMS Advanced User Guide AMS Advanced Concepts and Procedures ID 2.4 2.5 3.0 3.1 3.2 3.3 4.0 4.1 5.0 Technical standard Any gMSA service account(s) must be added under the "Managed Service Account" Organizational Unit (OU). Any non-gMSA service account(s) must be added under the "Users→Se rvice Accounts" OU. Group Policy Objects (GPO) Any setting under the "Windows Settings > Security Settings" GPO must not be modified if it reduces the security posture of the account in any manner from the current state. In MALZ, RFCs submitted from an applicati on account requesting a GPO creation, the GPO must be linked to the OU that correspon ds to the App account. Any GPOs that affects all accounts must be from the Shared Service account. Default RDP Idle Session time out must be set to 15 minutes for all the servers under the active directory domain. Active Directory Trust One-way outbound trust (AMS hosted Directory to Customer Directory) is permitted if the IPs of conditional forwarders are routed to VPC over DX, VPC-peer, or VPN. Others Standard controls in AMS Advanced Version May 08, 2025 816 AMS Advanced User Guide AMS Advanced Concepts and Procedures ID 5.1 6.0 6.1 6.2 Technical standard The log file integrity mechanism must be enabled. "Log file validation" must be configured in the AWS CloudTrail trails required by AMS teams. Logs forwarding Customer users, groups, computer objects, OU or other entities must not use AMS naming convention as per AMS naming convention. All the OUs must be managed by AMS. AMS-STD-009 - Miscellaneous The following is the standard control for 009 - Miscellaneous • If encryption is enabled in a resource, object, database, or file system, it must not be disabled. Changes that introduce high or very high security risks in your environment The following changes introduce high or very high security risk in your environment: AWS Identity and Access Management • High_Risk-IAM-001: Create access keys for root account • High_Risk-IAM-002: SCP policy modification to allow additional access • High_Risk-IAM-003: SCP policy modification that could break AMS infrastructure • High_Risk-IAM-004: Creation of a role/user with infrastructure mutating permissions (write, permission management or tagging) in customer account • High_Risk-IAM-005: IAM roles trust policies between AMS accounts and third-party accounts (not owned by the customer) • High_Risk-IAM-006: Cross-account policies to access any KMS key from an AMS account by a third-party account) Changes that introduce high or very high security risks in your environment Version May 08, 2025 817 AMS Advanced User Guide AMS Advanced Concepts and Procedures • High_Risk-IAM-007: Cross-account policies from third-party accounts to access an AMS customer S3 bucket or resources where data can be stored (such as Amazon RDS, Amazon DynamoDB, or Amazon Redshift) • High_Risk-IAM-008: Assign the IAM permissions with any infrastructure mutating permission in customer account • High_Risk-IAM-009: Allow listing and reading on all the S3 buckets in the account • High_Risk-IAM-010: Automated IAM Provisioning with read/write permissions Network security • High_Risk-NET-001: Open OS management ports SSH/22 or SSH/2222 (Not SFTP/2222), TELNET/23, RDP/3389, WinRM/5985-5986, VNC/ 5900-5901 TS/CITRIX/1494 or 1604, LDAP/389 or 636 and NETBIOS/137-139 from the internet • High_Risk-NET-002: Open database management ports MySQL/3306, PostgreSQL/5432, Oracle/1521, MSSQL/1433 or any management customer port from the internet • High_Risk-NET-003: Open application ports HTTP/80, HTTPS/8443 and HTTPS/443 on any compute resources directly. For example, EC2 instances, ECS/EKS/Fargate containers, and so on from the internet • High_Risk-NET-004: Any changes to the security groups which controls the access to the AMS infrastructure • High_Risk-NET-006: VPC peering with the third-party account (not owned by the customer) • High_Risk-NET-007: Adding customer firewall as egress point for all the AMS traffic • High_Risk-NET-008: Transit Gateway attachment with the third-party account is not allowed • High_Risk-S3-001: Provision or enable public access in the S3 bucket Logging • High_Risk-LOG-001: Disable CloudTrail. (Ops Site Manager Approval Required) • High_Risk-LOG-002: Disable VPC Flow Logs. (Ops Site Manager Approval Required) • High_Risk-LOG-003: Log forwarding through any method (S3 event notification, SIEM agent pull, SIEM agent push etc) from an AMS managed account to third party account (not owned by customer) • High_Risk-LOG-004: Use non-AMS trail for CloudTrail Changes that introduce high or very high security risks in your environment Version May 08, 2025 818 AMS Advanced User Guide Host Security AMS |
ams-ug-284 | ams-ug.pdf | 284 | with the third-party account is not allowed • High_Risk-S3-001: Provision or enable public access in the S3 bucket Logging • High_Risk-LOG-001: Disable CloudTrail. (Ops Site Manager Approval Required) • High_Risk-LOG-002: Disable VPC Flow Logs. (Ops Site Manager Approval Required) • High_Risk-LOG-003: Log forwarding through any method (S3 event notification, SIEM agent pull, SIEM agent push etc) from an AMS managed account to third party account (not owned by customer) • High_Risk-LOG-004: Use non-AMS trail for CloudTrail Changes that introduce high or very high security risks in your environment Version May 08, 2025 818 AMS Advanced User Guide Host Security AMS Advanced Concepts and Procedures • High_Risk-HOST-001: Disable End Point Security in the account for any reason.(Ops Site Manager Approval Required) • High_Risk-HOST-002: Disable patching in a resource or at account level. • High_Risk-HOST-003: Deploying an unmanaged EC2 instance in the account. • High_Risk-HOST-004: Running a custom script provided by the customer. • High_Risk-HOST-005: Creation of Local Administrator accounts on instances. • High_Risk-HOST-006: Trend Micro EPS file type / extension scan exclusions or disabling malware protection on endpoints. Note Risk acceptance isn't required for EPS anti-malware exclusions or GuardDuty Suppression rules related to penetration tests or vulnerability scans or service impacting events/ known performance issues warranting proactive actions. A risk notification is enough in these situations. • High_Risk-HOST-007: Create KeyPair for EC2 • High_Risk-HOST-008: Disable End Point Security in the EC2 • High_Risk-HOST-009: Accounts using End of Life(EOL) OS Miscellaneous • High_Risk-ENC-001: Disable encryption in any resource if it is enabled Managed Active Directory • High_Risk-AD-001: Provide admin rights to active director user or group • High_Risk-AD-002: GPO Policies capable of reducing security posture of the account Changes that introduce high or very high security risks in your environment Version May 08, 2025 819 AMS Advanced User Guide AMS Advanced Concepts and Procedures Continuity management in AMS Advanced As part of continuity management, AWS Managed Services (AMS) provides automated access to AWS Backup, a native service with AWS. This facilitates access to a service that supports Amazon EBS, Amazon EC2, Amazon RDS, Amazon EFS, and more. To learn more, see AWS Backup: How It Works. Topics • What is continuity management? • How continuity management works • Disaster recovery response • Disaster recovery planning What is continuity management? Continuity management is the process AMS uses to provide backups and snapshots for your account. AMS provides access to AWS Backup through change types that you use to create and manage backup jobs and plans. How continuity management works AMS uses AWS Backup for continuity management. When starting to work with AWS Backup in AMS: 1. Run an on-demand backup 2. Create a backup plan (optional, AMS provides default backup plans) 3. Use the default AMS a backup vaults (optional) 4. Manage (run, refine, delete, and so forth) your backup plans and recovery points What is continuity management? Version May 08, 2025 820 AMS Advanced User Guide AMS backup plans AMS Advanced Concepts and Procedures A backup plan is a policy expression that defines when and how you want to back up supported AWS resources, such as RDS databases, EBS volumes, DynamoDB tables, and EFS file systems. Scheduling and retention policies are managed via custom backup plans, which you can create using a change type (CT) with AMS Advanced or using AWS Backup with AMS Accelerate. Assign resources to your backup plans using tags and AWS Backup automatically backs up and retains backups for assigned resources according to the defined backup plan. You can create multiple backup plans if you have workloads with different backup requirements. A backup plan can have up to six backup rules that define a schedule and a retention period, among other details. The backup schedule determines when AWS Backup initiates a backup job and how often a backup is created. You can choose a frequency of hourly, daily, weekly, or monthly. The deletion days setting determines how many days the snapshot is stored before being automatically deleted. Note AMS Advanced: If you are migrated from the legacy AMS backup system, AMS creates a default backup plan for backwards compatibility. The key:value pair in this scenario is Backup:True. To support backwards compatibility, the value here is case insensitive, so Backup:True or Backup:TRUE are all valid tags. All other key:value pairs are case sensitive. AWS Backup can operate at the EBS volume level or at the Amazon EC2 instance level, but do not do both at the same time, as this can lead to a race condition where the backups may clash. Default backup plans, multi-account landing zone During the new Account creation RFC, AMS ensures that there is an overarching default backup plan at the account level to safeguard your workloads. The values for mandatory fields are set by default, as shown in the following section: Default AMS backup |
ams-ug-285 | ams-ug.pdf | 285 | Backup:True or Backup:TRUE are all valid tags. All other key:value pairs are case sensitive. AWS Backup can operate at the EBS volume level or at the Amazon EC2 instance level, but do not do both at the same time, as this can lead to a race condition where the backups may clash. Default backup plans, multi-account landing zone During the new Account creation RFC, AMS ensures that there is an overarching default backup plan at the account level to safeguard your workloads. The values for mandatory fields are set by default, as shown in the following section: Default AMS backup plan default-backup-plan TAG key: Backup Backup plans Version May 08, 2025 821 AMS Advanced User Guide TAG value: True AMS Advanced Concepts and Procedures RuleForDailyBackups schedule expression: cron(30 23 ? * *) (a daily backup for 23:30 UTC time) RuleForDailyBackups delete after days: 31 days RuleForWeeklyBackups schedule expression: cron(30 23 ? * 7 *) (a weekly backup for 23:30 UTC time only on Saturday) RuleForWeeklyBackups delete after weeks: 6 weeks RuleForMonthlyBackups schedule expression: cron(30 23 * ? *) (a monthly backup for 23:30 UTC time on day 1 of the month) RuleForMonthlyBackups delete after weeks: 26 weeks RuleForYearlyBackups schedule expression: cron(30 23 1 1 ? *) (a yearly backup for 23:30 UTC time on day 1 of the month, only in January) RuleForYearlyBackups delete after years: 2 years Default AMS backup plan Start Time Retention hourly backup N/A daily backup daily 11:30PM UTC weekly backup monthly backup yearly backup N/A 7 days 4 weeks weekly 11:30PM UTC, only on Saturday monthly 11:30 PM UTC, on day 1 of the month 26 weeks 11:30 PM UTC, on day 1 of the month 2 years Enhanced default AMS backup plan This plan is a blueprint for AWS Backup best practices to protect against ransomware attacks. It implements a daily, weekly, monthly, and yearly backup strategy. AWS Backup continuous backup is enabled with maximum retention (31 days) on supported resources. ams-enhanced-default-backup-plan TAG key: backup-orchestrator-enhanced TAG value: true Backup plans Version May 08, 2025 822 AMS Advanced User Guide AMS Advanced Concepts and Procedures RuleForDailyBackups schedule expression: cron(0 0 4 ? * * ) (a daily backup for 04:00 UTC time) RuleForDailyBackups delete after days: 31 days RuleForDailyBackups continuous backup: true RuleForWeeklyBackups schedule expression: cron(0 0 2 ? * 7) (a weekly backup for 02:00 UTC time only on Saturday) RuleForWeeklyBackups delete after weeks: 6 weeks RuleForMonthlyBackups schedule expression: cron(0 2 1 * ? *) (a monthly backup for 02:00 UTC time on day 1 of the month) RuleForMonthlyBackups delete after weeks: 26 weeks RuleForYearlyBackups schedule expression: cron(0 2 1 1 ? *) (a yearly backup for 02:00 UTC time on day 1 of the month, only in January) RuleForYearlyBackups delete after years: 2 years Enhanced AMS backup plan Start Time Retention hourly backup N/A daily backup daily 4:00 UTC weekly backup Saturday, 2:00 UTC N/A 31 days 6 weeks monthly backup 1st of the month, 2:00 UTC 26 weeks yearly backup Jan 1st, 2:00 UTC 2 years Data sensitive AMS backup plan This plan is a blueprint for AWS Backup best practices to protect against ransomware attacks for data-sensitive applications. It implements an hourly, daily, weekly, monthly, and yearly backup strategy. AWS Backup continuous backup is enabled with maximum retention (31 days) on supported resources. ams-data-sensitive-backup-plan TAG key: backup-orchestrator-data-sensitive TAG value: true RuleForHourlyBackups schedule expression: cron(0 * ? * * *) (an hourly backup at the hour mark) Backup plans Version May 08, 2025 823 AMS Advanced User Guide AMS Advanced Concepts and Procedures RuleForHourlyBackups delete after days: 7 days RuleForDailyBackups schedule expression: cron(0 0 4 ? * * ) (a daily backup for 04:00 UTC time) RuleForDailyBackups delete after days: 31 days RuleForWeeklyBackups schedule expression: cron(0 0 2 ? * 7) (a weekly backup for 02:00 UTC time only on Saturday) RuleForWeeklyBackups delete after weeks: 6 weeks RuleForMonthlyBackups schedule expression: cron(0 2 1 * ? *) (a monthly backup for 02:00 UTC time on day 1 of the month) RuleForMonthlyBackups delete after weeks: 26 weeks RuleForYearlyBackups schedule expression: cron(0 2 1 1 ? *) (a yearly backup for 02:00 UTC time on day 1 of the month, only in January) RuleForYearlyBackups delete after years: 2 years Data Sensitive AMS backup plan Start Time Retention hourly backup at the hour mark daily backup daily 4:00 UTC weekly backup Saturday, 2:00 UTC 7 days 31 days 6 weeks monthly backup 1st of the month, 2:00 UTC 26 weeks yearly backup Jan 1st, 2:00 UTC 2 years AMS backup vaults AWS Backup organizes snapshots into logical storage units called vaults. To view a list of your AMS backups, open the AWS Backup console. In the navigation pane, choose Backup vaults and select the one of the AMS backup vaults from the following tables. In the |
ams-ug-286 | ams-ug.pdf | 286 | after years: 2 years Data Sensitive AMS backup plan Start Time Retention hourly backup at the hour mark daily backup daily 4:00 UTC weekly backup Saturday, 2:00 UTC 7 days 31 days 6 weeks monthly backup 1st of the month, 2:00 UTC 26 weeks yearly backup Jan 1st, 2:00 UTC 2 years AMS backup vaults AWS Backup organizes snapshots into logical storage units called vaults. To view a list of your AMS backups, open the AWS Backup console. In the navigation pane, choose Backup vaults and select the one of the AMS backup vaults from the following tables. In the Backups section, view the list of all the backups in the backup vault. Select a backup to edit, delete, or restore. Vaults for AMS backup plans Backup vaults Version May 08, 2025 824 AMS Advanced User Guide AMS Advanced Concepts and Procedures AMS Vault Name Description ams-automated-backups ams-automated-enhanced-backups ams-automated-data-sensitive-backups ams-manual-backups ams-custom-backups This vault receives all recovery points taken by the AMS Advanced default AWS Backup plan default-backup-plan. This vault receives all recovery points taken by AMS Advanced enhanced default AWS Backup plan ams-enhanced-default-backup-plan. This vault receives all recovery points taken by AMS Advanced AWS Backup plan ams-data- sensitive-backup-plan. This is the default location for all backups from Start Backup Job RFC (ct-2hhud 2lx01tq7) backup plans, if no vault name is defined. This is the default location for the snapshots AMS takes prior to patching an instance using Patch Orchestrator or the monthly patch activities. These are automatically removed according to the AMS patch lifecycle default policy of 60 days. AMS backup change types AMS provides several CTs for you to create and use backup plans. Important Do not edit your AMS default backup plans as your changes may be lost. Instead, create new plans for your custom configurations. • Backup plan: Create Backup change types Version May 08, 2025 825 AMS Advanced Concepts and Procedures AMS Advanced User Guide • Backup Job: Start • Backup Job: Stop • Recovery Point: Delete • DynamoDB | Create from Backup • EBS Volume: Create From Backup • Amazon Elastic File System (EFS): Create From Backup AMS backup monitoring and reporting Important AMS backup monitoring and reporting are only available in AMS-supported regions. Those are US East (Virginia), US West (N. California), US West (Oregon), US East (Ohio), Canada (Central), South America (São Paulo), EU (Ireland), EU (Frankfurt), EU (London), EU (Paris), Asia Pacific (Mumbai), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo). AMS generates daily self-service reports as well as monthly reports on resource coverage and backup job status. The monthly reports are shared in Monthly Business Reviews (MBRs). To learn more about daily backup reports, see Daily backup report . AMS experts monitor all your backup tasks that are configured using AWS Backup. In case of backup failures, AMS investigates the failure and notifies you with the root cause and remediation options, if available. To avoid alert noise, during events that cause a high number of backup failures in your accounts, AMS makes a collective recommendation, through your CSDM, instead of notifying you for each individual failure. Note that AMS does not monitor any backups configured using an AWS service’s standalone backup feature. Disaster recovery response In addition to the options described in the following sections, it is good for you to know what steps to take to initiate a disaster recovery (DR) with AMS. If you experience a disaster and need to initiate a recovery, follow these general guidelines: Monitoring and reporting for backups Version May 08, 2025 826 AMS Advanced User Guide AMS Advanced Concepts and Procedures 1. Open a High priority incident with the Availability category. AMS will open a conference bridge and invite your team to join. 2. Know the list of resources you need to recover. 3. Know the target landing zone (LZ) you need to recover to (for example, the same account, different AZ or different account and different region). 4. Submit recover requests for each resource in the target landing zone. Follow your existing DR plan or see the options in the following section (for example, Disaster protection for EC2 with EBS snapshots on AMS, or Disaster protection for EC2 with Elastic Disaster Recovery on AMS). 5. Restore the application functionality and use AMS assistance to troubleshoot infrastructure- related issues. AMS can help you with preparing for this event and with creating a DR plan for your organization to cover these questions. For more details, contact your cloud service delivery manager (CSDM) or cloud architect (CA). Disaster recovery planning Disaster recovery (DR) is a critical service for enterprise business continuity and compliance. AMS partners with you to help you plan, implement and maintain your DR strategy on AMS. AMS landing zone (LZ), multi-account and single-account, provides native, multi-AZ, high- availability for |
ams-ug-287 | ams-ug.pdf | 287 | Elastic Disaster Recovery on AMS). 5. Restore the application functionality and use AMS assistance to troubleshoot infrastructure- related issues. AMS can help you with preparing for this event and with creating a DR plan for your organization to cover these questions. For more details, contact your cloud service delivery manager (CSDM) or cloud architect (CA). Disaster recovery planning Disaster recovery (DR) is a critical service for enterprise business continuity and compliance. AMS partners with you to help you plan, implement and maintain your DR strategy on AMS. AMS landing zone (LZ), multi-account and single-account, provides native, multi-AZ, high- availability for AMS infrastructure components that meet most disaster protection scenarios. However, depending on your business's geographical coverage, you might need regional protection. For cross-region availability and DR, another AMS account is required in a different region (this is so for both multi-account landing zone and single-account landing zone). AMS aligns with AWS DR guidance as described in this blog, Rapidly recover mission-critical systems in a disaster, and supports the following four options: • Multi Site (or Highly Available) • Warm Standby • Pilot Light • Backup and Restore These options and AMS support for them are described in the following sections. Disaster recovery planning Version May 08, 2025 827 AMS Advanced User Guide AMS Advanced Concepts and Procedures Multi-site or highly available (HA) The HA solution is usually provided by the application's built-in functionality, such as clustering or synchronous replication. Users are directed to both Prod and HA/DR nodes. DNS points either to the nodes directly or through an elastic load balancer (ELB). Your AMS cloud architect (CA) will work with you as part of your Well-Architected-Review and DR planning. HA DR utilizes application and AWS-native services and features, as illustrated in the following graphic: The DR site can be in the same or different AWS Region. Note Different region (Cross-Region) will have a different Active Directory environment. Multi-site or highly available (HA) Version May 08, 2025 828 AMS Advanced User Guide AMS Advanced Concepts and Procedures DR (failover) steps: Automatic failover, no manual steps are required. In case of a failure in the primary LZ, the users will be automatically re-routed to the DR/HA node. This is achieved by both DNS and application configuration. HA DR metrics: • Recovery Point Objective (RPO): <5 min • Recovery Time Objective and (RTO): <5 min • Maintenance: High (Synchronous changes are required in both environments, like Application configuration, patching, SG or ALB, certificates, and so on). • Cost: High Warm standby The term "warm standby" is used to describe a disaster recovery (DR) scenario in which a scaled- down version of the environment is running in the cloud. Data replication is handled by the application layer, usually asynchronously, to an online instance, while the rest of the instances (for example, Application and Web tier) might be turned off to save the cost. Users are directed only to the Production site. Other AWS resources like elastic load balancer (ELB) may be pre-provisioned in the DR site as well. Your AMS Cloud Architect (CA) will work with you as part of your Well-Architected-Review and DR planning. Warm Standby DR utilizes application and AWS-native services and features, as illustrated in the following graphic: Warm standby Version May 08, 2025 829 AMS Advanced User Guide AMS Advanced Concepts and Procedures DR site can be in the same or different AWS Region. Note Different region (Cross-Region) will have a different Active Directory environment. DR (failover) steps: 1. Brake the data replication and make the data instance in the DR site the master 2. Update application configuration as required (new IP, server name, and so on) 3. Redirect DNS to the DR site (ELB) Warm standby Version May 08, 2025 830 AMS Advanced User Guide AMS Advanced Concepts and Procedures 4. AD Dependencies if required (Service accounts, SPNs, GPOs, and so on) HA DR metrics: • Recovery Point Objective (RPO): <1hr • Recovery Time Objective and (RTO): <1 hr (depends on the number of instances and orchestration) • Maintenance: High (Synchronous changes are required in both environments, like Application configuration, patching, security groups (SG) or application load balancer (ALB), certificates, and so on). • Cost: Medium Pilot light In this disaster recovery (DR) approach, you replicate part of your Prod environment for a limited set of core services. A small part of your infrastructure is always running, simultaneously syncing mutable data (such as databases or documents), while other parts of your infrastructure are switched off and used only during testing. Unlike a backup and recovery approach, you must ensure that your most critical core elements are already configured and running in the DR landing zone (the pilot light). Your AMS Cloud Architect will work with you as part of your Well-Architected-Review and DR planning. Pilot Light DR utilizes application |
ams-ug-288 | ams-ug.pdf | 288 | this disaster recovery (DR) approach, you replicate part of your Prod environment for a limited set of core services. A small part of your infrastructure is always running, simultaneously syncing mutable data (such as databases or documents), while other parts of your infrastructure are switched off and used only during testing. Unlike a backup and recovery approach, you must ensure that your most critical core elements are already configured and running in the DR landing zone (the pilot light). Your AMS Cloud Architect will work with you as part of your Well-Architected-Review and DR planning. Pilot Light DR utilizes application and AWS-native services and features, as illustrated in the following graphic: Pilot light Version May 08, 2025 831 AMS Advanced User Guide AMS Advanced Concepts and Procedures DR site can be in the same or different AWS Region. Note Different region (Cross-Region) will have a different Active Directory environment. DR (failover) steps: 1. Brake the data replication and make the data instance in the DR site the master 2. Start the turned off instances and infrastructure 3. Update application configuration as required (new IP, server name, and so on) Pilot light Version May 08, 2025 832 AMS Advanced User Guide AMS Advanced Concepts and Procedures 4. Add the instances to the ELB as required 5. Redirect DNS to the DR site (ELB) 6. AD Dependencies, if required (Service accounts, SPNs, GPOs, and so on) Pilot Light DR metrics: • Recovery Point Objective (RPO): <1hr • Recovery Time Objective and (RTO): ~1 hr (depends on the number of instances and orchestration) • Maintenance: Medium • Cost: Medium Backup and restore This simple and low cost disaster recovery (DR) approach backs up your data and applications from anywhere to the DR landing zone for use during recovery from a disaster. Your AMS Cloud Architect works with you as part of your Backup and DR planning. Backup and Restore DR utilizes AMS automated tooling and processes, as illustrated in the following graphic: Backup and restore Version May 08, 2025 833 AMS Advanced User Guide AMS Advanced Concepts and Procedures Two backup and replication methods can be used: • EBS snapshot (Recovery Point Objective (RPO) > 1hr), known as "EBS" • AWS Elastic Disaster Recovery (Recovery Point Objective (RPO) ~ 0.25hrs), known as "DRS" The DR site can be in the same or in a different AWS Region. Note A different Region (Cross-Region) has a different Active Directory environment. Backup and restore Version May 08, 2025 834 AMS Advanced User Guide DR (failover) steps: AMS Advanced Concepts and Procedures 1. Restore the instances from snapshots (two-step process with placeholder instance first) 2. Update application configuration (new IP, server name,and so on) 3. Set up other infrastructure as required (SG, ELB, and so on) 4. Redirect DNS to the DR site (ELB) 5. Update or restore AD dependencies if required (service accounts, service principal names (SPNs), group policy objects (GPOs), and so on) Backup and Restore DR metrics: • Recovery Point Objective (RPO): >1hr or ~0.25hrs (depends on the solution selected - EBS or DRE) • Recovery Time Objective and (RTO): ~1 hr (depends on the number of instances and orchestration) • Maintenance: High (Synchronous changes are required in both environments, like application configuration, patching, security groups or application load balancers, certificates, and so on. • Cost: Medium Disaster protection for EC2 with EBS snapshots on AMS Prerequisites: • AMS Prod Landing Zone (source) • AMS DR Landing Zone (DR target) • EBS snapshots are enabled for EC2 instances (AWS Backup) Snapshot replication solution: • Cross AZ: Not applicable - EBS snapshot are highly available within the Region by design • Cross-Region: AWS Backup The following diagram represents the EC2 restore process from EBS snapshots on AMS: Backup and restore Version May 08, 2025 835 AMS Advanced User Guide AMS Advanced Concepts and Procedures EC2 DR steps on AMS: 1. Raise an RFC to share the EBS snapshots with the target account (required for Cross-Region DR). : Management, Advanced Stack Components, EBS Snapshot, Share 2. Create a placeholder EC2 AMS stack in the destination subnet (DR site subnet). The recommendation is to use CFN ingestion to create the stack as the customer can combine the steps of assigning security groups and other (like adding the instance to an ELB) in the same stack. Change type: Deployment, Ingestion, Stack from CloudFormation Template, Create 3. Raise an RFC to perform EC2 stack volume restore. Change type: Management, Advanced Stack Components, EC2 instance stack, Restore volumes. The CT restores the volumes from the snapshots shared in step 1 and attaches to the placeholder instance created in step 2. Volume Restore CT functionality: • Shut the placeholder instance down • Restore volumes from the snapshots Backup and restore Version May 08, 2025 836 AMS Advanced User Guide • Swap |
ams-ug-289 | ams-ug.pdf | 289 | steps of assigning security groups and other (like adding the instance to an ELB) in the same stack. Change type: Deployment, Ingestion, Stack from CloudFormation Template, Create 3. Raise an RFC to perform EC2 stack volume restore. Change type: Management, Advanced Stack Components, EC2 instance stack, Restore volumes. The CT restores the volumes from the snapshots shared in step 1 and attaches to the placeholder instance created in step 2. Volume Restore CT functionality: • Shut the placeholder instance down • Restore volumes from the snapshots Backup and restore Version May 08, 2025 836 AMS Advanced User Guide • Swap out the volumes • Start the instance • Leave the old domain • Change the hostname AMS Advanced Concepts and Procedures • Reboot. AMS bootstrap scripts join the instance to the target (DR) domain upon start up Volume restore CT input: • InstanceId (placeholder instance ID) • RootDeviceSnapshotId, the EBS snapshot for the restored root volume • KMSKeyId, the KMS key identifier, or ARN, to encrypt all restored volumes on the EC2 instance • DeviceNames, up to 25 (optional) • SnapshotIds, up to 25 (optional). List of snapshots of the volumes to be restored Disaster protection for EC2 with Elastic Disaster Recovery on AMS Prerequisites: • AMS Prod Landing Zone (source) • AMS DR Landing Zone (DR target) • You must first initialize the Elastic Disaster Recovery service for all AWS Regions that you plan to use it in. Create an IAM role in your DR landing zone (LZ) for Elastic Disaster Recovery console access. • Important: An SSM Document is created as a Post Launch Action within DRS. This Action must be enabled on all your servers on the PostLaunch settings. • the destination (placeholder) instance must have a tag key: "AWSDRS", value: "AllowLaunchingIntoThisInstance". Placeholder instance must be in the stopped state. Otherwise, AMS can't select the placeholder instance under the launch settings and Elastic Disaster Recovery can't restore on top of the placeholder instance. For a diagram of the Elastic Disaster Recovery setup and restore process for EC2 on AMS, see AWS Elastic Disaster Recovery (AWS DRS) general architecture. Backup and restore Version May 08, 2025 837 AMS Advanced User Guide AMS Advanced Concepts and Procedures EC2 DR steps with Elastic Disaster Recovery on AMS: 1. Create a placeholder EC2 AMS stack in the destination subnet (DR site subnet) with proper tags, for more information, see the previous section. We recommend using CFN ingestion to create the stack as you can combine the steps of assigning security groups and tagging the instance, EBS volume, and other (like adding the instance to an ELB) in the same stack. Change type: Deployment, Ingestion, Stack from CloudFormation Template, Create 2. Stop the placeholder instance. Change type: Management, Advanced stack components, EC2 instance, Stop 3. If not done in step 1, tag the placeholder instance and its EBS volume with key: "AWSDRS", value: "AllowLaunchingIntoThisInstance". Change type: Management, Advanced stack components, Tag, Update. 4. Use the placeholder instance from step 1 as the target under Launch into instance ID, DRS Launch Settings for the source server. Initiate instance recovery drill from the Elastic Disaster Recovery console for the Source Server. Note The placeholder instance volumes are retained in the account. To delete these volumes, submit a Management | Other | Other change type at the end of the disaster recovery operation. Elastic Disaster Recovery restore workflow: • The target (placeholder) instance needs to be in the stopped state • Swap out the volumes and delete the source (placeholder) root volume • Start the instance • Run the Post Launch Actions to complete the following items: • Activate the SSM Agent. • Swap out the volumes and delete the source (placeholder) root volume. • Start the instance • Run PostLaunchScript SSM Document. This document does following: Backup and restore Version May 08, 2025 838 AMS Advanced User Guide AMS Advanced Concepts and Procedures 1. Leaves the old domain. 2. Changes the hostname. 3. Reboot. AMS bootstrap scripts join the instance to the target (DR) domain during startup. Backup and restore Version May 08, 2025 839 AMS Advanced User Guide AMS Advanced Concepts and Procedures Patch management in AMS Topics • AMS Patch Orchestrator: a tag-based patching model • Using Patch Orchestrator • On-demand patching • AMS standard patching • Patching service commitments In AMS, patch management is a service that helps you maintain OS vendor updates on your Amazon Elastic Compute Cloud (Amazon EC2) instances. You have the freedom to customize the frequency and process of patching your Amazon EC2 instances. You configure patch management during onboarding, and you can update it by using the RFC process. Stacks created using the change management system and a patch-compatible template (for Amazon EC2, Auto Scaling group, HA one-tier or two-tier stack) are subscribed to patch management |
ams-ug-290 | ams-ug.pdf | 290 | tag-based patching model • Using Patch Orchestrator • On-demand patching • AMS standard patching • Patching service commitments In AMS, patch management is a service that helps you maintain OS vendor updates on your Amazon Elastic Compute Cloud (Amazon EC2) instances. You have the freedom to customize the frequency and process of patching your Amazon EC2 instances. You configure patch management during onboarding, and you can update it by using the RFC process. Stacks created using the change management system and a patch-compatible template (for Amazon EC2, Auto Scaling group, HA one-tier or two-tier stack) are subscribed to patch management automatically. AMS provides a feature, Patch Orchestrator – tag-based patching, for configuring patching. For definitions of patching terms, see AMS key terms. Important • It's not possible for stacks or a stack's constituent instances to opt out of patch management, if the AMS template from which the stack is created is compatible with patch management. Currently, patching is compatible with the following stack templates: • Amazon EC2 stack | Create, and Amazon EC2 stack | Create (with additional volumes) • Amazon EC2 instance launched with AWS CloudFormation ingest • Auto Scaling group | Create (the Amazon EC2 instances in the group are patched) • High Availability One-Tier stack | Create, and High Availability Two-Tier stack | Create • If there is an ongoing incident that affects a stack, AMS operators can reschedule or cancel scheduled patching. Version May 08, 2025 840 AMS Advanced User Guide AMS Advanced Concepts and Procedures • By default, all instances within a particular patch-compatible stack are patched in-place. To patch Auto Scaling groups with an Amazon Machine Image (AMI) replacement using the latest/patched AMS AMI, submit a service request. Updated AMIs are shared to accounts every month. Tip AMS recommends that you enable backups for instances that have valuable applications or services. For information about enabling backups, see Continuity management in AMS Advanced. AMS Patch Orchestrator: a tag-based patching model If you have been onboarded to the new AMS Patch Orchestrator tag-based patching model, you can use tags to apply your patch configuration to a precise set of resources, called a patch group, ranging from one instance to all of your instances. For information about AMS tags, see Using tags. Instructions on setting up Patch Orchestrator tags are provided in the following section. Patches are installed during the patch windows you define with the SSM Patch Window | Create. Each patch window is an AWS Systems Manager maintenance window that runs on a schedule of your choice, has a configured duration, and applies to one patch group. Instances that are not part of an explicit patch window are patched during the default maintenance window that you define when you onboard to Patch Orchestrator. Important If multiple patch maintenance windows are scheduled to run at the same time, they must have fewer than 1001 instances being processed at any given time. This is an AWS Systems Manager limitation. AMS recommends at least one hour per every fifty instances. By default, all operating system (OS) vendor-provided patches are installed during a maintenance window or an on-demand patch. This is called the default patch baseline. If you would like to restrict which patches are installed, you can define a custom patch baseline with one of the patch baseline create CTs (per OSes), see Patching subcategory. For example, you can use a custom patch AMS Patch Orchestrator: a tag-based patching model Version May 08, 2025 841 AMS Advanced User Guide AMS Advanced Concepts and Procedures baseline so that only critical and important security updates are installed for one or more patch groups. After patches are installed on an instance, the instance is rebooted. Patch notifications are sent before and after patching, and an additional reminder is sent within 96 hours before the scheduled start. In addition, AMS applies updates to infrastructure management tools (such as the AWS SSM agent) during the selected maintenance window. Important AMS is deprecating the monthly patch compliance reporting of instances with missing patches, and will not be sending monthly reports. This change has been made in view of the recently released self-serve operational reports that refresh every 24 hours and are available to you on demand and provide the most recent and granular data. To learn more about the reports, see Self-service reporting. To learn more about the reports, see Self- service reports. For more information on the notifications, see Patch notifications. Using Patch Orchestrator Enable AMS Patch Orchestrator for your account by submitting a service request that includes the following details: • Category: Other • Subject: Onboard to Patch Orchestrator • CC Emails: CC email addresses receive notifications when the status of this onboarding RFC changes • Details: Paste the following information into the email and provide your values. Note that the ThirdTagKey |
ams-ug-291 | ams-ug.pdf | 291 | on demand and provide the most recent and granular data. To learn more about the reports, see Self-service reporting. To learn more about the reports, see Self- service reports. For more information on the notifications, see Patch notifications. Using Patch Orchestrator Enable AMS Patch Orchestrator for your account by submitting a service request that includes the following details: • Category: Other • Subject: Onboard to Patch Orchestrator • CC Emails: CC email addresses receive notifications when the status of this onboarding RFC changes • Details: Paste the following information into the email and provide your values. Note that the ThirdTagKey is optional. For recommendations and examples, see the following table. Default maintenance window Schedule: Default Maintenance Window Schedule TimeZone: Default Maintenance Window Duration: Default Maintenance Window Cutoff: Default Patch Backup Retention In Days: Default Maintenance Window Notification Emails: First Tag Key: Using Patch Orchestrator Version May 08, 2025 842 AMS Advanced User Guide Second Tag Key: Third Tag Key: AMS Advanced Concepts and Procedures The following table describes the format and recommendations for your provided values. Patch orchestrator tag-based patching configurations Name of parameter Information Recommendation or example Default Maintenance Window Schedule The schedule of the default maintenance window in We recommend having the window run at least once the form of a cron or rate per month on a consistent expression. For example: weekday. • cron(0 3 ? * 6L *): 03:00 am on the last Friday of every month • rate(7 days): Every seven days For more information about creating cron expressions, and links to cron and rate expression resources, see Cron and rate expressions for maintenance windows. The time zone that the default maintenance window runs are based on, in Internet Assigned Numbers Authority (IANA) format. For example: • America/Los_Angeles • etc/UTC Default Maintenance Window Schedule Time Zone Default Maintenance Window Duration The duration of the default maintenance window in At least 1 hour per every 50 instances, plus 2 hours for hours. cutoff. Using Patch Orchestrator Version May 08, 2025 843 AMS Advanced User Guide AMS Advanced Concepts and Procedures Name of parameter Information Recommendation or example Default Maintenance Window Cutoff The number of hours before the end of the Default At least 2 hours. Maintenance Window in which no new patching commands are started. This interval exists to allow enough time for patching to complete before the window ends. Default Patch Backup Retention In Days (optional) The default time in days to keep the EBS restore points We recommend keeping the default, which is 60. created before patching instances. Default Maintenance Window Notification Emails One to five email addresses or distribution lists to We recommend using group distribution lists instead of receive notifications about individual emails. First Tag Key default maintenance window patching status. The first tag-key to use for creating your Patch Group tag values. Second Tag Key The second tag-key to use for creating your Patch Group tag values. For example, AppId. Specify null if you already have defined your own patch groups with a Patch Group tag. For example, Environme nt. Specify null if you have already defined your own patch groups with a Patch Group tag. Using Patch Orchestrator Version May 08, 2025 844 AMS Advanced User Guide AMS Advanced Concepts and Procedures Name of parameter Information Third Tag Key (optional) The optional third tag-key to use for creating your Patch Group tag values. Recommendation or example For example, Group. After you're onboarded to the new Patch Orchestrator patching service model, all appropriately tagged instances in your account belong to a patch group with a Patch Group tag. Patch Orchestrator uses either your existing Patch Group tag, or an AMS-created tag consisting of the two or three concatenated tag values that you specified during Patch Orchestrator onboarding. For example, {Tag Value 1}-{Tag Value 2}-{Tag Value 3}. AMS updates these AMS-applied Patch Group tags every 12 hours. If needed, you can update your Patch Group tag values with the Tag | Update (Review Required) or Tag | Update (Review Required) change types. For example, if your Amazon EC2 instance has the following tag key:value pairs: • AppId:MyApplication • Environment:Production • Group:1 During onboarding you specified the following tag keys: • First Tag Key = AppId • Second Tag Key = Environment • Third Tag Key = Group AMS creates the following Patch Group tag and applies it to your instances: Patch Group:MyApplication-Production-1. Note Patch failure alerts aren't created for instances that have unsupported operating systems, or that are stopped during the maintenance window. Using Patch Orchestrator Version May 08, 2025 845 AMS Advanced User Guide AMS Advanced Concepts and Procedures Patch Orchestrator prerequisites Patch Orchestrator workflow targets Amazon EC2 instances that are patched by latest version of System Manager Automation Document: AWSManagedServices- PatchInstanceFromMaintenanceWindow. As part of the document workflow, the run command |
ams-ug-292 | ams-ug.pdf | 292 | Key = AppId • Second Tag Key = Environment • Third Tag Key = Group AMS creates the following Patch Group tag and applies it to your instances: Patch Group:MyApplication-Production-1. Note Patch failure alerts aren't created for instances that have unsupported operating systems, or that are stopped during the maintenance window. Using Patch Orchestrator Version May 08, 2025 845 AMS Advanced User Guide AMS Advanced Concepts and Procedures Patch Orchestrator prerequisites Patch Orchestrator workflow targets Amazon EC2 instances that are patched by latest version of System Manager Automation Document: AWSManagedServices- PatchInstanceFromMaintenanceWindow. As part of the document workflow, the run command document "AWS-RunPatchBaseline" is run against each of the Amazon EC2 instances out of patch group members. To learn more, see About the SSM document AWS-RunPatchBaseline. Requirements: • Amazon EC2 instance deployed from AMS-provided Amazon Machine Image (AMI), or on an AMI through the "Stack from migration partner migrated instance" CT (ct-257p9zjk14ija). • Egress internet connection enabled. For firewall/proxy solutions the requirement is to allow Windows update endpoint and/or Linux repository mirror endpoints, AWS system manager proxy settings, and metadata proxy configuration. For more information, see Configure SSM Agent to use a proxy and Using an HTTP proxy • IAM role matching minimum permissive access for the SSM service of customer-mc-ec2- instance-profile IAM role. • We recommend 10 GB available root partition space. For Linux OS, at least 2 GB available in the /var partition. • Working and valid Certificate Authority for update downloads. • Windows Server Update Services (WSUS) - Registry including but not limited to: DisableWindowsUpdateAccess, NoWindowsUpdate; Automatic Updates must not impair operation of Windows Update process. Validation: • For Linux OS instances using yum package manager you can validate availability of updates by running #yum check-update • For Linux OS RedHat 5.7 and newer, 6.1 and newer, and 7.0 and newer; Amazon EC2 instances migrated to your AMS account via the "Stack from migration partner migrated instance" CT (ct-257p9zjk14ija), you need to validate subscription manager status for update performance. • On Windows OS, enable Windows Server Update Services (WSUS). No local policy should block WSUS ability to scan or install updates. Once logged as administrator you can validate it by Patch Orchestrator prerequisites Version May 08, 2025 846 AMS Advanced User Guide AMS Advanced Concepts and Procedures performing a scan for available updates from Windows Update Service console. Windows Server OS releases including 2012R2, 2016 and 2019 have default Windows Update settings to download and install. You can configure desired settings prior to scan. On later releases of OS, this operation can trigger installation; configure desired behavior beforehand. • Request validation from the AMS Operations team by submitting a service request: "AWSManagedServices-CheckPatchingPrerequisites Automation document to run against Amazon EC2 instance for assessment of patch readiness." Note Patch failure alerts aren't created for instances that have unsupported operating systems, or that are stopped during the maintenance window. Patch windows Instances in a specific patch group are patched during one or more patch windows. Patch windows run on a schedule defined as a cron or rate expression, and have a configurable duration intended to keep patching-related disruption within a chosen time interval. AMS recommends creating multiple patch windows that collectively cover all of your instances, to match your organization’s specific patching routines, and to use the default maintenance window as a fallback. Patch windows are created with the RFC change type Deployment | Patching | SSM patch window | Create (ct-0el2j07llrxs7). All instances that are not part of a patch window are patched during the default maintenance window created during onboarding. Normally, a patch window does not need to be updated to include new instances. Typically, this is done by modifying instance tags. For example, consider the following sequence of events: 1. Two instances are tagged with AppId:MyApplication, Environment:Production, Group:1. This produces a tag on these instances, assuming First Tag Key = AppId, Second Tag Key = Environment, Third Tag Key = Group and a patch window for MyApplication-Production-1 patch group is created. 2. Three more instances are created and tagged with AppId:MyApplication, Environment:Production, Group:1. Patch windows Version May 08, 2025 847 AMS Advanced User Guide AMS Advanced Concepts and Procedures This produces a tag for Patch Group:MyApplication-Production-1. No change to the patch window is needed because it picks up all five instances at the time of the next scheduled run. For a more detailed discussion and a walkthrough on using this change type, see SSM Patch Window | Create. Patch notifications Important Beginning February 1, 2025, AMS customers will no longer receive notifications for empty Patch Maintenance Windows in their managed accounts. The subscribed email addresses (up to five) receive an email similar to the following just before the patch maintenance window start: Dear Customer, The AMS Patch Maintenance Window THE_MAINTENANCE_WINDOW_NAME was started at: 2020-02-21T12:02:18.196Z. Details: Maintenance Window AccountId: |
ams-ug-293 | ams-ug.pdf | 293 | to the patch window is needed because it picks up all five instances at the time of the next scheduled run. For a more detailed discussion and a walkthrough on using this change type, see SSM Patch Window | Create. Patch notifications Important Beginning February 1, 2025, AMS customers will no longer receive notifications for empty Patch Maintenance Windows in their managed accounts. The subscribed email addresses (up to five) receive an email similar to the following just before the patch maintenance window start: Dear Customer, The AMS Patch Maintenance Window THE_MAINTENANCE_WINDOW_NAME was started at: 2020-02-21T12:02:18.196Z. Details: Maintenance Window AccountId: YOUR_ACCOUNT_ID Maintenance Window Region: YOUR_ACCOUNT_REGION Maintenance Window Id: THE_MAINTENANCE_WINDOW_ID Maintenance Window Name: THE_MAINTENANCE_WINDOW_NAME Maintenance Window Description: MaintenanceWindow for patching patch Group PATCH_GROUP_NAME Maintenance Window Patch Group: PATCH_GROUP_NAME Maintenance Window ExecutionId: THE_EXECUTION_ID Targets: InstanceId InstanceName StackId ------------------- -------------- ----------------------- THE_INSTANCE_ID THE_INSTANCE_NAME THE_STACK_NAME A follow-up message with a detailed report is sent as soon as the maintenance window is over. Patch notifications Version May 08, 2025 848 AMS Advanced User Guide AMS Advanced Concepts and Procedures Please raise a service request if you have any inquires about AMS Patch Orchestrator by following this URL: https://console.aws.amazon.com/managedservices/servicerequest/new Kind Regards, Amazon Web Services Amazon Managed Services Patch Team At the end of the patch activity, the subscribed email addresses receive an email similar to the following: Dear Customer, The AMS Patch Maintenance Window THE_MAINTENANCE_WINDOW_NAME ended at: 2020-02-21T12:03:20.058Z, with status: SUCCESS. Details: Maintenance Window AccountId: YOUR_ACCOUNT_ID Maintenance Window Region: YOUR_ACCOUNT_REGION Maintenance Window Id: THE_MAINTENANCE_WINDOW_ID Maintenance Window Name: THE_MAINTENANCE_WINDOW_NAME Maintenance Window Description: MaintenanceWindow for patching patch Group PATCH_GROUP_NAME Maintenance Window Patch Group: PATCH_GROUP_NAME Maintenance Window ExecutionId: THE_EXECUTION_ID Targets: RfcId InstanceId InstanceName StackId Status ----------------------- ------------------- -------------- ----------------------- -------- THE_RFC_ID THE_INSTANCE_ID THE_INSTANCE_NAME THE_STACK_NAME STATUS You can view the current Patch Compliance of your Amazon EC2 Instances by following this URL: https://console.aws.amazon.com/systems-manager/compliance?region=YOUR_ACCOUNT_REGION Please raise an Incident if an issue is impacting one of your production applications by following this URL: https://console.aws.amazon.com/managedservices/incident/new Kind Regards, Patch notifications Version May 08, 2025 849 AMS Advanced User Guide AMS Advanced Concepts and Procedures Amazon Web Services Amazon Managed Services Patch Team Every 96 hours AMS patching system identifies all upcoming patch managed maintenance windows within that 96 hours and sends a reminder notification to all subscribed email addresses that fall within that 96 hour window. This could be as little as one hours before the window, or the full 96 hours. For example: Dear Customer, The AMS Patch Maintenance Window THE_MAINTENANCE_WINDOW_NAME will start at: 2020-05-06T16:35:36.523Z. Details: Maintenance Window AccountId: YOUR_ACCOUNT_ID Maintenance Window Region: YOUR_ACCOUNT_REGION Maintenance Window Id: THE_MAINTENANCE_WINDOW_ID Maintenance Window Name: THE_MAINTENANCE_WINDOW_NAME Maintenance Window Description: MaintenanceWindow for patching patch Group PATCH_GROUP_NAME Maintenance Window Patch Group: PATCH_GROUP_NAME Maintenance Window Next Start Time: 2020-05-06T16:35:36.523Z Maintenance Window Schedule: rate(24 hours) Maintenance Window Timezone: THE_TIMEZONE At this time, these are the instances in the "PATCH_GROUP_NAME" Patch Group: InstanceId InstanceName StackId InstanceState ------------------------------------------------------------------------------------------------- THE_INSTANCE_ID THE_INSTANCE_NAME THE_STACK_NAME running/stopped THE_INSTANCE_ID THE_INSTANCE_NAME THE_STACK_NAME running/stopped THE_INSTANCE_ID THE_INSTANCE_NAME THE_STACK_NAME running/stopped A notification message is sent as soon as the maintenance window starts. You can view the current Patch Compliance of your Amazon EC2 Instances by following this URL: https://console.aws.amazon.com/systems-manager/compliance?region=YOUR_ACCOUNT_REGION If you would like to disable this maintenance window or you have inquires about the AMS Patch Orchestrator click on the following URL: https://console.aws.amazon.com/managedservices/servicerequest/new Patch notifications Version May 08, 2025 850 AMS Advanced User Guide AMS Advanced Concepts and Procedures If you would like to delete this maintenance window, you can run the CT with id "ct-0q0bic0ywqk6c" against the stack id "stack-rctyznutkyj4tkkzq". Kind Regards, Amazon Web Services Amazon Managed Services Patch Team Patch baselines By default, all operating system (OS) vendor-provided patches are installed using the AMS-default patch baseline. If you want to restrict which patches are installed, you can optionally create a patch baseline using the RFC change type Deployment | Patching | SSM patch baseline | Create OS (CT ID varies per operating system). For information about using these change types, see Patching subcategory. Patch Orchestrator reserved tags Patch Orchestrator also generates the following tags that can't be modified: • AMSPatchGroup – This tag is used for Patch Group tag value generation. You shouldn't modify the AMSPatchGroup. You can modify the "Patch Group" tag if you want to use a custom "Patch Group" value. Patch Orchestrator continues generating a value for AMSPatchGroup based on the tag-keys provided during onboarding, but won't modify the "Patch Group" tag value if it has been set to a custom value by you. To stop using a custom "Patch Group" value, you can set the value of "Patch Group" to match the AMSPatchGroup tag value. • AMSDefaultPatchGroup – This tag indicates whether an instance is part of the default maintenance window, with a value of either True or False. If an instance's Patch Group is not assigned to a maintenance window this value is set to True. |
ams-ug-294 | ams-ug.pdf | 294 | Group" value. Patch Orchestrator continues generating a value for AMSPatchGroup based on the tag-keys provided during onboarding, but won't modify the "Patch Group" tag value if it has been set to a custom value by you. To stop using a custom "Patch Group" value, you can set the value of "Patch Group" to match the AMSPatchGroup tag value. • AMSDefaultPatchGroup – This tag indicates whether an instance is part of the default maintenance window, with a value of either True or False. If an instance's Patch Group is not assigned to a maintenance window this value is set to True. On-demand patching AMS has a change type that works with your patch baseline, to enable you to run a patch on instances on demand. This can be either the default baseline you set at on boarding, or the Patch Orchestrator Systems Manager patch baseline that you set with the Patch Baseline change type (CT ID varies per operating system). Patch baselines Version May 08, 2025 851 AMS Advanced User Guide AMS Advanced Concepts and Procedures You can use the on-demand patching change type with or without Patch Orchestrator. For information about using this change type, see On Demand Patching | Run. Note You can't use instances that are part of an Auto Scaling group in an on-demand patching change type. AMS standard patching AMS supports existing customers using the AMS standard patching model, but this model is not available for new customers and is being retired in favor of AMS Patch Orchestrator. Typical patch contents for AMS standard patching include vendor updates for supported operating systems and software preinstalled with supported operating systems (for example, IIS and Apache Server). During AMS onboarding, you specify patching requirements, policy, frequency, and preferred patch windows. These configurations mean you can avoid taking applications offline all at once for infrastructure patching, so you can control what infrastructure gets patched when. Note The patching process described in this topic applies only to your stacks. AMS infrastructure is patched during a separate process. The AWS Managed Services Maintenance Window (or Maintenance Window) performs maintenance activities for AWS Managed Services (AMS) and recurs the second Thursday of every month from 3 PM to 4 PM Pacific Time. AMS may change the maintenance window with 48 hours notice. You configure the AMS patch window at onboarding, or you approve or reject the monthly patch service notification. AMS regularly scans managed Amazon EC2 instances for updates available through the operating system update functionality. We also provide regular updates to the AMS base Amazon Machine Images (AMIs) supported in our environment. After they are validated, AMS AMI releases are shared with all AMS accounts. You can view the available AWS AMI releases by using the DescribeImages Amazon EC2 API call or using the Amazon EC2 console. To find available AMS AMIs, see Find AMI IDs, AMS. AMS standard patching Version May 08, 2025 852 AMS Advanced User Guide AMS Advanced Concepts and Procedures AMS performs ad hoc patching schedules only when requested by you.Previously AMS would send a notification; currently, a notification is not sent. Note By default, AMS uses Systems Manager to apply patches by having the package manager (Linux) or System Update service (Windows) query its default repository to see which new packages are available. If, during the course of your day-to-day operations, you have installed a package on a Linux host using the default package manager, that package manager also picks up new packages for that software when they're available. In such a case, you may want to take a patching action (described in this section) to opt-out for that instance. Supported operating systems Supported operating systems (x86-64) • Amazon Linux 2023 • Amazon Linux 2 (expected AMS support end date June 30, 2025) • Oracle Linux 9.0-9.3, 8.0-8.9, 7.5-7.9 • Red Hat Enterprise Linux (RHEL) 9.0-9.4, 8.0-8.10 • SUSE Linux Enterprise Server 15 SP5 and SAP specific versions, SUSE Linux Enterprise Server 12 SP5 and SAP specific versions. • Microsoft Windows Server 2022, 2019, 2016 • Ubuntu 20.04, 22.04 Supported operating systems (ARM64) • Amazon Linux 2 (expected AMS support end date June 30, 2025) Supported patches AWS Managed Services supports patching primarily at the operating system level. The patches that are installed may differ by operating system. Supported operating systems Version May 08, 2025 853 AMS Advanced User Guide AMS Advanced Concepts and Procedures Important All updates are downloaded from the Systems Manager patch baseline service remote repositories configured on the instance, and described later in this topic. The instance must be able to connect to the repositories so the patching can be performed. To opt-out of the patch baseline service for repositories that deliver packages that you want to maintain yourself, run the following command to disable the repository: yum-config-manager DASHDASHdisable REPOSITORY_NAME Retrieve the |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.