Split (1)

train · 107k rows

id stringlengths 8 78	source stringclasses 743 values	chunk_id int64 1 5.05k	text stringlengths 593 49.7k
ams-og-190	ams-og.pdf	190	values are shown in the examples. Values in replaceable font should be changed as they are particular to your account. Create the Infrastructure This procedure utilizes the High availability two-tier stack CT followed by the Create S3 storage CT. Gathering the following data before you begin will make the deployment go more quickly. REQUIRED DATA HA STACK: • AutoScalingGroup: • UserData: This value is provided in this tutorial. It includes commands to set up the resource for CodeDeploy and start the CodeDeploy agent. • AMI-ID: This value determines the operating system of EC2 instances your Auto Scaling group (ASG) will spin up. Select an AMI in your account that starts with "customer-" and is of the operating system that you want. Find AMI IDs in the AMS Console VPCs -> VPCs details page. This walkthrough is for ASGs conﬁgured to use an Amazon Linux or RHEL AMI. • Database: • These parameters, DBEngine, EngineVersion, and LicenseModel should be set according to your situation though the values shown in the example have been tested. The tutorial uses these values, respectively: MySQL, 8.0.16, general-public-license. • These parameters, DBName, MasterUserPassword, and MasterUsername are required when deploying the application bundle. The tutorial uses these values, respectively: wordpressDB, p4ssw0rd, admin. Note that DBName can only contain alphanumeric characters. • When you enter the MasterUsername for the RDS DB, it will appear in cleartext, so log in to the database as soon as possible and change the password to ensure your security. • For RDSSubnetIds, use two Private subnets. Enter them one at a time pressing "Enter" after each. Find Subnet IDs with the For the AMS SKMS API reference, see the Reports tab in the Tutorials Version May 08, 2024 532 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information AWS Artifact Console. operation (CLI: list-subnet-summaries) or in the AMS Console VPCs -> VPC details page. • LoadBalancer: • Set this parameter, Public to true because the tutorial uses Public ELB subnets. • ELBSubnetIds: Use two Public subnets. Enter them one at a time pressing "Enter" after each. Find Subnet IDs with the For the AMS SKMS API reference, see the Reports tab in the AWS Artifact Console. operation (CLI: list-subnet-summaries) or in the AMS Console VPCs -> VPC details page. • Application: The ApplicationName value sets the CodeDeploy application name and CodeDeploy deployment group name. You use it to deploy your application. It must be unique in the account. To check your account for CodeDeploy names, see the CodeDeploy Console. The example uses WordPress but, if you will use that value, make sure that it is not already in use. 1. Launch the high availability stack. a. On the Create RFC page, select the category Deployment, subcategory Standard Stacks, item High availability two-tier stack and operation Create, from the list. b. IMPORTANT: Choose Advanced and set the values as shown. You only need to enter values for starred (*) options, tested values are shown in the example; you can leave not-required empty options blank. c. For the RFC Description section: Subject: WP-HA-2-Tier-RFC d. For the Resource information section, set parameters for AutoScalingGroup, Database, LoadBalancer, Application, and Tags. Also, the purpose of the "AppName" tag key is so you can easily search for the ASG instances in the EC2 console; you can call this tag key "Name" or any other key name that you want. Note that you can add up to 50 tags. UserData: #!/bin/bash REGION=$(curl 169.254.169.254/latest/meta-data/placement/availability-zone/ \| sed 's/[a-z]$//') yum -y install ruby httpd Tutorials Version May 08, 2024 533 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information chkconfig httpd on service httpd start touch /var/www/html/status cd /tmp curl -O https://aws-codedeploy-$REGION.s3.amazonaws.com/latest/install chmod +x ./install ./install auto chkconfig codedeploy-agent on service codedeploy-agent start AmiId: AMI-ID Description: WP-HA-2-Tier-Stack Database: LicenseModel: general-public-license (USE RADIO BUTTON) EngineVersion: 8.0.16 DBEngine: MySQL RDSSubnetIds: PRIVATE_AZ1 PRIVATE_AZ2 (ENTER ONE AT A TIME PRESSING "ENTER" AFTER EACH) MasterUserPassword: p4ssw0rd MasterUsername: admin DBName: wordpressDB LoadBalancer: Public: true (USE RADIO BUTTON) ELBSubnetIds: PUBLIC_AZ1 PUBLIC_AZ2 Application: ApplicationName: WordPress Tags: Name: WP-Rhel-Stack e. Click Submit when ﬁnished. Log in to the database that you created and change the password. Launch an S3 bucket Stack. 2. 3. Gathering the following data before you begin will make the deployment go more quickly. REQUIRED DATA S3 BUCKET: • VPC-ID: This value determines where your S3 Bucket will be. Find VPC IDs with the For the AMS SKMS API reference, see the Reports tab in the AWS Artifact Console. operation (CLI: list-vpc-summaries) or in the AMS Console VPCs page. Tutorials Version May 08, 2024 534 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information • BucketName: This value sets the S3 Bucket name, you use it to upload your application bundle. It must be unique across the region of the account and cannot include upper-case letters. Including your account
ams-og-191	ams-og.pdf	191	the deployment go more quickly. REQUIRED DATA S3 BUCKET: • VPC-ID: This value determines where your S3 Bucket will be. Find VPC IDs with the For the AMS SKMS API reference, see the Reports tab in the AWS Artifact Console. operation (CLI: list-vpc-summaries) or in the AMS Console VPCs page. Tutorials Version May 08, 2024 534 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information • BucketName: This value sets the S3 Bucket name, you use it to upload your application bundle. It must be unique across the region of the account and cannot include upper-case letters. Including your account ID as part of the BucketName is not a requirement but makes it easier to identify the bucket later. To see what S3 bucket names exist in the account, go to the Amazon S3 Console for your account. a. On the Create RFC page, select the category Deployment, subcategory Advanced Stack Components, item S3 storage, and operation Create from the RFC CT pick list. b. Keep the default Basic option and set the values as shown. Subject: S3-Bucket-WP-HA-RFC Description: S3BucketForWordPressBundles BucketName: ACCOUNT_ID-BUCKET_NAME AccessControl: Private VpcId: VPC_ID Name: S3-Bucket-WP-HA-Stack TimeoutInMinutes: 60 c. Click Submit when ﬁnished. The bucket deployed with this change type allows full read/ write access to the whole account. Create, Upload, and Deploy the Application First, create a WordPress application bundle, and then use the CodeDeploy CTs to create and deploy the application. 1. Download WordPress, extract the ﬁles and create a ./scripts directory. Linux command: wget https://github.com/WordPress/WordPress/archive/master.zip Windows: Paste https://github.com/WordPress/WordPress/archive/master.zip into a browser window and download the zip ﬁle. Create a temporary directory in which to assemble the package. Linux: Tutorials Version May 08, 2024 535 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information mkdir /tmp/WordPress Windows: Create a "WordPress" directory, you will use the directory path later. 2. Extract the WordPress source to the "WordPress" directory and create a ./scripts directory. Linux: unzip master.zip -d /tmp/WordPress_Temp cp -paf /tmp/WordPress_Temp/WordPress-master/* /tmp/WordPress rm -rf /tmp/WordPress_Temp rm -f master cd /tmp/WordPress mkdir scripts Windows: Go to the "WordPress" directory that you created and create a "scripts" directory there. If you are in a Windows environment, be sure to set the break type for the script ﬁles to Unix (LF). In Notepad ++, this is an option at the bottom right of the window. 3. Create the CodeDeploy appspec.yml ﬁle, in the WordPress directory (if copying the example, check the indentation, each space counts). IMPORTANT: Ensure that the "source" path is correct for copying the WordPress ﬁles (in this case, in your WordPress directory) to the expected destination (/var/www/html/WordPress). In the example, the appspec.yml ﬁle is in the directory with the WordPress ﬁles, so only "/" is needed. Also, even if you used a RHEL AMI for your Auto Scaling group, leave the "os: linux" line as-is. Example appspec.yml ﬁle: version: 0.0 os: linux files: - source: / destination: /var/www/html/WordPress hooks: BeforeInstall: - location: scripts/install_dependencies.sh timeout: 300 runas: root AfterInstall: - location: scripts/config_wordpress.sh timeout: 300 Tutorials Version May 08, 2024 536 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information runas: root ApplicationStart: - location: scripts/start_server.sh timeout: 300 runas: root ApplicationStop: - location: scripts/stop_server.sh timeout: 300 runas: root 4. Create bash ﬁle scripts in the WordPress ./scripts directory. First, create config_wordpress.sh with the following content (if you prefer, you can edit the wp-conﬁg.php ﬁle directly). Note Replace DBName with the value given in the HA Stack RFC (for example, wordpress). Replace DB_MasterUsername with the MasterUsername value given in the HA Stack RFC (for example, admin). Replace DB_MasterUserPassword with the MasterUserPassword value given in the HA Stack RFC (for example, p4ssw0rd). Replace DB_ENDPOINT with the endpoint DNS name in the execution outputs of the HA Stack RFC (for example, srt1cz23n45sfg.clgvd67uvydk.us- east-1.rds.amazonaws.com). You can ﬁnd this with the GetRfc operation (CLI: get- rfc --rfc-id RFC_ID) or in the AMS Console RFC details page for the HA Stack RFC that you previously submitted. #!/bin/bash chmod -R 755 /var/www/html/WordPress cp /var/www/html/WordPress/wp-config-sample.php /var/www/html/WordPress/wp- config.php cd /var/www/html/WordPress sed -i "s/database_name_here/DBName/g" wp-config.php sed -i "s/username_here/DB_MasterUsername/g" wp-config.php sed -i "s/password_here/DB_MasterUserPassword/g" wp-config.php sed -i "s/localhost/DB_ENDPOINT/g" wp-config.php 5. In the same directory create install_dependencies.sh with the following content: Tutorials Version May 08, 2024 537 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information #!/bin/bash yum install -y php yum install -y php-mysql yum install -y mysql service httpd restart Note HTTPS is installed as part of the user data at launch in order to allow health checks to work from the start. 6. In the same directory create start_server.sh with the following content: • For Amazon Linux instances, use this: #!/bin/bash service httpd start • For RHEL instances, use this (the extra commands are policies that allow SELINUX to accept WordPress): #!/bin/bash setsebool -P httpd_can_network_connect_db 1 setsebool -P httpd_can_network_connect 1 chcon -t httpd_sys_rw_content_t /var/www/html/WordPress/wp-content -R restorecon -Rv /var/www/html service
ams-og-192	ams-og.pdf	192	Advanced Account Onboarding Information #!/bin/bash yum install -y php yum install -y php-mysql yum install -y mysql service httpd restart Note HTTPS is installed as part of the user data at launch in order to allow health checks to work from the start. 6. In the same directory create start_server.sh with the following content: • For Amazon Linux instances, use this: #!/bin/bash service httpd start • For RHEL instances, use this (the extra commands are policies that allow SELINUX to accept WordPress): #!/bin/bash setsebool -P httpd_can_network_connect_db 1 setsebool -P httpd_can_network_connect 1 chcon -t httpd_sys_rw_content_t /var/www/html/WordPress/wp-content -R restorecon -Rv /var/www/html service httpd start 7. In the same directory create stop_server.sh with the following content: #!/bin/bash service httpd stop 8. Create the zip bundle. Linux: $ cd /tmp/WordPress $ zip -r wordpress.zip . Tutorials Version May 08, 2024 538 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Windows: Go to your "WordPress" directory and select all of the ﬁles and create a zip ﬁle, be sure to name it wordpress.zip. 1. Upload the application bundle to the S3 bucket The package needs to be in place in order to continue deploying the stack. You automatically have access to any S3 bucket instance that you create. You can access it through your Bastions (see Accessing Instances), or through the S3 console, and upload the CodeDeploy package with drag-and-drop, or by browsing to and selecting the ﬁle. You can also use the following command in a shell window; be sure that you have the correct path to the zip ﬁle: aws s3 cp wordpress/wordpress.zip s3://BUCKET_NAME/ 2. Deploy the WordPress CodeDeploy Application Bundle REQUIRED DATA CODEDEPLOY APPLICATION DEPLOYMENT: • CodeDeployApplicationName: The name you gave the CodeDeploy application. • CodeDeployGroupName: Since the CodeDeploy application and group were both created from the name you gave the CodeDeploy application in the HA stack RFC, this is the same name as the CodeDeployApplicationName. • S3Bucket: The name you gave the S3 bucket. • S3BundleType and S3Key: These are part of the WordPress application bundle you deployed. • VpcId: The relevant VPC. a. On the Create RFC page, select the category Deployment, subcategory Applications, item CodeDeploy application, and operation Deploy from the RFC CT pick list. b. Keep the default Basic option, and set the values as shown. Tutorials Version May 08, 2024 539 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Note Reference the CodeDeploy application, CodeDeploy deployment group, S3 bucket and bundle previously created. Subject: WP-CD-Deploy-RFC Description: DeployWordPress S3Bucket: BUCKET_NAME S3Key: wordpress.zip S3BundleType: zip CodeDeployApplicationName: WordPress CodeDeployDeploymentGroupName: WordPress CodeDeployIgnoreApplicationStopFailures: false RevisionType: S3 VpcId: VPC_ID Name: WP-CD-Deploy-Op TimeoutInMinutes: 60 c. Click Submit when ﬁnished. Validate the Application Deployment Navigate to the endpoint (LoadBalancerCName) of the previously-created load balancer, with the WordPress deployed path: /WordPress. For example: http://stack-ID-FOR-ELB.us-east-1.elb.amazonaws.com/WordPress You should see a page like this: Tutorials Version May 08, 2024 540 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Tear Down the High Availability Deployment To tear down the deployment, you submit the Delete Stack CT against the HA Two-Tier stack, and the S3 bucket, and you can request that RDS snapshots be deleted (they are deleted automatically after ten days, but they do cost a small amount while there). Gather the stack IDs for the HA stack and the S3 bucket and then follow these steps. See Stack \| Delete. Tutorials Version May 08, 2024 541 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Appendix: SALZ onboarding questionnaire Topics • Deployment summary • Environment architecture considerations • Single-Account Landing Zone Monitoring Alerts • Maintenance Window • Next Steps This is some of the information that you will need to think about before onboarding an account. Deployment summary A description of the deployment. For example: • This account is for a Line-of-Business application deployment (as opposed to a Product application deployment). • The deployment involves an auto-scaled ARP (authenticated reverse proxy) within the account’s public or DMZ subnet. • Web and application servers will be deployed within the account's private subnet. • An RDS (Amazon Relational Database Service) instance will also be deployed within the account’s private Subnet. • The servers (ARP, web, application, database, load balancer, etc.) are separated into distinct security groups. • The account requires an HA (high availability) design spread across availability zones (AZs) i.e. "Multi-AZ". Environment architecture considerations Consider the following criteria in deciding how to conﬁgure your environment and architecture. • Will your virtual data center connect back to your corporate network? • Do you have an existing AWS DirectConnect service or do you require a new DirectConnect service? Appendix: SALZ onboarding questionnaire Version May 08, 2024 542 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information • Do you have an existing VPN connection or do you require a new VPN service? • What is the available CIDR block
ams-og-193	ams-og.pdf	193	account requires an HA (high availability) design spread across availability zones (AZs) i.e. "Multi-AZ". Environment architecture considerations Consider the following criteria in deciding how to conﬁgure your environment and architecture. • Will your virtual data center connect back to your corporate network? • Do you have an existing AWS DirectConnect service or do you require a new DirectConnect service? Appendix: SALZ onboarding questionnaire Version May 08, 2024 542 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information • Do you have an existing VPN connection or do you require a new VPN service? • What is the available CIDR block range of internal addresses that you could allocate? (/16 recommended, must not overlap corporate network ranges) • Will your virtual data center require internet access? • Which Region(s) do you intend to use? (Sydney/N. Virginia/Dublin) • Will you require a Shared Services subnet to host applications that have connectivity to all other subnets? • What are your organizational divisions that you would like to be hosted as separate subnets. For each: • What connectivity to other subnets do you need? • Does the subnet require Internet access? • Are there any application deployment restrictions to that subnet? • Are there any particular network requirements for that subnet? • Would you like separate development and/or test environments? (Will include shared services duplicate for anytime access) • What are your snapshot backup requirements? • Do you have an existing maintenance process or patch window(s) that you would like to keep? • What are your domain registration requirements? • Do you have any single sign-on requirements? (e.g., AD, LDAP) • What are your overall expected operating system and anticipated capacity requirements? Single-Account Landing Zone Monitoring Alerts AMS provides a way for you to be directly alerted (versus getting AMS service notiﬁcations) for certain monitoring alerts. To sign up for this, make sure that your Cloud Architect (CA or Cloud Service Delivery Manager (CSDM) receive this information: Direct Alerts Email: These are the email addresses that you want AMS to send certain resource- based alerts to. For details of which alerts are sent directly to email, see Alerts from Baseline Monitoring in AMS in the AMS User Guide for Single-Account Landing Zone. For more information on AMS monitoring, see Monitoring Management in the AMS User Guide for Single-Account Landing Zone. Single-Account Landing Zone Monitoring Alerts Version May 08, 2024 543 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Maintenance Window You will want to create a maintenance window that considers diﬀerent application needs, diﬀerent AWS Regions, and diﬀerent stress periods. Your maintenance window is when AMS will apply patching. Here are some guidelines: • To limit the impact on users, plan your maintenance window according to the AWS Region where your environments are deployed. • Schedule a window outside of regular business hours and when the least traﬃc is expected on production servers. • Typically, infrastructure stacks require monthly updates. • Schedule a maintenance window for at least 300 minutes. Operating system patching takes 60-90 minutes, infrastructure stack patching takes 180-300 minutes. Next Steps The AMS onboarding team will assist you in every step of onboarding your account to AMS. These are onboarding requirements: • Provision a new AWS account to use for AMS and provide an AWS account ID. • Sign up for the desired level of Support. • Create a cross-account IAM role to grant the AMS provisioning account access and provide the role name to AMS. • Add the account 753102745277 as a Trusted Entity. Maintenance Window Version May 08, 2024 544 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Appendix: ActiveDirectory Federation Services (ADFS) claim rule and SAML settings For detailed step-by-step instructions on how to install and conﬁgure AD FS see Enabling Federation to AWS Using Windows Active Directory, ADFS, and SAML 2.0. ADFS claim rule conﬁgurations If you already have an ADFS implementation, conﬁgure following: • Relying party trust • Claims rules The relying party trust and claims rules steps are taken from Enabling Federation to AWS Using Windows Active Directory, AD FS, and SAML 2.0blog • Claims rules: • Nameid: Conﬁguration per blog post • RoleSessionName: Conﬁgure as follows • Claim rule name: RoleSessionName • Attribute store: Active Directory • LDAP Attribute: SAM-Account-Name • Outgoing Claim Type: https://aws.amazon.com/SAML/Attributes/ RoleSessionName • Get AD Groups: Conﬁguration per blog post • Role claim: Conﬁgure as follows c:[Type == "http://temp/variable", Value =~ "(?i)^AWS-([^d]{12})-"] => issue(Type = "https://aws.amazon.com/SAML/Attributes/Role", Value = RegExReplace(c.Value, "AWS-([^d]{12})-", "arn:aws:iam::$1:saml-provider/ customer-readonly-saml,arn:aws:iam::$1:role/")); ADFS claim rule conﬁgurations Version May 08, 2024 545 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Web console You can access the AWS Web console by using the link below replacing [ADFS-FQDN] with the FQDN of your ADFS implementation. https://[ADFS-FQDN]/adfs/ls/IdpInitiatedSignOn.aspx Your IT department can deploy the above link to the user population via a
ams-og-194	ams-og.pdf	194	Attribute store: Active Directory • LDAP Attribute: SAM-Account-Name • Outgoing Claim Type: https://aws.amazon.com/SAML/Attributes/ RoleSessionName • Get AD Groups: Conﬁguration per blog post • Role claim: Conﬁgure as follows c:[Type == "http://temp/variable", Value =~ "(?i)^AWS-([^d]{12})-"] => issue(Type = "https://aws.amazon.com/SAML/Attributes/Role", Value = RegExReplace(c.Value, "AWS-([^d]{12})-", "arn:aws:iam::$1:saml-provider/ customer-readonly-saml,arn:aws:iam::$1:role/")); ADFS claim rule conﬁgurations Version May 08, 2024 545 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Web console You can access the AWS Web console by using the link below replacing [ADFS-FQDN] with the FQDN of your ADFS implementation. https://[ADFS-FQDN]/adfs/ls/IdpInitiatedSignOn.aspx Your IT department can deploy the above link to the user population via a Group Policy. API and CLI access with SAML How to conﬁgure API and CLI access with SAML. The python packages are sourced from the blog posts below: • NTLM: How to Implement Federated API and CLI Access Using SAML 2.0 and AD FS • Forms: How to Implement a General Solution for Federated API/CLI Access Using SAML 2.0 • PowerShell: How to Set Up Federated API Access to AWS by Using Windows PowerShell Script conﬁguration 1. Using Notepad++, change the default region to the correct region 2. Using Notepad++, disable SSL veriﬁcation for test and dev environments 3. Using Notepad++, conﬁgure idpentryurl https://[ADFS-FDQN]/adfs/ls/IdpInitiatedSignOn.aspx? loginToRp=urn:amazon:webservices Windows conﬁguration The instructions below are for the python packages. The credentials generated will be valid for 1 hour. 1. Download and install python (2.7.11) 2. Download and install AWS CLI tools 3. Install the AMS CLI: Web console Version May 08, 2024 546 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information a. Download the AMS distributables zip ﬁle provided by your cloud service delivery manager (CSDM) and unzip. Several directories and ﬁles are made available. b. Open either the Managed Cloud Distributables -> CLI -> Windows or the Managed Cloud Distributables -> CLI -> Linux / MacOS directory, depending on your operating system, and: For Windows, execute the appropriate installer (this method only works on Windows 32 or 64 bits systems): • 32 Bits: ManagedCloudAPI_x86.msi • 64 Bits: ManagedCloudAPI_x64.msi For Mac/Linux, execute the ﬁle named: MC_CLI.sh. You can do this by running this command: sh MC_CLI.sh. Note that the amscm and amsskms directories and their contents must be in the same directory as the MC_CLI.sh ﬁle. c. If your corporate credentials are used via federation with AWS (the AMS default conﬁguration) you must install a credential management tool that can access your federation service. For example, you can use this AWS Security Blog How to Implement Federated API and CLI Access Using SAML 2.0 and AD FS for help conﬁguring your credential management tooling. d. After the installation, run aws amscm help and aws amsskms help to see commands and options. 4. Download the required SAML script Download to c:\aws\scripts 5. Download PIP Download to c:\aws\downloads 6. Using PowerShell, install PIP <pythondir>.\python.exe c:\aws\downloads\get-pip.py 7. Using PowerShell, install boto module <pythondir\scripts>pip install boto Windows conﬁguration Version May 08, 2024 547 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information 8. Using PowerShell, install requests module <pythondir\scripts>pip install requests 9. Using PowerShell, install requests security module <pythondir\scripts>pip install requests[security] 10. Using PowerShell, install beautifulsoup module <pythondir\scripts>pip install beautifulsoup4 11. Using PowerShell, create a folder called .aws in the users proﬁle (%userproﬁle%\.aws) mkdir .aws 12. Using PowerShell, create a credential ﬁle in the .aws folder New-Item credentials -type ﬁle –force The credentials ﬁle mustn’t have a ﬁle extension The ﬁlename must be all lowercase and have the name credentials 13. Open the credentials ﬁle with notepad and paste in the following data, specifying the correct region [default] output = json region = us-east-1 aws_access_key_id = aws_secret_access_key = 14. Using PowerShell, the SAML script and logon <pythondir>.\python.exe c:\aws\scripts\samlapi.py Username: [USERNAME]@upn Choose the role you would like to assume Linux conﬁguration The credentials generated will be valid for 1 hour. Linux conﬁguration Version May 08, 2024 548 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information 1. Using WinSCP, transfer the SAML script 2. Using WinSCP, transfer the Root CA certiﬁcate (ignore for test and dev) 3. Add the ROOT CA to the trusted root certiﬁcates (ignore for test and dev) $ openssl x509 -inform der -in [certname].cer -out certiﬁcate.pem (ignore for test and dev) Add contents of certiﬁcate.pem to end of /etc/ssl/certs/ca-bundle.crt ﬁle ((ignore for test dev) 4. Create .aws folder in home/ec2-user 5 [default] output = json region = us-east-1 aws_access_key_id = aws_secret_access_key = 5. Using WinSCP, transfer the credentials ﬁle to .aws folder 6. Install boto module $ sudo pip install boto 7. Install requests module $ sudo pip install requests 8. Install beautifulsoup module $ sudo pip install beautifulsoup4 9. Copy the script to home/ec2-user Set the required permissions Execute the script: samlapi.py Linux conﬁguration Version May 08, 2024 549 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Document history The following table describes
ams-og-195	ams-og.pdf	195	to end of /etc/ssl/certs/ca-bundle.crt ﬁle ((ignore for test dev) 4. Create .aws folder in home/ec2-user 5 [default] output = json region = us-east-1 aws_access_key_id = aws_secret_access_key = 5. Using WinSCP, transfer the credentials ﬁle to .aws folder 6. Install boto module $ sudo pip install boto 7. Install requests module $ sudo pip install requests 8. Install beautifulsoup module $ sudo pip install beautifulsoup4 9. Copy the script to home/ec2-user Set the required permissions Execute the script: samlapi.py Linux conﬁguration Version May 08, 2024 549 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Document history The following table describes the important changes to the documentation since the last release of AMS. • API version: 2019-05-21 • Latest documentation update: March 21, 2024 Change Description Added link for prescription guidance Set up consolidated billing–link new account to Payer account. Updated instructions to activate IAM access to the AWS Management Console Clariﬁed the instructions for activating IAM access to the AWS Management Console. Updated number of allowed transit virtual interfaces on Direct Connect dedicated connections now have a limit of 4 transit virtual interfaces per Direct Connect dedicated connection connections Improve wording. Speciﬁed that "only used as a "Deny" list " must include "Allow All" to ensure AMS monitoring and management operations. Date May 08, 2025 Activate IAM access to the AWS console Connectin g Direct Connect to Transit Gateway Network conﬁguration Additional information on using the AMS CLI. "Added note that the --region option may be needed for some CLI commands" Install the AMS CLIs Updated: Chapter headings for consistency and readabili y, moved some topic sub-secti ons into more appropriate sections "Modes for change management" is the new heading for "Change management" Change management modes Version May 08, 2024 550 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Change Description Updated content Updated content The AMS mode previously known as "Change Management mode" or "Standard CM mode" is now known as "RFC mode." The modes section has been expanded. The AMS mode previously known as "Change Management mode" or "Standard CM mode" is now known as "RFC mode." The modes section has been shortened and links to the AMS Advanced User Guide sections on modes added. Date RFC mode. AMS modes. MALZ: Updated network architecture diagram Networking account architecturem June 16, 2022 Moved topic list to below opening paragraphs AWS Managed Services Onboarding Introduct ion June 16, 2022 Updated content, inclusive language initiative "Management account" not "Master account. Updated content, Tools account role names Updated role name CustomerMigrationA ccessRole to AWSManagedServicesMigration Role. IAM user role in AMS , "Policy examples" section AWS Application Migration Service (AWS MGN) SALZ: Continuity managemen t defaults Updated link and removed obsolete informati on from VPC tag and defaults February 28, 2022 Version May 08, 2024 551 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information AWS Glossary For the latest AWS terminology, see the AWS glossary in the AWS Glossary Reference. Version May 08, 2024 552
ams-ug-001	ams-ug.pdf	1	AMS Advanced Concepts and Procedures AMS Advanced User Guide Version May 08, 2025 Copyright © 2025 Amazon Web Services, Inc. and/or its aﬃliates. All rights reserved. AMS Advanced User Guide AMS Advanced Concepts and Procedures AMS Advanced User Guide: AMS Advanced Concepts and Procedures Copyright © 2025 Amazon Web Services, Inc. and/or its aﬃliates. All rights reserved. Amazon's trademarks and trade dress may not be used in connection with any product or service that is not Amazon's, in any manner that is likely to cause confusion among customers, or in any manner that disparages or discredits Amazon. All other trademarks not owned by Amazon are the property of their respective owners, who may or may not be aﬃliated with, connected to, or sponsored by Amazon. AMS Advanced User Guide AMS Advanced Concepts and Procedures Table of Contents What is AWS Managed Services? .................................................................................................... 1 About this guide ........................................................................................................................................... 3 Operations plans ........................................................................................................................................... 3 Accelerate operations plan .................................................................................................................... 4 Advanced operations plan ..................................................................................................................... 4 Getting started .............................................................................................................................................. 4 Key terms ....................................................................................................................................................... 5 Service description ..................................................................................................................................... 11 AWS Managed Services (AMS) AMS Advanced operation plan features .................................... 11 What we do, what we do not do ...................................................................................................... 16 AMS responsibility matrix (RACI) ....................................................................................................... 17 AMS environment basic components ............................................................................................... 39 AMS account limits ............................................................................................................................... 42 AMS service level objectives (SLOs) .................................................................................................. 44 Supported AWS services ..................................................................................................................... 46 Supported conﬁgurations ................................................................................................................... 49 Unsupported operating systems ....................................................................................................... 51 AMS Advanced interfaces .................................................................................................................... 52 VPC endpoints ....................................................................................................................................... 53 AMS protected namespaces ............................................................................................................... 54 AMS reserved preﬁxes ......................................................................................................................... 55 AMS maintenance window .................................................................................................................. 56 AMS information resources ...................................................................................................................... 56 AMS compliance ......................................................................................................................................... 57 AMS Supported Compliance Standards ........................................................................................... 58 Shared Responsibility ........................................................................................................................... 61 AMS Amazon Machine Images (AMIs) .................................................................................................... 61 Security enhanced AMIs ...................................................................................................................... 64 How integration between AD FS and AMS works ............................................................................... 65 AMS Managed Active Directory ............................................................................................................... 66 Application deployments .......................................................................................................................... 69 Service management ..................................................................................................................... 71 Account governance ................................................................................................................................... 71 Service commencement ............................................................................................................................ 72 Version May 08, 2025 iii AMS Advanced User Guide AMS Advanced Concepts and Procedures Customer relationship management (CRM) .......................................................................................... 72 CRM Process ........................................................................................................................................... 73 CRM meetings ........................................................................................................................................ 74 CRM Meeting Arrangements ............................................................................................................... 75 CRM monthly reports ........................................................................................................................... 76 Cost optimization ....................................................................................................................................... 77 Cost optimization framework ............................................................................................................. 77 Cost optimization responsibility matrix ........................................................................................... 79 Service hours ............................................................................................................................................... 81 Getting help ................................................................................................................................................ 82 Planned event management ......................................................................................................... 83 AMS PEM criteria ........................................................................................................................................ 83 Types of PEM .............................................................................................................................................. 83 The AMS PEM process ............................................................................................................................... 84 PEM FAQs ..................................................................................................................................................... 84 Network architecture .................................................................................................................... 86 MALZ network architecture ...................................................................................................................... 86 About multi-account landing zone network architecture ............................................................. 86 Choosing single MALZ or multiple MALZs ....................................................................................... 89 Multi-Account Landing Zone accounts ............................................................................................. 94 SALZ network architecture .................................................................................................................... 139 AMS Single-account landing zone shared services ...................................................................... 141 Setting up AMS ............................................................................................................................ 143 AMS default settings ............................................................................................................................... 144 DNS resolution defaults (MALZ) ...................................................................................................... 144 EC2 IAM instance proﬁle ................................................................................................................... 145 Alerts from baseline monitoring in AMS ....................................................................................... 152 Log retention and rotation defaults ............................................................................................... 168 Using the AMS consoles ......................................................................................................................... 169 Using the AMS API and CLI ................................................................................................................... 170 AMS API HTTP endpoints for REST calls ....................................................................................... 170 Installing or upgrading the AMS CLI .............................................................................................. 171 Using the AMS API in CLI, Ruby, Python, and Java ..................................................................... 173 AMS bring your own EPS ....................................................................................................................... 182 Turn on BYOEPS for your account .................................................................................................. 183 Receiving AMS notiﬁcations .................................................................................................................. 186 Version May 08, 2025 iv AMS Advanced User Guide AMS Advanced Concepts and Procedures AMS AMI notiﬁcations with SNS ..................................................................................................... 188 Service notiﬁcations ........................................................................................................................... 191 RFC state change notiﬁcations ........................................................................................................ 192 Setting up private and public DNS ...................................................................................................... 196 AMS egress traﬃc management .......................................................................................................... 200 Deploying IAM resources ........................................................................................................................ 201 Automated IAM Provisioning ........................................................................................................... 202 Setting permissions with IAM roles and proﬁles ............................................................................... 224 Requesting a new IAM user role or instance proﬁle ................................................................... 224 Restrict permissions with IAM role policy statements ................................................................ 225 Restrict permissions with Amazon EC2 IAM instance proﬁles ................................................... 227 AD FS claim rule and SAML settings ................................................................................................... 228 ADFS claim rule conﬁgurations ....................................................................................................... 228 Web console ........................................................................................................................................ 229 API and CLI access with SAML ......................................................................................................... 229 Restrict with network ACL ..................................................................................................................... 233 AMS on Outposts ..................................................................................................................................... 233 AWS Outposts installation and operational management ........................................................ 234 Provisioning AMS managed resources on AWS Outposts .......................................................... 236 Limitations of AMS on AWS Outposts ........................................................................................... 237 AMS on AWS Outposts compliance ................................................................................................ 238 AMS on AWS Outposts FAQs ........................................................................................................... 239 Using tags .................................................................................................................................................. 241 AMS infrastructure automatic tagging .......................................................................................... 242 AMS recommended tags ................................................................................................................... 244 Tag bulk update notes ...................................................................................................................... 248 Resource Scheduler ................................................................................................................................. 250 Deploying Resource Scheduler ........................................................................................................ 251 Customizing Resource Scheduler .................................................................................................... 251 Using Resource Scheduler ................................................................................................................. 252 AMS Resource Scheduler cost estimator ....................................................................................... 252 AMS Resource Scheduler best practices ........................................................................................ 254 AWS Systems Manager in AMS Advanced .......................................................................................... 256 Available AMS Advanced SSM documents .................................................................................... 256 AMS Advanced SSM document versions ........................................................................................ 256 Systems Manager
ams-ug-002	ams-ug.pdf	2	Limitations of AMS on AWS Outposts ........................................................................................... 237 AMS on AWS Outposts compliance ................................................................................................ 238 AMS on AWS Outposts FAQs ........................................................................................................... 239 Using tags .................................................................................................................................................. 241 AMS infrastructure automatic tagging .......................................................................................... 242 AMS recommended tags ................................................................................................................... 244 Tag bulk update notes ...................................................................................................................... 248 Resource Scheduler ................................................................................................................................. 250 Deploying Resource Scheduler ........................................................................................................ 251 Customizing Resource Scheduler .................................................................................................... 251 Using Resource Scheduler ................................................................................................................. 252 AMS Resource Scheduler cost estimator ....................................................................................... 252 AMS Resource Scheduler best practices ........................................................................................ 254 AWS Systems Manager in AMS Advanced .......................................................................................... 256 Available AMS Advanced SSM documents .................................................................................... 256 AMS Advanced SSM document versions ........................................................................................ 256 Systems Manager pricing .................................................................................................................. 257 Version May 08, 2025 v AMS Advanced User Guide AMS Advanced Concepts and Procedures Oﬀboard AMS accounts .......................................................................................................................... 257 Oﬀboard from single-account landing zone accounts ................................................................ 258 Oﬀboard from multi-account landing zone accounts ................................................................. 262 Change management modes ...................................................................................................... 281 Modes overview ....................................................................................................................................... 282 Types of modes and accounts in AMS ........................................................................................... 282 AMS modes and applications or workloads .................................................................................. 287 Real world use cases for AMS modes ............................................................................................ 295 RFC mode .................................................................................................................................................. 299 Learn about RFCs ............................................................................................................................... 299 What are change types? .................................................................................................................... 345 Troubleshooting RFC errors .............................................................................................................. 357 Direct Change mode ............................................................................................................................... 368 Getting Started with Direct Change mode ................................................................................... 369 Security and compliance ................................................................................................................... 371 Change management in Direct Change mode ............................................................................. 376 Creating stacks using Direct Change mode .................................................................................. 379 Direct Change Mode use cases ........................................................................................................ 382 Developer mode ....................................................................................................................................... 383 Getting started with Developer mode ........................................................................................... 384 Security and compliance ................................................................................................................... 386 Change management ......................................................................................................................... 388 Provisioning infrastructure ............................................................................................................... 393 Detective controls ............................................................................................................................... 394 Logging, monitoring, and event management ............................................................................. 394 Incident management ........................................................................................................................ 394 Patch management ............................................................................................................................ 394 Continuity management ................................................................................................................... 395 Security and access management ................................................................................................... 395 Self-Service Provisioning mode in AMS .............................................................................................. 395 Getting started with SSP mode in AMS ........................................................................................ 396 Amazon API Gateway ........................................................................................................................ 397 Alexa for Business .............................................................................................................................. 398 Amazon AppStream 2.0 .................................................................................................................... 399 Amazon Athena ................................................................................................................................... 402 Amazon Bedrock ................................................................................................................................. 402 Version May 08, 2025 vi AMS Advanced User Guide AMS Advanced Concepts and Procedures Amazon CloudSearch ......................................................................................................................... 404 Amazon CloudWatch Synthetics ...................................................................................................... 405 Amazon Cognito ................................................................................................................................. 406 Amazon Comprehend ........................................................................................................................ 407 Amazon Connect ................................................................................................................................. 408 Amazon Data Firehose ...................................................................................................................... 410 Amazon DevOps Guru ........................................................................................................................ 411 Amazon DocumentDB (with MongoDB compatibility) ................................................................ 412 Amazon DynamoDB ........................................................................................................................... 413 Amazon Elastic Container Registry ................................................................................................. 414 EC2 Image Builder .............................................................................................................................. 415 Amazon ECS on AWS Fargate .......................................................................................................... 417 Amazon EKS on AWS Fargate .......................................................................................................... 419 Amazon EMR ....................................................................................................................................... 422 Amazon EventBridge .......................................................................................................................... 425 Amazon Forecast ................................................................................................................................ 427 Amazon FSx ......................................................................................................................................... 430 Amazon FSx for OpenZFS ................................................................................................................. 431 Amazon FSx for NetApp ONTAP ..................................................................................................... 433 Amazon Inspector Classic ................................................................................................................. 434 Amazon Kendra ................................................................................................................................... 435 Amazon Kinesis Data Streams ......................................................................................................... 436 Amazon Kinesis Video Streams ....................................................................................................... 437 Amazon Lex ......................................................................................................................................... 438 Amazon MQ ......................................................................................................................................... 438 Amazon Managed Service for Apache Flink ................................................................................. 439 Amazon Managed Streaming for Apache Kafka .......................................................................... 441 Amazon Managed Service for Prometheus ................................................................................... 442 Amazon Personalize ........................................................................................................................... 443 Amazon QuickSight ............................................................................................................................ 445 Amazon Rekognition .......................................................................................................................... 447 Amazon SageMaker AI ....................................................................................................................... 448 Amazon Simple Email Service ......................................................................................................... 451 Amazon Simple Workﬂow Service .................................................................................................. 452 Amazon Textract ................................................................................................................................. 453 Amazon Transcribe ............................................................................................................................. 454 Version May 08, 2025 vii AMS Advanced User Guide AMS Advanced Concepts and Procedures Amazon WorkDocs ............................................................................................................................. 455 Amazon WorkSpaces .......................................................................................................................... 456 AMS Code services ............................................................................................................................. 458 AWS Amplify ........................................................................................................................................ 461 AWS AppSync ...................................................................................................................................... 462 AWS App Mesh .................................................................................................................................... 463 AWS Audit Manager ........................................................................................................................... 463 AWS Batch ............................................................................................................................................ 465 AWS Certiﬁcate Manager .................................................................................................................. 466 AWS Private Certiﬁcate Authority ................................................................................................... 467 AWS CloudEndure ............................................................................................................................... 470 AWS CloudHSM ................................................................................................................................... 471 AWS CodeBuild ................................................................................................................................... 472 AWS CodeCommit .............................................................................................................................. 474 AWS CodeDeploy ................................................................................................................................ 475 AWS CodePipeline .............................................................................................................................. 476 AWS Compute Optimizer .................................................................................................................. 478 AWS DataSync ..................................................................................................................................... 479 AWS Device Farm ............................................................................................................................... 481 AWS Elastic Disaster Recovery ......................................................................................................... 481 AWS Elemental MediaConvert ......................................................................................................... 483 AWS Elemental MediaLive ................................................................................................................ 483 AWS Elemental MediaPackage ........................................................................................................ 484 AWS Elemental MediaStore .............................................................................................................. 485 AWS Elemental MediaTailor ............................................................................................................. 486 AWS Global Accelerator .................................................................................................................... 487 AWS Glue .............................................................................................................................................. 488 AWS Lake Formation ......................................................................................................................... 489 AWS Lambda ....................................................................................................................................... 491 AWS License Manager ....................................................................................................................... 492 AWS Migration Hub ........................................................................................................................... 493 AWS Outposts ..................................................................................................................................... 493 AWS Resilience Hub ........................................................................................................................... 494 AWS Secrets Manager ........................................................................................................................ 495 AWS Security Hub .............................................................................................................................. 498 AWS Service Catalog AppRegistry .................................................................................................. 499 Version May 08, 2025 viii AMS Advanced User Guide AMS Advanced Concepts and Procedures AWS Shield ........................................................................................................................................... 500 AWS Snowball Edge ........................................................................................................................... 501 AWS Step Functions ........................................................................................................................... 503 AWS Systems Manager Parameter Store ....................................................................................... 504 AWS Systems Manager Automation ............................................................................................... 505 AWS Transfer Family .......................................................................................................................... 508 AWS Transit Gateway ......................................................................................................................... 509 AWS WAF .............................................................................................................................................. 511 AWS Well-Architected Tool .............................................................................................................. 512 AWS X-Ray ........................................................................................................................................... 512 VM Import/Export .............................................................................................................................. 514 Customer Managed mode ...................................................................................................................... 515 Getting started with Customer Managed mode .......................................................................... 516 AMS and AWS Service Catalog ............................................................................................................. 516 Getting started with Service Catalog
ams-ug-003	ams-ug.pdf	3	498 AWS Service Catalog AppRegistry .................................................................................................. 499 Version May 08, 2025 viii AMS Advanced User Guide AMS Advanced Concepts and Procedures AWS Shield ........................................................................................................................................... 500 AWS Snowball Edge ........................................................................................................................... 501 AWS Step Functions ........................................................................................................................... 503 AWS Systems Manager Parameter Store ....................................................................................... 504 AWS Systems Manager Automation ............................................................................................... 505 AWS Transfer Family .......................................................................................................................... 508 AWS Transit Gateway ......................................................................................................................... 509 AWS WAF .............................................................................................................................................. 511 AWS Well-Architected Tool .............................................................................................................. 512 AWS X-Ray ........................................................................................................................................... 512 VM Import/Export .............................................................................................................................. 514 Customer Managed mode ...................................................................................................................... 515 Getting started with Customer Managed mode .......................................................................... 516 AMS and AWS Service Catalog ............................................................................................................. 516 Getting started with Service Catalog ............................................................................................. 516 Service Catalog in AMS before you begin ..................................................................................... 517 Finding the data you need (SKMS) ............................................................................................ 521 What Is service knowledge management? ......................................................................................... 521 Find VPC IDs ............................................................................................................................................. 522 Find subnet IDs ........................................................................................................................................ 524 Find AMI IDs .............................................................................................................................................. 526 Find security group (SG) IDs .................................................................................................................. 528 Find IAM entities ...................................................................................................................................... 528 Find stack IDs ........................................................................................................................................... 529 Find instance IDs or IP addresses ......................................................................................................... 531 Find ARNs .................................................................................................................................................. 533 Find resources by ARN ............................................................................................................................ 535 Find account settings .............................................................................................................................. 536 Find FQDNs .......................................................................................................................................... 538 Find availability zones (AZs) ............................................................................................................. 538 Find SNS topics ................................................................................................................................... 539 Find backup settings .......................................................................................................................... 540 Access management .................................................................................................................... 541 What is Access Management? ............................................................................................................... 541 Why and when we access your account ........................................................................................ 542 How and when to use root .................................................................................................................... 547 Version May 08, 2025 ix AMS Advanced User Guide AMS Advanced Concepts and Procedures AMS Advanced console and Amazon EC2 access .............................................................................. 548 Accessing the AWS Management console and the AMS console ................................................... 549 Temporary AMS console access ....................................................................................................... 550 Accessing instances using bastions ...................................................................................................... 551 DNS friendly bastion names ............................................................................................................ 552 Saving costs on Single-account landing zone (SALZ) bastions ................................................. 554 Using bastion IP addresses ............................................................................................................... 554 Instance access examples .................................................................................................................. 555 Team, or role, based access control in an AMS account ............................................................. 567 Automated EC2 instance conﬁguration ...................................................................................... 568 Prerequisites for automated instance conﬁguration ........................................................................ 568 SSM Agent automatic installation ........................................................................................................ 569 Prerequisites ........................................................................................................................................ 569 Request automatic installation of SSM Agent .............................................................................. 570 How SSM Agent automatic installation works ............................................................................. 570 Automated changes ................................................................................................................................ 571 Automatically update code on Linux instances ............................................................................ 571 Automatically update PBIS on Linux instances ............................................................................ 571 Automatically update the minimum version of SSM and CloudWatch agents ....................... 572 CloudWatch conﬁguration ﬁles, update details ........................................................................... 573 Automatically conﬁgured logs ......................................................................................................... 574 Monitoring and event management ........................................................................................... 576 What is monitoring? ................................................................................................................................ 577 What does the AMS monitoring system monitor? ............................................................................ 578 Single-Account Landing Zone proactive monitoring of Active Directory Trust ...................... 579 How monitoring works ........................................................................................................................... 579 EC2 instance grouped notiﬁcations ................................................................................................ 581 Tag-based alert notiﬁcation ............................................................................................................. 582 Viewing the monitoring conﬁguration for an account .................................................................... 583 Changing the monitoring conﬁguration for an account .................................................................. 583 Application aware incident notiﬁcations in AMS .............................................................................. 584 Provision AppRegistry in your AMS account and create applications ...................................... 584 Create tags to enable case enrichment ......................................................................................... 584 Customize AMS support case severity for your applications ..................................................... 584 Review required permissions ............................................................................................................ 586 Using OpsCenter ...................................................................................................................................... 586 Version May 08, 2025 x AMS Advanced User Guide AMS Advanced Concepts and Procedures Alert notiﬁcations .................................................................................................................................... 587 Receiving alerts ................................................................................................................................... 587 Tag-based alert notiﬁcations ........................................................................................................... 588 AMS automatic remediation of alerts ............................................................................................ 589 Creating additional CloudWatch alarms ............................................................................................. 595 Creating custom CloudWatch metrics and alarms ............................................................................ 596 Using CloudWatch Application Insights for .Net and SQL server .................................................. 597 AMS Event Router .................................................................................................................................... 598 Amazon EventBridge Managed Rules deployed by AMS ............................................................ 599 Creating Managed Rules for AMS ................................................................................................... 599 Editing Managed Rules for AMS ...................................................................................................... 599 Deleting Managed Rules for AMS ................................................................................................... 599 Trusted Remediator ................................................................................................................................. 600 Key beneﬁts ......................................................................................................................................... 600 How Trusted Remediator works ...................................................................................................... 601 Key terms ............................................................................................................................................. 602 Get started with Trusted Remediator ............................................................................................ 603 Supported Trusted Advisor checks ................................................................................................. 607 Conﬁgure check remediation ........................................................................................................... 653 Execution mode decision workﬂow ................................................................................................ 658 Conﬁgure remediation tutorials ...................................................................................................... 660 Work with remediations .................................................................................................................... 662 Remediation logs ................................................................................................................................ 668 Best practices ...................................................................................................................................... 670 FAQs ....................................................................................................................................................... 670 Log management ......................................................................................................................... 673 What is log management? ..................................................................................................................... 673 How AMS logging works ........................................................................................................................ 673 Accessing your logs ................................................................................................................................. 674 AMS aggregated service logs ........................................................................................................... 674 AMS shared services logs .................................................................................................................. 687 Amazon Elastic Compute Cloud (Amazon EC2) - system level logs ......................................... 689 Integrating with Splunk .................................................................................................................... 691 Customizing your log conﬁguration .................................................................................................... 692 Altering CloudWatch log retention ................................................................................................. 692 Enabling logging for supported services ....................................................................................... 693 Version May 08, 2025 xi AMS Advanced User Guide AMS Advanced Concepts and Procedures Security management ................................................................................................................. 694 Data protection in AMS .......................................................................................................................... 694 Amazon Macie ..................................................................................................................................... 695 GuardDuty ............................................................................................................................................ 696 Amazon Route 53 Resolver DNS Firewall ...................................................................................... 699 AWS Certiﬁcate Manager (ACM) certiﬁcate ................................................................................... 700 Data encryption in AMS .................................................................................................................... 701 Identity and access management ......................................................................................................... 702 Multi-Account Landing Zone (MALZ) IAM safeguards ................................................................. 702 Authenticating with
ams-ug-004	ams-ug.pdf	4	(Amazon EC2) - system level logs ......................................... 689 Integrating with Splunk .................................................................................................................... 691 Customizing your log conﬁguration .................................................................................................... 692 Altering CloudWatch log retention ................................................................................................. 692 Enabling logging for supported services ....................................................................................... 693 Version May 08, 2025 xi AMS Advanced User Guide AMS Advanced Concepts and Procedures Security management ................................................................................................................. 694 Data protection in AMS .......................................................................................................................... 694 Amazon Macie ..................................................................................................................................... 695 GuardDuty ............................................................................................................................................ 696 Amazon Route 53 Resolver DNS Firewall ...................................................................................... 699 AWS Certiﬁcate Manager (ACM) certiﬁcate ................................................................................... 700 Data encryption in AMS .................................................................................................................... 701 Identity and access management ......................................................................................................... 702 Multi-Account Landing Zone (MALZ) IAM safeguards ................................................................. 702 Authenticating with identities ......................................................................................................... 704 Security event logging and monitoring ......................................................................................... 732 Endpoint Security (EPS) .................................................................................................................... 732 Malware mitigation process ............................................................................................................. 737 Amazon Inspector security ............................................................................................................... 738 AMS incident response ...................................................................................................................... 740 Compliance validation ....................................................................................................................... 741 Multi-Account Landing Zone viewing the compliance status of your AWS Conﬁg Rules ...... 742 AMS multi-account landing zone service control policy restrictions ....................................... 743 Resilience .............................................................................................................................................. 744 Infrastructure security ....................................................................................................................... 744 Security best practices ...................................................................................................................... 777 AMS multi-account landing zone EPS non-default settings ...................................................... 777 AMS Guardrails .................................................................................................................................... 777 MALZ Service control policies .......................................................................................................... 777 Security Incident Response .................................................................................................................... 777 How it works ....................................................................................................................................... 778 Prepare .................................................................................................................................................. 779 Detect .................................................................................................................................................... 780 Analyze .................................................................................................................................................. 780 Contain .................................................................................................................................................. 781 Eradicate ............................................................................................................................................... 783 Recover .................................................................................................................................................. 784 Post Incident Report .......................................................................................................................... 784 Security Incident Response Runbooks ........................................................................................... 785 Change request security reviews in AMS Advanced ......................................................................... 791 Customer Security Risk Management process .............................................................................. 791 Version May 08, 2025 xii AMS Advanced User Guide AMS Advanced Concepts and Procedures AMS Advanced technical standards ................................................................................................ 792 Standard controls in AMS Advanced .............................................................................................. 793 Changes that introduce high or very high security risks in your environment ....................... 817 Continuity management ............................................................................................................. 820 What is continuity management? ........................................................................................................ 820 How continuity management works .................................................................................................... 820 Backup plans ....................................................................................................................................... 821 Backup vaults ...................................................................................................................................... 824 Backup change types ......................................................................................................................... 825 Monitoring and reporting for backups .......................................................................................... 826 Disaster recovery response .................................................................................................................... 826 Disaster recovery planning .................................................................................................................... 827 Multi-site or highly available (HA) .................................................................................................. 828 Warm standby ..................................................................................................................................... 829 Pilot light .............................................................................................................................................. 831 Backup and restore ............................................................................................................................ 833 Patch management ...................................................................................................................... 840 AMS Patch Orchestrator: a tag-based patching model ................................................................... 841 Using Patch Orchestrator ....................................................................................................................... 842 Patch Orchestrator prerequisites .................................................................................................... 846 Patch windows .................................................................................................................................... 847 Patch notiﬁcations .............................................................................................................................. 848 Patch baselines ................................................................................................................................... 851 Patch Orchestrator reserved tags ................................................................................................... 851 On-demand patching .............................................................................................................................. 851 AMS standard patching .......................................................................................................................... 852 Supported operating systems .......................................................................................................... 853 Supported patches ............................................................................................................................. 853 Patching and infrastructure design ................................................................................................ 856 How AMS standard patching works ............................................................................................... 857 AMS standard patching failures ...................................................................................................... 862 Actions you can take in AMS standard patching ......................................................................... 863 AMS standard patching FAQs .......................................................................................................... 866 Patching service commitments ............................................................................................................. 868 Standard patching .............................................................................................................................. 868 Critical patching .................................................................................................................................. 870 Version May 08, 2025 xiii AMS Advanced User Guide AMS Advanced Concepts and Procedures Reports and options .................................................................................................................... 874 On-request reports .................................................................................................................................. 874 AMS Patch reports ............................................................................................................................. 875 AMS Backup reports .......................................................................................................................... 883 Incidents Prevented and Monitoring Top Talkers reports .......................................................... 886 Billing Charges Details report .......................................................................................................... 888 Trusted Remediator reports ............................................................................................................. 889 Self-service reports .................................................................................................................................. 892 Patch report (daily) ............................................................................................................................ 893 Backup report (daily) ......................................................................................................................... 902 Incident report (weekly) .................................................................................................................... 906 Billing report (monthly) .................................................................................................................... 909 Aggregated reports ............................................................................................................................ 912 AMS self-service reports dashboards ............................................................................................. 914 Data retention policy ......................................................................................................................... 921 Oﬀboard from SSR ............................................................................................................................. 922 Get support .................................................................................................................................. 923 Incident management ............................................................................................................................. 923 What is incident management? ....................................................................................................... 924 Incident management service commitments ................................................................................ 926 Incident management examples ..................................................................................................... 928 Service request management ................................................................................................................ 937 When to use a service request ........................................................................................................ 938 How service request management works ..................................................................................... 939 Testing a service request .................................................................................................................. 939 Creating a service request ................................................................................................................ 940 Monitoring and updating service requests ................................................................................... 944 Responding to an AMS-generated service requests .................................................................... 946 Billing questions ....................................................................................................................................... 946 Operations On Demand .............................................................................................................. 948 Requesting AMS Operations On Demand .......................................................................................... 956 Making changes to Operations on Demand oﬀerings ..................................................................... 957 Document history ........................................................................................................................ 958 Earlier updates .......................................................................................................................................... 966 AWS Glossary ............................................................................................................................... 993 Version May 08, 2025 xiv AMS Advanced User Guide AMS Advanced Concepts and Procedures What is AWS Managed Services? Welcome to AWS Managed Services (AMS), infrastructure operations management for Amazon Web Services (AWS). AMS is an enterprise service that provides ongoing management of your AWS infrastructure. This user guide is intended for IT and application developer professionals. A basic understanding of IT functionality, networking, and application deployment terms and practices is assumed. AMS implements best practices and maintains your infrastructure to reduce your operational overhead and risk. AMS provides full-lifecycle services to provision, run, and support your infrastructure, and automates common activities such as change requests, monitoring, patch management, security, and backup services. AMS enforces your corporate and security infrastructure policies, and enables you to develop solutions and applications using your preferred development approach. To better
ams-ug-005	ams-ug.pdf	5	enterprise service that provides ongoing management of your AWS infrastructure. This user guide is intended for IT and application developer professionals. A basic understanding of IT functionality, networking, and application deployment terms and practices is assumed. AMS implements best practices and maintains your infrastructure to reduce your operational overhead and risk. AMS provides full-lifecycle services to provision, run, and support your infrastructure, and automates common activities such as change requests, monitoring, patch management, security, and backup services. AMS enforces your corporate and security infrastructure policies, and enables you to develop solutions and applications using your preferred development approach. To better understand AMS architecture, see these diagrams. Topics • About this AMS user guide • AMS operations plans • Getting started with AWS Managed Services • AMS key terms • Service description • AMS information resources • AMS compliance • AMS Amazon Machine Images (AMIs) • How integration between AD FS and AMS works • AMS Managed Active Directory • AMS application deployments Version May 08, 2025 1 AMS Advanced User Guide AMS Advanced Concepts and Procedures Note New AWS Regions are added frequently. For the most recent AMS-supported AWS Regions, and the most recent AMS-supported operating systems, see Supported conﬁgurations. To learn more about AWS Regions, see Managing AWS Regions. AMS seeks to continuously improve our services based on your feedback. We use several mechanisms to enable your self-service, to automate repetitive tasks, and to implement new AWS services and features as they are released. You can submit an AMS service request at any time to suggest new features or feature improvements. AMS business hours are 24 hours a day, 7 days a week, 365 days a year. AMS follows a set of practices for IT service management (ITSM) that focuses on aligning IT services with the needs of your business. Version May 08, 2025 2 AMS Advanced User Guide AMS Advanced Concepts and Procedures About this AMS user guide This user guide is intended for AMS Advanced customers with either a multi-account or single- account landing zone. For more details about the AMS landing zone oﬀerings, see the AMS Key Terms; also see Multi-Account Landing Zone architecture and Single-Account Landing Zone architecture. AMS operations plans AWS Managed Services (AMS) is available with two operations plans: AMS Accelerate and AMS Advanced. An operations plan oﬀers a speciﬁc set of features and has diﬀering levels of service, technical capabilities, requirements, price, and restrictions. Our operations plans give you the ﬂexibility to select the right-sized operational capabilities for each of your AWS workloads. This section outlines the capabilities and diﬀerences, as well as the responsibilities, features, and beneﬁts associated with each plan, so that you can understand which operations plan is best for your accounts. For a detailed feature comparison of the two operations plans, see AWS Managed Services Features. About this guide Version May 08, 2025 3 AMS Advanced User Guide AMS Advanced Concepts and Procedures AMS Accelerate operations plan AMS Accelerate is the AMS operations plan that helps you operate the day-to-day infrastructure management of your new or existing AWS environment. AMS Accelerate provides operational services, such as monitoring, incident management, and security. AMS Accelerate also oﬀers an optional patch add-on for Amazon EC2-based workloads that require regular patching. With AMS Accelerate, you decide which AWS accounts you want AMS Accelerate to operate, the AWS Regions you want AMS Accelerate to operate in, the add-ons you require, and the service-level agreements (SLAs) you need. For more details, see Using the AMS Accelerate operations plan and Service Description. AMS Advanced operations plan AMS Advanced provides full-lifecycle services to provision, run, and support your infrastructure. In addition to the operational services provided by AMS Accelerate, AMS Advanced also includes additional services, such as landing zone management, infrastructure changes and provisioning, access management, and endpoint security. AMS Advanced deploys a landing zone to which you migrate your AWS workloads and receive AMS operational services. Our managed multi-account landing zones are pre-conﬁgured with the infrastructure to facilitate authentication, security, networking, and logging. AMS Advanced also includes a change and access management system that protects your workloads by preventing unauthorized access or the implementation of risky changes to your AWS infrastructure. Customers need to create a request for change (RFC) using our change management system to implement most changes in your AMS Advanced accounts. You create RFCs from a library of automated changes that are pre-vetted by our security and operations teams or request manual changes that are reviewed and implemented by our operations team if they are deemed both safe and supported by AMS Advanced. AMS Advanced also oﬀers diﬀerent SLAs. For more information, see the AWS Managed Services AMS Advanced service description. Getting started with AWS Managed Services For details about getting started with the multi-account landing zone AMS service, see the AWS
ams-ug-006	ams-ug.pdf	6	a request for change (RFC) using our change management system to implement most changes in your AMS Advanced accounts. You create RFCs from a library of automated changes that are pre-vetted by our security and operations teams or request manual changes that are reviewed and implemented by our operations team if they are deemed both safe and supported by AMS Advanced. AMS Advanced also oﬀers diﬀerent SLAs. For more information, see the AWS Managed Services AMS Advanced service description. Getting started with AWS Managed Services For details about getting started with the multi-account landing zone AMS service, see the AWS Managed Services Onboarding Introduction. The two onboarding guides provide descriptions of Accelerate operations plan Version May 08, 2025 4 AMS Advanced User Guide AMS Advanced Concepts and Procedures the service and questions to consider to help you get started. Review the feature set AWS Managed Services Features, and current resources at AWS Managed Services Resources. AMS key terms • AMS Advanced: The services described in the "Service Description" section of the AMS Advanced Documentation. See Service Description. • AMS Advanced Accounts: AWS accounts that at all times meet all requirements in the AMS Advanced Onboarding Requirements. For information on AMS Advanced beneﬁts, case studies, and to contact a sales person, see AWS Managed Services. • AMS Accelerate Accounts: AWS accounts that at all times meet all requirements in the AMS Accelerate Onboarding Requirements. See Getting Started with AMS Accelerate. • AWS Managed Services: AMS and or AMS Accelerate. • AWS Managed Services accounts: The AMS accounts and or AMS Accelerate accounts. • Critical Recommendation: A recommendation issued by AWS through a service request informing you that your action is required to protect against potential risks or disruptions to your resources or the AWS services. If you decide not to follow a Critical Recommendation by the speciﬁed date, you are solely responsible for any harm resulting from your decision. • Customer-Requested Conﬁguration: Any software, services or other conﬁgurations that are not identiﬁed in: • Accelerate: Supported Conﬁgurations or AMS Accelerate; Service Description. • AMS Advanced: Supported Conﬁgurations or AMS Advanced; Service Description. • Incident communication: AMS communicates an Incident to you or you request an Incident with AMS via an Incident created in Support Center for AMS Accelerate and in the AMS Console for AMS. The AMS Accelerate Console provides a summary of Incidents and Service Requests on the Dashboard and links to Support Center for details. • Managed Environment: The AMS Advanced accounts and or the AMS Accelerate accounts operated by AMS. For AMS Advanced, these include multi-account landing zone (MALZ) and single-account landing zone (SALZ) accounts. • Billing start date: The next business day after AWS receives the your information requested in the AWS Managed Services Onboarding Email. The AWS Managed Services Onboarding Email refers to the email sent by AWS to the you to collect the information needed to activate AWS Managed Services on the your accounts. Key terms Version May 08, 2025 5 AMS Advanced User Guide AMS Advanced Concepts and Procedures For accounts subsequently enrolled by you, the billing start date is the next business day after AWS Managed Services sends an AWS Managed Services Activation Notiﬁcation for the enrolled account. An AWS Managed Services Activation Notiﬁcation occurs when: 1. You grants access to a compatible AWS account and hand it over to AWS Managed Services. 2. AWS Managed Services designs and builds the AWS Managed Services Account. • Service Termination: You can terminate the AWS Managed Services for all AWS Managed Services accounts, or for a speciﬁed AWS Managed Services account for any reason by providing AWS at least 30 days notice through a service request. On the Service Termination Date, either: 1. AWS hands over the controls of all AWS Managed Services accounts or the speciﬁed AWS Managed Services accounts as applicable, to you, or 2. The parties remove the AWS Identity and Access Management roles that give AWS access from all AWS Managed Services accounts or the speciﬁed AWS Managed Services accounts, as applicable. • Service termination date: The service termination date is the last day of the calendar month following the end of the 30 days requisite termination notice period. If the end of the requisite termination notice period falls after the 20th day of the calendar month, then the service termination date is the last day of the following calendar month. The following are example scenarios for termination dates. • If the termination notice is provided on April 12, then the 30 days notice ends on May 12. The service termination date is May 31. • If a termination notice is provided on April 29, then the 30 days notice ends on May 29. The service termination date is June 30. • Provision of AWS Managed Services: AWS makes available to
ams-ug-007	ams-ug.pdf	7	end of the requisite termination notice period falls after the 20th day of the calendar month, then the service termination date is the last day of the following calendar month. The following are example scenarios for termination dates. • If the termination notice is provided on April 12, then the 30 days notice ends on May 12. The service termination date is May 31. • If a termination notice is provided on April 29, then the 30 days notice ends on May 29. The service termination date is June 30. • Provision of AWS Managed Services: AWS makes available to you and you can access and use AWS Managed Services for each AWS Managed Services account from the service commencement date. • Termination for speciﬁed AWS Managed Services accounts: You can terminate the AWS Managed Services for a speciﬁed AWS Managed Services account for any reason by providing AWS notice through a service request ("AMS Account Termination Request"). Incident management terms: • Event: A change in your AMS environment. Key terms Version May 08, 2025 6 AMS Advanced User Guide AMS Advanced Concepts and Procedures • Alert: Whenever an event from a supported AWS service exceeds a threshold and triggers an alarm, an alert is created and notice is sent to your contacts list. Additionally, an incident is created in your Incident list. • Incident: An unplanned interruption or performance degradation of your AMS environment or AWS Managed Services that results in an impact as reported by AWS Managed Services or you. • Problem: A shared underlying root cause of one or more incidents. • Incident Resolution or Resolve an Incident: • AMS has restored all unavailable AMS services or resources pertaining to that incident to an available state, or • AMS has determined that unavailable stacks or resources cannot be restored to an available state, or • AMS has initiated an infrastructure restore authorized by you. • Incident Response Time: The diﬀerence in time between when you create an incident, and when AMS provides an initial response by way of the console, email, service center, or telephone. • Incident Resolution Time: The diﬀerence in time between when either AMS or you creates an incident, and when the incident is resolved. • Incident Priority: How incidents are prioritized by AMS, or by you, as either Low, Medium, or High. • Low: A non-critical problem with your AMS service. • Medium: An AWS service within your managed environment is available but is not performing as intended (per the applicable service description). • High: Either (1) the AMS Console, or one or more AMS APIs within your managed environment are unavailable; or (2) one or more AMS stacks or resources within your managed environment are unavailable and the unavailability prevents your application from performing its function. AMS may re-categorize incidents in accordance with the above guidelines. • Infrastructure Restore: Re-deploying existing stacks, based on templates of impacted stacks, and initiating a data restore based on the last known restore point, unless otherwise speciﬁed by you, when incident resolution is not possible. Infrastructure terms: • Managed production environment: A customer account where the customer’s production applications reside. Key terms Version May 08, 2025 7 AMS Advanced User Guide AMS Advanced Concepts and Procedures • Managed non-production environment: A customer account that only contains non-production applications, such as applications for development and testing. • AMS stack: A group of one or more AWS resources that are managed by AMS as a single unit. • Immutable infrastructure: An infrastructure maintenance model typical for Amazon EC2 Auto Scaling groups (ASGs) where updated infrastructure components, (in AWS, the AMI) are replaced for every deployment, rather than being updated in-place. The advantages to immutable infrastructure is that all components stay in a synchronous state since they are always generated from the same base. Immutability is independent of any tool or workﬂow for building the AMI. • Mutable infrastructure: An infrastructure maintenance model typical for stacks that are not Amazon EC2 Auto Scaling groups and contain a single instance or just a few instances. This model most closely represents traditional, hardware-based, system deployment where a system is deployed at the beginning of its life cycle and then updates are layered onto that system over time. Any updates to the system are applied to the instances individually, and may incur system downtime (depending on the stack conﬁguration) due to application or system restarts. • Security groups: Virtual ﬁrewalls for your instance to control inbound and outbound traﬃc. Security groups act at the instance level, not the subnet level. Therefore, each instance in a subnet in your VPC could have a diﬀerent set of security groups assigned to it. • Service Level Agreements (SLAs): Part of AMS contracts with you that deﬁne the level of expected service. • SLA Unavailable and
ams-ug-008	ams-ug.pdf	8	layered onto that system over time. Any updates to the system are applied to the instances individually, and may incur system downtime (depending on the stack conﬁguration) due to application or system restarts. • Security groups: Virtual ﬁrewalls for your instance to control inbound and outbound traﬃc. Security groups act at the instance level, not the subnet level. Therefore, each instance in a subnet in your VPC could have a diﬀerent set of security groups assigned to it. • Service Level Agreements (SLAs): Part of AMS contracts with you that deﬁne the level of expected service. • SLA Unavailable and Unavailability: • An API request submitted by you that results in an error. • A Console request submitted by you that results in a 5xx HTTP response (the server is incapable of performing the request). • Any of the AWS service oﬀerings that constitute stacks or resources in your AMS-managed infrastructure are in a state of "Service Disruption" as shown in the Service Health Dashboard. • Unavailability resulting directly or indirectly from an AMS exclusion is not considered in determining eligibility for service credits. Services are considered available unless they meet the criteria for being unavailable. • Service Level Objectives (SLOs): Part of AMS contracts with you that deﬁne speciﬁc service goals for AMS services. Patching terms: Key terms Version May 08, 2025 8 AMS Advanced User Guide AMS Advanced Concepts and Procedures • Mandatory patches: Critical security updates to address issues that could compromise the security state of your environment or account. A "Critical Security update" is a security update rated as "Critical" by the vendor of an AMS-supported operating system. • Patches announced versus released: Patches are generally announced and released on a schedule. Emergent patches are announced when the need for the patch has been discovered and, usually soon after, the patch is released. • Patch add-on: Tag-based patching for AMS instances that leverages AWS Systems Manager (SSM) functionality so you can tag instances and have those instances patched using a baseline and a window that you conﬁgure. • Patch methods: • In-place patching: Patching that is done by changing existing instances. • AMI replacement patching: Patching that is done by changing the AMI reference parameter of an existing EC2 Auto Scaling group launch conﬁguration. • Patch provider (OS vendors, third party): Patches are provided by the vendor or governing body of the application. • Patch Types: • Critical Security Update (CSU): A security update rated as "Critical" by the vendor of a supported operating system. • Important Update (IU): A security update rated as "Important" or a non-security update rated as "Critical" by the vendor of a supported operating system. • Other Update (OU): An update by the vendor of a supported operating system that is not a CSU or an IU. • Supported patches: AMS supports operating system level patches. Upgrades are released by the vendor to ﬁx security vulnerabilities or other bugs or to improve performance. For a list of currently supported OSs, see Support Conﬁgurations. Security terms: • Detective Controls: A library of AMS-created or enabled monitors that provide ongoing oversight of customer managed environments and workloads for conﬁgurations that do not align with security, operational, or customer controls, and take action by notifying owners, proactively modifying, or terminating resources. Service Request terms: Key terms Version May 08, 2025 9 AMS Advanced User Guide AMS Advanced Concepts and Procedures • Service request: A request by you for an action that you want AMS to take on your behalf. • Alert notiﬁcation: A notice posted by AMS to your Service requests list page when an AMS alert is triggered. The contact conﬁgured for your account is also notiﬁed by the conﬁgured method (for example, email). If you have contact tags on your instances/resources, and have provided consent to your cloud service delivery manager (CSDM) for tag-based notiﬁcations, the contact information (key value) in the tag is also notiﬁed for automated AMS alerts. • Service notiﬁcation: A notice from AMS that is posted to your Service request list page. Miscellaneous terms: • AWS Managed Services Interface: For AMS: The AWS Managed Services Advanced Console, AMS CM API, and Support API. For AMS Accelerate: The Support Console and Support API. • Customer satisfaction (CSAT): AMS CSAT is informed with deep analytics including Case Correspondence Ratings on every case or correspondence when given, quarterly surveys, and so forth. • DevOps: DevOps is a development methodology that strongly advocates automation and monitoring at all steps. DevOps aims at shorter development cycles, increased deployment frequency, and more dependable releases by bringing together the traditionally-separate functions of development and operations over a foundation of automation. When developers can manage operations, and operations informs development, issues and problems are more quickly discovered and solved, and business objectives are more readily achieved.
ams-ug-009	ams-ug.pdf	9	Console and Support API. • Customer satisfaction (CSAT): AMS CSAT is informed with deep analytics including Case Correspondence Ratings on every case or correspondence when given, quarterly surveys, and so forth. • DevOps: DevOps is a development methodology that strongly advocates automation and monitoring at all steps. DevOps aims at shorter development cycles, increased deployment frequency, and more dependable releases by bringing together the traditionally-separate functions of development and operations over a foundation of automation. When developers can manage operations, and operations informs development, issues and problems are more quickly discovered and solved, and business objectives are more readily achieved. • ITIL: Information Technology Infrastructure Library (called ITIL) is an ITSM framework designed to standardize the lifecycle of IT services. ITIL is arranged in ﬁve stages that cover the IT service lifecycle: service strategy, service design, service transition, service operation, and service improvement. • IT service management (ITSM): A set of practices that align IT services with the needs of your business. • Managed Monitoring Services (MMS): AMS operates its own monitoring system, Managed Monitoring Service (MMS), that consumes AWS Health events and aggregates Amazon CloudWatch data, and data from other AWS services, notifying AMS operators (online 24x7) of any alarms created through an Amazon Simple Notiﬁcation Service (Amazon SNS) topic. • Namespace: When you create IAM policies or work with Amazon Resource Names (ARNs), you identify an AWS service by using a namespace. You use namespaces when identifying actions and resources. Key terms Version May 08, 2025 10 AMS Advanced User Guide AMS Advanced Concepts and Procedures Service description AMS Advanced (AMS) is an operation plan of the AWS Managed Services service for managing operations of your AWS infrastructure. AMS Advanced provides routine infrastructure operations such as patch, continuity management, security management, and IT management processes such as incident, change and service request management. For a list of supported services, see Supported AWS services. YouTube Video: How can AMS help me achieve operational excellence in the cloud? Topics • AWS Managed Services (AMS) AMS Advanced operation plan features • What we do, what we do not do • AMS responsibility matrix (RACI) • AMS environment basic components • AMS account limits • AMS service level objectives (SLOs) • Supported AWS services • Supported conﬁgurations • Capabilities for unsupported operating systems in AMS • AMS Advanced interfaces • AMS VPC endpoints • AMS protected namespaces • AMS reserved preﬁxes • AMS maintenance window AWS Managed Services (AMS) AMS Advanced operation plan features AMS Advanced oﬀers the following features for supported AWS services: • Logging, Monitoring, Guardrails, and Event Management: AMS conﬁgures and monitors your managed environment for logging activity and deﬁnes alerts based on a variety of health checks. Alerts are investigated by AMS for applicable AWS Service description Version May 08, 2025 11 AMS Advanced User Guide AMS Advanced Concepts and Procedures services, and those that negatively impact your usage of those services result in the creation of incidents. AMS aggregates and stores all logs generated as a result of all operations in CloudWatch, CloudTrail, and system logs in Amazon S3. You can ask for additional alerts to be put in place. In addition to AMS’ preventative controls, AMS deploys conﬁguration guardrails and detective controls to provide ongoing protection for you from misconﬁgurations that could reduce the operational and security integrity of the managed accounts, to enforce your controls such as tagging and compliance. When a monitored control is detected an alarm is generated that results in notiﬁcation, modiﬁcation, or termination of resources based on predeﬁned AMS defaults that can be modiﬁed by you. • Continuity management (Backup and Restore): AMS provides backups of resources using standard, existing AWS Backup functionality on a scheduled interval determined by you. Restore actions from speciﬁc snapshots can be performed by AMS with your RFC. Data changes that occur between snapshot intervals are the responsibility of you to backup. You can submit an RFC for backup or snapshot requests outside of scheduled intervals. In the case of Availability Zone (AZ) unavailability in an AWS Region, with your permission, AMS restores the managed environment by recreating new stack(s) based on templates and available EBS snapshots of the impacted Stacks. • Security and access management: AMS provides endpoint security (EPS) such as conﬁguring anti-virus and anti-malware protection. You can also use your own EPS tool and processes and not use AMS for EPS using a feature called bring your own EPS (BYOEPS). AMS also conﬁgures default AWS security capabilities that are approved by you during onboarding, such as AWS Identity and Access Management (IAM) roles and Amazon EC2 security groups, and uses standard AWS tools (e.g. AWS Security Hub, Amazon Macie, Amazon GuardDuty) to monitor and respond to security issues. You manage your users through an approved directory service provided by you. For a list
ams-ug-010	ams-ug.pdf	10	AMS provides endpoint security (EPS) such as conﬁguring anti-virus and anti-malware protection. You can also use your own EPS tool and processes and not use AMS for EPS using a feature called bring your own EPS (BYOEPS). AMS also conﬁgures default AWS security capabilities that are approved by you during onboarding, such as AWS Identity and Access Management (IAM) roles and Amazon EC2 security groups, and uses standard AWS tools (e.g. AWS Security Hub, Amazon Macie, Amazon GuardDuty) to monitor and respond to security issues. You manage your users through an approved directory service provided by you. For a list of approved directory services, see Supported conﬁgurations. AMS includes endpoint security (EPS), which is inclusive of antivirus (AV), and anti-malware protection, malware and intrusion detection (Trend Micro). Security groups are deﬁned per stack template and are modiﬁed at launch depending on the visibility of the application (public/ private) security groups. Access to systems is requested through change management requests for change (RFCs). Access management provides access to distinct resources, such as Amazon EC2 instances, the AWS Management Console, and APIs. After establishing a one-way trust with an AMS Microsoft Active AWS Managed Services (AMS) AMS Advanced operation plan features Version May 08, 2025 12 AMS Advanced User Guide AMS Advanced Concepts and Procedures Directory deployment during onboarding and federating to AWS, you can use your existing corporate credentials for all interactions. • Patch management: AMS applies and installs updates to EC2 instances for supported operating systems (OSs) and software pre-installed with supported operating systems. For a list of supported operating systems, see Supported conﬁgurations. AMS oﬀers two models for patching: • AMS standard patch for traditional account-based patching, and • AMS Patch Orchestrator, for tag-based patching. In AMS standard patch, a monthly maintenance window is chosen by you for AMS to perform most patching activities. AMS applies critical security updates outside of the selected maintenance window (with appropriate notiﬁcations) and important updates during the selected maintenance window. AMS additionally applies updates to infrastructure management tools during the selected maintenance window. You can exclude stacks from patch management or reject updates, if you want. With AMS Patch Orchestrator, a default maintenance window per account, is deﬁned by you for AMS to perform patching activities. You can schedule additional custom maintenance windows for AMS to patch a speciﬁc set of instances deﬁned by you with tags. AMS applies all available updates, but you can ﬁlter or reject updates by creating a custom patch baseline. For both models, if you approve or reject an update provided under patch management but later change your mind, you are responsible for initiating the update via an RFC. AMS tracks the patch status of resources and highlights systems that aren’t current in the monthly business review. Patch management is limited to stacks in the managed environment, including all AMS managed applications and supported AWS services with patching capabilities (for example, RDS). In order to support all types of infrastructure conﬁgurations when an update is released, AMS a) updates the EC2 instance and b) provides an updated AMS AMI for you to use. It is your responsibility to install, conﬁgure, patch, and monitor any additional applications not speciﬁcally covered above. • Change management: AMS change management is the mechanism for you to control changes in your managed environment. AMS uses a combination of preventative and detective controls to facilitate this process and provides diﬀerent level of control and associated risk depending on the AMS mode selected. AWS Managed Services (AMS) AMS Advanced operation plan features Version May 08, 2025 13 AMS Advanced User Guide AMS Advanced Concepts and Procedures All actions in your AMS environment are logged in AWS CloudTrail. For more information about AMS Change Management and diﬀerent modes, see AMS Change Management guide and AMS Modes. • Automated and self-service provisioning management: You can provision AWS resources on AMS Advanced in several ways: • Submit provisioning and conﬁguration Requests for Change (RFCs) • Deploy through AWS Service Catalog • Deploy through Direct Change mode • Deploy through Developer mode. Remember that the resources created through the Developer mode are not managed by AMS. • Conﬁgure AWS services directly using self-service provisioning for select AWS services (see Supported AWS services). • Incident management: AMS proactively notiﬁes you of incidents detected by AMS. AMS responds to both customer- submitted and AMS-generated incidents and resolves incidents based on the incident priority. Unless otherwise instructed by you, incidents that are determined by AMS to be a risk to the security of your managed environment, and incidents relating to the availability of AMS and other AWS services, are proactively actioned. AMS takes action on all other incidents once your authorization is received. Recurring incidents are addressed by the problem management process. • Problem management: AMS performs trend analysis to identify and
ams-ug-011	ams-ug.pdf	11	Supported AWS services). • Incident management: AMS proactively notiﬁes you of incidents detected by AMS. AMS responds to both customer- submitted and AMS-generated incidents and resolves incidents based on the incident priority. Unless otherwise instructed by you, incidents that are determined by AMS to be a risk to the security of your managed environment, and incidents relating to the availability of AMS and other AWS services, are proactively actioned. AMS takes action on all other incidents once your authorization is received. Recurring incidents are addressed by the problem management process. • Problem management: AMS performs trend analysis to identify and investigate problems and to identify the root cause. Problems are remediated either with a workaround or a permanent solution that prevents recurrence of similar future service impact. A post incident report (PIR) may be requested for any "High" incident, upon resolution. The PIR captures the root cause and preventative actions taken, including implementation of preventative measures. • Reporting: AMS provides you with a monthly service report that summarizes key performance metrics of AMS, including an executive summary and insights, operational metrics, managed resources, AMS service level agreement (SLA) adherence, and ﬁnancial metrics around spending, savings, AWS Managed Services (AMS) AMS Advanced operation plan features Version May 08, 2025 14 AMS Advanced User Guide AMS Advanced Concepts and Procedures and cost optimization. Reports are delivered by the AMS cloud service delivery manager (CSDM) assigned to you. • Service request management : To request information about your managed environment, AMS, or AWS service oﬀerings, submit service requests using the AMS console. You can submit a service request for "How to" questions about AWS services and features or to request additional AMS services. • Service Desk : AMS staﬀs engineering operations with full-time Amazon employees to fulﬁll non-automated requests including incident management, service request management, and change management. The Service Desk operates 24 x 7 365 days a year. • Designated resources: Each customer is assigned a Cloud Service Delivery Manager (CSDM) and a Cloud Architect (CA). • CSDMs can be contacted directly. They perform service reviews, and delivery reporting and insights through all phases of the implementation, migration and operational life cycle. CSDMs conduct monthly business reviews and detail items such as ﬁnancial spend, cost-saving recommendations, service utilization, and risk reporting. They dive deep into operational performance statistics and provide recommendations of areas of improvements. • CAs can be contacted directly and provide technical expertise to help you optimize your use of the AWS cloud. Example CA activities include, selecting workloads for migration, assisting with the onboarding additional accounts and workloads, acting as the technical lead in operational activities such as game days, disaster recovery testing, problem management, and technical advice to get the most out of AMS and AWS. CAs drive technical discussions at all levels of your organization and assist with incident management, making trade-oﬀs, establishing best practices, and technical risk mitigation. • Developer mode : This feature enables you to iterate infrastructure designs and deployments quickly within AMS- conﬁgured accounts[1] by allowing direct access to AWS service APIs and the AWS console in addition to access to the AMS change management process. Resources provisioned or conﬁgured with developer mode permissions outside of the change management process are your responsibility to manage (See "Automated and Self-Service Provisioning Management"). Resources provisioned through the AMS change management process are supported like other change management-provisioned workloads on AMS. AWS Managed Services (AMS) AMS Advanced operation plan features Version May 08, 2025 15 AMS Advanced User Guide • AWS support: AMS Advanced Concepts and Procedures AMS customers can choose the level of AWS Support they require to complement their AMS Operations plan. Accounts enrolled in AMS can be subscribed to either Business Support or Enterprise Support. To learn about the diﬀerences in Support Plans, see AWS Support Plans. • Customer-managed account: This feature enables you to request AWS accounts within the same managed environment but the ongoing operations of workloads and AWS resources within those accounts are your responsibility. AMS provisions customer-managed accounts, but once the accounts are created, no other AMS features or services are provided to those accounts. AWS will not enroll customer- managed accounts in enterprise-level premium support. It will be your responsibility to enroll customer-managed accounts in AWS support at the support rate you choose. • Firewall management: AMS provides an optional managed ﬁrewall solution for Supported Firewall Services, which enables internet-bound egress traﬃc ﬁltering for networks in your managed environment. This excludes public-facing services that do not use the AWS network infrastructure and whose traﬃc goes directly to the internet. The solution combines industry-leading ﬁrewall technology with AMS infrastructure management capabilities to deploy, monitor, manage, scale, and restore the ﬁrewall infrastructure. When you onboard AMS, you receive a complete list of your AMS network infrastructure. To get an updated
ams-ug-012	ams-ug.pdf	12	your responsibility to enroll customer-managed accounts in AWS support at the support rate you choose. • Firewall management: AMS provides an optional managed ﬁrewall solution for Supported Firewall Services, which enables internet-bound egress traﬃc ﬁltering for networks in your managed environment. This excludes public-facing services that do not use the AWS network infrastructure and whose traﬃc goes directly to the internet. The solution combines industry-leading ﬁrewall technology with AMS infrastructure management capabilities to deploy, monitor, manage, scale, and restore the ﬁrewall infrastructure. When you onboard AMS, you receive a complete list of your AMS network infrastructure. To get an updated list of services running in support of your AMS infrastructure at any time, ﬁle a service request with speciﬁcs about the information you want. To request a change to your network design, create a service request describing the changes you want to make—for example, adding a VPC or requesting a security group rule change. What we do, what we do not do AMS gives you a standardized approach to deploying AWS infrastructure and provides the necessary ongoing operational management. For a full description of roles, responsibilities, and supported services, see Service Description. What we do, what we do not do Version May 08, 2025 16 AMS Advanced User Guide AMS Advanced Concepts and Procedures Note To request that AMS provide an additional AWS service, ﬁle a service request. For more information, see Making Service Requests. • What we do: After you complete onboarding, the AMS environment is available to receive requests for change (RFCs), incidents, and service requests. Your interaction with the AMS service revolves around the lifecycle of an application stack. New stacks are ordered from a preconﬁgured list of templates, launched into speciﬁc virtual private cloud (VPC) subnets, modiﬁed during their operational life through requests for change (RFCs), and monitored for events and incidents 24/7. Active application stacks are monitored and maintained by AMS, including patching, and require no further action for the life of the stack unless a change is required or the stack is decommissioned. Incidents detected by AMS that aﬀect the health and function of the stack generate a notiﬁcation and may or may not need your action to resolve or verify. How-to questions and other inquiries can be made by submitting a service request. Additionally, AMS allows you to enable compatible AWS services that are not managed by AMS. For information about AWS-AMS compatible services, see Self-service provisioning mode. • What we DON'T do: While AMS simpliﬁes application deployment by providing a number of manual and automated options, you're responsible for the development, testing, updating, and management of your application. AMS provides troubleshooting assistance for infrastructure issues that impact applications, but AMS can't access or validate your application conﬁgurations. AMS responsibility matrix (RACI) Note In order to fulﬁll its obligations in a timely manner, AWS Managed Services (AMS) may require inputs from you for deciding an appropriate course of action. AMS will contact the designated customer contact for all such clariﬁcations and inputs. AMS will expect AMS responsibility matrix (RACI) Version May 08, 2025 17 AMS Advanced User Guide AMS Advanced Concepts and Procedures a response to such queries within 24 business hours. In case there is no reply within 24 business hours, AMS may choose an action on your behalf. The AMS responsible, accountable, consulted, and informed, or RACI, matrix assigns primary responsibility either to the customer or AMS for a variety of activities. AMS manages your AWS infrastructure. The following table provides an overview of the responsibilities of customer and AMS for activities in the lifecycle of an application running within an AMS managed environment. AMS is not responsible for any of the following activities for Customer Managed accounts or the infrastructure running within them; therefore this RACI is not applicable. • R stands for responsible party that does the work to achieve the task. • C stands for consulted; a party whose opinions are sought, typically as subject matter experts; and with whom there is bilateral communication. • I stands for informed; a party which is informed on progress, often only on completion of the task or deliverable. • Self-service Provisioning refers to resources that are provisioned by the customer with self- service through the AWS API or Console, including Developer Mode and Self-Service Provisioned Services. Note Some sections contain 'R' for both AMS and Customers. This is because, in the AWS Shared Responsibility model, both AMS and the customers take joint ownership to respond to infrastructure and application issues. To provide self-service provisioning capabilities, AMS has created elevated IAM roles with permission boundaries to limit unintended changes from direct AWS service access. Roles do not prevent all changes and you are responsible to adhere to your internal controls, compliance, and to validate that all AWS services being used meet the
ams-ug-013	ams-ug.pdf	13	self- service through the AWS API or Console, including Developer Mode and Self-Service Provisioned Services. Note Some sections contain 'R' for both AMS and Customers. This is because, in the AWS Shared Responsibility model, both AMS and the customers take joint ownership to respond to infrastructure and application issues. To provide self-service provisioning capabilities, AMS has created elevated IAM roles with permission boundaries to limit unintended changes from direct AWS service access. Roles do not prevent all changes and you are responsible to adhere to your internal controls, compliance, and to validate that all AWS services being used meet the required certiﬁcations. We call this the Self-Service Provisioning mode. For details on AWS compliance requirements, see AWS Compliance. AMS responsibility matrix (RACI) Version May 08, 2025 18 AMS Advanced User Guide AMS Advanced Concepts and Procedures For resources that you provision through self-service, AMS provides incident management, detective controls and guardrails, reporting, designated resources (Cloud Service Delivery Manager and Cloud Architect), Security & access, and technical support through service requests. Additionally, where applicable, you assume responsibility for continuity management, patch management, infrastructure monitoring, and change management for resources provisioned or conﬁgured outside of the AMS change management system. Activity Customer AWS Managed Services (AMS) Application lifecycle Application development Application infrastructure requirements analysis and design Design and optimization for non-standard AMS stacks Design and optimization of AMS standard stack Application deployment AWS Infrastructure deployment Application monitoring Application testing/optimization AWS infrastructure optimization guidance AWS infrastructure monitoring Troubleshoot and resolve application issues Troubleshoot and resolve AWS network issues R R R I R C R R I I R C I C C R C R I I R R C R AMS responsibility matrix (RACI) Version May 08, 2025 19 AMS Advanced User Guide AMS Advanced Concepts and Procedures Activity Customer AWS Managed Services (AMS) Troubleshoot and resolve operating system and infrastructure issues Self-Service Provisioning Application and ITSM Integration Application integration with AWS Service Oﬀerings ITSM integration with the AWS Managed Services Interface Networking Managed Environment VPC and VPC set-up and conﬁguration Allocate private address space for VPCs (e.g. /16) Conﬁgure & Operate non-AWS Managed Services, Customer managed Firewalls/Proxy/ Bastions/HOSTs Conﬁgure & Operate AWS Security Groups/ NAT/Customer Bastions/NACL inside the Managed Environment Networking (e.g. DirectConnect) conﬁguration and implementation within customer network Networking conﬁguration and implementation within the Managed Environment Managed environment conﬁguration C R R R C R R I R C R C C C R C C R C R AMS responsibility matrix (RACI) Version May 08, 2025 20 AMS Advanced User Guide AMS Advanced Concepts and Procedures Activity Customer AWS Managed Services (AMS) Deﬁne default Auto Scaling settings for baseline Stack templates Recommend RI optimization Purchase RI and PIOP capacity Remove capacity when capacity is over provisioned (when supported by customer application) Create/update AWS customer speciﬁc information for AWS Managed Services S3 conﬁguration Self-service provisioning Glacier conﬁguration Deﬁne archival policy Archival policy conﬁguration Selecting customer maintenance window AWS RDS Management Monitor source/replica/RO replication health Identify RCA of source failover Automated snapshot (backup) conﬁguration Self-service provisioning I C R C C C R C R C R I I C R R R C R R R C R C R I R R R C AMS responsibility matrix (RACI) Version May 08, 2025 21 AMS Advanced User Guide AMS Advanced Concepts and Procedures Activity Customer AWS Managed Services (AMS) Coordinate and schedule DB engine patch management Self-service provisioning Recommend DB storage and PIOP capacity Self-service provisioning Recommend instance sizing for running databases Self-service provisioning Recommend RI optimization for Managed Environment Self-service provisioning RDS performance monitoring (CloudWatch) Self-service provisioning RDS event subscription conﬁguration (SNS) Self-service provisioning RDS security group conﬁguration Self-service provisioning RDS engine parameter/option conﬁguration DB table design DB indexing DB log analysis C R C R C R C R C R C R C R R R R R R C R C R C R C R C R C R C C I I I AMS responsibility matrix (RACI) Version May 08, 2025 22 AMS Advanced User Guide AMS Advanced Concepts and Procedures Activity Customer AWS Managed Services (AMS) AMS Change Management Creating customer RFCs (e.g. access to resources creating/updating/deleting managed stacks, deploying/updating applicati ons, changes to conﬁguration of AWS Service Oﬀerings) Approving Customer RFCs Creating AWS Managed Services RFCs (e.g. access to resources, creating resources on customer’s behalf, applying updates to OS as part of Patch Management) Approving non-automated RFCs Submitting request for new Change Types Creating new Change Types Maintenance of application change calendar Notice of upcoming Maintenance Window AWS Service Catalog Create portfolios and products Distribute products to end users Create tags and tag option library Sharing portfolios and products with end users Revise / update portfolios and products R I I R R I R I R R R R R
ams-ug-014	ams-ug.pdf	14	changes to conﬁguration of AWS Service Oﬀerings) Approving Customer RFCs Creating AWS Managed Services RFCs (e.g. access to resources, creating resources on customer’s behalf, applying updates to OS as part of Patch Management) Approving non-automated RFCs Submitting request for new Change Types Creating new Change Types Maintenance of application change calendar Notice of upcoming Maintenance Window AWS Service Catalog Create portfolios and products Distribute products to end users Create tags and tag option library Sharing portfolios and products with end users Revise / update portfolios and products R I I R R I R I R R R R R I R R I C R C R I I C I I AMS responsibility matrix (RACI) Version May 08, 2025 23 AMS Advanced User Guide AMS Advanced Concepts and Procedures Activity Customer AWS Managed Services (AMS) Create and assign constraints to portfolios and products Associate Service Actions to products Update provisioned resources with new version of product Provisioning Customer speciﬁc additions to AWS Managed Services baseline AMI Conﬁgure additional approved Change Types used to provision Stack templates Launch managed Stacks and associated AWS resources submitted through AMS change management process or AWS Service Catalog. Self-service provisioning Install/Update custom and 3rd party applicati ons on Instances provisioned through AMS change management process or AWS Service Catalog. Provisioning - Stack Architecture Providing OS licenses (including usage fees for the applicable AWS services – e.g. EC2 and RDS) Self-Service Provisioning R R R R C I R R I R C C I C R R I I R I AMS responsibility matrix (RACI) Version May 08, 2025 24 AMS Advanced User Guide AMS Advanced Concepts and Procedures Activity Customer AWS Managed Services (AMS) Deﬁne baseline infrastructure templates (Stacks) for application deployment through AMS change management system. Self-Service Provisioning Creating baseline approved AMIs8 Evaluate customer application inventory and determine ﬁt with available infrastructure templates (Stacks) Deﬁne unique Stacks that are in addition to the baseline template oﬀerings Logging, Monitoring and Event Management Recording AWS infrastructure change logs Recording all application change logs Installation and conﬁguration of agents and scripts for patching, security, monitoring, etc. of AWS infrastructure provisioned through the AMS change management process. Self-Service Provisioning Deﬁne customer speciﬁc monitoring and incident requirements Conﬁguring alerts for Managed Environment Monitoring all AMS conﬁgured alerts Self-Service Provisioning I R I R R I R I R R I I R R I R C C R C R C C R R C AMS responsibility matrix (RACI) Version May 08, 2025 25 AMS Advanced User Guide AMS Advanced Concepts and Procedures Activity Customer AWS Managed Services (AMS) R C C R C I R R R Investigating infrastructure Alerts for Incident notiﬁcation Self-Service Provisioning Investigating application alarms Incident Management Proactively notify Incidents on AWS infrastru cture based on monitoring Self-Service Provisioning Handle application performance issues and outages Categorize Incident priority Provide Incident response Provide Incident resolution / infrastructure restore I R R I R R I I C Note SLAs do not apply to instance-based resources provisioned outside AMS change management, including those provisioned using self-service provisioning and developer mode. Problem Management Identify Problems in Managed Environment C R AMS responsibility matrix (RACI) Version May 08, 2025 26 AMS Advanced User Guide AMS Advanced Concepts and Procedures Activity Customer AWS Managed Services (AMS) Perform RCA for Problems in Managed Environment Remediation of Problems in Managed Environment Identify and remediate application problems Security Management Customer infrastructure security and/or establishing baseline for security compliance process as determined and agreed to during customer onboarding. Self-Service Provisioning Maintaining valid licenses for Managed EPS Conﬁgure Managed EPS Self-Service Provisioning Update Managed EPS Self-Service Provisioning Monitoring malware on instances provisioned through the AMS CM process. Self-Service Provisioning Maintaining and updating virus signatures. Self-Service Provisioning C C R C R R I R I R I R I R R R I R C C R C R C R C R C AMS responsibility matrix (RACI) Version May 08, 2025 27 AMS Advanced User Guide AMS Advanced Concepts and Procedures Activity Customer AWS Managed Services (AMS) Remediating instances infected with malware. Self-Service Provisioning Security event management Security - Access Management Manage the lifecycle of users, and their permissions for local directory services, which are used to access AWS Managed Services Operate federated authentication system(s) for customer access to AWS console/APIs Accept and maintain Active Directory (AD) trust from AWS Managed Services AD to customer managed AD During onboarding, create cross-account IAM Admin roles within each managed account Secure the AWS root credential for each account Deﬁne IAM resources for Managed Environme nt Manage privileged credentials for OS access for AMS engineers Manage privileged credentials for OS access provided to customer by AMS Security Incident Response - Prepare Communications C R C R R R R I C I R R
ams-ug-015	ams-ug.pdf	15	directory services, which are used to access AWS Managed Services Operate federated authentication system(s) for customer access to AWS console/APIs Accept and maintain Active Directory (AD) trust from AWS Managed Services AD to customer managed AD During onboarding, create cross-account IAM Admin roles within each managed account Secure the AWS root credential for each account Deﬁne IAM resources for Managed Environme nt Manage privileged credentials for OS access for AMS engineers Manage privileged credentials for OS access provided to customer by AMS Security Incident Response - Prepare Communications C R C R R R R I C I R R C R I C C C R R R I AMS responsibility matrix (RACI) Version May 08, 2025 28 AMS Advanced User Guide AMS Advanced Concepts and Procedures Activity Customer AWS Managed Services (AMS) Provide customer security contact details for AMS to use during security events notiﬁcat ions and security escalations Store and manage the supplied customer security contact details to use during security events and security escalations Training Provide customer with documentation to support AMS during incident response process Practice shared responsibility during incident response processes through security gamedays Resource management Conﬁgure supported security management AWS services for alerting, alerts correlation, noise reduction and additional rules Maintain asset (AWS resources) inventory, and know the asset value and criticality of assets. This information is helpful during incident containment strategy Employ AWS tags to identify resources and workloads Deﬁne and conﬁgure log retention and archival Secure baselining of AWS account, conﬁgura tions, policies and access management R CI I RI I R R CI CI I R R RC R CI CI R RC AMS responsibility matrix (RACI) Version May 08, 2025 29 AMS Advanced User Guide AMS Advanced Concepts and Procedures Activity Customer AWS Managed Services (AMS) Security Incident Response - Detect Logging, indicators and monitoring Conﬁgure logging and monitoring to enable event management for instance and accounts Monitor supported AWS services for security alerts CI I Deploy and manage endpoint security tools CI Monitor for malware on instances using AMS supported endpoint security tool Notify customer of detected events through outbound messaging Route notiﬁcation and any subsequent updates to the decision makers for speciﬁc accounts and workloads to improve incident response time Deﬁne, deploy, and maintain AMS standard detection services (for example, Amazon GuardDuty and AWS Conﬁg) Record AWS infrastructure change logs Enable and conﬁgure logging, monitoring to enable event management for the application Implement and maintain an allow-list, deny- list, and custom detections on supported AWS security services (for example, Amazon GuardDuty) I I R CI I R RCI R R R R R CI R RC C R AMS responsibility matrix (RACI) Version May 08, 2025 30 AMS Advanced User Guide AMS Advanced Concepts and Procedures Activity Customer AWS Managed Services (AMS) Security event reporting Notify AMS of a suspicious activity or an active security investigation Notify detected security events and incidents to the customer Notify planned event that might trigger Security Incident Response process Security Incident Response - Analyze Investigation and analysis R I R Perform initial response for supported security alert generated by a supported detection I source Assess false/true positives using the available data RI Generate a snapshot of aﬀected instances to be shared with the customer if needed Perform forensics tasks such as chain of custody, ﬁle system analysis, memory forensics, and binary analysis Collect application logs to aid investigation Collect data and logs to aid investigation on security alerts Engage SMEs within AWS services on security investigations I R R RCI CI CI R CI RC RC R CI I RC R AMS responsibility matrix (RACI) Version May 08, 2025 31 AMS Advanced User Guide AMS Advanced Concepts and Procedures Activity Customer AWS Managed Services (AMS) Engage third-party vendors during investiga tion (for example, for EPS anti-malware RCI investigation and engaging with TrendMicro support team) Share investigation logs from supported AWS services to customers during an investigation Communication Send alert and notiﬁcations from AMS detection sources for managed resources Manage alert and notiﬁcations for application security events Engage customer security point of contact during a security incident investigation Security Incident Response - Contain Containment strategy and execution Decide on the execution of the agreed containment strategy and agree with the consequences that might aﬀect the availability of services during the containment window Make a backup of aﬀected systems for further analysis Contain applications and workloads (through application speciﬁc conﬁguration or response activity) I I R R R CI R I R R I I CI R CI AMS responsibility matrix (RACI) Version May 08, 2025 32 AMS Advanced User Guide AMS Advanced Concepts and Procedures Activity Customer AWS Managed Services (AMS) CI CI CI R R CI CI R Deﬁne the containment strategy based on the security incident and the aﬀected resource
ams-ug-016	ams-ug.pdf	16	the agreed containment strategy and agree with the consequences that might aﬀect the availability of services during the containment window Make a backup of aﬀected systems for further analysis Contain applications and workloads (through application speciﬁc conﬁguration or response activity) I I R R R CI R I R R I I CI R CI AMS responsibility matrix (RACI) Version May 08, 2025 32 AMS Advanced User Guide AMS Advanced Concepts and Procedures Activity Customer AWS Managed Services (AMS) CI CI CI R R CI CI R Deﬁne the containment strategy based on the security incident and the aﬀected resource Enable encryption and secure storage of point in time backups of aﬀected systems Execute supported containment actions for AWS resources including EC2 instances, network, and IAM Security Incident Response - Eradicate Eradication strategy and execution Deﬁne eradication options based on the security incident and the aﬀected resource on customer application workloads Decide on the agreed eradication strategy, timing of eradication execution, and the consequences Deﬁne eradication steps based on the security incident and the aﬀected resource on AMS managed workloads Eradicate and harden AWS resources including EC2 instances, network, and IAM eradication Eradicate and harden applications and workloads (through application speciﬁc conﬁguration or response activity) Security Incident Response - Recover Recovery preparation and execution R R R CI CI R R I AMS responsibility matrix (RACI) Version May 08, 2025 33 AMS Advanced User Guide AMS Advanced Concepts and Procedures Activity Customer AWS Managed Services (AMS) Conﬁgure backup plans and targets as requested by the customer Review backup plans to restore AMS managed workloads Perform backup restoration activities for resources of supported AWS services Backup customer application, APP conﬁgura tion, and deployment settings, and review backup plans to restore customer applications and workloads post-incident Restore applications and customer workloads (through application speciﬁc restoration steps) R CI I R R Security Incident Response – Post Incident Report Post incident reporting Share appropriate lessons learned and action items with customer post incident as required Patch Management9 Monitor for applicable updates to supported OS and software preinstalled with supported OS for EC2 instances. Self-Service Provisioning Notify customer of upcoming updates (applies to AMS Standard Patch only) Exclude certain updates and/or certain Stacks from patching activities I I R I R I R R I I R R C R I AMS responsibility matrix (RACI) Version May 08, 2025 34 AMS Advanced User Guide AMS Advanced Concepts and Procedures Activity Customer AWS Managed Services (AMS) Deﬁne default and custom maintenance windows schedules and other parameters (e.g. maintenance window duration) to apply patches (applies to AMS Patch Orchestrator only) Deﬁne custom Patch Baselines to ﬁlter and exclude speciﬁc patches (applies to AMS Patch Orchestrator only) Tag instances to associate them with custom maintenance windows and Patch Baselines (applies to AMS Patch Orchestrator only) Track the patch status of resources and highlight systems that aren’t current in the monthly business review. Patch the Windows operating system, and Microsoft packages installed on the operating system which are governed by Windows Update Self-Service Provisioning Patch installed applications, software, or application dependencies not managed by Windows Update Self-service provisioning R R R C I R R R I I I R R - I - AMS responsibility matrix (RACI) Version May 08, 2025 35 AMS Advanced User Guide AMS Advanced Concepts and Procedures Activity Customer AWS Managed Services (AMS) Patch the Linux operating system and any package that is enabled for management by the operating system's native package manager (for example Yum, Apt, Zypper) Self-service provisioning Patch installed applications, software, or application dependencies not managed by the Linux operating system's native package manager Self-service provisioning Continuity Management Specify backup schedules Execute backups per schedule. Self-Service Provisioning Validate backups Request backup restoration activities Execute backup restoration activities. Self-Service Provisioning Restore aﬀected Stacks and VPCs. Self-Service Provisioning Restore aﬀected custom/3rd party application Reporting I R R R R I R R R I R I R R R - I - I R C I I R C R C C AMS responsibility matrix (RACI) Version May 08, 2025 36 AMS Advanced User Guide AMS Advanced Concepts and Procedures Activity Customer AWS Managed Services (AMS) Prepare and deliver monthly service report AMS on AWS Outposts Conﬁgure and retrieve API audit history on demand (CloudTrail). Self-service provisioning Provide access to incident history through AWS Managed Services Interface Provide access to change history through AWS Managed Services Interface. I R I R I I R I R I R R N/A N/A Self-service provisioning Service Request Management Request information using service requests Reply to service requests Managed Firewall Request the deployment of AMS-Managed Firewall Design and optimization of AMS-Managed Firewall architecture Deployment of AWS Infrastructure and AMS- Managed Firewall appliance Providing Firewall licenses (including usage fees for the applicable AWS services – e.g.
ams-ug-017	ams-ug.pdf	17	AMS on AWS Outposts Conﬁgure and retrieve API audit history on demand (CloudTrail). Self-service provisioning Provide access to incident history through AWS Managed Services Interface Provide access to change history through AWS Managed Services Interface. I R I R I I R I R I R R N/A N/A Self-service provisioning Service Request Management Request information using service requests Reply to service requests Managed Firewall Request the deployment of AMS-Managed Firewall Design and optimization of AMS-Managed Firewall architecture Deployment of AWS Infrastructure and AMS- Managed Firewall appliance Providing Firewall licenses (including usage fees for the applicable AWS services – e.g. EC2) R I R I I R I R I R R I AMS responsibility matrix (RACI) Version May 08, 2025 37 AMS Advanced User Guide AMS Advanced Concepts and Procedures Activity Customer AWS Managed Services (AMS) Deﬁne default domain allow-list Request to add, modify, and delete custom allow-lists and security policies Conﬁguring alerts for AMS-Managed Firewall Monitoring all AMS-Managed Firewall conﬁgured alerts Execute Backups of ﬁrewall conﬁguration Request backup restoration activities Update provisioned resources with new version of product Recording AMS-Managed Firewall logs Forward logs from AMS-Managed Firewall to CloudWatch Request conﬁguration changes in the AMS- Managed Firewall Approve conﬁguration changes in the AMS- Managed Firewall Execute conﬁguration changes in the AMS- Managed Firewall I R I I I R I I I R I I R I R R R I R R R I R R 8AMS provides AMIs for Amazon EC2 only 9AMS is responsible for End of Life OSes only when the customer signs an extended support agreement with OS vendor AMS responsibility matrix (RACI) Version May 08, 2025 38 AMS Advanced User Guide AMS Advanced Concepts and Procedures AMS environment basic components Multi-Account Landing Zone This is an estimate of the components, and potential costs, of the infrastructure in the core accounts. This does not include other costs such as bandwidth, CloudWatch detailed monitoring, logging, alarms, Route53, Amazon S3, Simple Notiﬁcation Service (Amazon SNS), snapshots, or reserved Amazon EC2 instances. You pay for the components required by the AMS-Managed AWS landing zone infrastructure. Estimates place the cost of a plain AMS multi-account landing zone environment at $2,450 per month and $50 for a plain application account. For information about pricing, see AWS pricing. Basic Environment Components Component Est. Cost Description Management account $60 An AWS Organizations Management account; creates and ﬁnancially manages member accounts. It contains the AWS Landing Zone (ALZ) framework, account conﬁguration stack sets, and AWS Organization service control policies (SCPs). Shared Services Account $2000 • Directory Service: $35 • CloudTrail: $7 • CloudWatch: $6 • Others: $12 Contains infrastructure and resources required for access management (i.e., Active Directory), end-point security management (Trend Micro), and your bastions (SSH/RDP); estimate is $2400 a month. This estimate does not include the cost of the Trend Micro licenses. • EC2: $800 (with the minimum number of Bastions) • RDS: $300 (EPS) • VPC (endpoints): $400 AMS environment basic components Version May 08, 2025 39 AMS Advanced User Guide AMS Advanced Concepts and Procedures Component Est. Cost Description Networking Account $350 • Directory Service: $300 • CloudWatch: $100 • GuardDuty : $15 • Secrets Manager: $10 • Data Transfer: $10 • Conﬁg: $10 • Others: $45 The central hub for network routing between AMS accounts, your on-premise network, and egress traﬃc to the Internet. Additionally, contains public DMZ bastions (the entry point for AMS engineers to access hosts in your AMS environment). Price may increase depending on traﬃc traversing the Transit Gateway and Direct Connect. • EC2: $250 (Bastions) • VPC: $80 • Others: $20 Log Archive Account $20 An S3 bucket with copies of AWS CloudTrail and AWS Conﬁg log ﬁles from each of your AMS environment accounts. Costs increase as more logs are collected. • S3: $10 • CloudWatch: $5 • Others: $5 AMS environment basic components Version May 08, 2025 40 AMS Advanced User Guide AMS Advanced Concepts and Procedures Component Est. Cost Description Security Account $20 The central hub for security related operations, and the main point for funneling notiﬁcations and alerts to AMS control plane services. Additionally, houses the Amazon Guard Duty management account. Costs increase as more events are analyzed using Amazon GuardDuty. • CloudWatch: $15 • Others: $5 Single-Account Landing Zone The following table lists the components of an example AMS-managed infrastructure. Basic Environment Components, Last Updated 2020/07/09 Name Instance Type OS # of Component s 2 2 2 2 2 mc-eps-dsm m5.large Linux mc-management m5.large Windows mc-bastion-dmz-ssh m5.large Linux mc-bastion-customer-rdp m5.large Windows mc-eps-relay m5.large Linux directory services additional components N/A N/A N/A N/A For information about pricing, see AWS Pricing. AMS environment basic components Version May 08, 2025 41 AMS Advanced User Guide AMS Advanced Concepts and Procedures AMS account limits There are three distinct types of limits
ams-ug-018	ams-ug.pdf	18	using Amazon GuardDuty. • CloudWatch: $15 • Others: $5 Single-Account Landing Zone The following table lists the components of an example AMS-managed infrastructure. Basic Environment Components, Last Updated 2020/07/09 Name Instance Type OS # of Component s 2 2 2 2 2 mc-eps-dsm m5.large Linux mc-management m5.large Windows mc-bastion-dmz-ssh m5.large Linux mc-bastion-customer-rdp m5.large Windows mc-eps-relay m5.large Linux directory services additional components N/A N/A N/A N/A For information about pricing, see AWS Pricing. AMS environment basic components Version May 08, 2025 41 AMS Advanced User Guide AMS Advanced Concepts and Procedures AMS account limits There are three distinct types of limits to consider within AMS multi-account landing zone: AMS API limits, AMS resource limits, and AWS limits. There are two distinct types of limits to consider within AMS single-account landing zone: AMS API limits, and AWS limits. AMS account API limits This section describes the account level limits after which AWS Managed Services (AMS) throttles the AMS SKMS API service. This means, if you call any of the listed APIs more than 10 times in a second, one of the calls is "throttled" (you receive a ThrottleException). Under rare situations, an external or downstream dependency might throttle the AMS API and then AMS may throttle your API calls at a possibly lower rate. Note For information on the AMS SKMS API, download the reference through the Reports tab of the AWS Artifact console. For each AMS SKMS API listed, the operation is throttled after 10 TPS (transactions per second): • GetStack • GetSubnet • GetVpc • ListAmis • ListStackSummaries • ListSubnetSummaries • ListVpcSummaries AMS multi-account landing zone account resource limits Account resource limits relate to AMS multi-account landing zone application accounts and VPCs and subnets. AMS account limits Version May 08, 2025 42 AMS Advanced User Guide AMS Advanced Concepts and Procedures Application account resource limits There is a soft limit of 50 application accounts per organization. If you have a use case for more than 50 application accounts, contact your cloud service delivery manager (CSDM) to relay your requirements. VPCs and subnets resource limits There is a soft limit of 10 VPCs per application account within the pre-deﬁned AWS Region for the organization. Each VPC may have 1 to 10 private subnet tiers spanned across 2 to 3 availability zones. Additionally, each VPC may have 0 to 5 public subnet tiers spanned across 2 to 3 availability zones. If you have requirements beyond these limits, inform your CSDM or Cloud Architect to review your use case. AMS multi-account landing zone application to account ratio One account per application is supported in AMS multi-account landing zone; however, each Application account has a small cost, and you are charged for the number of connections to the Transit Gateway per hour, and the amount of traﬃc that ﬂows through AWS Transit Gateway. So, the more segregated applications are into accounts or VPCs, the higher the costs. To reduce costs and still ensure an appropriate segregation of duties, AMS recommends that you 1) group applications by teams with tightly coupled business processes, and 2) do not mix applications that are in diﬀerent stages (prod vs. non-prod) or managed by diﬀerent teams. In this way, you will have fewer accounts, access management and the segregation of duties will be easier, and traﬃc cost could be mitigated. For example: An enterprise has in production a Trading application and a Portfolio Management application, both applications are managed by the Investments IT team and exchange a lot of traﬃc with each other. In this scenario the company can beneﬁt from grouping both applications in the same account and same the VPC, because the Investments IT team won’t have to request access to multiple Application accounts and the company will save on traﬃc costs. In this case, the company should create another account for the same applications in development stage and provide access to the development team. In another scenario, the enterprise has in production a Payroll application and an Accounting application, managed by the Human Resources IT and Accounting IT teams respectively. Although AMS account limits Version May 08, 2025 43 AMS Advanced User Guide AMS Advanced Concepts and Procedures the Payroll application has to exchange information with the Accounting application, we recommend segregating both applications in diﬀerent accounts, one per team, and establishing a connection between both application’s VPCs using the Networking account. In this way, the company will prevent HR IT team request changes aﬀecting the accounting application infrastructure, of which they would have no knowledge. Tips on how to group accounts into organizational units (OUs). An OU is logical grouping mechanism that enables you to categorize (group) accounts and apply policies and conﬁgurations to based on those groups. The recommended approach for creating OUs is to base them on policies that need to be applied
ams-ug-019	ams-ug.pdf	19	the Accounting application, we recommend segregating both applications in diﬀerent accounts, one per team, and establishing a connection between both application’s VPCs using the Networking account. In this way, the company will prevent HR IT team request changes aﬀecting the accounting application infrastructure, of which they would have no knowledge. Tips on how to group accounts into organizational units (OUs). An OU is logical grouping mechanism that enables you to categorize (group) accounts and apply policies and conﬁgurations to based on those groups. The recommended approach for creating OUs is to base them on policies that need to be applied to a speciﬁc group of accounts, not on the internal hierarchy of teams within your reporting structure. An OU is not equivalent to an Active Directory’s OU, and attempting to replicate the AD OU structure in AWS Organizations is discouraged and results in a diﬃcult to maintain and/or operate structure. AWS account limits AWS account limits apply to your AWS Managed Services (AMS) accounts. The easiest method to determine default and current limits for AWS services is by leveraging AWS Service Quotas. AMS recommends right-sizing individual service limits to the appropriate size to run the service(s) in the account. Limits act like guard-rails to protect your accounts for security and cost runaways. If you would like to raise a speciﬁc limit, submit a service request with AMS, and AMS Operations will raise the limit on your behalf. For example, the default limit (or quota) for RDS instances is 40; if your workload requires 50 RDS instances, raise a service request for AMS Operations to raise the limit to your needed value. AMS service level objectives (SLOs) The following table describes the goals of the AWS Managed Services (AMS) service. Service Level Agreements (SLAs) for other aspects of the AMS service, including incident management, are covered in the SLA document shared with you when you subscribed to AMS. For more information, speak to your CSDM. AMS service level objectives (SLOs) Version May 08, 2025 44 AMS Advanced User Guide AMS Advanced Concepts and Procedures AMS Service Level Objectives Feature Performance Indicator (PI) Plus Premium Change management Problem managemen t Service request management (Business Days, M-F 8AM to (Calendar Days, 24 x 7) 6PM local time) <=30 min <=30 min <=1 min <=1 min <=48 hours <=24 hours <=5 days <=5 days <=10 days <=10 days <=8 hours <=4 hours Time taken to schedule or reject automated RFCs Time of initiatio n of scheduled RFCs compared to scheduled execution time Time taken to approve/reject non- automated RFCs, available in CT catalog Time taken to approve/reject non- automated RFCs not available in CT catalog Time taken to complete root cause analysis (RCA) Response time for ﬁrst and every subsequent reply AMS service level objectives (SLOs) Version May 08, 2025 45 AMS Advanced User Guide AMS Advanced Concepts and Procedures Supported AWS services AWS Managed Services (AMS) provides operational management support services for the following AWS services. Each AWS service is distinct, and as a result AMS's level of operational management, support varies depending on the nature and characteristics of the underlying AWS service. Speciﬁc AWS services are grouped based on the complexity and scope of the operational management support service provided by AMS. Note The three groups, A, B, and C, indicate pricing as a percentage of total monthly spend per account for the AMS service, based on support plan (Plus or Premium), for AMS customers before March 16, 2021. AMS customers onboarded after March 16, 2021 should submit a service request for additional pricing information. Group A indicates no additional charge. Group B indicates an additional charge of 12% (Plus) or 18% (Premium). Group C indicates an additional charge of 25% (Plus) or 42% (Premium). One star () indicates services that are deployed within an AMS managed environment by a customer using the AWS Console and APIs. See 'Automated and self-service provisioning management' in AWS Managed Services (AMS) AMS Advanced operation plan features for additional details on customer responsibilities when provisioning and conﬁguring services in this manner. Two stars () indicate that Amazon EC2 on AWS Outposts will be billed as a Group B service; all other resources hosted on AWS Outposts will be billed at their standard rate. Supported AWS services Group A Group B Group C Amazon Alexa for Business Amazon API Gateway* Amazon AppStream* Amazon Aurora Amazon CloudWatch Amazon Managed Streaming Amazon Athena* Amazon Elastic Block for Apache Kafka* Amazon CloudFront Amazon Bedrock* Store (EBS) Amazon CloudSearch* Amazon Elastic Compute Amazon Elastic File Amazon Cognito* Cloud** System Amazon Glacier Amazon Comprehend* Amazon Connect* Amazon Elastic Load Balancing (classic, Amazon Simple Storage Amazon Document DB (with application, and Service MongoDB compatibility)* network; not gateway) Supported AWS services Version May 08, 2025 46 AMS Advanced User Guide AMS Advanced Concepts and
ams-ug-020	ams-ug.pdf	20	will be billed at their standard rate. Supported AWS services Group A Group B Group C Amazon Alexa for Business* Amazon API Gateway* Amazon AppStream* Amazon Aurora Amazon CloudWatch Amazon Managed Streaming Amazon Athena* Amazon Elastic Block for Apache Kafka* Amazon CloudFront Amazon Bedrock* Store (EBS) Amazon CloudSearch* Amazon Elastic Compute Amazon Elastic File Amazon Cognito* Cloud** System Amazon Glacier Amazon Comprehend* Amazon Connect* Amazon Elastic Load Balancing (classic, Amazon Simple Storage Amazon Document DB (with application, and Service MongoDB compatibility)* network; not gateway) Supported AWS services Version May 08, 2025 46 AMS Advanced User Guide AMS Advanced Concepts and Procedures Group A Group B Group C AWS Amplify* AWS AppMesh* AWS Auto Scaling AWS Backup Amazon DynamoDB* Amazon EC2 Container Registry (ECR)* Amazon ElastiCache Amazon OpenSearch Service Amazon Elastic Container Amazon GuardDuty AWS CloudFormation Service (ECS) on AWS Amazon Macie AWS Compute Optimizer Fargate* Amazon Redshift AWS Global Accelerator* Amazon Elastic Kubernete Amazon Relational AWS Identity and Access s Service (EKS) on Management Fargate* Database Service Amazon Route 53 AWS License Manager* Amazon Elemental Amazon Route 53 Resolver AWS Management Console MediaConvert* DNS Firewall AWS Marketplace Amazon Elemental Amazon Simple Email AWS Lake Formation* MediaPackage* Service AWS Well Architected Amazon Elemental Amazon Simple Notificat Tool* MediaStore* ion Service VM Import/ Export* Amazon Elemental Amazon Simple Queue MediaTailor* Service Amazon Elastic MapReduce Amazon Virtual Private * AmazonEventBridge* Amazon Forecast* Amazon FSx* Amazon Inspector* Amazon Kendra* Cloud (VPC) AWS CloudTrail AWS Config AWS Database Migration Service AWS Data Transfer Amazon Kinesis Analytics AWS Direct Connect * AWS Directory Service Amazon Kinesis Data AWS Key Management Service AWS Systems Manager (SSM) Stream* Amazon Kinesis Firehose* Amazon Kinesis Video Streams* Amazon Lex* Amazon Managed Service for Prometheus* Amazon MQ* Amazon Personalize** Amazon Quantum Ledger Database (QLDB)* Amazon QuickSight* Amazon Rekognition* Amazon SageMaker* Supported AWS services Version May 08, 2025 47 AMS Advanced User Guide AMS Advanced Concepts and Procedures Group A Group B Group C Amazon SimpleDB* Amazon Simple Workflow* Amazon Textract* Amazon Transcribe* Amazon Translate* Amazon WorkDocs* Amazon WorkSpaces* AWS AppSync* AWS Audit Manager* AWS Batch* AWS Certificate Manager* AWS CloudEndure* AWS CloudHSM* AWS CodeBuild* AWS CodeCommit* AWS CodeDeploy* AWS CodePipeline* AWS DataSync* AWS Elemental MediaLive* AWS Glue* AWS Lambda* AWS MigrationHub* AWS Outposts** AWS Resilience Hub* AWS Secrets Manager* AWS Security Hub* AWS Service Catalog AWS Service Catalog AppRegistry* AWS Transfer for SFTP* AWS Shield* AWS Snowball* AWS Step Functions* AWS Transit Gateway* AWS WAF* AWS X-Ray* Supported AWS services Version May 08, 2025 48 AMS Advanced User Guide AMS Advanced Concepts and Procedures If you request AWS Managed Services to provide services for any software or service that is not expressly identiﬁed as supported below, any AWS Managed Services provided for such customer requested conﬁgurations will be treated as a "Beta Service" under the Service Terms. Supported conﬁgurations These are the conﬁgurations AWS Managed Services (AMS) supports: • Language: AMS is available in English. • Firewall Services: • Amazon Route 53 Resolver DNS Firewall • Palo Alto VM-Series Next-Generation Firewall • Security software: Deep Security from Trend Micro (Required). AWS Marketplace: Trend Micro Deep Security • Approved directory services: Microsoft Active Directory (AD) • Supported AWS services. • Supported AWS Regions: AMS operates in a subset of all AWS Regions; however, the AMS API/CLI runs out of the "USA East (N. Virginia)" Region only. If you run either the AMS change management API (amscm) or the AMS service knowledge management API (amsskms), in a non-USA East Region, you must add --region us-east-1 to the command. • 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 West (Paris) • Asia Paciﬁc (Mumbai) • Asia Paciﬁc (Seoul) Supported conﬁgurations Version May 08, 2025 49 AMS Advanced User Guide AMS Advanced Concepts and Procedures • Asia Paciﬁc (Singapore) • Asia Paciﬁc (Sydney) • Asia Paciﬁc (Tokyo) • Amazon machine images (AMIs): AMS provides security enhanced images (AMIs) based on the CIS Level 1 benchmark for a subset of operating systems supported by AMS. To ﬁnd operating systems that have a security enhanced image available, see the AMS Security User Guide. To access this guide, in AWS Artifact, ﬁlter the Reports tab for AWS Managed Services. To access AWS Artifact, contact your CSDM or see, Getting Started with AWS Artifact. • 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 speciﬁc versions, SUSE Linux Enterprise Server 12 SP5 and SAP speciﬁc versions. • Microsoft Windows Server 2022, 2019, 2016 • Ubuntu
ams-ug-021	ams-ug.pdf	21	Security User Guide. To access this guide, in AWS Artifact, ﬁlter the Reports tab for AWS Managed Services. To access AWS Artifact, contact your CSDM or see, Getting Started with AWS Artifact. • 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 speciﬁc versions, SUSE Linux Enterprise Server 12 SP5 and SAP speciﬁc 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 End of Support (EOS) operating systems: Note End of Support (EOS) operating systems are outside of the general support period of the operating system manufacturer and have increased security risk. EOS operating systems are considered supported conﬁgurations only if AMS-required agents support the operating system and... 1. you have extended support with the operating system vendor that allows you to receive updates, or 2. any instances using an EOS operating system follow the security controls as speciﬁed Supported conﬁgurations by AMS in the Advanced User Guide, or Version May 08, 2025 50 AMS Advanced User Guide AMS Advanced Concepts and Procedures 3. you comply with any other compensating security controls required by AMS. In the event AMS is no longer able to support an EOS operating system, AMS issues a Critical Recommendation to upgrade the operating system. AMS-required agents may include but are not limited to: AWS Systems Manager, Amazon CloudWatch, Endpoint Security (EPS) agent, and Active Directory (AD) Bridge (Linux only). • Ubuntu Linux 18.04 • SUSE Linux Enterprise Server 15 SP3 and SP4 • Microsoft Windows Server 2012/2012 R2 • Red Hat Enterprise Linux (RHEL):7.x Capabilities for unsupported operating systems in AMS An unsupported operating system is any operating system not listed in the Supported conﬁgurations. AMS considers instances with unsupported operating systems to be "Customer- Requested Conﬁgurations" that are subject to the AWS Betas and Previews service terms. The following limited set of AMS capabilities are available to instances with unsupported operating systems: Capability Notes Incident management AMS provides incident response. Service request management AMS responds to service requests. Requests for change (RFCs) Monitoring AMS evaluates RFCs for execution. Unsupported operating systems may impact the ability to execute RFCs. AMS monitors and responds to Amazon EC2 system status checks and instance status checks. System status checks include: loss of network connectivity, loss of system power, software issues on the physical host, and hardware issues on the physical host that impact network reachability. Unsupported operating systems Version May 08, 2025 51 AMS Advanced User Guide AMS Advanced Concepts and Procedures Capability Notes Security management Backup management Instance status checks include: incorrect networking or startup conﬁguration, exhausted memory, corrupted ﬁle system, and incompatible kernel. AMS monitors and responds to Amazon EC2 GuardDuty ﬁndings. AMS provides Continuity management in AMS Advanced for EC2 using AMS-customized AWS Backup plans and vaults. AMS Advanced interfaces • AMS Advanced console: You use the AMS Advanced console to create RFCs, report and respond to incidents, make service requests, and ﬁnd information on existing VPCs and stacks. When in doubt of what to do, or when you need help with AMS or your managed resources, create a service request by using this interface. • AWS Management Console: Many AWS consoles can be useful for viewing AMS information, for example: • Amazon EC2 console: Use to view instance information including bastion IP addresses, Amazon EC2 Auto Scaling groups, and load balancers. • Multi-Account Landing Zone AWS Conﬁg Rules compliance: You can view compliance status across your accounts and identify non-compliant resources. • AWS CloudFormation console: Use to view stack information including stack IDs (you can ﬁnd Amazon RDS stacks and Amazon RDS instance IDs here, and event information). • Amazon RDS console: Use to view event information such as a post made to a WordPress app on a site in your account. Note you must have the Amazon RDS instance ID. Depending on the mode of your login role, you have diﬀerent level of access to the AWS Management Console. For more information on modes, see AMS modes. • AMS Advanced change management API – Read/Write: Use the change management API (CM API) to request additions and speciﬁc changes to your managed infrastructure including resource monitoring, log, backup, and patch conﬁgurations. Also, use this API to request access to AMS Advanced interfaces Version May 08, 2025 52 AMS Advanced User Guide AMS Advanced Concepts and Procedures resources, delete resources, create AMIs, and create IAM instance proﬁles. You can access the CM API through the AMS CLI and SDKs. • AMS SKMS API – Read-Only: Use this
ams-ug-022	ams-ug.pdf	22	the AWS Management Console. For more information on modes, see AMS modes. • AMS Advanced change management API – Read/Write: Use the change management API (CM API) to request additions and speciﬁc changes to your managed infrastructure including resource monitoring, log, backup, and patch conﬁgurations. Also, use this API to request access to AMS Advanced interfaces Version May 08, 2025 52 AMS Advanced User Guide AMS Advanced Concepts and Procedures resources, delete resources, create AMIs, and create IAM instance proﬁles. You can access the CM API through the AMS CLI and SDKs. • AMS SKMS API – Read-Only: Use this API to list managed resources and get information needed for reporting or preparing requests for change. • Support API: Use the standard Support API to programmatically create and respond to incidents and service requests. To learn more, see Getting Started with Support. • AWS APIs – Read Only: Your main IT administrator can use the AWS APIs to see all resources under management, view CloudTrail logs, billing information, and many other read functions. AMS VPC endpoints A VPC endpoint lets you privately connect your VPC to AWS services without requiring an Internet gateway. Instances in your VPC do not require public IP addresses to communicate with resources in the service. Endpoints are virtual devices. They are horizontally scaled, redundant, and highly available VPC components that allow communication between instances in your VPC and services without imposing availability risks or bandwidth constraints on your network traﬃc. To learn more, see VPC Endpoints. There are two types of VPC endpoints: interface endpoints and gateway endpoints. • Gateway endpoints: The VPC in the account has an Amazon S3 Gateway endpoint enabled by default. • Interface endpoints: Instances in your AMS environment can talk to supported services without leaving the Amazon network. This is optional for single-account landing zone and it is not enabled in the account by default; submit a service request to AMS operations to get this enabled. However, for multi-account landing zone, interface endpoints are enabled by default in the Shared Services account. List of interface endpoints supported by AMS: • AWS CloudFormation • AWS CloudTrail • AWS Conﬁg • Amazon EC2 API • AWS Key Management Service VPC endpoints Version May 08, 2025 53 AMS Advanced User Guide AMS Advanced Concepts and Procedures • Amazon CloudWatch • Amazon CloudWatch Events • Amazon CloudWatch Logs • AWS Secrets Manager • Amazon SNS • AWS Systems Manager • AWS Security Token Service AMS protected namespaces The list of protected namespaces for AWS Managed Services (AMS). When you work with AWS resources, prevent conﬂict with AMS by not using these namespaces. For details on other AWS service namespaces, see Amazon Resource Names (ARNs) and AWS Service Namespaces. • ams-* (this is the preferred naming standard for new resources) • /ams/* (this is the preferred naming standard for path-based resources) • AWSManagedServices* (this is the preferred naming standard for resources where CamelCase is appropriate) • ams* and AMS* and Ams* • AWS_* and aws* • /aws_reserved/ • CloudTrail* and Cloudtrail* • codedeploy_service_role • customer-mc-* • eps and EPS • EPSMarketplaceSubscriptionRole • EPSDB* • IAMPolicy* • INGEST* • LandingZone* • Managed_Services* AMS protected namespaces Version May 08, 2025 54 AMS Advanced Concepts and Procedures AMS Advanced User Guide • managementhost • mc* and MC* and Mc* • MMS* • ms- • NewAMS* • Root* • sentinel* and Sentinel* • sentinel.int. • StateMachine* • StackSet-ams* • StackSet-AWS-Landing-Zone • TemplateId* • UnhealthyInServiceBastion • VPC_* AMS reserved preﬁxes AMS resource attributes must comply with certain patterns; for example, IAM instance proﬁle names, BackupVault names, tag names, and so forth, must not start with AMS reserved preﬁxes. Those reserved preﬁxes are: /aws_reserved/ ams-* /ams/* ams* AMS* Ams* aws* AWS* AWS_* AWSManagedServices* codedeploy_service_role CloudTrail* Cloudtrail* customer-mc-* AMS reserved preﬁxes Version May 08, 2025 55 AMS Advanced User Guide AMS Advanced Concepts and Procedures eps EPSDB* IAMPolicy* INGEST* LandingZone* Managed_Services* managementhost mc* MC* Mc* MMS* ms- NewAMS* Root* sentinel* Sentinel* sentinel.int. StackSet-ams* StackSet-AWS-Landing-Zone StateMachine* TemplateId* VPC_* UnhealthyInServiceBastion AMS maintenance window 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 Paciﬁc Time. AMS may change the maintenance window with 48 hours notice. This is for AWS Managed Services (AMS); to perform maintenance activities for managed infrastructures, such as deploying new AMS AMIs. Your maintenance window is when AMS will apply patching and you determine your maintenance window at onboarding. You can also agree to the proposed patching window provided in your patching service notiﬁcation, or suggest a diﬀerent window. For guidance on creating a maintenance window, see Maintenance Window. AMS information resources AMS provides several information resources to help you succeed. AMS maintenance window Version May 08, 2025 56 AMS
ams-ug-023	ams-ug.pdf	23	Paciﬁc Time. AMS may change the maintenance window with 48 hours notice. This is for AWS Managed Services (AMS); to perform maintenance activities for managed infrastructures, such as deploying new AMS AMIs. Your maintenance window is when AMS will apply patching and you determine your maintenance window at onboarding. You can also agree to the proposed patching window provided in your patching service notiﬁcation, or suggest a diﬀerent window. For guidance on creating a maintenance window, see Maintenance Window. AMS information resources AMS provides several information resources to help you succeed. AMS maintenance window Version May 08, 2025 56 AMS Advanced User Guide AMS Advanced Concepts and Procedures • AMS Accelerate User Guide: Helps you understand the components and features that AMS Accelerate provides and how to use them. Look here for AMS Accelerate background information and details on default settings, ﬁnding resources, and how-to examples. HTML index, PDF • AMS Advanced User Guide: Helps you understand the components and features that AMS Advanced provides and how to use them. Look here for AMS Advanced background information and details on default settings, ﬁnding resources, and how-to examples. HTML index, PDF • AMS Advanced Application Guide: Describes the steps for deploying applications to AWS Managed Services infrastructure. Look here for information on application deployment and maintenance methodologies and considerations. HTML index, PDF. • AMS Advanced Onboarding Guide: Describes the initial steps for creating the basic AWS Managed Services multi-account, or single-account, landing zone infrastructure in an AMS account. Look here for information on AMS account basics, validation, and questions to prepare you for onboarding to AMS. HTML index, PDF. • AMS Advanced Change Type Reference: Provides reference material on the current change types that AWS Managed Services provides, including change type schemas and example walkthroughs for each change type and tips. Includes general information about change types Helps you understand all aspects of requests for change (RFCs) and AMS change types (CTs). Look here for speciﬁcs on change types, including links to relevant information. HTML index, PDF. • AMS CM (change management) API Reference: Describes the AWS Managed Services CM API, which provides operations for creating and monitoring change requests and provides information about your resources that are managed by Managed Services. HTML index. • AMS Security Guides: Describe proprietary AMS security information. Private; available on the AMS Reports tab in the AWS Artifact Console. • AMS Developer's Resources: Access to the AMS CLI and SDK, for both amscm and amsskms. See https://console.aws.amazon.com/managedservices/. • AMS YouTube Videos: Key customer operations explained in video. See AWS Managed Services YouTube Instructional Videos. • AMS Blog posts: Specialty information on AWS Managed Services. See AWS Blogs. AMS compliance AMS has undergone auditing for the following standards and is eligible for use as part of solutions for which you must obtain compliance certiﬁcation. AMS compliance Version May 08, 2025 57 AMS Advanced User Guide AMS Advanced Concepts and Procedures AMS Supported Compliance Standards AMS supports AWS compliance standards. To learn more about AWS compliance programs, see AWS Compliance. These are the current compliance standards supported by AMS. FedRAMP: The US Federal Government is dedicated to delivering its services to the American people in the most innovative, secure, and cost-eﬃcient fashion. Cloud computing plays a key part in how the federal government can achieve operational eﬃciencies and innovate on demand to advance their mission across the nation. That is why many federal agencies today are using AWS cloud services to process, store, and transmit federal government data. For more information, see FedRAMP. HIPAA: AWS has expanded its Health Insurance Portability and Accountability Act (HIPAA) compliance program to include AMS as a HIPAA Eligible Service. If you have a Business Associate Agreement (BAA) with AWS, you can use AMS to help build your HIPAA-compliant applications. See HIPAA-focused whitepaper to learn how to leverage AMS for the processing and storage of health information. For more information, see HIPAA Compliance. HITRUST: The Health Information Trust Alliance Common Security Framework (HITRUST CSF) leverages nationally and internationally accepted standards and regulations such as GDPR, ISO, NIST, PCI, and HIPAA to create a comprehensive set of baseline security and privacy controls. For more information, see HITRUST CSF. AMS Supported Compliance Standards Version May 08, 2025 58 AMS Advanced User Guide AMS Advanced Concepts and Procedures ISO 27001: ISO/IEC 27001:2013 is a security management standard that speciﬁes security management best practices and comprehensive security controls following the ISO/IEC 27002 best practice guidance. The basis of this certiﬁcation is the development and implementation of a rigorous security program, which includes the development and implementation of an Information Security Management System (ISMS) which deﬁnes how AWS perpetually manages security in a holistic, comprehensive manner. For more information, see ISO/IEC 27001:2013. ISO 27017: ISO/IEC 27017:2015 provides guidance on the information security aspects of cloud computing, recommend
ams-ug-024	ams-ug.pdf	24	May 08, 2025 58 AMS Advanced User Guide AMS Advanced Concepts and Procedures ISO 27001: ISO/IEC 27001:2013 is a security management standard that speciﬁes security management best practices and comprehensive security controls following the ISO/IEC 27002 best practice guidance. The basis of this certiﬁcation is the development and implementation of a rigorous security program, which includes the development and implementation of an Information Security Management System (ISMS) which deﬁnes how AWS perpetually manages security in a holistic, comprehensive manner. For more information, see ISO/IEC 27001:2013. ISO 27017: ISO/IEC 27017:2015 provides guidance on the information security aspects of cloud computing, recommend ing the implementation of cloud-speciﬁc information security controls that supplement the guidance of the ISO/IEC 27002 and ISO/IEC 27001 standards. This code of practice provides additional information security controls implementation guidance speciﬁc to cloud service providers. For more information, see ISO/IEC 27017:2015 Compliance. ISO 27018: ISO/IEC 27018:2019 is a code of practice that focuses on protection of personal data in the cloud. It is based on ISO/IEC information security standard 27002 and provides implementation guidance on ISO/IEC 27002 controls applicabl e to public cloud Personally Identiﬁable Information (PII). It also provides a set of additional controls and associate d guidance intended to address public cloud PII protection requirements not addressed by the existing ISO/IEC 27002 control set. For more information, see ISO/IEC 27018:2019 Compliance. AMS Supported Compliance Standards Version May 08, 2025 59 AMS Advanced User Guide AMS Advanced Concepts and Procedures ISO 9001: ISO 9001:2015 outlines a process-oriented approach to documenting and reviewing the structure, responsib ilities, and procedures required to achieve eﬀective quality management within an organization. Speciﬁc sections of the standard contain information on topics such as: • Requirements for a quality management system, including documentation of a quality manual, document control, and determining process interactions • Responsibilities of management • Management of resources, including human resources and an organization’s work environment • Service development, including the steps from design to delivery • Customer satisfaction • Measurement, analysis, and improvement of the QMS through activities like internal audits and corrective and preventive actions For more information, see ISO 9001:2015 Compliance. PCI: AMS has an Attestation of Compliance for Payment Card Industry (PCI) Data Security Standard (DSS) version 3.2 at Service Provider Level 1. Customers who use AWS products and services to store, process, or transmit cardholder data can use AMS as they manage their own PCI DSS compliance certiﬁca tion. For more information about PCI DSS, including how to request a copy of the AWS PCI Compliance Package, see PCI DSS Level 1. Importantly, you must conﬁgure ﬁne-grained password policies in AMS to be consistent with PCI DSS version 3.2 standards. For details on which policies must be enforced, see Enable PCI Compliance for Your AWS Microsoft AD Directory. AMS Supported Compliance Standards Version May 08, 2025 60 AMS Advanced User Guide AMS Advanced Concepts and Procedures SOC: AMS System & Organization Control (SOC) Reports are independent, third-party examination reports that demonstra te how AMS achieves key compliance controls and objectives. The purpose of these reports is to help you and your auditors understand the AMS controls established to support operation s and compliance. There are three types of AMS SOC reports: • AWS SOC 1 Report - Download with AWS Artifact • AWS SOC 2: Security, Availability, & Conﬁdentiality Report - Download with AWS Artifact • AWS SOC 3: Security, Availability, & Conﬁdentiality Report For more information, see SOC Compliance. Shared Responsibility Security, including PCI compliance, is a shared responsibility. It is important to understand that AMS compliance status does not automatically apply to applications that you run in the AWS Cloud. You need to ensure that your use of AWS services complies with the standards. For more details on how AMS works together with customers across speciﬁc activities, see the AMS AMS responsibility matrix (RACI). AMS Amazon Machine Images (AMIs) AMS produces updated Amazon Machine Images (AMIs) every month for AMS supported operating systems. In addition, AMS also produces security enhanced images (AMIs) based on CIS Level 1 benchmark for a subset of AMS's supported operating systems. To ﬁnd out which operating systems have a security enhanced image available, see the AMS Security User Guide, which is available through AWS Artifact -> Reports page (ﬁnd the Reports option in the left navigation pane) ﬁltered for AWS Managed Services. To access AWS Artifact, can contact your CSDM for instructions or go to Getting Started with AWS Artifact. To receive alerts when new AMS AMIs are released, you can subscribe to an Amazon Simple Notiﬁcation Service (Amazon SNS) notiﬁcation topic called "AMS AMI". For details, see AMS AMI notiﬁcations with SNS. Shared Responsibility Version May 08, 2025 61 AMS Advanced User Guide AMS Advanced Concepts and Procedures The AMS AMI naming convention is: customer-ams-<operating system>-<release date> -
ams-ug-025	ams-ug.pdf	25	which is available through AWS Artifact -> Reports page (ﬁnd the Reports option in the left navigation pane) ﬁltered for AWS Managed Services. To access AWS Artifact, can contact your CSDM for instructions or go to Getting Started with AWS Artifact. To receive alerts when new AMS AMIs are released, you can subscribe to an Amazon Simple Notiﬁcation Service (Amazon SNS) notiﬁcation topic called "AMS AMI". For details, see AMS AMI notiﬁcations with SNS. Shared Responsibility Version May 08, 2025 61 AMS Advanced User Guide AMS Advanced Concepts and Procedures The AMS AMI naming convention is: customer-ams-<operating system>-<release date> - <version>. (for example, customer-ams-rhel6-2018.11-3) Only use AMS AMIs that start with customer. AMS recommends always using the most recent AMI. You can ﬁnd the most recent AMIs by either: • Looking in the AMS console, on the AMIs page. • Viewing the latest AMS AMI CSV ﬁle, available from your CSDM or through this ZIP ﬁle: AMS 11.2024 AMI contents and CSV ﬁle in a ZIP. For past AMI ZIP ﬁles, see the Doc History. • Running this AMS SKMS command (AMS SKMS SDK required): aws amsskms list-amis --vpc-id VPC_ID --query "Amis.sort_by(@,&Name)[? starts_with(Name,'customer')].[Name,AmiId,CreationTime]" --output table AMS AMI content added to base AWS AMIs, by operating system (OS) • Linux AMIs: • AWS CLI Tools • NTP • Trend Micro Endpoint Protection Service Agent • Code Deploy • PBIS / Beyond Trust AD Bridge • SSM Agent • Yum Upgrade for critical patches • AMS custom scripts / management software (controlling boot, AD join, monitoring, security, and logging) • Windows Server AMIs: • Microsoft .NET Framework 4.5 • PowerShell 5.1 • AWS Tools for Windows PowerShell • AMS PowerShell Modules controlling boot, AD join, monitoring, security, and logging • Trend Micro Endpoint Protection Service Agent AMS Amazon Machine Images (AMIs) Version May 08, 2025 62 AMS Advanced User Guide • SSM Agent • CloudWatch Agent AMS Advanced Concepts and Procedures • EC2Conﬁg service (through Windows Server 2012 R2) • EC2Launch (Windows Server 2016 and Windows Server 2019) • EC2LaunchV2 (Windows Server 2022 and later) Linux-based AMIs: • Amazon Linux 2023 (Latest Minor Release) (Minimal AMI not supported) • Amazon Linux 2 (Latest Minor Release) • Amazon Linux 2 (ARM64) • Red Hat Enterprise 7 (Latest Minor Release) • Red Hat Enterprise 8 (Latest Minor Release) • Red Hat Enterprise 9 (Latest Minor Release) • SUSE Linux Enterprise Server 15 SP5 • Ubuntu Linux 18.04 • Ubuntu Linux 20.04 • Ubuntu Linux 22.04 • Amazon Linux: For product overview, pricing information, usage information, and support information, see Amazon Linux AMI (HVM / 64-bit) and Amazon Linux 2. For more information, see Amazon Linux 2 FAQs. • RedHat Enterprise Linux (RHEL): For product overview, pricing information, usage information, and support information, see Red Hat Enterprise Linux (RHEL) 7 (HVM). • Ubuntu Linux 18.04: For product overview, pricing information, usage information, and support information, see Ubuntu 18.04 LTS - Bionic. • SUSE Linux Enterprise Server for SAP applications 15 SP5: • Run the following steps once per account: 1. Navigate to the AWS Marketplace. 2. Search for the SUSE 15 SAP product. 3. Choose Continue to subscribe. AMS Amazon Machine Images (AMIs) Version May 08, 2025 63 AMS Advanced User Guide AMS Advanced Concepts and Procedures 4. Choose Accept terms. • Complete the following steps every time you need to launch a new SUSE Linux Enterprise Server for SAP Applications 15 SP5 instance: 1. Note the AMI ID for the subscribed SUSE Linux Enterprise Server for SAP Applications 15 AMI. 2. Create a manual (Management \| Other \| Other \| Create) RFC with the following wording; replace AMI ID with the AWS Marketplace AMI ID you have subscribed to. Windows-based AMIs: Microsoft Windows Server (2016, 2019 and 2022), based on latest Windows AMIs. For examples of creating AMIs, see Create AMI. Oﬀboarding AMS AMIs: AMS does not unshare any AMIs from you during oﬀboarding to avoid impact for any of your depedencies. If you want to remove AMS AMIs from your account, you can use the cancel- image-launch-permission API to hide speciﬁc AMIs. For example, you can use the script below to hide all of the AMS AMIs that were shared with your account earlier: for ami in $(aws ec2 describe-images --executable-users self --owners 027415890775 -- query 'Images[].ImageId' --output text) ; do aws ec2 cancel-image-launch-permission --image-id $ami ; done You must have the AWS CLI v2 installed for the script to execute without any errors. For AWS CLI installation steps, see Installing or updating the latest version of the AWS CLI. For details on the cancel-image-launch-permission command, see cancel-image-launch-permission. Security enhanced AMIs AMS provides security enhanced images (AMIs) based on CIS Level 1 benchmark for a subset of AMS's supported operating systems. To ﬁnd which operating systems have a security enhanced image available, see
ams-ug-026	ams-ug.pdf	26	earlier: for ami in $(aws ec2 describe-images --executable-users self --owners 027415890775 -- query 'Images[].ImageId' --output text) ; do aws ec2 cancel-image-launch-permission --image-id $ami ; done You must have the AWS CLI v2 installed for the script to execute without any errors. For AWS CLI installation steps, see Installing or updating the latest version of the AWS CLI. For details on the cancel-image-launch-permission command, see cancel-image-launch-permission. Security enhanced AMIs AMS provides security enhanced images (AMIs) based on CIS Level 1 benchmark for a subset of AMS's supported operating systems. To ﬁnd which operating systems have a security enhanced image available, see the AWS Managed Services (AMS) Customer Security Guide. To access this guide, open AWS Artifact, select Reports in the left navigation pane, and then ﬁlter for AWS Managed Services. For instructions on how to access AWS Artifact, contact your CSDM or see Getting Started with AWS Artifact for more information. Security enhanced AMIs Version May 08, 2025 64 AMS Advanced User Guide AMS Advanced Concepts and Procedures How integration between AD FS and AMS works A one-way trust between your on-premises network and the AMS domain is the default means for access to stacks and VPCs. When a VPC and stack are created, access is granted via pre-conﬁgured Active Directory security groups. In addition, access to the AWS Management Console can be conﬁgured using Active Directory Federation Service (AD FS), or any federation software that supports SAML, for a single sign-on (SSO) to the AWS Management Console. Note AMS can federate to many federation services, Ping, Okta, and so on. You aren't limited to AD FS; we provide here an example of one federation technology available to you. Information here is duplicated from this blog post: Enabling Federation to AWS Using Windows Active Directory, AD FS, and SAML 2.0. 1. The ﬂow is initiated when a user (let’s call him Bob) browses to the AD FS sample site (https:// Fully.Qualiﬁed.Domain.Name.Here/adfs/ls/IdpInitiatedSignOn.aspx) inside his domain. When How integration between AD FS and AMS works Version May 08, 2025 65 AMS Advanced User Guide AMS Advanced Concepts and Procedures you install AD FS, you get a new virtual directory named adfs for your default website, which includes this page. 2. The sign-on page authenticates Bob against AD. Depending on the browser Bob is using, he might be prompted for his AD username and password. 3. Bob’s browser receives a SAML assertion in the form of an authentication response from AD FS. 4. Bob’s browser posts the SAML assertion to the AWS sign-in endpoint for SAML (https:// signin.aws.amazon.com/saml). Behind the scenes, sign-in uses the AssumeRoleWithSAML API to request temporary security credentials and then constructs a sign-in URL for the AWS Management Console. 5. Bob’s browser receives the sign-in URL and is redirected to the console. From Bob’s perspective, the process happens transparently. He starts at an internal website and ends up at the AWS Management Console, without ever having to supply any AWS credentials. Note More information on conﬁguring federation to the AMS console is provided in: • Multi-Account Landing Zone: Conﬁguring Federation to the AMS Console • Single-Account Landing Zone: Conﬁguring Federation to the AMS Console Additionally, see Appendix: AD FS claim rule and SAML settings. For information about using AWS Microsoft AD to support your Active Directory–aware applications, in the AWS Cloud, that are subject to compliance requirements, see Manage Microsoft AD Compliance. AMS Managed Active Directory AMS is now oﬀering a new service called Managed Active Directory (aka Managed AD) that allows AMS to take care of your Active Directory (AD) infrastructure operations, while keeping you in control of your Active Directory administration. AMS support for Managed AD is similar to AMS support for the Amazon Relational Database Service (Amazon RDS). In both cases, AWS (including AMS) supports the creation and management of the infrastructure running the service, while you perform access control and all administration functions. This model has the following advantages: AMS Managed Active Directory Version May 08, 2025 66 AMS Advanced User Guide AMS Advanced Concepts and Procedures • Limits security risks: AWS and AMS don't need administrative privileges to your domain. • Direct integrations: You can use your current authorization model and integrate it with AD without needing to interface with AMS. Notes: • Neither AMS nor you will have access to your Managed AD domain controllers, so no software can be installed on the domain controllers. This is important because third-party solutions that require software to be installed on domain controllers is not allowed. Access works like this: • AWS Directory Service team: Has access to domain controllers. • AMS: Has access to Directory Service APIs to perform certain actions on the domain. These actions include taking AD snapshots, changing AD schema, and others actions. • You: Have access to the domain (AD) for creating users,
ams-ug-027	ams-ug.pdf	27	needing to interface with AMS. Notes: • Neither AMS nor you will have access to your Managed AD domain controllers, so no software can be installed on the domain controllers. This is important because third-party solutions that require software to be installed on domain controllers is not allowed. Access works like this: • AWS Directory Service team: Has access to domain controllers. • AMS: Has access to Directory Service APIs to perform certain actions on the domain. These actions include taking AD snapshots, changing AD schema, and others actions. • You: Have access to the domain (AD) for creating users, groups, and so on. • We recommend that you perform a proof of concept on Managed AD before migrating your corporate AD, because not all functionality from a traditional AD environment is available in a Managed AD environment. • AMS will not manage or provide guidance on your AD management. For example, AMS will not provide guidance on Organizational Unit structure, group policy structure, AD user naming conventions, and so forth. It works like this: 1. AMS onboards a new AWS account for you, separate from and in addition to your AMS account, and provisions an Active Directory (AD) environment through AWS Directory Service (see also What Is AWS Directory Service?). The following is the information a systems integrator would need to gather from you in order for AMS to on board Managed AD: • Account information • Account ID of the AWS account that was created for your AMS-Managed AD: AWS account number • Region to onboard your Managed AD to: AWS Region • Managed Active Directory information: AMS Managed Active Directory Version May 08, 2025 67 AMS Advanced User Guide AMS Advanced Concepts and Procedures • Microsoft AD Edition: Standard/Enterprise. AWS Microsoft AD (Standard Edition) includes 1 GB of directory object storage. This capacity can support up to 5,000 users or 30,000 directory objects, including users, groups, and computers. AWS Microsoft AD (Enterprise Edition) includes 17 GB of directory object storage, which can support up to 100,000 users or 500,000 objects. For more information, see AWS Directory Service FAQs. • Domain FQDN: The FQDN for your AMS Managed AD domain. • Domain NetBIOS name: The NetBIOS name for your AMS Managed AD domain. • Account numbers of AMS-standard accounts you would like Managed AD integration to (AMS conﬁgures a one way trust from the AMS-standard account's AD to the Managed AD) • Are Active Directory Schema modiﬁcations required and if so, what modiﬁcations? • By default, two domain controllers are provisioned. Do you require more? If so, how many do you require and for what reason? • Networking for Managed Active Directory information: • Managed AD VPC CIDR for domain controllers (a CIDR in your private subnet range for the Managed AD domain controllers): • Subnet CIDR 1 for domain controllers: [your CIDR, needs to be part of AMS Managed AD VPC CIDR] • Subnet CIDR 2 for domain controllers: [your CIDR, needs to be part of AMS Managed AD VPC CIDR] For example: • Managed AD VPC CIDR: 192.168.0.0/16 • CIDR 1 for domain controllers: 192.168.1.0/24 • CIDR 2 for domain controllers: 192.168.2.0/24 To avoid IP address conﬂicts, be sure that the Managed AD VPC CIDR you specify does not conﬂict with any other private subnet CIDR you are using in your corporate network. • VPN Technology (optional): [Direct Connect/Direct Connect and VPN] • Your gateway's BGP Autonomous System Number (ASN): [Customer-provided ASN] • The Internet-routable IP address for your gateway's outside interface, the address must be static: [Customer Provided IP Address] AMS Managed Active Directory • Whether or not your VPN connection requires static routes: [yes/no] Version May 08, 2025 68 AMS Advanced User Guide AMS Advanced Concepts and Procedures 2. AMS provides you with the Admin account password for the AD environment and asks you to reset the password so AMS engineers can no longer access your AD environment. 3. To reset the Admin account password, connect to your Active Directory environment using Active Directory Users and Computers (ADUC). ADUC and other Remote Server Administration Tools (RSAT) should be installed and run on Administrative hosts provisioned by you on non- AMS infrastructure. Microsoft has best practices for securing such administrative hosts. For information, see Implementing Secure Administrative Hosts. You manage your Active Directory environment using these Administrative hosts. 4. In daily operations, AMS manages the AWS account up to the AWS Directory Service side of things; for example, VPC conﬁguration, AD backups, AD trust creation and deletion, and so forth. You use, and manage, your AD environment; for example, user creation, group creation, group policy creation, and so forth. For the most recent RACI table, see the "Roles and Responsibilities" section in the See Service description. AMS application deployments AMS Application Developer's guide provides detailed
ams-ug-028	ams-ug.pdf	28	practices for securing such administrative hosts. For information, see Implementing Secure Administrative Hosts. You manage your Active Directory environment using these Administrative hosts. 4. In daily operations, AMS manages the AWS account up to the AWS Directory Service side of things; for example, VPC conﬁguration, AD backups, AD trust creation and deletion, and so forth. You use, and manage, your AD environment; for example, user creation, group creation, group policy creation, and so forth. For the most recent RACI table, see the "Roles and Responsibilities" section in the See Service description. AMS application deployments AMS Application Developer's guide provides detailed descriptions and walkthroughs for the following deployments: • The AMS workload ingest CT allows you and an AMS cloud migration partner to easily move your existing workloads into an AMS-managed VPC. Using AMS workload ingest, you can create an AMS AMI by submitting an RFC with the Deployment \| Ingestion \| Stack from migration partner migrated instance \| Create CT (ct-257p9zjk14ija). You must have an instance migrated from your on-premises to AWS by a migration partner, as well as a target AMS VPC and subnet, into which the instance will be ingested. For details, see the AMS Application Developer's guide at Workload Ingest. • The AWS CloudFormation ingest change type (ct-36cn2avfrrj9v) feature allows you to easily use an existing CloudFormation template to deploy custom stacks in an AMS-managed VPC. For details, see the AMS Application Developer's guide at CloudFormation Template Ingest. • You can import your on-premises database into a new database to your AMS-managed Amazon S3 bucket or Amazon RDS instance. You do this using a Deployment \| Advanced stack Application deployments Version May 08, 2025 69 AMS Advanced User Guide AMS Advanced Concepts and Procedures components \| Database Migration Service (DMS) change types, including Create replication instance (ct-27apldkhqr0ol), Create replication subnet group (ct-2q5azjd8p1ag5), Create replication task (ct-1d2fml15b9eth), Create source endpoint (ct-0attesnjqy2cx) or Create source endpoint (S3) (ct-2oxl37nphsrjz), and Create target endpoint (ct-3gf8dolbo8x9p) or Create target endpoint (S3) (ct-05muqzievnxk5). For details, see the AMS Application Developer's guide at Database Migration Service. • You can import your on-premises MS SQL database into a new database on your AMS-managed RDS SQL instance. You do this using a variety of AMS change types, and the Amazon RDS API, plus AWS consoles. For details, see the AMS Application Guide at Database (DB) Import to MS SQL RDS. Application deployments Version May 08, 2025 70 AMS Advanced User Guide AMS Advanced Concepts and Procedures Service management in AWS Managed Services Topics • Account governance in AWS Managed Services • Service commencement in AWS Managed Services • Customer relationship management (CRM) • Cost optimization in AWS Managed Services • Service hours in AWS Managed Services • Getting help in AWS Managed Services How the AMS service works for you. Account governance in AWS Managed Services This section covers AMS account governance. You are designated a cloud service delivery manager (CSDM) who provides advisory assistance across AMS, and has a detailed understanding of your use case and technology architecture for the managed environment. CSDMs work with account managers, technical account managers, AWS Managed Services cloud architects (CAs), and AWS solution architects (SAs), as applicable, to help launch new projects and give best-practices recommendations throughout the software development and operations processes. The CSDM is the primary point of contact for AMS. Key responsibilities of your CSDM are: • Organize and lead monthly service review meetings with customers. • Provide details on security, software updates for environment and opportunities for optimization. • Champion your requirements including feature requests for AMS. • Respond to and resolve billing and service reporting requests. • Provide insights for ﬁnancial and capacity optimization recommendations. Account governance Version May 08, 2025 71 AMS Advanced User Guide AMS Advanced Concepts and Procedures Service commencement in AWS Managed Services Service Commencement: The Service Commencement Date for an AWS Managed Services account is the ﬁrst day of the ﬁrst calendar month after which AWS notiﬁes you that the activities set out in the Onboarding Requirements for that AWS Managed Services account have been completed; provided that if AWS makes such notiﬁcation after the 20th day of a calendar month, the Service Commencement Date is the ﬁrst day of the second calendar month following the date of such notiﬁcation. Service Commencement • R stands for responsible party that does the work to achieve the task. • I stands for informed; a party which is informed on progress, often only on completion of the task or deliverable. Service commencement Step # Step title Description CustomerAMS 1. 2. 3. Customer AWS account handover Customer creates a new AWS account and hands it over to AWS Managed Services AWS Managed Services Account Finalize design of AWS Managed Services Account - design AWS Managed Services Account - build An AWS Managed Services
ams-ug-029	ams-ug.pdf	29	of the second calendar month following the date of such notiﬁcation. Service Commencement • R stands for responsible party that does the work to achieve the task. • I stands for informed; a party which is informed on progress, often only on completion of the task or deliverable. Service commencement Step # Step title Description CustomerAMS 1. 2. 3. Customer AWS account handover Customer creates a new AWS account and hands it over to AWS Managed Services AWS Managed Services Account Finalize design of AWS Managed Services Account - design AWS Managed Services Account - build An AWS Managed Services account is built per the design in Step 2 R I I I R R Customer relationship management (CRM) AWS Managed Services (AMS) provides a customer relationship management (CRM) process to ensure that a well-deﬁned relationship is established and maintained with you. The foundation of this relationship is based on AMS’s insight into your business requirements. The CRM process facilitates accurate and comprehensive understanding of: Service commencement Version May 08, 2025 72 AMS Advanced User Guide AMS Advanced Concepts and Procedures • Your business needs and how to ﬁll those needs • Your capabilities and constraints • AMS and your diﬀerent responsibilities and obligations The CRM process allows AMS to use consistent methods to deliver services to you and provide governance for your relationship with AMS. The CRM process includes: • Identifying your key stakeholders • Establishing a governance team • Conducting and documenting service review meetings with you • Providing a formal service complaint procedure with an escalation procedure • Implementing and monitoring your satisfaction and feedback process • Managing your contract CRM Process The CRM process includes these activities: • Identifying and understanding your business processes and needs. Your agreement with AMS identiﬁes your stakeholders. • Deﬁning the services to be provided to meet your needs and requirements. • Meeting with you in the service review meetings to discuss any changes in the AMS service scope, SLA, contract, and your business needs. Interim meetings may be held with you to discuss performance, achievements, issues, and action plans. • Monitoring your satisfaction by using our customer satisfaction survey and feedback given at meetings. • Reporting performance on monthly internally-measured performance reports. • Reviewing the service with you to determine opportunities for improvements. This includes frequent communication with you regarding the level and quality of the AMS service provided. CRM Process Version May 08, 2025 73 AMS Advanced User Guide CRM meetings AMS Advanced Concepts and Procedures AMS cloud service delivery managers (CSDMs) conduct meetings with you regularly to discuss service tracks (operations, security, and product innovations) and executive tracks (SLA reports, satisfaction measures, and changes in your business needs). Meeting Purpose Mode Participants Weekly status review (optional) Outstanding issues or incidents, patching, security events, problem records On-site customer location/ Telecom/Chime 12-week operational trend (+/- 6) Application operator concerns Weekend schedule AMS: CSDM and cloud architect (CA) Customer assigned team members (ex: Cloud/ Infrastructu re, Applicati on Support, Architecture teams, etc.) Monthly business review Review service level performance (reports, analysis, and trends) Financial analysis Product roadmap CSAT On-site customer location/ AMS: CSDM, cloud architect (CA), AMS Telecom/Chime account team, AMS technical product manager (TPM) (optional), AMS OPS manager (optional) You: Applicati on Operator representative CRM meetings Version May 08, 2025 74 AMS Advanced User Guide AMS Advanced Concepts and Procedures Meeting Purpose Mode Participants Quarterly business review Scorecard and service level agreement (SLA) performance and trends (6 months) On-site customer location Upcoming 3/6/9/12 months plans/ migrations Risk and risk mitigations Key improvement initiatives Product roadmap items Future direction aligned opportuni ties Financials Cost savings initiatives Business optimization AMS: CSDM, cloud architect , AMS account team, AMS service director, AMS operation manager You: Applicati on operator representative, service represent ative, service director CRM Meeting Arrangements The AMS CSDM is responsible for documenting the meeting, including: • Creating the agenda, including action items, issues, and list of attendees. • Creating the list of action items reviewed at each meeting to ensure items are completed and resolved on schedule. • Distributing meeting minutes and the action item list to meeting attendees by email within one business day after the meeting. • Storing meeting minutes in the appropriate document repository. In absence of the CSDM, the AMS representative leading the meeting creates and distributes minutes. CRM Meeting Arrangements Version May 08, 2025 75 AMS Advanced User Guide AMS Advanced Concepts and Procedures Note Your CSDM works with you to establish your account governance. CRM monthly reports Your AMS CSDM prepares and sends out monthly service performance presentations. The presentations include information on the following: • Report date • Summary and Insights: • Key Call Outs: total and active stack count, stack patching status, account onboarding status (during onboarding only), customer-speciﬁc issues summaries • Performance:
ams-ug-030	ams-ug.pdf	30	minutes in the appropriate document repository. In absence of the CSDM, the AMS representative leading the meeting creates and distributes minutes. CRM Meeting Arrangements Version May 08, 2025 75 AMS Advanced User Guide AMS Advanced Concepts and Procedures Note Your CSDM works with you to establish your account governance. CRM monthly reports Your AMS CSDM prepares and sends out monthly service performance presentations. The presentations include information on the following: • Report date • Summary and Insights: • Key Call Outs: total and active stack count, stack patching status, account onboarding status (during onboarding only), customer-speciﬁc issues summaries • Performance: Stats on incident resolution, alerts, patching, requests for change (RFCs), service requests, and console and API availability • Issues, challenges, concerns, and risks: Customer-speciﬁc issues status • Upcoming items: Customer-speciﬁc onboarding or incident resolution plans • Managed Resources: Graphs and pie charts of stacks • AMS Metrics: Monitoring and event metrics, incident metrics, AMS SLA adherence metrics, service request metrics, change management metrics, storage metrics, continuity metrics, Trusted Advisor metrics, and cost summaries (presented several ways). Feature requests. Contact information. Note In addition to the described information, your CSDM also informs you of any material change in scope or terms, including use of subcontractors by AMS for operational activities. AMS generates reports about patching and backup that your CSDM includes in your monthly report. As part of the report generating system, AMS adds some infrastructure to your account that is not accessible to you: • An S3 Bucket, with the raw data reported • An Athena instance, with query deﬁnitions to query the data • A Glue Crawler to read the raw data from the S3 bucket CRM monthly reports Version May 08, 2025 76 AMS Advanced User Guide AMS Advanced Concepts and Procedures Cost optimization in AWS Managed Services AWS Managed Services provides a detailed cost utilization and savings reports every month to you during your monthly business reviews (MBRs). AMS follows a standard set of processes and mechanisms to identify cost saving avenues in your managed accounts and assist you to plan and roll-out the changes to optimize your AWS spend. Note AMS is developing a video to help with cost optimization. The ﬁrst step is providing you with a PDF and an Excel spreadsheet of cost optimization best practices. To access these resources, open the Quick guide to cost optimization ZIP ﬁle. Cost optimization framework AMS follows a three-staged approach with you to optimize your AWS costs: 1. Identify cost optimization avenues in your managed environment 2. Present a cost optimization plan to you 3. Assist in achieving cost optimization in a measurable way Identify cost optimization avenues in the managed environment AMS utilizes AWS native tools like Cost explorer, and Trusted Advisor while leveraging over 20 cost savings patterns across architecture optimization, EC2 instance, and AWS account-focused optimizations to build tailored cost savings recommendations for you. Some of the optimization recommendations include the following. Architectural optimization recommendations: • Optimal S3 storage class use: Amazon S3 oﬀers a range of storage classes to meet various workload requirements based on data access, resiliency, and cost. S3 Intelligent-Tiering and S3 storage class analysis based on the workload needs allow you to manage the S3 costs eﬃciently. • Using caching architectures: Leveraging cache instances, where applicable, can help you replace some database instances, while simultaneously meeting your IOPS requirements. Cost optimization Version May 08, 2025 77 AMS Advanced User Guide AMS Advanced Concepts and Procedures • EBS upgrade savings: Migrating your EBS volumes from gp2 to gp3 provides a cost savings of up to 20% and you can take advantage of predictable 3,000 IOPS baseline performance and 125 MiB/s, regardless of volume size. • Using elasticity: The auto-scaling capabilities that AWS provides allow eﬀective resource utilization and avenues for cost optimization. Reviewing and updating the instance scaling policies regularly based on need, further provides cost savings. EC2 instance-focused recommendations • Instance rightsizing: Recommendations focused on sizing the instances and optimal conﬁgurations based on the usage. Recommendations also include utilizing Amazon EC2 Auto Scaling feature and replacing EC2 instances where applicable with AWS Lambda or static web content on Amazon S3, etc. • Instance scheduling: Using AMS Resource Scheduler to automatically start and stop instances based on a time schedule helps contain costs, especially for non-production instances that are not utilized during non-business hours. • Subscribing to Savings plans: Savings plan is the easiest way to save on AWS usage. The EC2 Instance Savings Plans oﬀer up to 72% savings compared to On-Demand pricing on your Amazon EC2 instances usage. The Amazon SageMaker AI Savings Plans oﬀer up to 64% savings on your Amazon SageMaker AI services usage. AMS provides appropriate recommendations on Savings plans based on your AWS resource usage. • Reserved instance (RI) usage and consumption guidance: Amazon EC2
ams-ug-031	ams-ug.pdf	31	start and stop instances based on a time schedule helps contain costs, especially for non-production instances that are not utilized during non-business hours. • Subscribing to Savings plans: Savings plan is the easiest way to save on AWS usage. The EC2 Instance Savings Plans oﬀer up to 72% savings compared to On-Demand pricing on your Amazon EC2 instances usage. The Amazon SageMaker AI Savings Plans oﬀer up to 64% savings on your Amazon SageMaker AI services usage. AMS provides appropriate recommendations on Savings plans based on your AWS resource usage. • Reserved instance (RI) usage and consumption guidance: Amazon EC2 Reserved Instances (RI) provide a signiﬁcant discount (up to 75%) compared to On-Demand pricing and provide a capacity reservation when used in a speciﬁc availability zone. • Spot instance usage: Fault tolerant workloads can utilize Spot instances and reduce prices up to 90%. • Idle instance termination: Identifying and reporting instances that are idle or have low utilization that can be terminated. Account-focused recommendations • Account cleanup: At an account level, AMS also identiﬁes un-utilized EBS volumes, duplicate CloudTrail trails, empty accounts with unused resources, and so forth, and provides recommendations for clean-up. Cost optimization framework Version May 08, 2025 78 AMS Advanced User Guide AMS Advanced Concepts and Procedures • SLA recommendations: Further, AMS regularly reviews your Plus and Premium accounts and recommends choosing the right SLA level for the accounts. • AMS automation optimization: AMS continuously optmizes AMS automation and infrastructure used to provide AMS services. Present to customers and assist in planning AMS conducts monthly business reviews (MBRs) with the key customer stakeholders and present the cost saving avenues, mechanisms and recommendations identiﬁed along with potential cost savings. We further work with you to plan the changes needed. Assist in recommendation implementation and measure the cost impact AMS assists in achieving and measuring cost impacts and optimization changes. You assess the application impact, risk and success criteria of the recommended changes, and raise the appropriate requests for change (RFCs) through the AMS console. AMS collaborates with you and implements the changes related to cost optimization in your managed accounts. AMS measures the cost impact and include the savings realised in the monthly business reviews (MBRs). Cost optimization responsibility matrix Responsibilities in AMS cost optimization. Cost optimization RACI Activity Customer Compiling cost I saving recommend ations and preparing the report Presentin g cost C AMS R R Cost optimization responsibility matrix Version May 08, 2025 79 AMS Advanced User Guide AMS Advanced Concepts and Procedures Activity Customer AMS R R R savings report Planning changes associate d with cost savings Assessing the change impact and risk Raising RFCs for implement ing the changes Reviewing the RFCs C and implement ing the changes C C C R Cost optimization responsibility matrix Version May 08, 2025 80 AMS Advanced User Guide AMS Advanced Concepts and Procedures AMS C R Activity Customer R Testing the applicati on and validatin g the change implement ation I Measuring the cost impact post change and presentin g to customer Service hours in AWS Managed Services Feature Service request Incident management (P2-P3) Backup and recovery Patch management Monitoring and alerting AMS Advanced Premium Tier 24/7 24/7 24/7 24/7 24/7 Service hours Version May 08, 2025 81 AMS Advanced User Guide AMS Advanced Concepts and Procedures Feature Automated request for change (RFC) Non-automated request for change (RFC) Cloud service delivery manager (CSDM) AMS Advanced Premium Tier 24/7 24/7 Monday to Friday: 08:00– 17:00, local business hours Getting help in AWS Managed Services AMS supports you with Incident Management, Service Request Management, and Change Management 24 hours a day, 7 days a week, 365 days a year (in accordance with the AMS Service Level Agreement applied to the account). To report an AWS or AMS service performance issue that impacts your managed environment, use the AMS console and submit an incident report. For details, see Reporting an incident. For general information about AMS incident management, see Incident response. To ask for information or advice, or to request additional services from AMS, use the AMS console and submit a service request. For details, Creating a Service Request. For general information about AMS service requests, see Service Request Management. Getting help Version May 08, 2025 82 AMS Advanced User Guide AMS Advanced Concepts and Procedures Planned event management in AWS Managed Services AWS Managed Services (AMS) planned event management (PEM) is an AMS service oﬀering. PEM engages, coordinates, and assists during customer events and projects using AMS services. PEM assists in coordinating a set of related RFCs that align with the agreed scope and timeline of the PEM event or project. AMS PEM criteria A planned event is a scope-bound and time-bound project. AMS uses details that you provide (including plan and scope, expected outcomes, and changes that AMS
ams-ug-032	ams-ug.pdf	32	Getting help Version May 08, 2025 82 AMS Advanced User Guide AMS Advanced Concepts and Procedures Planned event management in AWS Managed Services AWS Managed Services (AMS) planned event management (PEM) is an AMS service oﬀering. PEM engages, coordinates, and assists during customer events and projects using AMS services. PEM assists in coordinating a set of related RFCs that align with the agreed scope and timeline of the PEM event or project. AMS PEM criteria A planned event is a scope-bound and time-bound project. AMS uses details that you provide (including plan and scope, expected outcomes, and changes that AMS operations are expected to perform) to eﬀectively support you during PEM activity. Your Cloud Architects (CAs) then review and assess the PEM activity for completeness, technical implementation, and AMS operations engagement. After CA review, AMS operations reviews the plans and coordinates with your cloud service delivery manager (CSDM) for operations team engagement. Types of PEM The following are the available PEM types: • Gamedays • Operational Gameday: A scenario-based gaming approach to operational response, aimed at validating the integration of processes, people, and systems. • Security Gameday: A security incident response strategy that employs a scenario-based gaming approach to assess the integration of systems, processes, and personnel. • BYOEPS: Use the AMS "bring your own endpoint security" (BYOEPS) feature to substitute the default Trend Micro Deep Security agent with your preferred endpoint security solution or a custom Trend Micro license. For more information, see AMS bring your own EPS. • Disaster Recovery: Disaster Recovery events involve AMS assisting you during your planned DR activities. For more information, see Disaster recovery planning. • Customer Security Event: Planned security events. For example, root user activity and penetration testing. • Migration Support: Support for planned onboarding and migration activity. AMS PEM criteria Version May 08, 2025 83 AMS Advanced User Guide AMS Advanced Concepts and Procedures This workﬂow facilitates collaboration with AMS for coordinating planned events and migration activities regarding AMS support. For priority execution of RFCs, it's a best practice to use the Operations on Demand (OOD) engagement. For more information, see Operations On Demand. The AMS PEM process The PEM process consists of the following phases: • PEM initiation: You work with your CSDM to deﬁne your objective for the planned event and determine what's needed from AMS Operations. AMS CAs review the technical aspects of the PEM plan. The CAs work with AMS Security and Operations on compliance, execution optimization and automation, and to deﬁne pre-PEM execution tasks and deliverables. Then, your CSDM creates the PEM ticket and provides AMS with the project information and technical details. AMS requires a lead time of 14 calendar days to allow the AMS Operations team time to plan, provide technical review, and assign resources. • PEM review: The AMS Operations team reviews the PEM request and works with your CSDM to verify that the information in the PEM plan is correct and complete. • PEM acceptance: AMS reviews the provided information and communicates to the CSDM what the level of support will be during the PEM activity. If the PEM contains complete information and your CSDM agrees with the scope of work, then the PEM is approved. • Readiness and execution: AMS makes sure that tasks needed before the PEM begins are completed and facilitates internal and customer communications. AMS makes sure that the PEM plan runs correctly and provides status and progress reporting. PEM FAQs How do I engage AMS with a RFC/Service Request (SR) during a PEM event? • Use the PEM ID shared by your CSDM in the RFC/SR subject line in the format PEM-ID. • You can also create a Service Request (SR) to discuss your use cases or for questions about your planned event. If you use an SR, then the PEM doesn't have to be valid. What validations are performed when a PEM-related RFC is submitted? • Veriﬁcation that the Account ID is listed on the PEM. The AMS PEM process Version May 08, 2025 84 AMS Advanced User Guide AMS Advanced Concepts and Procedures • Veriﬁcation that the PEM status is approved and active between the provided start and end dates. Are there SLAs or SLOs for PEM requests? • PEMs are not associated with SLAs or SLOs. • SLAs and SLOs for PEM-related work items (RFC/Service Request) are deﬁned by AMS SLOs. For more information, see AMS service level objectives (SLOs). Can we create a PEM through a Service Request (SR)? • No, PEM creation must be managed by the Cloud Service Delivery Manager (CSDM). PEM FAQs Version May 08, 2025 85 AMS Advanced User Guide AMS Advanced Concepts and Procedures Network architecture AWS Managed Services (AMS) oﬀers two network architectures: • Multi-account landing zone (MALZ): provides common services - such as access, end point
ams-ug-033	ams-ug.pdf	33	for PEM requests? • PEMs are not associated with SLAs or SLOs. • SLAs and SLOs for PEM-related work items (RFC/Service Request) are deﬁned by AMS SLOs. For more information, see AMS service level objectives (SLOs). Can we create a PEM through a Service Request (SR)? • No, PEM creation must be managed by the Cloud Service Delivery Manager (CSDM). PEM FAQs Version May 08, 2025 85 AMS Advanced User Guide AMS Advanced Concepts and Procedures Network architecture AWS Managed Services (AMS) oﬀers two network architectures: • Multi-account landing zone (MALZ): provides common services - such as access, end point security, networking - from shared accounts for workloads that are deployed in separate member accounts. • Single-account landing zone (SALZ): provides self contained accounts where common services such as access, end point security, networking are deployed in the same account as the workload. It is recommended for workloads that require a high level of isolation as it incurs higher AWS costs. MALZ network architecture About multi-account landing zone network architecture Before you start the onboarding process to AWS Managed Services (AMS) Multi-account landing zone (MALZ), it is important to understand the baseline architecture, or landing zone, that AMS creates on your behalf, its components, and functions. AMS multi-account landing zone is a multi-account architecture, pre-conﬁgured with the infrastructure to facilitate authentication, security, networking, and logging. Note For estimates of costs, see AMS multi-account landing zone environment basic components. Topics • Service region • Organizational units • Service control policies and AWS Organization The following diagram outlines at a high level the account structure and how infrastructure is segregated into each of the accounts: MALZ network architecture Version May 08, 2025 86 AMS Advanced User Guide AMS Advanced Concepts and Procedures Service region All resources within an AMS multi-account landing zone are deployed within a single AWS Region of your choice, due to current cross region limitation with Active Directory and Transit Gateway. Organizational units A typical AMS multi-account landing zone consists of four top-level organizational units (OUs): • The core Organizational unit (OU) (used to group accounts together to administer as a single unit) • The applications OU • The customer-managed OU • The accelerate OU AMS-managed multi-account landing zone also enables you to create custom OUs for grouping and organizing AWS Accounts and to associate custom SCPs with them; for examples on doing this, About multi-account landing zone network architecture Version May 08, 2025 87 AMS Advanced User Guide AMS Advanced Concepts and Procedures see Management account \| Create Custom OUs and Management account \| Create Custom SCP (review required), respectively. AMS provides four existing OUs under which new OUs and accounts can be requested: accelerate, applications > managed, applications > development, and customer- managed. • accelerate OU: This is a top-level OU in AMS multi-account landing zone (MALZ). Accounts under this OU are provisioned by AMS with an RFC (Deployment \| Managed landing zone \| Management account \| Create Accelerate account, change type ID: ct-2p93tyd5angmi). In these accelerate application accounts, you can beneﬁt from accelerate operational services such as monitoring and alerting, incident management, security management, and backup management. For more details, see AMS Accelerate accounts. • applications > managed OU: In this sub organizational unit of the Application OU, accounts are fully managed by AMS including all operational tasks. The operational tasks include service request management, incident management, security management, continuity management, patch management, cost optimization, monitoring and event management. These tasks are carried out for your infrastructure's management. Multiple child OUs can be created as needed, until a maximum limit of nested OUs is reached for AWS organizations. For details, see Quotas for AWS Organizations. • applications > development OU: Under this sub-OU of the application OU in AMS-managed landing zone, accounts are Developer mode accounts that provide you with elevated permissions to provision and update AWS resources outside of the AMS change management process. This OU also supports the creation of new children OU as needed. • customer-managed OU: This is a top-level OU in AMS multi-account landing zone. Accounts under this OU are provisioned by AMS with an RFC. In these accounts, the operations of workloads and AWS resources are your responsibility. This OU also supports the creation of new children OU as needed. As a best practice, we recommend that accounts under these OUs and custom-requested sub-OUs be grouped based on their functionalities and policies. About multi-account landing zone network architecture Version May 08, 2025 88 AMS Advanced User Guide AMS Advanced Concepts and Procedures Service control policies and AWS Organization AWS provides service control policies (SCPs) for permissions management in an AWS Organization. SCPs are used to deﬁne additional guardrails for what actions users can perform in which OUs. By default, AMS provides a set of SCPs deployed in management accounts which
ams-ug-034	ams-ug.pdf	34	also supports the creation of new children OU as needed. As a best practice, we recommend that accounts under these OUs and custom-requested sub-OUs be grouped based on their functionalities and policies. About multi-account landing zone network architecture Version May 08, 2025 88 AMS Advanced User Guide AMS Advanced Concepts and Procedures Service control policies and AWS Organization AWS provides service control policies (SCPs) for permissions management in an AWS Organization. SCPs are used to deﬁne additional guardrails for what actions users can perform in which OUs. By default, AMS provides a set of SCPs deployed in management accounts which provide protections at diﬀerent default OU levels. For SCP restrictions, please contact your CSDM. You can also create custom SCPs and attach them to speciﬁc OUs. They can be requested from your Management account using change type ct-33ste5yc7hprs. AMS then reviews the custom SCPs requested before applying them to the target OUs. For examples, see Management account \| Create Custom OUs and Management account \| Create Custom SCP (Review Required). Choosing single MALZ or multiple MALZs The following table provides some high level considerations on deciding between a single multi- account landing zone (MALZ) vs multiple multi-account landing zones (for example, two multi- account landing zones - Prod and non-Prod). In general, the choice depends upon individual needs, legal requirements, and operating practices. Single multi-account landing zone vs. multiple multi-account landing zones Entity Single AMS landing zone Multiple (two or more) landing zones Base cost Lower, optimized at approximately $3,000 per month. Higher, an additional cost of approximately $3,000 per environme Billing Single bill, due to single Billing/ Management account. Portability of existing reserved instances Low. AWS RIs are currently not convertible across multiple billing accounts. You would repurpose existing RIs for multi-account landing (RIs) zone. nt. Separate bill for each multi-account landing zone. Currently AWS Org does not support multi-Management accounts with a single bill. Lower. You would repurpose and distribute RIs across all multi-account landing zone. Choosing single MALZ or multiple MALZs Version May 08, 2025 89 AMS Advanced User Guide AMS Advanced Concepts and Procedures Entity Single AMS landing zone Multiple (two or more) landing zones High. See Volume discounts. Low. See Volume discounts. Product tiering discounts Initial setup overhead Low. Active Directory, networking and single sign-on (SSO) integrations once High. You would perform Active Directory, network integration, and (on project/ only. migration timelines) Common services conﬁgura bility SSO integrations for every landing zone. This could cause potential delays to any migration project. Low eﬀorts. You conﬁgure common/ shared services like DNS, backup, High eﬀorts. Additional planning is required to address where the monitoring, logging etc. common infrastructure or services will be sitting. Traﬃc traversing across multiple transit gateways (TGWs) in each landing zone, could lead to extra cost. Scalability Medium. AMS has a current practical limit of 150 accounts per multi-acc High. Ability to leverage multiple multi-account landing zone to ount landing zone. Multiple teams distribute the accounts while or vendors running applications in achieving an account or application same account could have access to level of segregation. Managing large stacks owned by diﬀerent teams. numbers of accounts could lead to This limitation can be mitigated by operational or cost overhead. controlling access to application- specific stacks at the ServiceNow layer (by integrating the AMS ServiceNow Connector application and making use of tags). Ask AMS technical delivery managers (TDMs) or cloud architects (CAs) how to implement this. Choosing single MALZ or multiple MALZs Version May 08, 2025 90 AMS Advanced User Guide AMS Advanced Concepts and Procedures Entity Single AMS landing zone Multiple (two or more) landing zones Operational Risk (Depends) Low. Operational integrati on and readiness once only. Less (Depends) Low. Multiple integrati on and operational activities. Drift chance of process drifts. in multiple landing zones over the period could lead to operational risks. Multi AWS Region Single AWS Region. AMS multi-acc ount landing zone is restricted to a Multi AWS Region. With multiple multi-account landing zones, you single AWS Region. To span multiple can have each MALZ deployed in one AWS Regions, use multiple multi-acc region and interconnect them using ount landing zone. transit gateway (TGW) peering. Account migration or Yes. Moving accounts from one OU to another within the same AWS No. AMS doesn't support migration of an account across landing zones; portability Organization is possible. that is, across AWS Organizations. Workloads can reach across landing zones with transit gateway (TGW) or VPC peering. Change management Medium. Making destructive changes to common components like TGW, Low. Making destructive changes to common components like TGW, AD, Active Directory (AD), or outbound or outbound (egress) can impact only (egress) can impact all workloads in a the workloads in that speciﬁc multi- multi-account landing zone. However, account landing zone. Data and access controls changes to AMS-managed
ams-ug-035	ams-ug.pdf	35	one OU to another within the same AWS No. AMS doesn't support migration of an account across landing zones; portability Organization is possible. that is, across AWS Organizations. Workloads can reach across landing zones with transit gateway (TGW) or VPC peering. Change management Medium. Making destructive changes to common components like TGW, Low. Making destructive changes to common components like TGW, AD, Active Directory (AD), or outbound or outbound (egress) can impact only (egress) can impact all workloads in a the workloads in that speciﬁc multi- multi-account landing zone. However, account landing zone. Data and access controls changes to AMS-managed component s are tested internally and are pushed in rolling updates. (Depends) Low control if you’d like to connect to diﬀerent on-premise ADs and networks for Prod vs Non-Prod workloads. SAML federation, TGW domains, and security groups (SGs) can help implement required controls too. (Depends) High control if you’d like to connect to diﬀerent on-premise ADs and networks for Prod vs Non- Prod workloads. Use separate landing zones for strict compliance requireme nts. Choosing single MALZ or multiple MALZs Version May 08, 2025 91 AMS Advanced User Guide AMS Advanced Concepts and Procedures Entity Single AMS landing zone Multiple (two or more) landing zones Compliance and Security (Depends) Low if there are strict compliance needs to completely (Depends) High as multiple multi-acc ount landing zone could help achieve segregate material vs non-material strict compliance requirements by workloads. AMS standard preventative completely segregating material and detective controls in place. vs non-material workloads. AMS standard preventative and detective controls in place. Recommendation: Without strict Compliance or multi-Region need, starting with single AMS multi-account landing zone would strike a good balance among cost, security, operational excellence, and migration complexity. You can always setup additional landing zone, if any account or business constraints are encountered. Single multi-account landing zone vs. Multiple multi-account landing zone FAQs Some commonly asked questions when choosing to set up a single multi-account landing zone or multiple multi-account landing zones: Q1: Can I start with a single multi-account landing zone and move to multiple multi-account landing zone, if any account limits or business constraints are encountered? A: Yes. You can choose to set up another multi-account landing zone at any given time: • A new billing payer account will be required to be setup (currently AWS doesn’t support multi- payer accounts in a single AWS org). • Multi-Account Landing Zone base build takes up to 2 weeks lead time once the multi-account landing zone questionnaire is ﬁlled out. • Every multi-account landing zone means an addition of ~3K USD / month running cost. • N/W, AD, DNS, and SSO integration will be required to establish for new MALZ. • Any Reserved Instances (RIs), Cost Saving plans will be needed to be setup for the new multi- account landing zone (RIs are not transferrable). • AMS multi-account landing zone doesn't support migration of an account across multi-account landing zone accounts; for example, across AWS Orgs. However, to move applications from one account to another is possible using standard migration methods. Choosing single MALZ or multiple MALZs Version May 08, 2025 92 AMS Advanced User Guide AMS Advanced Concepts and Procedures Q2: What is AMS approach to MALZ updates/changes to underlying/shared infrastructure and quantify the risk to customers? Provide details on what assurances are wrapped into the process. How do Customers get comfortable that MALZ updates/changes will not impact customers? Is there any measures Customer need to take to prevent disruption? A: AMS follows a strict change methodology using internal tools that enables us to deﬁne, review, schedule and execute changes to customers' environments. The process to release updates enforces code reviews, integration testing, deployment in gamma and beta environments, and additional baking time and testing in beta and gamma environments before releasing to customers environments. All releases include rollback procedures and are closely monitored by the releases team and the team who created and requested the change. The scope of the releases are conﬁned to stacks owned and provisioned by AMS. On average, we execute at least one release per week. In addition: • AMS SLA are applicable. As per AMS service description any incident raised post shared infra maintenance activity would adhere to entitled SLA for resolution or credits. • No special preventive measures are required by Customers to prevent disruption to common infrastructure. Customers have Read-Only permissions at AWS Org or Core OU accounts, so customers can’t make any destructive changes to the MALZ core env. All customer’s requests to Core infrastructure requires AMS review and approval. • Customers can test certain Org level changes like SCPs/Roles at individual non-prod account levels before propagating changes at App OU level. It is on the AMS roadmap to allow multiple APP OUs (Q2 2020), which would further alleviate risk in making
ams-ug-036	ams-ug.pdf	36	would adhere to entitled SLA for resolution or credits. • No special preventive measures are required by Customers to prevent disruption to common infrastructure. Customers have Read-Only permissions at AWS Org or Core OU accounts, so customers can’t make any destructive changes to the MALZ core env. All customer’s requests to Core infrastructure requires AMS review and approval. • Customers can test certain Org level changes like SCPs/Roles at individual non-prod account levels before propagating changes at App OU level. It is on the AMS roadmap to allow multiple APP OUs (Q2 2020), which would further alleviate risk in making some of the ORG level changes. MALZ team has already released separate OU for “Build Mode” accounts, to ensure clear segregation of customer ownership and separate controls. • Most of these are changes that allow AMS to operate the workload in eﬀective and eﬃcient manner and does not necessarily impact customers workload. Where AMS believes a shared infra change can have an impact to customers’ workload they are then aligned with customers’ change window. High level recommendation, start with multiple multi-account landing zones if: • If it helps you achieve any speciﬁc compliance. • If you need to use Multi-Region. Choosing single MALZ or multiple MALZs Version May 08, 2025 93 AMS Advanced User Guide AMS Advanced Concepts and Procedures • If you have diﬀerent on-prem ADs and Networks for Prod/Material vs Non-Prod/Non-Material workloads, to clearly segregate b/w the workloads. Multi-Account Landing Zone accounts Topics • Management account • Networking account • Shared Services account • Log Archive account • Security account • Application account types • AMS Tools account (migrating workloads) Management account The management account is your initial AWS account when you begin onboarding with AMS. It utilizes AWS Organizations as a management account (also known as the payer account that pays the charges of all the member accounts), which gives the account the ability to create and ﬁnancially manage member accounts. It contains the AWS landing zone (ALZ) framework, account conﬁguration stack sets, AWS Organization service control policies (SCPs), etc. For more information on using a management account, see Best practices for the management account. The following diagram provides a high-level overview of the resources contained in the management account. Multi-Account Landing Zone accounts Version May 08, 2025 94 AMS Advanced User Guide AMS Advanced Concepts and Procedures Resources in the management account Other than the above standard services, no additional AWS resources are created in the management account during onboarding. The following inputs are required during onboarding to AMS: • Management account ID: AWS Account ID that is created initially by you. • Core Accounts emails: Provide the emails to be associated with each of the core accounts: Networking, Shared Services, Logging, and Security account. • Service Region: Provide the AWS region to which all resources of your AMS landing zone will be deployed. Multi-Account Landing Zone accounts Version May 08, 2025 95 AMS Advanced User Guide Networking account AMS Advanced Concepts and Procedures The Networking account serves as the central hub for network routing between AMS multi- account landing zone accounts, your on-premises network, and egress traﬃc out to the Internet. In addition, this account contains public DMZ bastions that are the entry point for AMS engineers to access hosts in the AMS environment. For details, see the following high-level diagram of the networking account below. Multi-Account Landing Zone accounts Version May 08, 2025 96 AMS Advanced User Guide AMS Advanced Concepts and Procedures Networking account architecture The following diagram depicts the AMS multi-account landing zone environment, showcasing network traﬃc ﬂows across account, and is an example of a highly-available setup. Multi-Account Landing Zone accounts Version May 08, 2025 97 AMS Advanced User Guide AMS Advanced Concepts and Procedures AMS conﬁgures all aspects of networking for you based on our standard templates and your selected options provided during onboarding. A standard AWS network design is applied to your AWS account, and a VPC is created for you and connected to AMS by either VPN or Direct Connect. For more information about Direct Connect, see AWS Direct Connect. Standard VPCs include the DMZ, shared services, and an application subnet. During the onboarding process, additional VPCs might be requested and created to match your needs (for example, customer divisions, partners). After onboarding, you are provided with a network diagram: an environment document that explains how your network has been set up. Note For information about default service limits and constraints for all active services, see the AWS Service Limits documentation. Our network design is built around the Amazon "Principle of Least Privilege". In order to accomplish this, we route all traﬃc, ingress and egress, through a DMZ, except traﬃc coming from a trusted network. The only trusted network is the one conﬁgured between your on-premises environment and
ams-ug-037	ams-ug.pdf	37	be requested and created to match your needs (for example, customer divisions, partners). After onboarding, you are provided with a network diagram: an environment document that explains how your network has been set up. Note For information about default service limits and constraints for all active services, see the AWS Service Limits documentation. Our network design is built around the Amazon "Principle of Least Privilege". In order to accomplish this, we route all traﬃc, ingress and egress, through a DMZ, except traﬃc coming from a trusted network. The only trusted network is the one conﬁgured between your on-premises environment and the VPC through the use of a VPN and/or an AWS Direct Connect (DX). Access is granted through the use of bastion instances, thereby preventing direct access to any production resources. All of your applications and resources reside inside private subnets that are reachable through public load balancers. Public egress traﬃc ﬂows through the NAT Gateways in the egress Multi-Account Landing Zone accounts Version May 08, 2025 98 AMS Advanced User Guide AMS Advanced Concepts and Procedures VPC (in the Networking account) to the Internet Gateway and then to the Internet. Alternatively, the traﬃc can ﬂow over your VPN or Direct Connect to your on-premises environment. Private network connectivity to AMS Multi-account landing zone environment AWS oﬀers private connectivity via either virtual private network (VPN) connectivity, or dedicated lines with AWS Direct Connect. Private connectivity in your multi-account environment, is set up using one of the methods described next: • Centralized Edge connectivity using Transit Gateway • Connecting Direct Connect (DX) and/or VPN to account virtual private clouds (VPCs) Centralized edge connectivity using transit gateway AWS Transit Gateway is a service that enables you to connect your VPCs and your on-premises networks to a single gateway. Transit gateway (TGW) can be used to consolidate your existing edge connectivity and route it through a single ingress/egress point. Transit gateway is created in the networking account of your AMS multi-account environment. For more details about transit gateway, see AWS Transit Gateway. AWS Direct Connect (DX) gateway is used to connect your DX connection over a transit virtual interface to the VPCs or VPNs that are attached to your transit gateway. You associate a Direct Connect gateway with the transit gateway. Then, create a transit virtual interface for your AWS Direct Connect connection to the Direct Connect gateway. For information on DX virtual interfaces, see AWS Direct Connect Virtual Interfaces. This conﬁguration oﬀers the following beneﬁts. You can: • Manage a single connection for multiple VPCs or VPNs that are in the same AWS Region. • Advertise preﬁxes from on-premises to AWS, and from AWS to on-premises. Note For information about using a DX with AWS services, see the Resiliency Toolkit section Classic. For more information, see Transit Gateway associations. Multi-Account Landing Zone accounts Version May 08, 2025 99 AMS Advanced User Guide AMS Advanced Concepts and Procedures To increase the resiliency of your connectivity, we recommend that you attach at least two transit virtual interfaces from diﬀerent AWS Direct Connect locations to the Direct Connect gateway. For more information, see the AWS Direct Connect resiliency recommendation. Connecting DX or VPN to account VPCs With this option, the VPCs in your AMS multi-account landing zone environments are directly connected to Direct Connect or VPN. The traﬃc directly ﬂows from the VPCs to Direct Connect or VPN without traversing through the transit gateway. Resources in the networking account As shown in the networking account diagram, the following components are created in the account and require your input. The Networking account contains two VPCs: Egress VPC and DMZ VPC also known as the Perimeter VPC. AWS Network Manager AWS Network Manager is a service that enables you to visualize your transit gateway (TGW) networks at no additional cost to AMS. It provides centralized network monitoring on both AWS resources and on on-premises networks, a single global view of their private network in a topology diagram and in a geographical map, and utilization metrics, such as bytes in/out, packets in/out, packets dropped, and alerts for changes in the topology, routing, and up/down connection status. For information, see AWS Network Manager. Use one of the following roles to access this resource: • AWSManagedServicesCaseRole Multi-Account Landing Zone accounts Version May 08, 2025 100 AMS Advanced User Guide AMS Advanced Concepts and Procedures • AWSManagedServicesReadOnlyRole • AWSManagedServicesChangeManagementRole Egress VPC The Egress VPC is primarily used for egress traﬃc to the Internet and is composed of public/private subnets in up to three availability zones (AZs). Network address translation (NAT) gateways are provisioned in the public subnets, and transit gateway (TGW) VPC attachments are created in the private subnets. Egress, or outbound, internet traﬃc from all networks enter through the private subnet via TGW, where it is then routed to a
ams-ug-038	ams-ug.pdf	38	to access this resource: • AWSManagedServicesCaseRole Multi-Account Landing Zone accounts Version May 08, 2025 100 AMS Advanced User Guide AMS Advanced Concepts and Procedures • AWSManagedServicesReadOnlyRole • AWSManagedServicesChangeManagementRole Egress VPC The Egress VPC is primarily used for egress traﬃc to the Internet and is composed of public/private subnets in up to three availability zones (AZs). Network address translation (NAT) gateways are provisioned in the public subnets, and transit gateway (TGW) VPC attachments are created in the private subnets. Egress, or outbound, internet traﬃc from all networks enter through the private subnet via TGW, where it is then routed to a NAT via VPC route tables. For your VPCs that contain public-facing applications in a public subnet, traﬃc originating from the internet is contained within that VPC. Return traﬃc is not routed to the TGW or Egress VPC, but routed back through the internet gateway (IGW) in the VPC. Note Networking VPC CIDR range: When you create a VPC, you must specify a range of IPv4 addresses for the VPC in the form of a Classless Inter-Domain Routing (CIDR) block; for example, 10.0.16.0/24. This is the primary CIDR block for your VPC. The AMS multi-account landing zone team recommends the range of 24 (with more IP address) to provide some buﬀer in case other resources/appliances, are deployed in the future. Managed Palo Alto egress ﬁrewall AMS provides a Managed Palo Alto egress ﬁrewall solution, which enables internet-bound outbound traﬃc ﬁltering for all networks in the Multi-Account Landing Zone environment (excluding public facing services). This solution combines industry-leading ﬁrewall technology (Palo Alto VM-300) with AMS' infrastructure management capabilities to deploy, monitor, manage, scale, and restore infrastructure within compliant operating environments. Third parties, including Palo Alto Networks, do not have access to the ﬁrewalls; they are managed solely by AMS engineers. Traﬃc control The managed outbound ﬁrewall solution manages a domain allow-list composed of AMS-required domains for services such as backup and patch, as well as your deﬁned domains. When outbound Multi-Account Landing Zone accounts Version May 08, 2025 101 AMS Advanced User Guide AMS Advanced Concepts and Procedures internet traﬃc is routed to the ﬁrewall, a session is opened, traﬃc is evaluated, and if it matches an allowed domain, the traﬃc is forwarded to the destination. Architecture The managed egress ﬁrewall solution follows a high-availability model, where two to three ﬁrewalls are deployed depending on number of availability zones (AZs). The solution utilizes part of the IP space from the default egress VPC, but also provisions a VPC extension (/24) for additional resources required for managing the ﬁrewalls. Multi-Account Landing Zone accounts Version May 08, 2025 102 AMS Advanced User Guide Network ﬂow AMS Advanced Concepts and Procedures At a high level, public egress traﬃc routing remains the same, except for how traﬃc is routed to the internet from the egress VPC: 1. Egress traﬃc destined for the internet is sent to the Transit Gateway (TGW) through VPC route table 2. TGW routes traﬃc to the egress VPC via the TGW route table 3. VPC routes traﬃc to the internet via the private subnet route tables Multi-Account Landing Zone accounts Version May 08, 2025 103 AMS Advanced User Guide AMS Advanced Concepts and Procedures a. In the default Multi-Account Landing Zone environment, internet traﬃc is sent directly to a network address translation (NAT) gateway. The managed ﬁrewall solution reconﬁgures the private subnet route tables to point the default route (0.0.0.0/0) to a ﬁrewall interface instead. The ﬁrewalls themselves contain three interfaces: 1. Trusted interface: Private interface for receiving traﬃc to be processed. 2. Untrusted interface: Public interface to send traﬃc to the internet. Because the ﬁrewalls perform NAT, external servers accept requests from these public IP addresses. 3. Management interface: Private interface for ﬁrewall API, updates, console, and so on. Throughout all the routing, traﬃc is maintained within the same availability zone (AZ) to reduce cross-AZ traﬃc. Traﬃc only crosses AZs when a failover occurs. Allow-list modiﬁcation After onboarding, a default allow-list named ams-allowlist is created, containing AMS- required public endpoints as well as public endpoints for patching Windows and Linux hosts. Once operating, you can create RFC's in the AMS console under the Management \| Managed Firewall \| Outbound (Palo Alto) category to create or delete allow-lists, or modify the domains. Be aware that ams-allowlist cannot be modiﬁed. The RFC's are handled with full automation (they are not manual). Custom security policy Security policies determine whether to block or allow a session based on traﬃc attributes, such as the source and destination security zone, the source and destination IP address, and the service. Custom security policies are supported with fully automated RFCs. CTs to create or delete security policy can be found under Management \| Managed Firewall \| Outbound (Palo Alto) category, and the CT to edit an existing security policy
ams-ug-039	ams-ug.pdf	39	category to create or delete allow-lists, or modify the domains. Be aware that ams-allowlist cannot be modiﬁed. The RFC's are handled with full automation (they are not manual). Custom security policy Security policies determine whether to block or allow a session based on traﬃc attributes, such as the source and destination security zone, the source and destination IP address, and the service. Custom security policies are supported with fully automated RFCs. CTs to create or delete security policy can be found under Management \| Managed Firewall \| Outbound (Palo Alto) category, and the CT to edit an existing security policy can be found under Deployment \| Managed Firewall \| Outbound (Palo Alto) category. You'll be able to create new security policies, modify security policies, or delete security policies. Note The default security policy ams-allowlist cannot be modiﬁed Multi-Account Landing Zone accounts Version May 08, 2025 104 AMS Advanced User Guide AMS Advanced Concepts and Procedures CloudWatch PA egress dashboards Two dashboards can be found in CloudWatch to provide an aggregated view of Palo Alto (PA). the AMS-MF-PA-Egress-Conﬁg-Dashboard provides a PA conﬁg overview, links to allow-lists, and a list of all security policies including their attributes. The AMS-MF-PA-Egress-Dashboard can be customized to ﬁlter traﬃc logs. For example, to create a dashboard for a security policy, you can create an RFC with a ﬁlter like: fields @timestamp, @message \| filter @logStream like /pa-traffic-logs/ \| filter @message like /<Security Policy Name>/ \| parse @message ",,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,," as x1, @x2, @x3, @x4, @type, @x6, @x7, @source_ip, @destination_ip, @source_nat_ip, @dest_nat_ip, @rule, @x13, @x14, @application, @x16, @from_zone, @to_zone, @x19, @x20, @x21, @x22, @session_id, @x24, @source_port, @destination_port, @source_nat_port, @destination_nat_port, @x29, @protocol, @action, @bytes, @bytes_sent, @bytes_recieved, @packets, @x36, @x37, @category, @x39, @x40, @x41, @source_country, @destination_country, @x44, @packets_sent, @packets_recieved, @session_end_reason, @x48, @x49, @x50 \| display @timestamp, @rule, @action, @session_end_reason, @protocol, @source_ip, @destination_ip, @source_port, @destination_port, @session_id, @from_zone, @to_zone, @category, @bytes_sent, @bytes_recieved, @packets_sent, @packets_recieved, @source_country, @destination_country Failover model The ﬁrewalls solution includes two-three Palo Alto (PA) hosts (one per AZ). Healthy check canaries run on a constant schedule to evaluate the health of the hosts. If a host is identiﬁed as unhealthy, AMS is notiﬁed and the traﬃc for that AZ is automatically shifted to a healthy host in a diﬀerent AZ via route table change. Since the health check workﬂow is running constantly, if the host becomes healthy again due to transient issues or manual remediation, then traﬃc is shifted back to the correct AZ with the healthy host. Scaling AMS monitors the ﬁrewall for throughput and scaling limits. When throughput limits exceed lower watermark thresholds (CPU/Networking), AMS receives an alert. A low watermaker threshold indicates that resources are approaching saturation, reaching a point where AMS will evaluate the metrics over time and reach out to suggest scaling solutions. Multi-Account Landing Zone accounts Version May 08, 2025 105 AMS Advanced User Guide Backup and Restore AMS Advanced Concepts and Procedures Backups are created during initial launch, after any conﬁguration changes, and on a regular interval. Initial launch backups are created on a per host basis, but conﬁguration change and regular interval backups are performed across all ﬁrewall hosts when the backup workﬂow is invoked. AMS engineers can create additional backups outside of those windows or provide backup details if requested. AMS engineers can perform restoration of conﬁguration backups if required. If a restoration is required, it will occur across all hosts to keep conﬁguration between hosts in sync. Restoration also can occur when a host requires a complete recycle of an instance. An automatic restoration of the latest backup occurs when a new EC2 instance is provisioned. In general, hosts are not recycled regularly, and are reserved for severe failures or required AMI swaps. Host recycles are initiated manually, and you are notiﬁed before a recycle occurs. Other than the ﬁrewall conﬁguration backups, your speciﬁc allow-list rules are backed up separately. A backup is automatically created when your deﬁned allow-list rules are modiﬁed. Restoration of the allow-list backup can be performed by an AMS engineer, if required. Updates AMS Managed Firewall Solution requires various updates over time to add improvements to the system, additional features, or updates to the ﬁrewall operating system (OS) or software. Most changes will not aﬀect the running environment such as updating automation infrastructure, but other changes such as ﬁrewall instance rotation or OS update may cause disruption. When a potential service disruption due to updates is evaluated, AMS will coordinate with you to accommodate maintenance windows. Operator access AMS operators use their ActiveDirectory credentials to log into the Palo Alto device to perform operations (e.g., patching, responding to an event, etc.). The solution retains standard AMS Operator authentication and conﬁguration change logs to track actions performed on the Palo Alto Hosts. Default logs By default, the logs generated by the ﬁrewall reside in local storage for
ams-ug-040	ams-ug.pdf	40	running environment such as updating automation infrastructure, but other changes such as ﬁrewall instance rotation or OS update may cause disruption. When a potential service disruption due to updates is evaluated, AMS will coordinate with you to accommodate maintenance windows. Operator access AMS operators use their ActiveDirectory credentials to log into the Palo Alto device to perform operations (e.g., patching, responding to an event, etc.). The solution retains standard AMS Operator authentication and conﬁguration change logs to track actions performed on the Palo Alto Hosts. Default logs By default, the logs generated by the ﬁrewall reside in local storage for each ﬁrewall. Overtime, local logs will be deleted based on storage utilization. The AMS solution provides real-time Multi-Account Landing Zone accounts Version May 08, 2025 106 AMS Advanced User Guide AMS Advanced Concepts and Procedures shipment of logs oﬀ of the machines to CloudWatch logs; for more information, see CloudWatch Logs integration. AMS engineers still have the ability to query and export logs directly oﬀ the machines if required. In addition, logs can be shipped to a customer-owned Panorama; for more information, see Panorama integration. The Logs collected by the solution are the following: RFC Status Codes Log Type Description Traﬃc Threat Displays an entry for the start and end of each session. Each entry includes the date and time, source and destination zones, addresses and ports, application name, security rule name applied to the ﬂow, rule action (allow, deny, or drop), ingress and egress interface, number of bytes, and session end reason. The Type column indicates whether the entry is for the start or end of the session, or whether the session was denied or dropped. A "drop" indicates that the security rule that blocked the traﬃc speciﬁed "any" application, while a "deny" indicates the rule identiﬁed a speciﬁc application. If traﬃc is dropped before the application is identiﬁed, such as when a rule drops all traﬃc for a speciﬁc service, the application is shown as "not-applicable". Displays an entry for each security alarm generated by the ﬁrewall. Each entry includes the date and time, a threat name or URL, the source and destination zones, addresses, and ports, the application name, and the alarm action (allow or block) and severity. The Type column indicates the type of threat, such as "virus" or "spyware;" the Name column is the threat description or URL; and the Category column is the threat category (such as "keylogger") or URL category. Multi-Account Landing Zone accounts Version May 08, 2025 107 AMS Advanced User Guide AMS Advanced Concepts and Procedures Log Type Description URL Filtering Conﬁguration System Alarms Authentication Displays logs for URL ﬁlters, which control access to websites and whether users can submit credentials to websites. Displays an entry for each conﬁguration change. Each entry includes the date and time, the administrator user name, the IP address from where the change was made, the type of client (web interface or CLI), the type of command run, whether the command succeeded or failed, the conﬁguration path, and the values before and after the change. Displays an entry for each system event. Each entry includes the date and time, the event severity, and an event description. The alarms log records detailed information on alarms that are generated by the system. The information in this log is also reported in Alarms. Refer to "Deﬁne Alarm Settings". Displays information about authentication events that occur when end users try to access network resources for which access is controlled by Authentication policy rules. Users can use this information to help troubleshoot access issues and to adjust user Authentication policy as needed. In conjunction with correlation objects, users can also use Authentication logs to identify suspicious activity on the users network, such as brute force attacks. Optionally, users can conﬁgure Authentication rules to Log Authentic ation Timeouts. These timeouts relate to the period of time when a user needs authenticate for a resource only once but can access it repeatedly. Seeing information about the timeouts helps users decide if and how to adjust them. Multi-Account Landing Zone accounts Version May 08, 2025 108 AMS Advanced User Guide AMS Advanced Concepts and Procedures Log Type Description Uniﬁed Displays the latest Traﬃc, Threat, URL Filtering, WildFire Submissio ns, and Data Filtering log entries in a single view. The collective log view enables users to investigate and ﬁlter these diﬀerent types of logs together (instead of searching each log set separately). Or, users can choose which log types to display: click the arrow to the left of the ﬁlter ﬁeld and select traﬃc, threat, url, data, and/or wildﬁre to display only the selected log types. Event management AMS continually monitors the capacity, health status, and availability of the ﬁrewall. Metrics generated from the ﬁrewall, as well as AWS/AMS generated metrics, are used to create
ams-ug-041	ams-ug.pdf	41	URL Filtering, WildFire Submissio ns, and Data Filtering log entries in a single view. The collective log view enables users to investigate and ﬁlter these diﬀerent types of logs together (instead of searching each log set separately). Or, users can choose which log types to display: click the arrow to the left of the ﬁlter ﬁeld and select traﬃc, threat, url, data, and/or wildﬁre to display only the selected log types. Event management AMS continually monitors the capacity, health status, and availability of the ﬁrewall. Metrics generated from the ﬁrewall, as well as AWS/AMS generated metrics, are used to create alarms that are received by AMS operations engineers, who will investigate and resolve the issue. The current alarms cover the following cases: Event Alarms: • Firewall Dataplane CPU Utilization • CPU Utilization - Dataplane CPU (Processing traﬃc) • Firewall Dataplane Packet Utilization is above 80% • Packet utilization - Dataplane (Processing traﬃc) • Firewall Dataplane Session Utilization • Firewall Dataplane Session Active • Aggregate Firewall CPU Utilization • CPU Utilization across all CPUs • Failover By AZ • Alarms when a fail over occurs in an AZ • Unhealthy Syslog Host • Syslog host fails health check Management Alarms: • Health Check Monitor Failure Alarm Multi-Account Landing Zone accounts Version May 08, 2025 109 AMS Advanced User Guide AMS Advanced Concepts and Procedures • When health check workﬂow fails unexpectedly • This is for the workﬂow itself, not if a ﬁrewall health check fails • Password Rotation Failure Alarm • When password rotation fails • API/Service user password is rotated every 90 days Metrics All metrics are captured and stored in CloudWatch in the Networking account. These can be viewed by gaining console access to the Networking account and navigating to the CloudWatch console. Individual metrics can be viewed under the metrics tab or a single-pane dashboard view of select metrics and aggregated metrics can be viewed by navigating to the Dashboard tab, and selecting AMS-MF-PA-Egress-Dashboard. Custom Metrics: • Health Check • Namespace: AMS/MF/PA/Egress • PARouteTableConnectionsByAZ • PAUnhealthyByInstance • PAUnhealthyAggregatedByAZ • PAHealthCheckLockState • Firewall Generated • Namespace: AMS/MF/PA/Egress/<instance-id> • DataPlaneCPUUtilizationPct • DataPlanePacketBuﬀferUtilization • panGPGatewayUtilizationPct • panSessionActive • panSessionUtilization Multi-Account Landing Zone accounts Version May 08, 2025 110 AMS Advanced User Guide AMS Advanced Concepts and Procedures CloudWatch Logs integration CloudWatch Logs integration forwards logs from the ﬁrewalls into CloudWatch Logs, which mitigates the risk of losing logs due to local storage utilization. Logs are populated in real-time as the ﬁrewalls generate them, and can be viewed on-demand through the console or API. Complex queries can be built for log analysis or exported to CSV using CloudWatch Insights. In addition, the custom AMS Managed Firewall CloudWatch dashboard will also show a quick view of speciﬁc traﬃc log queries and a graph visualization of traﬃc and policy hits over time. Utilizing CloudWatch logs also enables native integration to other AWS services such as a AWS Kinesis. Note PA logs cannot be directly forwarded to an existing on-prem or 3rd party Syslog collector. AMS Managed Firewall solution provides real-time shipment of logs oﬀ of the PA machines to AWS CloudWatch Logs. You can use CloudWatch Logs Insight feature to run ad-hoc queries. In addition, logs can be shipped to your Palo Alto's Panorama management solution. CloudWatch logs can also be forwarded to other destinations using CloudWatch Subscription Filters. Learn more about Panorama in the following section. To learn more about Splunk, see Integrating with Splunk. Panorama integration AMS Managed Firewall can, optionally, be integrated with your existing Panorama. This allows you to view ﬁrewall conﬁgurations from Panorama or forward logs from the ﬁrewall to the Panorama. Panorama integration with AMS Managed Firewall is read only, and conﬁguration changes to the ﬁrewalls from Panorama are not allowed. Panorama is completely managed and conﬁgured by you, AMS will only be responsible for conﬁguring the ﬁrewalls to communicate with it. Licensing The price of the AMS Managed Firewall depends on the type of license used, hourly or bring your own license (BYOL), and the instance size in which the appliance runs. You are required to order the instances size and the licenses of the Palo Alto ﬁrewall you prefer through AWS Marketplace. • Marketplace Licenses: Accept the terms and conditions of the VM-Series Next-Generation Firewall Bundle 1 from the networking account in MALZ. Multi-Account Landing Zone accounts Version May 08, 2025 111 AMS Advanced User Guide AMS Advanced Concepts and Procedures • BYOL Licenses: Accept the terms and conditions of the VM-Series Next-Generation Firewall (BYOL) from the networking account in MALZ and share the "BYOL auth code" obtained after purchasing the license to AMS. Limitations At this time, AMS supports VM-300 series or VM-500 series ﬁrewall. Conﬁgurations can be found here: VM-Series Models on AWS EC2 Instances, Note The AMS solution runs in Active-Active mode as
ams-ug-042	ams-ug.pdf	42	the terms and conditions of the VM-Series Next-Generation Firewall Bundle 1 from the networking account in MALZ. Multi-Account Landing Zone accounts Version May 08, 2025 111 AMS Advanced User Guide AMS Advanced Concepts and Procedures • BYOL Licenses: Accept the terms and conditions of the VM-Series Next-Generation Firewall (BYOL) from the networking account in MALZ and share the "BYOL auth code" obtained after purchasing the license to AMS. Limitations At this time, AMS supports VM-300 series or VM-500 series ﬁrewall. Conﬁgurations can be found here: VM-Series Models on AWS EC2 Instances, Note The AMS solution runs in Active-Active mode as each PA instance in its AZ handles egress traﬃc for their respected AZ. So, with two AZs, each PA instance handles egress traﬃc up to 5 Gbps and eﬀectively provides overall 10 Gbps throughput across two AZs. The same is true for all limits in each AZ. Should the AMS health check fail, we shift traﬃc from the AZ with the bad PA to another AZ, and during the instance replacement, capacity is reduced to the remaining AZs limits. AMS does not currently support other Palo Alto bundles available on AWS Marketplace; for example, you cannot ask for the "VM-Series Next-Generation Firewall Bundle 2". Note that the AMS Managed Firewall solution using Palo Alto currently provides only an egress traﬃc ﬁltering oﬀering, so using advanced VM-Series bundles would not provide any additional features or beneﬁts. Onboarding requirements • You must review and accept the Terms and Conditions of the VM-Series Next-Generation Firewall from Palo Alto in AWS Marketplace. • You must conﬁrm the instance size you want to use based on your expected workload. • You must provide a /24 CIDR Block that does not conﬂict with networks in your Multi-Account Landing Zone environment or On-Prem. It must be of same class as the Egress VPC (the Solution provisions a /24 VPC extension to the Egress VPC). Multi-Account Landing Zone accounts Version May 08, 2025 112 AMS Advanced User Guide Pricing AMS Advanced Concepts and Procedures AMS Managed Firewall base infrastructure costs are divided in three main drivers: the EC2 instance that hosts the Palo Alto ﬁrewall, the software license Palo Alto VM-Series licenses, and CloudWatch Integrations. The following pricing is based on the VM-300 series ﬁrewall. • EC2 Instances: The Palo Alto ﬁrewall runs in a high-availability model of 2-3 EC2 instances, where instance is based on expected workloads. Cost for the instance depends on the region and number of AZs • Ex. us-east-1, m5.xlarge, 3AZs • $0.192 * 24 * 30 * 3 = $414.72 • https://aws.amazon.com/ec2/pricing/on-demand/ • Palo Alto Licenses: The software license cost of a Palo Alto VM-300 next-generation ﬁrewall depends on the number of AZ as well as instance type. • Ex. us-east-1, m5.xlarge, 3AZs • $0.87 * 24 * 30 * 3 = $1879.20 • https://aws.amazon.com/marketplace/pp/B083M7JPKB?ref_=srh_res_product_title#pdp- pricing • CloudWatch Logs Integration: CloudWatch logs integration utilizes SysLog servers (EC2 - t3.medium), NLB, and CloudWatch Logs. The cost of the servers is based on region and number of AZs, and the cost of the NLB/CloudWatch logs varies based on traﬃc utilization. • Ex. us-east-1, t3.medium, 3AZ • $0.0416 * 24 * 30 * 3 = $89.86 • https://aws.amazon.com/ec2/pricing/on-demand/ • https://aws.amazon.com/cloudwatch/pricing/ Perimeter (DMZ) VPC The Perimeter, or DMZ, VPC contains the necessary resources for AMS Operations engineers to access AMS networks. It contains public subnets across 2-3 AZs, with SSH Bastions hosts in an Auto Scaling group (ASG) for AMS Operations engineers to log into or tunnel through. The security groups attached to the DMZ bastions contain port 22 inbound rules from Amazon Corp Networks. Multi-Account Landing Zone accounts Version May 08, 2025 113 AMS Advanced User Guide AMS Advanced Concepts and Procedures DMZ VPC CIDR range: When you create a VPC, you must specify a range of IPv4 addresses for the VPC in the form of a Classless Inter-Domain Routing (CIDR) block; for example, 10.0.16.0/24. This is the primary CIDR block for your VPC. Note The AMS team recommends the range of 24 (with more IP address) to provide some buﬀer in case other resources, such as a ﬁrewall, are deployed in the future. AWS Transit Gateway AWS Transit Gateway (TGW) is a service that enables you to connect your Amazon Virtual Private Clouds (VPCs) and your on-premises networks to a single gateway. Transit gateway is the networking backbone that handles the routing between AMS account networks and external networks. For information about Transit Gateway, see AWS Transit Gateway. Provide the following input to create this resource: • Transit Gateway ASN number*: Provide the private Autonomous System Number (ASN) for your transit gateway. This should be the ASN for the AWS side of a Border Gateway Protocol (BGP) session. The range is 64512 to 65534 for 16-bit ASNs. Shared Services account The Shared Services account serves
ams-ug-043	ams-ug.pdf	43	you to connect your Amazon Virtual Private Clouds (VPCs) and your on-premises networks to a single gateway. Transit gateway is the networking backbone that handles the routing between AMS account networks and external networks. For information about Transit Gateway, see AWS Transit Gateway. Provide the following input to create this resource: • Transit Gateway ASN number*: Provide the private Autonomous System Number (ASN) for your transit gateway. This should be the ASN for the AWS side of a Border Gateway Protocol (BGP) session. The range is 64512 to 65534 for 16-bit ASNs. Shared Services account The Shared Services account serves as the central hub for most AMS data plane services. The account contains infrastructure and resources required for access management (AD), end-point security management (Trend Micro), and it contains the customer bastions (SSH/RDP). A high- level overview of the resources contained within Shared Services Account is shown in the following graphic. Multi-Account Landing Zone accounts Version May 08, 2025 114 AMS Advanced User Guide AMS Advanced Concepts and Procedures The Shared Services VPC is composed of the AD subnet, the EPS subnet, and the customer bastions subnet in the three availability zones (AZs). The resources created in the Shared Services VPC are listed below and require your input. • Shared Services VPC CIDR range: When you create a VPC, you must specify a range of IPv4 addresses for the VPC in the form of a Classless Inter-Domain Routing (CIDR) block; for example, 10.0.1.0/24. This is the primary CIDR block for your VPC. Multi-Account Landing Zone accounts Version May 08, 2025 115 AMS Advanced User Guide AMS Advanced Concepts and Procedures Note The AMS team recommends the range of /23. • Active Directory Details: Microsoft Active Directory (AD) is utilized for user/resource management, authentication/authorization, and DNS, across all of your AMS multi-account landing zone accounts. AMS AD is also conﬁgured with a one-way trust to your Active Directory for trust-based authentication. The following input is required to create the AD: • Domain Fully Qualiﬁed Domain Name (FQDN): The fully qualiﬁed domain name for the AWS Managed Microsoft AD directory. The domain should not be an existing domain or child domain of an existing domain in your network. • Domain NetBIOS Name: If you don't specify a NetBIOS name, AMS defaults the name to the ﬁrst part of your directory DNS. For example, corp for the directory DNS corp.example.com. • Trend Micro – endpoint protection security (EPS): Trend Micro endpoint protection (EPS) is the primary component within AMS for operating system security. The system is comprised of Deep Security Manager (DSM), EC2 instances, relay EC2 instances, and an agent present within all data plane and customer EC2 instances. You must assume the EPSMarketplaceSubscriptionRole in the Shared Services account, and subscribe to either the Trend Micro Deep Security (BYOL) AMI, or the Trend Micro Deep Security (Marketplace). The following default inputs are required to create EPS (if you want to change from the defaults): • Relay Instance Type: Default Value - m5.large • DSM Instance Type: Default Value - m5.xlarge • DB Instance Size: Default Value - 200 GB • RDS Instance Type: Default Value - db.m5.large • Customer bastions: You are provided with SSH or RDP bastions (or both) in the Shared Services Account, to access other hosts in your AMS environment. In order to access the AMS network as a user (SSH/RDP), you must use "customer" Bastions as the entry point. The network path originates from the on-premise network, goes through DX/VPN to the transit gateway (TGW), Multi-Account Landing Zone accounts Version May 08, 2025 116 AMS Advanced User Guide AMS Advanced Concepts and Procedures and then is routed to the Shared Services VPC. Once you are able to access the bastion, you can jump to other hosts in the AMS environment, provided that the access request has been granted. • The following inputs are required for SSH bastions. • SSH Bastion Desired Instance Capacity: Default Value - 2. • SSH Bastion Maximum Instances: Default Value - 4. • SSH Bastion Minimum Instances: Default Value -2. • SSH Bastion Instance Type: Default Value - m5.large (can be changed to save costs; for example a t3.medium). • SSH Bastion Ingress CIDRs: IP address ranges from which users in your network access SSH Bastions. • The following inputs are required for Windows RDP bastions. • RDP Bastion Instance Type: Default Value - t3.medium. • RDP Bastion Desired Minimum Sessions: Default Value - 2. • RDP Maximum Sessions: Default Value -10. • RDP Bastion Conﬁguration Type: You can choose one of the below conﬁguration • SecureStandard = A user receives one bastion and only one user can connect to the bastion. • SecureHA = A user receives two bastions in two diﬀerent AZ's to connect to and only one user can connect to the
ams-ug-044	ams-ug.pdf	44	address ranges from which users in your network access SSH Bastions. • The following inputs are required for Windows RDP bastions. • RDP Bastion Instance Type: Default Value - t3.medium. • RDP Bastion Desired Minimum Sessions: Default Value - 2. • RDP Maximum Sessions: Default Value -10. • RDP Bastion Conﬁguration Type: You can choose one of the below conﬁguration • SecureStandard = A user receives one bastion and only one user can connect to the bastion. • SecureHA = A user receives two bastions in two diﬀerent AZ's to connect to and only one user can connect to the bastion. • SharedStandard = A user receives one bastion to connect to and two users can connect to the same bastion at once. • SharedHA = A user receives two bastions in two diﬀerent AZ's to connect to and two users can connect to the same bastion at once. • Customer RDP Ingress CIDRs: IP address ranges from which users in your network will access RDP Bastions. Updates to shared services: Multi-Account Landing Zone AMS applies data plane releases to managed accounts on a monthly basis, without prior notice. AMS uses the core OU to provide shared services such as access, networking, EPS, log storage, alert aggregation in your Multi-Account Landing Zone. AMS is responsible for addressing vulnerabilities, patching, and deployments of these shared services. AMS regularly updates the resources used for Version May 08, 2025 117 Multi-Account Landing Zone accounts AMS Advanced User Guide AMS Advanced Concepts and Procedures providing these shared services so that users have access to latest features, and security updates. The updates typically happen on a monthly basis. Resources that are part of these updates are: • Accounts that are part of the core OU. The management account, shared services account, network account, security account, and log archive account have resources for RDP and SSH bastions, proxies, management hosts, and endpoint security (EPS), that are typically updated every month. AMS uses immutable EC2 deployments as part of the shared services infrastructure. • New AMS AMIs incorporating the latest updates. Note AMS operators utilize an internal alarm suppression change type (CT) when executing data plane changes and the RFC for that CT appears in your RFC list. This is because, as the data plane release is deployed, various infrastructure may be shut down, rebooted, taken oﬄine, or there may be CPU spikes or other eﬀects of the deployment that trigger alarms that, during the data plane deployment, are extraneous. Once the deployment is complete, all infrastructure is veriﬁed to be running properly and alarms are re-enabled. Log Archive account The Log Archive account serves as the central hub for archiving logs across your AMS multi-account landing zone environment. There is an S3 bucket in the account that contains copies of AWS CloudTrail and AWS Conﬁg log ﬁles from each of the AMS multi-account landing zone environment accounts. You could use this account for your Centralised Logging solution with AWS Firehose, or Splunk, and so forth. AMS access to this account is limited to a few users; restricted to auditors and security teams for compliance and forensic investigations related to account activity. Multi-Account Landing Zone accounts Version May 08, 2025 118 AMS Advanced User Guide AMS Advanced Concepts and Procedures Security account The Security account is the central hub for housing security related operations and the main point for funneling notiﬁcations and alerts to the AMS control plane services. In addition, the Security account houses the Amazon Guard Duty management account and the AWS Conﬁg aggregator. Multi-Account Landing Zone accounts Version May 08, 2025 119 AMS Advanced User Guide AMS Advanced Concepts and Procedures Application account types Application accounts are AWS accounts within the AMS-managed landing zone architecture that you use to host your workloads. AMS oﬀers three types of Application accounts: • AMS-managed application accounts • AMS Accelerate accounts • Customer Managed application accounts Application accounts are grouped in diﬀerent OUs in AWS Organizations depending on the Application account type: • Root OU: 1. Applications OU • Managed OU: AMS-managed accounts • Development OU: AMS-managed accounts with Developer mode enabled 2. Accelerate OU: AMS Accelerate Application accounts 3. Customer-managed OU: Customer-managed Application accounts Multi-Account Landing Zone accounts Version May 08, 2025 120 AMS Advanced User Guide AMS Advanced Concepts and Procedures Application accounts are provisioned through an RFC submitted from the Management account: • Create Application Account With VPC ct-1zdasmc2ewzrs • Create Accelerate Account ct-2p93tyd5angmi • Create Customer-Managed Application Account ct-3pwbixz27n3tn AMS-managed application accounts Application accounts that are fully managed by AMS are referred to as AMS-managed application accounts, where some or all operational tasks, like service request management, incident management, security management, continuity management (backup), patch management, cost- optimization, or monitoring and event management of infrastructure, are performed by AMS. The amount of tasks performed
ams-ug-045	ams-ug.pdf	45	accounts Version May 08, 2025 120 AMS Advanced User Guide AMS Advanced Concepts and Procedures Application accounts are provisioned through an RFC submitted from the Management account: • Create Application Account With VPC ct-1zdasmc2ewzrs • Create Accelerate Account ct-2p93tyd5angmi • Create Customer-Managed Application Account ct-3pwbixz27n3tn AMS-managed application accounts Application accounts that are fully managed by AMS are referred to as AMS-managed application accounts, where some or all operational tasks, like service request management, incident management, security management, continuity management (backup), patch management, cost- optimization, or monitoring and event management of infrastructure, are performed by AMS. The amount of tasks performed by AMS depends on the Change Management mode that you select. AMS-managed accounts support diﬀerent modes for change management: • RFC mode • Direct Change mode in AMS • AMS and AWS Service Catalog • AMS Advanced Developer mode • Self-Service Provisioning mode in AMS For more information about change management and diﬀerent modes, see Change management modes. There are some AWS services that you can use in your AMS-managed account without AMS management. The list of these AWS services and how to add them into your AMS account are described in the Self-service provisioning section. AMS Accelerate accounts AMS Accelerate is the AMS operations plan that can operate AWS infrastructure supporting workloads. You can beneﬁt from AMS Accelerate operational services such as monitoring and alerting, incident management, security management, and backup management, without going through a new migration, experiencing downtime, or changing how you use AWS. AMS Accelerate also oﬀers an optional patch add-on for EC2 based workloads that require regular patching. Multi-Account Landing Zone accounts Version May 08, 2025 121 AMS Advanced User Guide AMS Advanced Concepts and Procedures With AMS Accelerate you have the freedom to use, conﬁgure, and deploy all AWS services natively, or with your preferred tools. You will use your preferred access and change mechanisms while AMS consistently applies proven practices that help scale your team, optimize costs, increase security and eﬃciency, and improve resiliency. Note AMS Accelerate accounts in AMS Advanced do not have AMS change management (RFCs) or the AMS Advanced console. Instead, they have the AMS Accelerate console and functionality. Accelerate accounts can only be provisioned from your AMS multi-account landing zone Management account. Accelerate oﬀers diﬀerent operational capabilities. To learn more see the Accelerate service description. • You will continue to enjoy some of the features from the multi-account landing zone (MALZ) core accounts such as centralized logging, single billing, Conﬁg Aggregator in the security account and SCPs. • AMS Accelerate does not provide some AMS Advanced services like EPS, Access management, Change management and provisioning. We recommend you follow the next steps to gain access and conﬁgure the transit gateway (TGW). For more details about Accelerate, see What is Accelerate. Creating your Accelerate account To create an Accelerate account, follow the steps outlined here Create an Accelerate account. Accessing your Accelerate account After you provision an Accelerate account in your multi-account landing zone (MALZ) account, a role with Administrative access permissions, AccelerateDefaultAdminRole, is in the account for you to assume. To access the new Accelerate account: 1. Log into the IAM console for the management account with the CustomerDefaultAssumeRole role. Multi-Account Landing Zone accounts Version May 08, 2025 122 AMS Advanced User Guide AMS Advanced Concepts and Procedures 2. In the IAM console, on the navigation bar, choose your username. 3. Choose Switch Role. If this is the ﬁrst time choosing this option, a page appears with more information. After reading it, choose Switch Role. If you clear your browser cookies, this page can appear again. 4. On the Switch Role page, type the Accelerate account ID and the name of the role to assume: AccelerateDefaultAdminRole. Now that you have access, you can create new IAM Roles to continue to access your environment. If you would like to leverage SAML Federation for your Accelerate account, see Enabling SAML 2.0 federated users to access the AWS Management Console. Connecting your Accelerate account with Transit Gateway AMS does not manage the network setup of an Accelerate account. You have the option of managing your own network using AWS APIs (see Networking Solutions) or connecting to the MALZ network managed by AMS, using the existing Transit Gateway (TGW) deployed in AMS MALZ. Note You can only have a VPC attached to the TGW if the Accelerate account is in the same AWS Region. For more information see Transit gateways. To add your Accelerate account to Transit Gateway, request a new route using the Deployment \| Managed landing zone \| Networking account \| Add static route (ct-3r2ckznmt0a59) change type, include this information: • Blackhole: True to indicate that the route's target isn't available. Do this when the traﬃc for the static route is to be dropped by the Transit Gateway. False to route
ams-ug-046	ams-ug.pdf	46	using the existing Transit Gateway (TGW) deployed in AMS MALZ. Note You can only have a VPC attached to the TGW if the Accelerate account is in the same AWS Region. For more information see Transit gateways. To add your Accelerate account to Transit Gateway, request a new route using the Deployment \| Managed landing zone \| Networking account \| Add static route (ct-3r2ckznmt0a59) change type, include this information: • Blackhole: True to indicate that the route's target isn't available. Do this when the traﬃc for the static route is to be dropped by the Transit Gateway. False to route the traﬃc to the speciﬁed TGW attachment ID. Default value is false. • DestinationCidrBlock: The IPV4 CIDR range used for destination matches. Routing decisions are based on the most speciﬁc match. Example: 10.0.2.0/24. • TransitGatewayAttachmentId: The TGW Attachment ID that will serve as the route table target. If Blackhole is false, this parameter is required, otherwise leave this parameter blank. Example: tgw-attach-04eb40d1e14ec7272. • TransitGatewayRouteTableId: The ID of the TGW route table. Example: tgw- rtb-06ddc751c0c0c881c. Multi-Account Landing Zone accounts Version May 08, 2025 123 AMS Advanced User Guide AMS Advanced Concepts and Procedures Create routes in the TGW route tables to connect to this VPC: 1. By default this VPC will not be able to communicate with any of the other VPCs in your MALZ network. 2. Decide with your solutions architect what VPCs you want this Accelerate VPC to communicate with. 3. Submit a Deployment \| Managed landing zone \| Networking account \| Add static route (ct-3r2ckznmt0a59) change type, include this information: • Blackhole: True to indicate that the route's target isn't available. Do this when the traﬃc for the static route is to be dropped by the Transit Gateway. False to route the traﬃc to the speciﬁed TGW attachment ID. Default value is false. • DestinationCidrBlock: The IPV4 CIDR range used for destination matches. Routing decisions are based on the most speciﬁc match. Example: 10.0.2.0/24. • TransitGatewayAttachmentId: The TGW Attachment ID that will serve as the route table target. If Blackhole is false, this parameter is required, otherwise leave this parameter blank. Example: tgw-attach-04eb40d1e14ec7272. • TransitGatewayRouteTableId: The ID of the TGW route table. Example: tgw- rtb-06ddc751c0c0c881c. Connecting a new Accelerate account VPC to the AMS Multi-Account Landing Zone network (creating a TGW VPC attachment): 1. In your multi-account landing zone Networking account, open the Amazon VPC console. 2. On the navigation pane, choose Transit Gateways. Record the TGW ID of the transit gateway you see. 3. In your Accelerate account, open the Amazon VPC console. 4. In the navigation pane, choose Transit Gateway Attachments > Create Transit Gateway Attachment. Make these choices: • For the Transit Gateway ID, choose the transit gateway ID you recorded in Step 2. • For Attachment type, choose VPC. • Under VPC Attachment, optionally type a name for Attachment name tag. • Choose whether to enable DNS Support and IPv6 Support. • For VPC ID, choose the VPC to attach to the transit gateway. This VPC must have at least one subnet associated with it. Multi-Account Landing Zone accounts Version May 08, 2025 124 AMS Advanced User Guide AMS Advanced Concepts and Procedures • For Subnet IDs, select one subnet for each Availability Zone to be used by the transit gateway to route traﬃc. You must select at least one subnet. You can select only one subnet per Availability Zone. 5. Choose Create attachment. Record the ID of the newly created TGW Attachment. Associating the TGW attachment to a route table: 1. Decide which TGW route table you want to associate the VPC with. We recommend creating a new application route table for Accelerate account VPCs using Deployment \| Managed landing zone \| Networking account \| Create transit gateway route table (ct-3dscwaeyi6cup) change type. 2. Submit a Management \| Managed landing zone \| Networking account \| Associate TGW attachment (ct-3nmhh0qr338q6) RFC on the Networking account to associate the VPC or TGW attachment to the route table you select. Create routes in the TGW route tables to connect to this VPC: 1. By default, this VPC will not be able to communicate with any of the other VPCs in your multi- account landing zone network. 2. Decide with your solutions architect what VPCs you want this Accelerate account VPC to communicate with. 3. Submit a Deployment \| Managed landing zone \| Networking account \| Add static route (ct-3r2ckznmt0a59) RFC against the networking account to create the TGW routes you need. Conﬁguring your VPC Route tables to point at the AMS multi-account landing zone transit gateway: 1. Decide with your solutions architect what traﬃc you want to send to the AMS Multi-Account Landing Zone transit gateway. 2. Submit a Deployment \| Managed landing zone \| Networking account \| Add static route (ct-3r2ckznmt0a59) RFC against the networking
ams-ug-047	ams-ug.pdf	47	2. Decide with your solutions architect what VPCs you want this Accelerate account VPC to communicate with. 3. Submit a Deployment \| Managed landing zone \| Networking account \| Add static route (ct-3r2ckznmt0a59) RFC against the networking account to create the TGW routes you need. Conﬁguring your VPC Route tables to point at the AMS multi-account landing zone transit gateway: 1. Decide with your solutions architect what traﬃc you want to send to the AMS Multi-Account Landing Zone transit gateway. 2. Submit a Deployment \| Managed landing zone \| Networking account \| Add static route (ct-3r2ckznmt0a59) RFC against the networking account to create the TGW routes you need. Multi-Account Landing Zone accounts Version May 08, 2025 125 AMS Advanced User Guide AMS Advanced Concepts and Procedures Customer Managed application accounts You can create accounts that AMS doesn't manage in the standard way. Those accounts are called Customer Managed accounts and they give you full control to self-operate the infrastructure within the accounts while enjoying the beneﬁts of the centralized architecture managed by AMS. Customer Managed accounts do not have access to the AMS console or any of the services we provide (patch, backup, and so on). Customer Managed accounts can only be provisioned from your AMS multi-account landing zone management account. Diﬀerent AMS modes work with Application accounts diﬀerently; to learn more about the modes, see AWS Managed Services modes. To create your Customer Managed application account, see Management account \| Create Customer-Managed Application Account. To delete a Customer Managed application account, use Management account \| Oﬀboard Application Account. (The Conﬁrm Oﬀboarding CT does not apply to Customer Managed application accounts.) Accessing your Customer Managed account After you provision a Customer Managed account (CMA) in multi-account landing zone, (MALZ) an Admin role, CustomerDefaultAdminRole, is in the account for you to assume, through SAML federation, to conﬁgure the account. To access the CMA: 1. Log into the IAM console for the management account with the CustomerDefaultAssumeRole role. 2. In the IAM console, on the navigation bar, choose your username. 3. Choose Switch Role. If this is the ﬁrst time choosing this option, a page appears with more information. After reading it, choose Switch Role. If you clear your browser cookies, this page can appear again. 4. On the Switch Role page, type the Customer Managed account ID and the name of the role to assume: CustomerDefaultAdminRole. Multi-Account Landing Zone accounts Version May 08, 2025 126 AMS Advanced User Guide AMS Advanced Concepts and Procedures Now that you have access, you can create new IAM Roles to continue to access your environment. If you would like to leverage SAML Federation for your CMA Account, see Enabling SAML 2.0 federated users to access the AWS Management Console. Connecting your CMA with Transit Gateway AMS does not manage the network setup of Customer Managed accounts (CMAs). You have the option of managing your own network using AWS APIs (see Networking Solutions) or connecting to the multi-account landing zone network managed by AMS, using the existing Transit Gateway (TGW) deployed in AMS MALZ. Note You can only have a VPC attached to the TGW if the CMA is in the same AWS Region. For more information see Transit gateways. To add your CMA to Transit Gateway, request a new route with the Networking account \| Add static route (ct-3r2ckznmt0a59) change type and include this information: • Blackhole: True to indicate that the route's target isn't available. Do this when the traﬃc for the static route is to be dropped by the Transit Gateway. False to route the traﬃc to the speciﬁed TGW attachment ID. Default value is false. • DestinationCidrBlock: The IPV4 CIDR range used for destination matches. Routing decisions are based on the most speciﬁc match. Example: 10.0.2.0/24. • TransitGatewayAttachmentId: The TGW Attachment ID that will serve as route table target. If Blackhole is false, this parameter is required, otherwise leave this parameter blank. Example: tgw-attach-04eb40d1e14ec7272. • TransitGatewayRouteTableId: The ID of the TGW route table. Example: tgw- rtb-06ddc751c0c0c881c. Connecting a new customer-managed VPC to the AMS Multi-Account Landing Zone network (creating a TGW VPC attachment): 1. 2. In your multi-account landing zone Networking account, open the Amazon VPC console. In the navigation pane, choose Transit Gateways. Record the TGW ID of the transit gateway you see. Multi-Account Landing Zone accounts Version May 08, 2025 127 AMS Advanced User Guide AMS Advanced Concepts and Procedures 3. 4. In your Customer Managed account, open the Amazon VPC console. In the navigation pane, choose Transit Gateway Attachments > Create Transit Gateway Attachment. Make these choices: a. b. For the Transit Gateway ID, choose the transit gateway ID you recorded in Step 2. For Attachment type, choose VPC. c. Under VPC Attachment, optionally type a name for Attachment name tag. d. Choose whether to enable DNS Support and
ams-ug-048	ams-ug.pdf	48	Transit Gateways. Record the TGW ID of the transit gateway you see. Multi-Account Landing Zone accounts Version May 08, 2025 127 AMS Advanced User Guide AMS Advanced Concepts and Procedures 3. 4. In your Customer Managed account, open the Amazon VPC console. In the navigation pane, choose Transit Gateway Attachments > Create Transit Gateway Attachment. Make these choices: a. b. For the Transit Gateway ID, choose the transit gateway ID you recorded in Step 2. For Attachment type, choose VPC. c. Under VPC Attachment, optionally type a name for Attachment name tag. d. Choose whether to enable DNS Support and IPv6 Support. e. f. For VPC ID, choose the VPC to attach to the transit gateway. This VPC must have at least one subnet associated with it. For Subnet IDs, select one subnet for each Availability Zone to be used by the transit gateway to route traﬃc. You must select at least one subnet. You can select only one subnet per Availability Zone. 5. Choose Create attachment. Record the ID of the newly created TGW Attachment. Associating the TGW attachment to a route table: Decide which TGW route table you want to associate the VPC with. We recommend creating a new application route table for Customer Managed VPCs by submitting a Deployment \| Managed landing zone \| Networking account \| Create transit gateway route table (ct-3dscwaeyi6cup) RFC. To associate the VPC or TGW attachment to the route table you select, submit a Deployment \| Managed landing zone \| Networking account \| Associate TGW attachment (ct-3nmhh0qr338q6) RFC on the Networking account. Create routes in the TGW route tables to connect to this VPC: 1. By default, this VPC will not be able to communicate with any of the other VPCs in your Multi- Account Landing Zone network. 2. Decide with your solutions architect what VPCs you want this customer-managed VPC to communicate with. Submit a Deployment \| Managed landing zone \| Networking account \| Add static route (ct-3r2ckznmt0a59) RFC against the networking account to create the TGW routes you need. Multi-Account Landing Zone accounts Version May 08, 2025 128 AMS Advanced User Guide AMS Advanced Concepts and Procedures Note This CT (ct-3r2ckznmt0a59) does not allow adding static routes to core route table EgressRouteDomain; if your CMA needs to allow egress traﬃc, submit a Management \| Other \| Other (MOO) RFC with ct-0xdawir96cy7k. Conﬁguring your VPC Route tables to point at the AMS Multi-Account Landing Zone transit gateway: Decide with your solutions architect what traﬃc you want to send to the AMS Multi-Account Landing Zone transit gateway. Update your VPC route tables to send traﬃc to TGW attachment created earlier Getting operational help with your Customer Managed accounts AMS can help you operate the workloads you deployed in your Customer Managed accounts by on- boarding the account into AMS Accelerate. With AMS Accelerate you can beneﬁt from operational services such as monitoring and alerting, incident management, security management, and backup management, without going through a new migration, experiencing downtime, or changing how you use AWS. AMS Accelerate also oﬀers an optional patch add-on for EC2-based workloads that require regular patching. With AMS Accelerate you continue using, conﬁguring, and deploying all AWS services natively, or with your preferred tools; as you do with AMS Advanced Customer Managed accounts. You use your preferred access and change mechanisms while AMS applies proven practices that help scale your team, optimize costs, increase security and eﬃciency, and improve resiliency. To learn more see the Accelerate service description. To onboard your Customer Managed account into Accelerate, contact your CSDM and follow the steps from Getting Started with AMS Accelerate. Note AMS Accelerate accounts in AMS Advanced do not have AMS change management (requests for change or RFCs) or the AMS Advanced console. Instead, they have the AMS Accelerate console and functionality. Multi-Account Landing Zone accounts Version May 08, 2025 129 AMS Advanced User Guide AMS Advanced Concepts and Procedures AMS Tools account (migrating workloads) Your Multi-Account Landing Zone tools account (with VPC) helps accelerate migration eﬀorts, increases your security position, reduces cost and complexity, and standardizes your usage pattern. A tools account provides the following: • A well-deﬁned boundary for access to replication instances for system integrators outside of your production workloads. • Enables you to create an isolated chamber to check a workload for malware, or unknown network routes, before placing it into an account with other workloads. • As a deﬁned account setup, it provides faster time to onboard and get set up for migrating workloads. • Isolated network routes to secure traﬃc from on-premise -> CloudEndure -> Tools account -> AMS ingested image. Once an image has been ingested, you can share the image to the destination account via an AMS Management \| Advanced stack components \| AMI \| Share (ct-1eiczxw8ihc18) RFC. High level architecture
ams-ug-049	ams-ug.pdf	49	of your production workloads. • Enables you to create an isolated chamber to check a workload for malware, or unknown network routes, before placing it into an account with other workloads. • As a deﬁned account setup, it provides faster time to onboard and get set up for migrating workloads. • Isolated network routes to secure traﬃc from on-premise -> CloudEndure -> Tools account -> AMS ingested image. Once an image has been ingested, you can share the image to the destination account via an AMS Management \| Advanced stack components \| AMI \| Share (ct-1eiczxw8ihc18) RFC. High level architecture diagram: Multi-Account Landing Zone accounts Version May 08, 2025 130 AMS Advanced User Guide AMS Advanced Concepts and Procedures Use the Deployment \| Managed landing zone \| Management account \| Create tools account (with VPC) change type (ct-2j7q1hgf26x5c), to quickly deploy a tools account and instantiate a Workload Ingestion process within a Multi-Account Landing Zone environment. See Management account, Tools account: Creating (with VPC). Note We recommend having two availability zones (AZs), since this is a migration hub. By default, AMS creates the following two security groups (SGs) in every account. Conﬁrm the that the two SGs are present, and, if not, open a new Management \| Other \| Other \| Create CT (ct-1e1xtak34nx76) to request them: • SentinelDefaultSecurityGroupPrivateOnlyEgressAll • InitialGarden-SentinelDefaultSecurityGroupPrivateOnly Multi-Account Landing Zone accounts Version May 08, 2025 131 AMS Advanced User Guide AMS Advanced Concepts and Procedures Ensure that CloudEndure replication instances are created in the private subnet where there are routes back to on-premise. You can conﬁrm that by ensuring that the route tables for the private subnet has a default route back to TGW. However, performing a CloudEndure machine cut over should go into the "isolated" private subnet where there is no route back to on-premise, only Internet outbound traﬃc is allowed. It is critical to ensure cutover occurs in the isolated subnet to avoid potential issues to the on-premise resources. Prerequisites: 1. Either Plus or Premium support level. 2. The application account IDs for the KMS key where the AMIs are deployed. 3. The tools account, created as described previously. AWS Application Migration Service (AWS MGN) AWS Application Migration Service (AWS MGN) can be used in your MALZ Tools account through the AWSManagedServicesMigrationRole IAM role that is created automatically during Tools account provisioning. You can use AWS MGN to migrate applications and databases that run on supported versions of Windows and Linux operating systems. For the most up-to-date information on AWS Region support, see the AWS Regional Services List. If your preferred AWS Region is not currently supported by AWS MGN, or the operating system on which your applications run is not currently supported by AWS MGN, consider using the CloudEndure Migration in your Tools account instead. Requesting AWS MGN Initialization AWS MGN must be initialized by AMS before ﬁrst use. To request this for a new Tools account, submit a Management \| Other \| Other RFC from the Tools account with these details: RFC Subject=Please initialize AWS MGN in this account RFC Comment=Please click 'Get started' on the MGN welcome page here: https://console.aws.amazon.com/mgn/home?region=MALZ_PRIMARY_REGION#/welcome using all default values Multi-Account Landing Zone accounts Version May 08, 2025 132 AMS Advanced User Guide AMS Advanced Concepts and Procedures to 'Create template' and complete the initialization process. Once AMS successfully completes the RFC and initializes AWS MGN in your Tools account, you can use AWSManagedServicesMigrationRole to edit the default template for your requirements. Multi-Account Landing Zone accounts Version May 08, 2025 133 AMS Advanced User Guide AMS Advanced Concepts and Procedures Multi-Account Landing Zone accounts Version May 08, 2025 134 AMS Advanced User Guide AMS Advanced Concepts and Procedures Enable access to the new AMS Tools account Once the tools account is created, AMS provides you with an account ID. Your next step is to conﬁgure access to the new account. Follow these steps. 1. Update the appropriate Active Directory groups to the appropriate account IDs. New AMS-created accounts are provisioned with the ReadOnly role policy as well as a role to allow users to ﬁle RFCs. The Tools account also has an additional IAM role and user available: • IAM role: AWSManagedServicesMigrationRole • IAM user: customer_cloud_endure_user 2. Request policies and roles to allow service integration team members to set up the next level of tools. Navigate to the AMS console and ﬁle the following RFCs: a. Create KMS key. Use either Create KMS Key (auto) or Create KMS Key (review required). As you use KMS to encrypt ingested resources, using a single KMS key that is shared with the rest of the Multi-Account Landing Zone application accounts, provides security for ingested images where they can be decrypted in the destination account. b. Share the KMS key. Use the Management \| Other \| Other \| Create (ct-1e1xtak34nx76) change
ams-ug-050	ams-ug.pdf	50	Request policies and roles to allow service integration team members to set up the next level of tools. Navigate to the AMS console and ﬁle the following RFCs: a. Create KMS key. Use either Create KMS Key (auto) or Create KMS Key (review required). As you use KMS to encrypt ingested resources, using a single KMS key that is shared with the rest of the Multi-Account Landing Zone application accounts, provides security for ingested images where they can be decrypted in the destination account. b. Share the KMS key. Use the Management \| Other \| Other \| Create (ct-1e1xtak34nx76) change type to request that the new KMS key be shared with your application accounts where ingested AMIs will reside. Example graphic of a ﬁnal account setup: Multi-Account Landing Zone accounts Version May 08, 2025 135 AMS Advanced User Guide AMS Advanced Concepts and Procedures Example AMS pre-approved IAM CloudEndure policy To see an AMS pre-approved IAM CloudEndure policy: Unpack the WIGS Cloud Endure Landing Zone Example ﬁle and open the customer_cloud_endure_policy.json. Testing AMS Tools account connectivity and end-to-end setup 1. Start with conﬁguring CloudEndure and installing the CloudEndure agent on a server that will replicate to AMS. 2. Create a project in CloudEndure. 3. Enter the AWS credentials shared when you performed the prerequisites, though secrets manager. Multi-Account Landing Zone accounts Version May 08, 2025 136 AMS Advanced User Guide 4. In Replication settings: AMS Advanced Concepts and Procedures a. Select both AMS "Sentinel" security groups (Private Only and EgressAll) for the Choose the Security Groups to apply to the Replication Servers option. b. Deﬁne cutover options for the machines (instances). For information, see Step 5. Cut over c. Subnet: Private subnet. 5. Security Group: a. Select both AMS "Sentinel" security groups (Private Only and EgressAll). b. Cutover instances have to communicate to the AMS-managed Active Directory (MAD) and to AWS public endpoints: i. Elastic IP: None ii. Public IP: no iii. IAM role: customer-mc-ec2-instance-proﬁle c. Set tags as per your internal tagging convention. 6. Install the CloudEndure agent on the machine and look for the replication instance to come up in your AMS account in the EC2 console. The AMS ingestion process: Multi-Account Landing Zone accounts Version May 08, 2025 137 AMS Advanced User Guide AMS Advanced Concepts and Procedures Multi-Account Landing Zone accounts Version May 08, 2025 138 AMS Advanced User Guide AMS Advanced Concepts and Procedures AMS Tools account hygiene You'll want to clean up after you are done in the account have shared the AMI and no longer have a need for the replicated instances: • Post instance WIGs ingestion: • Cutover instance: At a minimum, stop or terminate this instance, after the work has been completed, via the AWS console • Pre-Ingestion AMI backups: Remove once the instance has been ingested and the on-premise instance terminated • AMS-ingested instances: Turn oﬀ the stack or terminate once the AMI has been shared • AMS-ingested AMIs: Delete once sharing with the destination account is completed • End of migration clean up: Document the resources deployed through Developer mode to ensure clean-up happens on regular basis, for example: • Security groups • Resources created via Cloud-formation • Network ACK • Subnet • VPC • Route Table • Roles • Users and accounts Migration at scale - Migration Factory See Introducing AWS CloudEndure Migration Factory Solution. SALZ network architecture The following diagram depicts the AWS Managed Services (AMS) single-account landing zone (SALZ) VPC network layout and is an example of the highly available setup. SALZ network architecture Version May 08, 2025 139 AMS Advanced User Guide AMS Advanced Concepts and Procedures SALZ network architecture Version May 08, 2025 140 AMS Advanced User Guide AMS Advanced Concepts and Procedures AMS conﬁgures all aspects of networking for you based on our standard templates and your selected options provided during onboarding. A standard AWS network design is applied to your AWS account, and a virtual private cloud (VPC) is created for you and connected to AMS by either VPN or Direct Connect. Learn more about Direct Connect at AWS Direct Connect. Standard VPCs include the DMZ, shared services, and an application subnet. During the onboarding process, additional VPCs might be requested and created to match your needs (for example, customer divisions, partners). After onboarding, you're provided with a network diagram. an environment document that explains how your network has been set up. Note To learn about default service limits and constraints for all active services, see the AWS Service Limits documentation. Our network design is built around the Amazon "Principle of Least Privilege". In order to accomplish this, we route all traﬃc, inbound and outbound, through gateways, except traﬃc coming from a trusted network. The only trusted network is the one conﬁgured between your on- premises environment and the VPC through the
ams-ug-051	ams-ug.pdf	51	created to match your needs (for example, customer divisions, partners). After onboarding, you're provided with a network diagram. an environment document that explains how your network has been set up. Note To learn about default service limits and constraints for all active services, see the AWS Service Limits documentation. Our network design is built around the Amazon "Principle of Least Privilege". In order to accomplish this, we route all traﬃc, inbound and outbound, through gateways, except traﬃc coming from a trusted network. The only trusted network is the one conﬁgured between your on- premises environment and the VPC through the use of a VPN and/or an AWS Direct Connect (DX). Access is granted through the use of bastion instances, thereby preventing direct access to any production resources. All of your applications and resources reside inside private subnets that are reachable through public load balancers. Public egress traﬃc ﬂows through our forward proxies to the Internet Gateway and then to the Internet. Alternatively, the traﬃc can ﬂow over your VPN or Direct Connect to your on-premises environment. AMS Single-account landing zone shared services Shared services subnets contain AMS Directory Services, the Management Host that automates provisioning and common tasks, antivirus (TrendMicro) management server, and internal bastion hosts: • AMS Directory Services = AD Domain Controller Creates an Active Directory in AMS accounts, creates the AMS domain, joins managed stacks to the domain on launch. • Management hosts = AMS Management Host (automate provisioning and common tasks) AMS Single-account landing zone shared services Version May 08, 2025 141 AMS Advanced User Guide AMS Advanced Concepts and Procedures Act as an API endpoint to modify AWS Directory Service, interact with AWS Directory Service domain controllers. • Security services: Antivirus (TrendMicro) management server = EPS DSM + EPS Relay Leverages Trend Micro™ Deep Security software (DSM), operates in a client-server model and has a back-end database, includes Deep Security managers, agents, and relays. • Internal bastion hosts = Customer bastions Special purpose servers designed to be the primary access point from the Internet and act as a proxy to your other Amazon EC2 instances. AMS Single-account landing zone shared services Version May 08, 2025 142 AMS Advanced User Guide AMS Advanced Concepts and Procedures Setting up AMS Topics • Understand AMS default settings • Using the AMS consoles • Using the AMS API and CLI • AMS bring your own EPS • Receiving AMS notiﬁcations • Setting up private and public DNS • AMS egress traﬃc management • Deploying IAM resources in AMS Advanced • Setting permissions in AMS with IAM roles and proﬁles • AD FS claim rule and SAML settings • Restrict with network ACL • AMS on Outposts • Using tags in AMS • AWS Managed Services Resource Scheduler • AWS Systems Manager in AMS Advanced • Oﬀboard AMS accounts Some AMS setup tasks might be completed at onboarding. For a full description of roles and responsibilities, including the AMS Supported AWS services, see AMS responsibility matrix (RACI). Note To request that AMS provide an additional AWS service, ﬁle a service request. For information about how to make this request, see Service request management. Version May 08, 2025 143 AMS Advanced User Guide AMS Advanced Concepts and Procedures Understand AMS default settings Your AWS Managed Services (AMS) network has a standardized conﬁguration with defaults for most services. This section describes the default settings that AMS uses for access, monitoring, and logging, management. For an example of multi-account landing zone or single-account landing zone infrastructure costs, see AMS environment basic components. Topics • DNS resolution defaults (MALZ) • EC2 IAM instance proﬁle • Alerts from baseline monitoring in AMS • Log retention and rotation defaults DNS resolution defaults (MALZ) AWS Managed Services (AMS) multi-account landing zone: In AWS environments, domain name system (DNS) resolution between Route 53 Resolver and DNS resolvers in a VPC can be integrated by conﬁguring Resolver forwarding rules. Before these rules can be used for forwarding DNS queries, inbound and outbound resolver endpoints need to be set up to which these queries can be forwarded. By default, DNS queries within application account VPCs in multi-account settings in AMS are forwarded to the conditional forwarders of the AWS Directory Service for Microsoft Active Directory (also known as Managed AD) domain present in the shared services account. AMS optionally enables you to make use of the AmazonProvidedDNS; for example, AmazonProvidedDNS to forward DNS queries to. This helps you utilize VPC endpoints that today only support Amazon-provided DNS through Amazon Route 53. Correspondingly, Resolver Rules are also automatically set up for common VPC endpoints that are deployed by default in the shared services account. For more information on these common VPC endpoints, see AMS VPC endpoints. To conﬁgure Dynamic Host Conﬁguration Protocol (DHCP) Option Sets in all of your application account
ams-ug-052	ams-ug.pdf	52	Service for Microsoft Active Directory (also known as Managed AD) domain present in the shared services account. AMS optionally enables you to make use of the AmazonProvidedDNS; for example, AmazonProvidedDNS to forward DNS queries to. This helps you utilize VPC endpoints that today only support Amazon-provided DNS through Amazon Route 53. Correspondingly, Resolver Rules are also automatically set up for common VPC endpoints that are deployed by default in the shared services account. For more information on these common VPC endpoints, see AMS VPC endpoints. To conﬁgure Dynamic Host Conﬁguration Protocol (DHCP) Option Sets in all of your application account VPCs to use Amazon-provided DNS for VPC endpoints, and have Route53 Resolver rules AMS default settings Version May 08, 2025 144 AMS Advanced User Guide AMS Advanced Concepts and Procedures pointing to the common VPC endpoints in your shared services accounts (with an optional Resolver Rule for on-premises domain), create a Management \| Other \| Other \| Create request for change (RFC) specifying the shared services account, and requesting enablement of the application account VPC local DNS and Route 53 Resolver rules for VPC endpoints. EC2 IAM instance proﬁle An instance proﬁle is a container for an IAM role that you can use to pass role information to an EC2 instance when the instance starts. MALZ There are two AMS default instance proﬁles, customer-mc-ec2-instance-profile and customer-mc-ec2-instance-profile-s3. These instance proﬁles provide the permissions described in the following table. Policy descriptions Proﬁle Policies customer-mc-ec2-in stance-profile AmazonSSMManagedInstanceCore instances to use the SSM agent. : Allows Ec2 AMSInstanceProfileLoggingPolicy instances to push logs to S3 and CloudWatch. : Allows Ec2 AMSInstanceProfileManagementPolicy Ec2 instances to perform booting actions, like joining : Allows Active Directory. AMSInstanceProfileMonitoringPolicy Ec2 instances to report ﬁndings to AMS monitoring : Allows services. AMSInstanceProfilePatchPolicy instances to receive patches. : Allows Ec2 customer-mc-ec2-in stance-profile-s3 AMSInstanceProfileBYOEPSPolicy instances to use AMS bring your own EPS. : Allows Ec2 EC2 IAM instance proﬁle Version May 08, 2025 145 AMS Advanced User Guide AMS Advanced Concepts and Procedures Proﬁle Policies AMSInstanceProfileLoggingPolicy instances to push logs to S3 and CloudWatch. : Allows Ec2 AMSInstanceProfileManagementPolicy Ec2 instances to perform booting actions, like joining : Allows Active Directory. AMSInstanceProfileMonitoringPolicy Ec2 instances to report ﬁndings to AMS monitoring : Allows services. AMSInstanceProfilePatchPolicy instances to receive patches. : Allows Ec2 AMSInstanceProfileS3WritePolicy instances to read/write to customer S3 buckets. : Allows Ec2 SALZ There is one AMS default instance proﬁle, customer-mc-ec2- instance-profile, that grants permissions from the IAM instance policy customer_ec2_instance_profile_policy. This instance proﬁle provides the permissions described in the following table. The proﬁle grants permissions to the applications running on the instance, not to users logging into the instance. Policies often include multiple statements, where each statement grants permissions to a diﬀerent set of resources or grants permissions under a speciﬁc condition. CW = CloudWatch. ARN = Amazon Resource Name. * = wildcard (any). EC2 default IAM instance proﬁle permissions CW = CloudWatch. ARN = Amazon Resource Name. * = wildcard (any). Policy statement Eﬀect Actions Description and resource (ARN) Amazon Elastic Compute Cloud (Amazon EC2) EC2 IAM instance proﬁle Version May 08, 2025 146 AMS Advanced User Guide AMS Advanced Concepts and Procedures CW = CloudWatch. ARN = Amazon Resource Name. * = wildcard (any). Policy statement Eﬀect Actions Description and resource (ARN) EC2 Message Actions Allow AcknowledgeMessage, Allows EC2 Systems Manager messaging actions in your DeleteMessage, account. FailMessage, GetEndpoint, GetMessages, SendReply Ec2 Describe Allow * (All) Iam Get Role ID Allow GetRole Allows the console to display conﬁguration details of an EC2 in your account. Allows EC2 to get your IAM ID from aws:iam:::role/cu stomer- and aws:iam:: :role/customer_ . Instance To Upload Log Events Allow Create Log Group Allows logs to be created in: aws:logs:::log-g roup:i-* Create Log Stream Allows logs to be streamed to: aws:logs:::log-g roup:i-* EC2 IAM instance proﬁle Version May 08, 2025 147 AMS Advanced User Guide AMS Advanced Concepts and Procedures CW = CloudWatch. ARN = Amazon Resource Name. * = wildcard (any). Policy statement Eﬀect Actions Description and resource (ARN) CW For MMS Allow DescribeAlarms, PutMetricAlarm, PutMetricData Ec2 Tags Allow CreateTags, DescribeTags, Explicitly Deny CW Logs Deny DescribeLogStreams, FilterLogEvents, GetLogEvents Amazon EC2 Simple Systems Manager (SSM) SSM Actions Allow DescribeAssociation, Allows CloudWatch to retrieve alarms in your account. Allows CW to create or update an alarm and associate it with the speciﬁed metric. Allows CW to publish metric data points to your account. Allows tags to be added, overwritt en, and described on the speciﬁed instances in your account. Disallows listing, ﬁltering , or getting the log streams for: aws:logs:::log-g roup:/mc/* Allows a variety of SSM functions in your account. GetDocument, ListAssociations, UpdateAssociationS tatus, UpdateInstanceInfo rmation EC2 IAM instance proﬁle Version May 08, 2025 148 AMS Advanced User Guide AMS Advanced Concepts and Procedures CW = CloudWatch. ARN = Amazon Resource Name. * = wildcard (any).
ams-ug-053	ams-ug.pdf	53	your account. Allows CW to create or update an alarm and associate it with the speciﬁed metric. Allows CW to publish metric data points to your account. Allows tags to be added, overwritt en, and described on the speciﬁed instances in your account. Disallows listing, ﬁltering , or getting the log streams for: aws:logs:::log-g roup:/mc/* Allows a variety of SSM functions in your account. GetDocument, ListAssociations, UpdateAssociationS tatus, UpdateInstanceInfo rmation EC2 IAM instance proﬁle Version May 08, 2025 148 AMS Advanced User Guide AMS Advanced Concepts and Procedures CW = CloudWatch. ARN = Amazon Resource Name. * = wildcard (any). Policy statement Eﬀect Actions Description and resource (ARN) SSM Access In S3 Allow GetObject, PutObject, AbortMultipartUpload, Allows the SSM on the EC2 to get and update objects in, and to abort a multi-part object upload to, and list ports and buckets available for, multi-part uploads ListMultipartUploa in aws:s3:::mc--inte dPorts, rnal-/aws/ssm* . ListBucketMultipar tUploads Amazon EC2 Simple Storage Service (S3) Get Object In S3 Allow Get List Allows EC2 applications to retrieve and list objects in S3 buckets in your account. Customer Encrypted Log S3 Access Patch Data Put Object S3 Uploading Own Logs To S3 Allow PutObject Allows EC2 applications to update Allow PutObject objects in aws:s3:::mc-- logs-/encrypted/app/* Allows EC2 applications to upload patching data to your S3 buckets at aws:s3:::awsms-a- patch-data- Allow PutObject Allows EC2 applications to upload custom logs to: aws:s3::: mc-a-logs-/aws/i nstances//${aws:u serid}/ EC2 IAM instance proﬁle Version May 08, 2025 149 AMS Advanced User Guide AMS Advanced Concepts and Procedures CW = CloudWatch. ARN = Amazon Resource Name. * = wildcard (any). Policy statement Eﬀect Actions Description and resource (ARN) Explicitly Deny MC Namespace S3 Logs Deny GetObject* Put* Explicitly Deny S3 Delete Deny * (all) Explicitly Deny S3 CFN Bucket Deny Delete* Explicitly Deny List Bucket S3 Deny ListBucket AWS Secrets Manager in Amazon EC2 Disallows EC2 applications getting or putting any objects from or to: aws:s3:::mc--logs-/ encrypted/mc* , aws:s3:::mc--logs-/ mc/, aws:s3:::mc-a-logs-- audit/ Disallows EC2 applications taking any action on objects in: aws:s3:::mc-a-logs-/* , aws:s3:::mc-a-int ernal-/* , Disallows EC2 applications deleting any objects from: aws:s3:::cf-templates-* Disallows you listing any encrypted, audit log, or reserved (mc) objects from: aws:s3::: mc--logs- EC2 IAM instance proﬁle Version May 08, 2025 150 AMS Advanced User Guide AMS Advanced Concepts and Procedures CW = CloudWatch. ARN = Amazon Resource Name. * = wildcard (any). Policy statement Eﬀect Actions Description and resource (ARN) Trend Cloud One Secrets Access Allow GetSecretValue Allows EC2 to access secrets for Trend Cloud One migration: aws:secretsmanager :::secret:/ams/eps/ cloud-one-agent-tenant- id* , arn:aws:secretsman ager:::secret:/ams/ eps/cloud-one-agent- , activation-token* aws:secretsmanager :::secret:/ams/eps/ cloud-one-agent-tenant- id* , aws:secretsmanager :::secret:/ams/eps/ cloud-one-agent-tenant- guid* Allow EC2 to decrypt the AWS KMS key with alias name /ams/ eps/cloudone-migration aws:kms:::key/* AWS Key Management Service in Amazon EC2 Trend Cloud One Decryption Key Allow Decrypt If you're unfamiliar with Amazon IAM policies, see Overview of IAM Policies for important information. EC2 IAM instance proﬁle Version May 08, 2025 151 AMS Advanced User Guide AMS Advanced Concepts and Procedures Note Policies often include multiple statements, where each statement grants permissions to a diﬀerent set of resources or grants permissions under a speciﬁc condition. Alerts from baseline monitoring in AMS Learn about AMS monitoring defaults. For more information, see Monitoring and event management in AMS. The following table shows what is monitored, and the default alerting thresholds. You can change the alerting thresholds with a Management \| Other \| Other \| Update (ct-0xdawir96cy7k) RFC after determining what changes you want and subscribing to the relevant CloudWatch Amazon SNS topic. For information about creating and subscribing to topics, see Subscribe to a Topic. For general information, see Amazon SNS FAQs. To be notiﬁed directly when alarms cross their threshold, in addition to AMS's standard alerting process, follow these instructions about how to overwrite alarm conﬁgurations, Receiving alerts generated by AMS. Amazon CloudWatch provides extended retention of metrics. For more information, see CloudWatch Limits. Note AMS calibrates its baseline monitoring on a periodic basis. New accounts are always onboarded with the latest baseline monitoring and the table describes the baseline monitoring for an account that is newly onboarded. AMS updates the baseline monitoring in existing accounts on a periodic basis and you may experience a time lag before the updates are in place. For more information, see Viewing the monitoring conﬁguration for an AMS account. Note The EC2 instance alert Non-root volume usage is DISABLED by default. If you require alert generation based on this alarm, then you must enable it using the RFC Change Type ct-0erkoad6uyvvg Alerts from baseline monitoring in AMS Version May 08, 2025 152 AMS Advanced User Guide AMS Advanced Concepts and Procedures Alerts from baseline monitoring Service Security alert Alert name and trigger condition Notes For starred (*) alerts, AMS proactively assesses impact and remediates when possible; if
ams-ug-054	ams-ug.pdf	54	experience a time lag before the updates are in place. For more information, see Viewing the monitoring conﬁguration for an AMS account. Note The EC2 instance alert Non-root volume usage is DISABLED by default. If you require alert generation based on this alarm, then you must enable it using the RFC Change Type ct-0erkoad6uyvvg Alerts from baseline monitoring in AMS Version May 08, 2025 152 AMS Advanced User Guide AMS Advanced Concepts and Procedures Alerts from baseline monitoring Service Security alert Alert name and trigger condition Notes For starred () alerts, AMS proactively assesses impact and remediates when possible; if remediation is not possible, AMS creates an incident. Where automation fails to correct the issue, AMS informs you of the incident case and an AMS engineer is engaged. In addition, these alerts can be sent directly to your email (if you have opted in to the Direct-Customer-Alerts SNS topic). Applicati on Load Balancer (ALB) instance Applicati on Load Balancer No RejectedConnectionCount sum > 0 for 1 min, 5 consecutive times. CloudWatch alarm if the number of connections that were rejected because the load balancer reached its maximum. No TargetConnectionErrorCount sum > 0 for 1 min, 5 consecutive (ALB) target times. CloudWatch alarm if number of connections were unsuccess fully established between the load balancer and the registered instances. Aurora instance No CPUUtilization CloudWatch alarm. > 85% for 5 mins, 2 consecutive times. AWS Backup Yes DeleteRecoveryPoint An unexpected IAM role principal or IAM user principal has deleted an AWS Backup recovery point. CloudWatch event. Emitted when a backup recovery point is deleted. AWS Outposts Yes AMSOutpostsInstanceFamilyCa pacityAvailability InstanceF amilyCapacityAvailability CloudWatch alarm on instance family capacity availability of the AWS Outposts resource. Alerts from baseline monitoring in AMS Version May 08, 2025 153 AMS Advanced User Guide AMS Advanced Concepts and Procedures Service Security alert Alert name and trigger condition Notes = 80% for 5 minutes, 12 consecuti ve times. AMSOutpostsInstanceTypeCapa cityAvailability TypeCapacityAvaila CloudWatch alarm on instance type capacity availability of the bility AWS Outposts resource. = 80% for 5 minutes, 12 consecuti ve times. AMSOutpostsConnectedStatusC onnectedStatus CloudWatch alarm on AWS Outposts service link connectio n, less than 1 count is impaired. < 1 for 5 minutes, 1 consecutive time. AMSOutpostsCapacityExceptio nCapacityExceptions 0 for 5 minutes, 1 consecutive time. CPUUtilization >= 95% for 5 mins, 6 consecutive times. CloudWatch alarm on insuﬃci ent capacity errors for instance launches for AWS Outpostss resource . CloudWatch alarm. High CPU utilization is an indicator of a change in application state such as dead locks, inﬁnite loops, malicious attacks, and other anomalies. StatusCheckFailed > 0 for 5 minutes, 3 consecutive times. CloudWatch alarm. EC2 instance - all OSs No Alerts from baseline monitoring in AMS Version May 08, 2025 154 AMS Advanced User Guide AMS Advanced Concepts and Procedures Service Security alert Alert name and trigger condition Notes Root Volume Usage >= 95% for 5 mins, 6 consecutive times. Non-root Volume Usage > 85% for 5 mins, 2 consecutive times. Disabled by default; for details, see Additional Information. Memory Free* MemoryFree < 5% for 5 minutes, 6 consecutive times. Yes EPS Malware CloudWatch event. Malware found on instance. Root Volume Inode Usage Average >= 95% for 5 mins, 6 consecutive times. No Swap Free* Memory Swap < 5% for 5 minutes, 6 consecutive times. Amazon EC2 instance - Linux CloudWatch alarm. Applied to Linux instances only. Alerts from baseline monitoring in AMS Version May 08, 2025 155 AMS Advanced User Guide AMS Advanced Concepts and Procedures Service Security alert Alert name and trigger condition Notes ElastiCache Cluster No CurrConnections = 65000 This alarm notiﬁes AMS of the maximum connection limit of an ElastiCache Host. CloudWatch Alarm. If you would like to update this threshold, contact AMS support. Alerts from baseline monitoring in AMS Version May 08, 2025 156 AMS Advanced User Guide AMS Advanced Concepts and Procedures Service Security alert Alert name and trigger condition Notes ElastiCache Node No CPUUtilization Average > predeﬁned value for 15 mins, 2 consecutive times. CloudWatch alarm. Default is 90. If Redis, use one the following values based on instance type: • cache.t1.micro: 90% • cache.m1.small: 90% • cache.m1.medium: 90% • cache.m1.large: 45% • cache.m1.xlarge: 22.5% • cache.m2.xlarge: 45% • cache.m2.4xlarge: 11.25% • cache.c1.xlarge: 11.25% • cache.t2.micro: 90% • cache.t2.small: 90% • cache.t2.medium: 45% • cache.m3.medium: 90% • cache.m3.large: 45% • cache.m3.xlarge: 22.5% • cache.m3.2xlarge: 11.25% • cache.r3.large: 45% • cache.r3.xlarge: 22.5% • cache.r3.2xlarge: 11.25% • cache.r3.4xlarge: 5.625% • cache.r3.8xlarge: 2.8125% ElastiCac he Node - memcached No SwapUsage maximum > 50,000,000 bytes for 5 mins, 5 consecutive times. CloudWatch alarm. Applied to memcached only. Alerts from baseline monitoring in AMS Version May 08, 2025 157 AMS Advanced User Guide AMS Advanced Concepts and Procedures Service Security alert Alert name and trigger condition Notes OpenSearch cluster No ClusterStatus.red maximum is >=
ams-ug-055	ams-ug.pdf	55	cache.m2.4xlarge: 11.25% • cache.c1.xlarge: 11.25% • cache.t2.micro: 90% • cache.t2.small: 90% • cache.t2.medium: 45% • cache.m3.medium: 90% • cache.m3.large: 45% • cache.m3.xlarge: 22.5% • cache.m3.2xlarge: 11.25% • cache.r3.large: 45% • cache.r3.xlarge: 22.5% • cache.r3.2xlarge: 11.25% • cache.r3.4xlarge: 5.625% • cache.r3.8xlarge: 2.8125% ElastiCac he Node - memcached No SwapUsage maximum > 50,000,000 bytes for 5 mins, 5 consecutive times. CloudWatch alarm. Applied to memcached only. Alerts from baseline monitoring in AMS Version May 08, 2025 157 AMS Advanced User Guide AMS Advanced Concepts and Procedures Service Security alert Alert name and trigger condition Notes OpenSearch cluster No ClusterStatus.red maximum is >= 1 for 1 minute, 1 consecutive time. CloudWatch alarm. At least one primary shard and its replicas are not allocated to a node. To learn more, see Red Cluster AMS takes pro-active actions to reduce operational impact, when this Status. OpenSearch domain No alert is triggered. KMSKeyError >= 1 for 1 minute, 1 consecutive time. ClusterStatus.yellow maximum is >= 1 for 1 minute, 1 consecutive time AMS takes pro-active actions to reduce operational impact, when this alert is triggered. FreeStorageSpace minimum is <= 20480 for 1 minute, 1 consecutive time AMS takes pro-active actions to reduce operational impact, when this alert is triggered. CloudWatch alarm. The KMS encryption key that is used to encrypt data at rest in your domain is disabled. Re-enable it to restore normal operations. To learn more, see Encryption of Data at Rest for OpenSearch Service Service. At least one replica shard is not allocated to a node. To learn more, see Yellow Cluster Status. A node in your cluster is down to 20 GiB of free storage space. To learn more, see Lack of Available Storage Space. Alerts from baseline monitoring in AMS Version May 08, 2025 158 AMS Advanced User Guide AMS Advanced Concepts and Procedures Service Security alert Alert name and trigger condition Notes ClusterIndexWritesBlocked >= 1 for 5 minutes, 1 consecutive time The cluster is blocking write requests. To learn more, see ClusterBlockException. AMS takes pro-active actions to reduce operational impact, when this alert is triggered. Nodes minimum is < x for 1 day, 1 consecutive time AMS takes pro-active actions to reduce operational impact, when this alert is triggered. CPUUtilization average is >= 80% for 15 minutes, 3 consecutive times AMS takes pro-active actions to reduce operational impact, when this alert is triggered. x is the number of nodes in your cluster. This alarm indicates that at least one node in your cluster has been unreachable for one day. To learn more, see Failed Cluster Nodes. 100% CPU utilization is common, but sustained high averages are problematic. Consider using larger instance types or adding instances. Alerts from baseline monitoring in AMS Version May 08, 2025 159 AMS Advanced User Guide AMS Advanced Concepts and Procedures Service Security alert Alert name and trigger condition Notes JVMMemoryPressure maximum is >= 80% for 5 minutes, 3 consecutive times AMS takes pro-active actions to reduce operational impact, when this alert is triggered. MasterCPUUtilization average is >= 50% for 15 minutes, 3 consecutive times AMS takes pro-active actions to reduce operational impact, when this alert is triggered. MasterJVMMemoryPressure maximum is >= 80% for 15 minutes, 1 consecutive time AMS takes pro-active actions to reduce operational impact, when this alert is triggered. The cluster could encounter out of memory errors if usage increases. Consider scaling vertically. Amazon ES uses half of an instance's RAM for the Java heap, up to a heap size of 32 GiB. You can scale instances vertically up to 64 GiB of RAM, at which point you can scale horizontally by adding instances . Consider using larger instance types for your dedicated master nodes. Because of their role in cluster stability and blue/ green deployments, dedicated master nodes should have lower average CPU usage than data nodes. Consider using larger instance types for your dedicated master nodes. Because of their role in cluster stability and blue/ green deployments, dedicated master nodes should have lower average CPU usage than data nodes. Alerts from baseline monitoring in AMS Version May 08, 2025 160 AMS Advanced User Guide AMS Advanced Concepts and Procedures Service Security alert Alert name and trigger condition Notes OpenSearch instance No AutomatedSnapshotFailure maximum is >= 1 for 1 minute, 1 consecutive time. SurgeQueueLength CloudWatch alarm. An automated snapshot failed. This failure is often the result of a red cluster health status. See Red Cluster Status. CloudWatch alarm if an excess number of requests are pending > 100 for 1 minute, 15 consecutive routing. times. Elastic Load HTTPCode_ELB_5XX_Count Balancing No sum > 0 for 5 min, 3 consecutive instance times. SpilloverCount > 1 for 1 minute, 15 consecutive times. CloudWatch alarm on excess number of HTTP 5XX response codes that originate from the load balancer. CloudWatch alarm if an excess number of requests
ams-ug-056	ams-ug.pdf	56	maximum is >= 1 for 1 minute, 1 consecutive time. SurgeQueueLength CloudWatch alarm. An automated snapshot failed. This failure is often the result of a red cluster health status. See Red Cluster Status. CloudWatch alarm if an excess number of requests are pending > 100 for 1 minute, 15 consecutive routing. times. Elastic Load HTTPCode_ELB_5XX_Count Balancing No sum > 0 for 5 min, 3 consecutive instance times. SpilloverCount > 1 for 1 minute, 15 consecutive times. CloudWatch alarm on excess number of HTTP 5XX response codes that originate from the load balancer. CloudWatch alarm if an excess number of requests that were rejected because the surge queue is full. GuardDuty service Yes Not applicable; all ﬁndings (threat purposes) are monitored. Each List of supported GuardDuty ﬁnding types are on GuardDuty ﬁnding corresponds to an alert. Active Finding Types. Changes in the GuardDuty ﬁndings. These changes include newly generated ﬁndings or subsequent occurrences of existing ﬁndings. Alerts from baseline monitoring in AMS Version May 08, 2025 161 AMS Advanced User Guide AMS Advanced Concepts and Procedures Service Security alert Alert name and trigger condition Notes Health Varies AWS Health Dashboard AWS Managed Microsoft AD No Active Directory Status AWS Managed Microsoft AD instance sends an active status event. Impaired Directory Status AWS Managed Microsoft AD instance sends an impaired directory status event. Inoperable Directory Status AWS Managed Microsoft AD instance sends an inoperable status event. Deleting Directory Status AWS Managed Microsoft AD instance sends a deleting directory status event. Notiﬁcations are sent when there are changes in the status of AWS Health Dashboard (AWS Health) events in relation to baseline services supported by AMS. For more information, see Supported services. Service event. Emitted when the directory is operating normally after an event. Service event. Emitted when the directory is running in a degraded state. One or more issues have been detected, and not all directory operations may be working at full operational capacity. Service event. Emitted when the directory is not functiona l. All directory endpoints have reported issues. Service event. Emitted when the directory is currently being deleted. Alerts from baseline monitoring in AMS Version May 08, 2025 162 AMS Advanced User Guide AMS Advanced Concepts and Procedures Service Security alert Alert name and trigger condition Notes Failed Directory Status AWS Managed Microsoft AD instance sends a failed status event. RestoreFailed Directory Status AWS Managed Microsoft AD instance sends a restore failed directory status event. Service event. Emitted when the directory could not be created. Service event. Emitted when restoring the directory from a snapshot failed. Low Storage alert triggers when the allocated storage for the DB RDS-EVENT-0007, see details at Using Amazon RDS event instance has been exhausted. notiﬁcation. DB instance fail The DB instance has failed due to an incompatible conﬁguration or an underlying storage issue. Begin a point-in-time-restore for the DB instance. Failover not attempted Amazon RDS is not attempting a requested failover because a failover recently occurred on the DB instance. Service event. RDS-EVENT -0031, Amazon RDS Event Categories and Event Messages. Service event. RDS-EVENT -0034, Amazon RDS Event Categories and Event Messages. Amazon RDS instance No Alerts from baseline monitoring in AMS Version May 08, 2025 163 AMS Advanced User Guide AMS Advanced Concepts and Procedures Service Security alert Alert name and trigger condition Notes Service event. RDS-EVENT -0035, Amazon RDS Event Categories and Event Messages. Service event. RDS-EVENT -0036, Amazon RDS Event Categories and Event Messages. Service event. RDS-EVENT -0045, Amazon RDS Event Categories and Event Messages. DB instance invalid parameters For example, MySQL could not start because a memory-related parameter is set too high for this instance class, so the customer action would be to modify the memory parameter and reboot the DB instance. Invalid subnet IDs DB instance The DB instance is in an incompati ble network. Some of the speciﬁed subnet IDs are invalid or do not exist. DB instance read replica error An error has occurred in the read replication process. For more information, see the event message. For information on troubleshooting Read Replica errors, see Troublesh ooting a MySQL Read Replica Problem. DB instance read replication ended Replication on the Read Replica was ended. Service event. RDS-EVENT -0057, Amazon RDS Event Categories and Event Messages. Alerts from baseline monitoring in AMS Version May 08, 2025 164 AMS Advanced User Guide AMS Advanced Concepts and Procedures Service Security alert Alert name and trigger condition Notes Service event. RDS-EVENT -0058, Amazon RDS Event Categories and Event Messages. Service event. RDS-EVENT -0066, Amazon RDS Event Categories and Event Messages. Error create statspack user account Error while creating Statspack user account PERFSTAT. Drop the account before adding the Statspack option. DB instance recovery start The SQL Server DB instance is re- establishing its mirror. Performan ce will be degraded until the mirror is
ams-ug-057	ams-ug.pdf	57	RDS Event Categories and Event Messages. Alerts from baseline monitoring in AMS Version May 08, 2025 164 AMS Advanced User Guide AMS Advanced Concepts and Procedures Service Security alert Alert name and trigger condition Notes Service event. RDS-EVENT -0058, Amazon RDS Event Categories and Event Messages. Service event. RDS-EVENT -0066, Amazon RDS Event Categories and Event Messages. Error create statspack user account Error while creating Statspack user account PERFSTAT. Drop the account before adding the Statspack option. DB instance recovery start The SQL Server DB instance is re- establishing its mirror. Performan ce will be degraded until the mirror is reestablished. A database was found with non-FULL recovery model. The recovery model was changed back to FULL and mirroring recovery was started. (<dbname>: <recovery model found>[,…]). A failover for the DB cluster has failed. RDS-EVENT-0069, see details at Amazon RDS Event Categories and Event Messages. Service event. RDS-EVENT -0081, Amazon RDS Event Categories and Event Messages. Invalid permissions recovery S3 bucket The IAM role that you use to access your Amazon S3 bucket for SQL Server native backup and restore is conﬁgured incorrectly. For more information, see Setting Up for Native Backup and Restore. Alerts from baseline monitoring in AMS Version May 08, 2025 165 AMS Advanced User Guide AMS Advanced Concepts and Procedures Service Security alert Alert name and trigger condition Notes Aurora was unable to copy backup data from an Amazon S3 bucket. RDS-EVENT-0082, see details at Amazon RDS Event Categories and Event Messages. Low storage alert when the DB instance has consumed more than RDS-EVENT-0089, see details at Amazon RDS Event Categories 90% of its allocated storage and Event Messages. Notiﬁcation service when scaling failed for the Aurora Serverless DB RDS-EVENT-0143, see details at Amazon RDS Event Categories cluster. and Event Messages. The DB instance is in an invalid state. No actions are necessary. RDS-EVENT-0219, see details at Amazon RDS Event Categories Autoscaling will retry later. and Event Messages. The DB instance has reached the storage-full threshold, and the RDS-EVENT-0221, see details at Amazon RDS Event Categories database has been shut down. and Event Messages. This event indicates the RDS instance storage autoscaling is RDS-EVENT-0223, see details at Amazon RDS Event Categories unable to scale, there could be and Event Messages. multiple reasons for why the autoscaling failed. Storage autoscaling has triggered a pending scale storage task that would reach the maximum storage threshold. The DB instance has a storage type that's currently unavailable in the Availability Zone. Autoscaling will retry later. RDS-EVENT-0224, see details at Amazon RDS Event Categories and Event Messages. RDS-EVENT-0237, see details at Amazon RDS Event Categories and Event Messages. Alerts from baseline monitoring in AMS Version May 08, 2025 166 AMS Advanced User Guide AMS Advanced Concepts and Procedures Service Security alert Alert name and trigger condition Notes RDS couldn't provision capacity for the proxy because there aren't RDS-EVENT-0243, see details at Amazon RDS Event Categories enough IP addresses available in and Event Messages. your subnets. The storage for your AWS account has exceeded the allowed storage RDS-EVENT-0254, see details at Amazon RDS Event Categories and Event Messages. CloudWatch alarm. quota. CPUUtilization Average CPU utilization > 90% for 15 mins, 2 consecutive times. DiskQueueDepth Sum is > 75 for 1 mins, 15 consecuti ve times. FreeStorageSpace Average < 1,073,741,824 bytes for 5 mins, 2 consecutive times. SwapUsage Average >= 104,857,600 bytes for 5 mins, 2 consecutive times. Amazon Redshift cluster No RedshiftClusterStatus 1 represents a healthy cluster. The health of the cluster when not in maintenance mode < 1 for 5 min. Alerts from baseline monitoring in AMS Version May 08, 2025 167 AMS Advanced User Guide AMS Advanced Concepts and Procedures Service Amazon Macie Security alert Yes Alert name and trigger condition Notes Newly generated alerts and updates to existing alerts. Amazon Macie alert. For a list of supported Macie alert types, Macie ﬁnds any changes in the ﬁndings. These changes include newly generated ﬁndings or subsequent occurrences of existing ﬁndings. see Analyzing Amazon Macie Findings. Note that Macie is not enabled for all accounts. AMS takes pro-active actions (scaling the cluster) when this alert is triggered. For information on remediation eﬀorts, see AMS automatic remediation of alerts. Watch Andrew’s video to learn more (7:03) Log retention and rotation defaults This section describes AMS log management defaults; for more information, see Log Management. • Rotation = Log turnover inside the instances • Retention = Period of time we keep the logs in Amazon CloudWatch Logs and Amazon Simple Storage Service (S3) The logs are retained in CloudWatch Logs as needed (you can conﬁgure this), and in S3. They don't expire or get deleted and are subject to service durability. For detailed S3 durability information, see Data protection in Amazon S3. You can request a change to log retention for all logs,
ams-ug-058	ams-ug.pdf	58	to learn more (7:03) Log retention and rotation defaults This section describes AMS log management defaults; for more information, see Log Management. • Rotation = Log turnover inside the instances • Retention = Period of time we keep the logs in Amazon CloudWatch Logs and Amazon Simple Storage Service (S3) The logs are retained in CloudWatch Logs as needed (you can conﬁgure this), and in S3. They don't expire or get deleted and are subject to service durability. For detailed S3 durability information, see Data protection in Amazon S3. You can request a change to log retention for all logs, except AWS CloudTrail logs, which are kept indeﬁnitely for audit and security reasons. Log rotation is conﬁgured inside the instances. By default, operating system and security logs rotate hourly if they reach over 100MB, this is done to ensure that you don't run short on disk in the instances. The log agent inside the instances uploads the log online to CloudWatch Logs, from there the logs are archived to S3. Log retention and rotation defaults Version May 08, 2025 168 AMS Advanced User Guide AMS Advanced Concepts and Procedures The logs are stored in CloudWatch Logs and S3 in the raw format they are generated, there is no pre-processing. Using the AMS consoles The AMS consoles in the AWS Management Console are available for you to interact with AMS and operate your AMS Advanced-managed and AMS Accelerate resources. The AMS consoles generally behave like any AWS console; however, because AMS is a private organization, only accounts enabled for AMS can access the console. Once AMS is enabled in your account, you can access the console by searching for "Managed Services" in the uniﬁed search bar. Note Depending on your account role, you access the AMS Advanced console or the AMS Accelerate console. When using the AMS consoles, be aware of the following caveats: • The AMS console is account speciﬁc. So, if you are in a "Test" account for your organization, you won't be able to see resources in the "Prod" account for that organization. Likewise, you must have an AMS Advanced role to access the AMS Advanced console. • The AMS consoles apply an IAM policy when you authenticate that determines which console you can access and what you can do there. Your administrator may apply additional polices to the default AMS policy to restrict what you can see and do in the console. The AMS Advanced console has these features: • Opening page: The opening page has information boxes and links to facilitate your access to your existing RFCs, incidents, service request, and reports. • Feature pages, links in the left-hand navigation pane: • Dashboard: Provides an overview of the current status of your account including: • Requests for change: See how many RFCs are Awaiting your response, and jump to the RFC list page with that ﬁlter active. See how many RFCs are Awaiting your approval, and jump to the RFC list page with that ﬁlter active. See how many RFCs are Open, and jump to the RFC list page with that ﬁlter active. Open the list page for RFCs by clicking the View all link. Using the AMS consoles Version May 08, 2025 169 AMS Advanced User Guide AMS Advanced Concepts and Procedures • Incidents: See how many incident cases are Awaiting your response, and jump to the incident list page with that ﬁlter active. See and how many are Open, and jump to the incident list page with that ﬁlter active. Open the incident list page by clicking the View all link. • Service requests: See how many service requests are Awaiting your response, and jump to the service request list page with that ﬁlter active. See and how many are Open, and jump to the service request list page with that ﬁlter active. Open the service request list page by clicking the View all link. • Recently updated RFCs: Date, link to the RFC details, and status • Recently created incidents and service requests: Date, link to the case details, and type (incident or service request) • RFCs: Opens a list of the existing RFCs for the account • Incidents: Opens a list of the open incidents for the account • Service requests: Opens a list of the open service requests for the account • Reports: Opens the Reports page and the default reports, Daily Backup and Daily Patch and Monthly Billling • Resources: • VPCs: Opens a list of the existing VPCs for the account • Stacks: Opens a list of existing stacks for the account • AMIs: Opens a list of available AMS AMIs • Feature spotlight: Information on the latest updates to the console • Developer's Resources: A page of downloadable ﬁles, including the AMS Advanced change management SDK and more
ams-ug-059	ams-ug.pdf	59	the open incidents for the account • Service requests: Opens a list of the open service requests for the account • Reports: Opens the Reports page and the default reports, Daily Backup and Daily Patch and Monthly Billling • Resources: • VPCs: Opens a list of the existing VPCs for the account • Stacks: Opens a list of existing stacks for the account • AMIs: Opens a list of available AMS AMIs • Feature spotlight: Information on the latest updates to the console • Developer's Resources: A page of downloadable ﬁles, including the AMS Advanced change management SDK and more • Documentation: The AWS Managed Services documentation landing page Using the AMS API and CLI The AWS Managed Services (AMS) API is similar to the APIs for other AWS services. You can read about the AMS API in the AMS API Reference. AMS API HTTP endpoints for REST calls Besides the various SDKs, AMS provides a CLI; you can also invoke REST API calls against the AMS endpoint. Using the AMS API and CLI Version May 08, 2025 170 AMS Advanced User Guide AMS Advanced Concepts and Procedures There are two AMS APIs (the endpoint for both resides in us-east-1): • Change Management: Use this API to request access to or changes to your infrastructure, including creating and updating RFCs, deploying new instances, updating and deleting instances, getting information on CTs, and creating AMIs. The HTTP endpoint is: https://amscm.us-east-1.amazonaws.com • SKMS: Use this API to get information about your infrastructure, including VPCs, stacks, subnets, and AMIs. The HTTP endpoint is: https://amsskms.us-east-1.amazonaws.com Installing or upgrading the AMS CLI The AMS CLI is an easy way to interact with the AMS API and is used in the examples in this section. For usage conventions for the AWS CLI and AMS CLI, see Using the AWS command Line Interface. For information on installing SAML, see AD FS claim rule and SAML settings. To install or upgrade the AMS CLI, follow these instructions: Note You must have administrator credentials for this procedure. The AWS CLI is a prerequisite for using the AWS Managed Services (AMS) CLIs (Change Management and SKMS). 1. To install the AWS CLI, see Installing the AWS Command Line Interface, and follow the appropriate instructions. Note that at the bottom of that page there are instructions for using diﬀerent installers, Linux, MS Windows, macOS, Virtual Environment, Bundled Installer (Linux, macOS, or Unix). After the installation, run aws help to verify the installation. 2. Once the AWS CLI is installed, to install or upgrade the AMS CLI, download either the AMS AMS CLI or AMS SDK distributables zip ﬁle and unzip. You can access the AMS CLI distributables through the Developer's Resources link in the left nav of the AMS console. 3. The README ﬁle provides instructions for any install. Installing or upgrading the AMS CLI Version May 08, 2025 171 AMS Advanced User Guide Open either: AMS Advanced Concepts and Procedures • CLI zip: Provides the AMS CLI only. • SDK zip: Provides all of the AMS APIs and the AMS CLI. For Windows, run the appropriate installer (only 32 or 64 bits systems): • 32 Bits: ManagedCloudAPI_x86.msi • 64 Bits: ManagedCloudAPI_x64.msi For Mac/Linux, run the ﬁle named: AWSManagedServices_InstallCLI.sh by running this command: sh AWSManagedServices_InstallCLI.sh. Note that the amscm and amsskms directories and their contents must be in the same directory as the AWSManagedServices_InstallCLI.sh ﬁle. 4. If your corporate credentials are used through federation with AWS (the AMS default conﬁguration) you must install a credential management tool that can access your federation service. For example, you can use this AWS Security Blog How to Implement Federated API and CLI Access Using SAML 2.0 and AD FS for help conﬁguring your credential management tooling. 5. After the installation, run aws amscm help and aws amsskms help to see commands and options. 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. Installing or upgrading the AMS CLI Version May 08, 2025 172 AMS Advanced User Guide AMS Advanced Concepts and Procedures Using the AMS API in CLI, Ruby, Python, and Java The following is a list of code snippets for the AMS API ListChangeTypeClassificationSummaries operation, in all available languages. For the Python, Ruby, and Java SDKs, see Tools for Amazon Web Services and scroll down to the SDKs section. Each SDK installer
ams-ug-060	ams-ug.pdf	60	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. Installing or upgrading the AMS CLI Version May 08, 2025 172 AMS Advanced User Guide AMS Advanced Concepts and Procedures Using the AMS API in CLI, Ruby, Python, and Java The following is a list of code snippets for the AMS API ListChangeTypeClassificationSummaries operation, in all available languages. For the Python, Ruby, and Java SDKs, see Tools for Amazon Web Services and scroll down to the SDKs section. Each SDK installer contains a README with additional code snippets. AMS API to CLI example After you have installed the AMS CLI (requires the AWS CLI; see Installing or upgrading the AMS CLI), you can run any AMS API operation by reforming the call ﬁrst specifying which AMS API, aws amscm or aws amsskms, and then giving the action with hyphens replacing camel case. Finally, provide credentials, such as SAML. To learn more, see Using the AWS Command Line Interface. Example: • API: 'ChangeTypeClassificationSummaries[]. [Category,Subcategory,Item,Operation,ChangeTypeId]' • CLI: amscm list-change-type-classification-summaries --query "ChangeTypeClassificationSummaries[]. [Category,Subcategory,Item,Operation,ChangeTypeId]" --output table Note If you authenticate with SAML, add aws --profile saml to the beginning of the command. For example, aws --profile saml amscm list-change-type-classification- summaries --query "ChangeTypeClassificationSummaries[]. [Category,Subcategory,Item,Operation,ChangeTypeId]" --output table AMS API to Python example In order to use the AMS API with Python, install the AMS CLI and install boto3. Follow these steps: Using the AMS API in CLI, Ruby, Python, and Java Version May 08, 2025 173 AMS Advanced User Guide AMS Advanced Concepts and Procedures 1. 2. Install the AMS CLI. See Installing or upgrading the AMS CLI. Install boto3, the AWS SDK for Python. For more information, see this blog post Now Available – AWS SDK For Python (Boto3). import boto3 3. Get the AMS Change Management client: cm = boto3.client('amscm') 4. Get the AMS CTs: cts = cm.list_change_type_classification_summaries() print(cts) Python examples The following are some examples for using Python in AMS, to create EC2 instances, and/or use Lambda. Python example to create an EC2 This example shows how you can use the amscm RESTFul API from within Python code to ﬁle and perform RFC processes. 1. Install the AMS CLI somewhere you have access to; you need the ﬁles it supplies. 2. Call Python libraries and create the EC2 instance: import boto3 import json import time # Create the amscm client cm = boto3.client('amscm') # Define the execution parameters for EC2 Create AMSExecParams = { "Description": "EC2-Create", "VpcId": "VPC_ID", "Name": "My-EC2", "TimeoutInMinutes": 60, Using the AMS API in CLI, Ruby, Python, and Java Version May 08, 2025 174 AMS Advanced User Guide AMS Advanced Concepts and Procedures "Parameters": { "InstanceAmiId": "INSTANCE_ID", "InstanceSubnetId": "SUBNET_ID" } } # Create the AMS RFC cts = cm.create_rfc( ChangeTypeId="ct-14027q0sjyt1h", ChangeTypeVersion="3.0", Title="Python Code RFC Create", ExecutionParameters=json.dumps(AMSExecParams) ) # Extract the RFC ID from the response NewRfcID = cts['RfcId'] # Submit the RFC RFC_Submit_Return=cm.submit_rfc(RfcId=NewRfcID) # Check the RFC status every 30 seconds RFC_Status = cm.get_rfc(RfcId=NewRfcID) RFC_Status_Code = RFC_Status['Rfc']['Status']['Name'] while RFC_Status_Code != "Success": if RFC_Status_Code == "PendingApproval": print(RFC_Status_Code) time.sleep(30) elif RFC_Status_Code == "InProgress": print(RFC_Status_Code) time.sleep(30) elif RFC_Status_Code == "Failure": print(RFC_Status_Code) break else: print(RFC_Status_Code) RFC_Status = cm.get_rfc(RfcId=NewRfcID) RFC_Status_Code = RFC_Status['Rfc']['Status']['Name'] Using the AMS API in CLI, Ruby, Python, and Java Version May 08, 2025 175 AMS Advanced User Guide AMS Advanced Concepts and Procedures Python example with Lambda This example shows how to bundle the AMS models with your code so you can use it with Lambda, or EC2; places you won't, or can't, install amscli. Note AMS does not provide an importable AMS-speciﬁc Python SDK. The amscli install script installs the AMS service data models in the CLI’s normal path. For CLI usage and system Python usage, that is ﬁne, because both awscli and boto3 read their service models from the same default locations (~/.aws/models). However, when you want to use AMS services via boto3 in Lambda (or any other non-local runtime), it breaks, because you no longer have the data models. The following is a method to ﬁx this by packaging the data models with the function. There are simple steps that you can take to run your AMS-integrated Python code in Lambda or another runtime like EC2, Fargate, etc. The following workﬂow shows the steps necessary for AMS- integrated Lambda functions. By adding the data models to the code's deployment package and updating the SDK search path, you can simulate an SDK experience. Important This example and all of the non-python commands shown were tested on a Mac computer. Example Workﬂow: 1. Install the amscli. This creates a folder at ~/.aws/models on your computer (Mac). 2. Copy the models to a local directory: cp ~/.aws/models ./models. 3. Include the models into your code's deployment package. 4. Update your function code to
ams-ug-061	ams-ug.pdf	61	Lambda or another runtime like EC2, Fargate, etc. The following workﬂow shows the steps necessary for AMS- integrated Lambda functions. By adding the data models to the code's deployment package and updating the SDK search path, you can simulate an SDK experience. Important This example and all of the non-python commands shown were tested on a Mac computer. Example Workﬂow: 1. Install the amscli. This creates a folder at ~/.aws/models on your computer (Mac). 2. Copy the models to a local directory: cp ~/.aws/models ./models. 3. Include the models into your code's deployment package. 4. Update your function code to add the new models to the SDK path. Note that this code must run before boto3 or botocore are imported! # Force Python to search local directory for boto3 data models Using the AMS API in CLI, Ruby, Python, and Java Version May 08, 2025 176 AMS Advanced User Guide import os os.environ['AWS_DATA_PATH'] = './models' AMS Advanced Concepts and Procedures import boto3 import botocore Note Because the example models are in a directory named models, we add ./models to AWS_DATA_PATH. If the directory was named /ams/boto3models, we would add the following code: import os.environ['AWS_DATA_PATH'] = './ams/boto3models' import boto3 import botocore Your code should successfully ﬁnd the AMS models. As a more speciﬁc example re: packaging, here's the Lambda speciﬁc workﬂow. Example AMS Lambda Workﬂow: These steps apply the preceding generic example to creating an AWS Lambda function. 1. Install the amscli. This creates a folder at ~/.aws/models on your computer (Mac). 2. Copy the models to a local directory: cp ~/.aws/models ./models 3. Add the models to your function's deployment zip ﬁle: zip -r9 function.zip ./models Important Update your function code to add the new models to the SDK path. Note that this code must run before boto3 or botocore are imported! Using the AMS API in CLI, Ruby, Python, and Java Version May 08, 2025 177 AMS Advanced User Guide AMS Advanced Concepts and Procedures # Force Python to search local directory for boto3 data models import os os.environ['AWS_DATA_PATH'] = './models' import boto3 import botocore Note Because the example models are in a directory named models, We add ./models to AWS_DATA_PATH. If the directory was named /ams/boto3models, we would add the following code: import os os.environ['AWS_DATA_PATH'] = './ams/boto3models' import boto3 import botocore Now, deploy your function: 1. Add your function code to the deployment zip ﬁle (if you haven't done so already): zip -g function.zip lambda-amscm-test.py 2. Create or update your function with the zip ﬁle you created (console or CLI): aws lambda update-function-code --function-name lambda-amscm-test --zip-file fileb:// function.zip --region us-east-1 Your AMS-integrated Python Lambda should now work. Note Your function must have IAM permissions for amscm or you get a permissions error. Using the AMS API in CLI, Ruby, Python, and Java Version May 08, 2025 178 AMS Advanced User Guide AMS Advanced Concepts and Procedures Sample Lambda function code to test amscm (contents of lambda-amscm-test.py): import json # Force lambda to search local directory for boto3 data models import os os.environ['AWS_DATA_PATH'] = './models' import boto3 import botocore def lambda_handler(event, context): use_session = boto3.session.Session(region_name="us-east-1") try: cm = use_session.client("amscm") cts = cm.list_change_type_categories() print(cts) except botocore.exceptions.UnknownServiceError: print("amscm not found") return { 'statusCode': 200, 'body': json.dumps('Hello from Lambda!') } Test outputs (success): Function Response: { "statusCode": 200, "body": "\"Hello from Lambda!\"" } Request ID: "1cea13c0-ed46-43b1-b102-a8ea28529c27" Function Logs: START RequestId: 1cea13c0-ed46-43b1-b102-a8ea28529c27 Version: $LATEST {'ChangeTypeCategories': ['Deployment', 'Internal Infrastructure Management', 'Management'], 'ResponseMetadata': {'RequestId': 'e27276a0-e081-408d- Using the AMS API in CLI, Ruby, Python, and Java Version May 08, 2025 179 AMS Advanced User Guide AMS Advanced Concepts and Procedures bcc2-10cf0aa19ece', 'HTTPStatusCode': 200, 'HTTPHeaders': {'x-amzn-requestid': 'e27276a0-e081-408d-bcc2-10cf0aa19ece', 'content-type': 'application/x-amz-json-1.1', 'content-length': '89', 'date': 'Sun, 10 May 2020 23:21:19 GMT'}, 'RetryAttempts': 0}} END RequestId: 1cea13c0-ed46-43b1-b102-a8ea28529c27 AMS API to Ruby example In order to use the AMS API with Ruby, install the AWS Ruby SDK and AMS CLI. Follow these steps: 1. 2. Install the AMS CLI. See Installing or upgrading the AMS CLI. Install the AWS Ruby SDK. See Tools for Amazon Web Services. 3. Conﬁgure Ruby with these commands: require 'aws-sdk' config = { region: 'us-east-1', credentials: Aws::Credentials.new('ACCESS_KEY','SECRET_KEY')} 4. Get the AMS CTs: ams_cm = Aws::amscm::Client.new(config) cts = ams_cm.list_change_type_classification_summaries print(cts) AMS API to Java example In order to use the AMS API with Java, install the AWS Java SDK and AMS CLI. Follow these steps: 1. 2. Install the AMS CLI. See Installing or upgrading the AMS CLI. Install the AWS Java SDK. See Tools for Amazon Web Services. 3. Conﬁgure Java with these commands: import com.amazonaws.auth.BasicAWSCredentials; import com.amazonaws.services.amscm.model.AWSManagedServicesCMClient; Using the AMS API in CLI, Ruby, Python, and Java Version May 08, 2025 180 AMS Advanced User Guide import AMS Advanced Concepts and Procedures com.amazonaws.services.amscm.model.ListChangeTypeClassificationSummariesRequest; import com.amazonaws.services.amscm.model.ListChangeTypeClassificationSummariesResult; public static void getChangeTypeClassificationSummaries() { 4. Set the credentials. We recommend that you do not hardcode this. final BasicAWSCredentials awsCredsCm =
ams-ug-062	ams-ug.pdf	62	use the AMS API with Java, install the AWS Java SDK and AMS CLI. Follow these steps: 1. 2. Install the AMS CLI. See Installing or upgrading the AMS CLI. Install the AWS Java SDK. See Tools for Amazon Web Services. 3. Conﬁgure Java with these commands: import com.amazonaws.auth.BasicAWSCredentials; import com.amazonaws.services.amscm.model.AWSManagedServicesCMClient; Using the AMS API in CLI, Ruby, Python, and Java Version May 08, 2025 180 AMS Advanced User Guide import AMS Advanced Concepts and Procedures com.amazonaws.services.amscm.model.ListChangeTypeClassificationSummariesRequest; import com.amazonaws.services.amscm.model.ListChangeTypeClassificationSummariesResult; public static void getChangeTypeClassificationSummaries() { 4. Set the credentials. We recommend that you do not hardcode this. final BasicAWSCredentials awsCredsCm = new BasicAWSCredentials("ACCESS_KEY", "SECRET_KEY"); 5. Create the AMS Change Management client: final AWSManagedServicesCMClient cmClient = new AWSManagedServicesCMClient(awsCredsCm); 6. Get the AMS CTs: final ListChangeTypeClassificationSummariesRequest listCtsRequest = new ListChangeTypeClassification SummariesRequest(); final ListChangeTypeClassificationSummariesResult listCtsResult = cmClient.listChangeTypeClassificationSummaries(listCtsRequest); System.out.println("List of CTs"); listCtsResult.getChangeTypeClassificationSummaries().stream() .map(x -> x.getCategory() + "/" + x.getSubcategory() + "/" + x.getItem() + "/" + x.getOperation()) .forEach(System.out::println); } Using the AMS API in CLI, Ruby, Python, and Java Version May 08, 2025 181 AMS Advanced User Guide AMS Advanced Concepts and Procedures AMS bring your own EPS Use the AMS "bring your own end point security" (BYOEPS) feature to replace the default Trend Micro Deep Security agent with your own end point security solution, or Trend Micro license. If you already have cost eﬀective licenses for products other than Trend Micro Deep Security, or a team that provides your EPS, or if you want to use a speciﬁc EPS tool, then use BYOEPS in your instances. BYOEPS works at the account level. Your instances in the account either use BYOEPS or the default, AMS-managed EPS: • multi-account landing zone (MALZ): You designate application accounts that use BYOEPS or managed EPS. • single-account landing zone (SALZ): Your AMS accounts use BYOEPS or managed EPS. BYOEPS, reduces your AWS bill by the cost for Trend Micro Deep Security. You continue to incur a cost for EPS because the AMS-managed EPS is still required to protect AMS-created and maintained EC2 instances that are required for access management (bastions, and management hosts). To calculate the total cost impact, you must account for the cost of licenses for your new tool, and the cost of managing EPS at the service levels that you need. The use of BYOEPS changes the AMS roles and responsibilities for security management: • R stands for responsible party that does the work to achieve the task. • C stands for consulted; a party whose opinions are sought, typically as subject matter experts; and with whom there is bilateral communication. • I stands for informed; a party which is informed on progress, often only on completion of the task or deliverable. Security management Customer AWS Managed Services Maintaining valid licenses of Managed EPS for EC2 instances of AMS Shared Services R C AMS bring your own EPS Version May 08, 2025 182 AMS Advanced User Guide AMS Advanced Concepts and Procedures Security management Customer AWS Managed Services Conﬁgure Managed EPS for EC2 instances of AMS Shared Services Update Managed EPS for EC2 instances of AMS Shared Services Monitoring malware on EC2 instances of AMS Shared Services Maintaining and updating virus signatures for EC2 instances of AMS Shared Services I I I I Remediating instances infected with malware for C EC2 instances of AMS Shared Services R R R R R When you use BYOEPS, you lose one of the security controls oﬀered by AMS. You still have security management provided through tools such as Amazon GuardDuty, Amazon Macie, and process controls, such as reviews of IAM conﬁgurations. The use of BYOEPS doesn't aﬀect AMS compliance certiﬁcations and attestations. However, many security framework and certiﬁcations have requirements for protection from malware and malicious code. To help keep your account secure and in compliance, evaluate your planned controls to make sure that they meet the security requirements for your workload's compliance certiﬁcations. Turn on BYOEPS for your account The process to turn on BYOEPS contains three stages and uses several RFCs. Review the following information to learn about the three stages required to turn on BYOEPS. Then, coordinate with your CSDM to turn on BYOEPS for your account. Turn on BYOEPS for your account Version May 08, 2025 183 AMS Advanced Concepts and Procedures AMS Advanced User Guide Topics • Stage 1: Prerequisites • Stage 2: Enable BYOEPS in your account • Stage 3: Instance migration Stage 1: Prerequisites • The default Amazon EC2 instance proﬁle is customer-mc-ec2-instance-profile. If you use a diﬀerent Amazon EC2 instance proﬁle in addition to the default proﬁle, then allow the ssm:GetParameter action for the /ams/end-point-security resource to your EC2 instance proﬁle. If you can't update EC2 instance proﬁles, then submit an RFC that speciﬁes the instance proﬁles that you need to update. • Understand the scope of this change. Deployments through
ams-ug-063	ams-ug.pdf	63	2025 183 AMS Advanced Concepts and Procedures AMS Advanced User Guide Topics • Stage 1: Prerequisites • Stage 2: Enable BYOEPS in your account • Stage 3: Instance migration Stage 1: Prerequisites • The default Amazon EC2 instance proﬁle is customer-mc-ec2-instance-profile. If you use a diﬀerent Amazon EC2 instance proﬁle in addition to the default proﬁle, then allow the ssm:GetParameter action for the /ams/end-point-security resource to your EC2 instance proﬁle. If you can't update EC2 instance proﬁles, then submit an RFC that speciﬁes the instance proﬁles that you need to update. • Understand the scope of this change. Deployments through an AMS automated change type (CT) allow you to specify the AMI used in creation. To use BYOEPS with accounts that use AMS-managed EPS, you must work with AMS to uninstall the Trend Micro agents from those EC2 instances, and to update the AMS code (for example, boot scripts) on those instances. These actions might require a reboot, so it's a best practice to perform these actions as part of a maintenance window. Contact your CSDM to identify a maintenance window to perform this activity and to create a migration plan. For the migration plan, consider the following questions: 1. How many instances do you need to migrate? Divide the total number of instances into smaller, incremental batches. 2. How will you divide the instances in batches? For example, you might divide by resource groups and create a list to share with the AMS operations team. 3. How much time will each batch take? How much total time is required? Consider that you might want to install your preferred EPS tooling in the same maintenance window. How much time will this take? • Your CSDM shares the migration plan with the AMS operations team. If your instance ﬂeet is above 50, then work with your CSDM to create a planned event using the planned event management (PEM) process. For more information, see Planned event management in AWS Managed Services Turn on BYOEPS for your account Version May 08, 2025 184 AMS Advanced User Guide AMS Advanced Concepts and Procedures AMS Operations coordinates with your CSDM and advises how to submit RFCs in accordance with your maintenance windows, based upon the number of instances in your account. • Update EC2 instance launch automations or processes using custom or AMS AMIs to use AMS AMIs released after December 2020. Stage 2: Enable BYOEPS in your account When you use BYOEPS in your account, the responsibilities that AMS has for security management changes. Consult your security and cloud platform team before you enable BYOEPS. To request BYOEPS for your account, submit a "MOO" update RFC (Management \| Other \| Other \| Update) with ct-0xdawir96cy7k, with the following details: Please enable BYOEPS for this account/these accounts Account IDs: IDs for the accounts for BYOEPS. AMS deploys parameter store updates to the account and updates the Amazon EC2 IAM instance proﬁle. Note • Accounts with new instance launches that use the latest AMS AMIs can skip Trend Micro agent installation. AMIs older than December 2020 don't support the BYOEPS feature. Update automations that use old AMIs to use the latest AMS AMIs with BYOEPS feature support. • For existing EC2 instance handling, see Stage 3: Instance migrations Stage 3: Instance migration Use one of the following options to migrate your instances, depending on your use case. If you are unsure of which option to choose, contact your CA or CSDM. Accounts with EC2 instances that use AMS-managed EPS During the maintenance window, in alignment with planning from Stage 1, the following actions are performed on each instance that needs to be onboarded to BYOEPS: Turn on BYOEPS for your account Version May 08, 2025 185 AMS Advanced User Guide AMS Advanced Concepts and Procedures • Performed by AMS: Update AMS code (boot scripts, modules, and so on) to the latest versions. This is required because old AMS boot scripts don't have BYOEPS feature support and re-install Trend Micro agent on every boot. Also, uninstall the Trend Micro Agent. • Performed by you: Install and conﬁgure your preferred EPS tool. Important Trend Micro Agent provides malware protection. Make sure that you install an appropriate replacement to secure your instances. To make these changes submit RFCs with change type ct-2iz9nvw8zlhst, Trend Micro DSM \| Remove Trend Micro EPS Agent (Review Required), in batches. Accounts without EC2 instances that use AMS-managed EPS Accounts with new instance launches that use the latest AMS AMIs can skip Trend Micro agent installation. AMIs older than December 2020 don't support the BYOEPS feature. Update automations that use old AMIs to use the latest AMS AMIs with BYOEPS feature support. Add your agent on EC2 instances You can use AMS Patterns to deploy agents of tools such as CrowdStrike or Qualys, Submit a
ams-ug-064	ams-ug.pdf	64	secure your instances. To make these changes submit RFCs with change type ct-2iz9nvw8zlhst, Trend Micro DSM \| Remove Trend Micro EPS Agent (Review Required), in batches. Accounts without EC2 instances that use AMS-managed EPS Accounts with new instance launches that use the latest AMS AMIs can skip Trend Micro agent installation. AMIs older than December 2020 don't support the BYOEPS feature. Update automations that use old AMIs to use the latest AMS AMIs with BYOEPS feature support. Add your agent on EC2 instances You can use AMS Patterns to deploy agents of tools such as CrowdStrike or Qualys, Submit a service request for assistance. Receiving AMS notiﬁcations Communications between you and AMS occur for many reasons: • An RFC created by AMS that requires your approval • An AMS case created to investigate an RFC you created that has failed • Events created by monitoring alerts • Patching service notiﬁcations that inform you of upcoming patching • Service requests and incident reports • Monthly CRM reports • Occasional important AWS announcements (your CSDM contacts you if any action on your part is required) Receiving AMS notiﬁcations Version May 08, 2025 186 AMS Advanced User Guide AMS Advanced Concepts and Procedures All of these notiﬁcations are sent to the default contact information (the root account email) that you provided AMS when you were onboarded. Because it's diﬃcult to keep individual emails updated, we recommend that you use a group email that can be updated on your end. All notiﬁcations sent to you are also received by AMS operations and analyzed before making a response. AMS notiﬁcation service provides two additional ways to set up contacts for notiﬁcations: • Tag your resources with contact tags (the tag Key Value being contact information) and provide the tag Key Name to your CSDM. Alarms on those resources will be sent to the contacts provided in the Key Value, in addition to the account contact created at onboarding. This is especially useful for application owners. For more information, see Tag-based alert notiﬁcation. • (Required at onboarding) Send to your CSDM named lists of contacts for non-resource based notiﬁcations. For example, you might have a list named "SecurityContacts" and another named "OperationsContacts", and so forth. AMS adds the list to the notiﬁcation service, and alarms that apply to that list's context are sent to those contacts. This is especially useful for organizational matters. This advanced alert routing feature is active for most of the essential CloudWatch alarms such as Amazon EC2 instance failure, Amazon Elastic Block Store (Amazon EBS) volume capacity utilization - Root usage, Amazon EBS NonRoot usage, High Memory utilization, High Swap usage, and High CPU utilization for Amazon EC2. Additionally, when you ﬁle a service request, or incident report, you have the option of adding "CC Emails" (highly recommended) and those email addresses receive notiﬁcations about the service request or incident. Important While the CC email addresses provided in service requests and incident reports receive email notiﬁcations of communications, other notiﬁcations, such as patching notiﬁcations, appear in your Service Request list (an email is also sent to the default contact), without explicit notiﬁcation to you that you have a communication awaiting your attention. This is why we strongly recommend adding a CC email where you can, and setting up the default contact email as a group to which everyone using AMS is a member. Receiving AMS notiﬁcations Version May 08, 2025 187 AMS Advanced User Guide AMS Advanced Concepts and Procedures Additionally, you can request special notiﬁcations for new AMIs, for RFC state change, and for conﬁguration changes in your AMS account. These optional notiﬁcation services are discussed next. AMS AMI notiﬁcations with SNS AMS provides an AMI notiﬁcation service. You can use it to subscribe to an Amazon Simple Notiﬁcation Service (SNS) topic that notiﬁes you when AMS AMI updates have been released. You can choose to receive notiﬁcations for only the AMS AMIs you use, or you can sign up to receive update notiﬁcations for all AMS AMIs. For more information on SNS topics, see What is Amazon Simple Notiﬁcation Service? Whenever AMIs are released, we send notiﬁcations to the subscribers of the corresponding topic; this section describes how to subscribe to the AMS AMI notiﬁcations. Sample message { "Type" : "Notification", "MessageId" : "example messageId", "TopicArn" : "arn:aws:sns:us-east-1:591688410472:customer-ams-windows2019", "Subject" : "New AMS AMIs are Now Available", "Message" : "{"v1": {"Message": "A new version of the AMS Amazon Machine Images has been released. You are now able to launch new EC2 stacks from these AMIs. Please use this time to update any dependencies such as CloudFormation or Autoscaling groups. Release Notes Windows - Contains latest Windows Patches: Microsoft Windows Server 2008 R2 Datacenter - (KB2819745, KB3018238, KB4507004, KB4507437) Microsoft Windows Server 2016 Datacenter Security Enhancedn - (KB4509091, KB4507459) Microsoft Windows Server
ams-ug-065	ams-ug.pdf	65	to the AMS AMI notiﬁcations. Sample message { "Type" : "Notification", "MessageId" : "example messageId", "TopicArn" : "arn:aws:sns:us-east-1:591688410472:customer-ams-windows2019", "Subject" : "New AMS AMIs are Now Available", "Message" : "{"v1": {"Message": "A new version of the AMS Amazon Machine Images has been released. You are now able to launch new EC2 stacks from these AMIs. Please use this time to update any dependencies such as CloudFormation or Autoscaling groups. Release Notes Windows - Contains latest Windows Patches: Microsoft Windows Server 2008 R2 Datacenter - (KB2819745, KB3018238, KB4507004, KB4507437) Microsoft Windows Server 2016 Datacenter Security Enhancedn - (KB4509091, KB4507459) Microsoft Windows Server 2016 Datacentern - (KB4509091, KB4507459) Microsoft Windows Server 2012 R2 Security Enhancedn - (KB3191564, KB3003057, KB3013172, KB3185319, KB4504418, KB4506996, KB4507463) Microsoft Windows Server 2012 R2 Standardn - (KB3003057, KB3013172, KB3185319, KB4504418, KB4506996, KB4507463) Linux - Contains latest Linux patches - All AMIs now force domainjoin-cli leave before domainjoin-cli join for better stability in the domain join process.", "images": {"images": {"image_name": "customer-ams-windows2019-2021.08-1", "image_id": "ami-05dfa45396fddaa5e"}}, "region": "us-east-1"}}", "Timestamp" : "2021-09-03T19:05:57.882Z", "SignatureVersion" : "1", "Signature" : "example sig", "SigningCertURL" : "example url", AMS AMI notiﬁcations with SNS Version May 08, 2025 188 AMS Advanced User Guide AMS Advanced Concepts and Procedures "UnsubscribeURL" : "example url" } Possible AMS AMI topics to subscribe to: • ALL: Use customer-ams-all-amis. This topic subscription notiﬁes you when any of the AMS AMIs are updated. • AMS AWS Linux AMIs: For Amazon Linux, use customer-ams-amazon1 and customer-ams- amazon1-security-enhanced. For Amazon Linux 2, use customer-ams-amazon2 and customer-ams-amazon2-security-enhanced. • AMS SUSE Linux AMIs: Use customer-ams-sles12 or customer-ams-sles15. • AMS AWS RedHat AMIs: Use customer-ams-rhel8, customer-ams-rhel8-security- enhanced, customer-ams-rhel7, customer-ams-rhel7-security-enhanced. • AMS AWS CentOs AMIs: Use customer-ams-centos7, customer-ams-centos7-security- enhanced. • AMS Ubuntu AMIs: Use customer-ams-ubuntu18. • AMS AWS Windows AMIs: Use customer-ams-windows2019, customer-ams- windows2019-security-enhanced, customer-ams-windows2016, customer-ams- windows2016-security-enhanced, customer-ams-windows2012, customer-ams- windows2012r2, customer-ams-windows2012r2-security-enhanced, customer-ams- windows2022. To subscribe to AMS new AMI notiﬁcations by using the Amazon SNS console: 1. Open the Amazon SNS console to the Dashboard. 2. 3. In the upper-right corner, change to the AWS Region for the AMIs that you are subscribing to. In the left-navigation pane, choose Subscriptions, and then choose Create subscription. 4. Provide the following information: a. Topic ARN: arn:aws:sns:{REGION}:287847593866:{AMS_AMI_NAME} where REGION is the selected AWS Region (where the SNS notiﬁcation was created) and AMS_AMI_NAME is the AMI that you want notiﬁcations about. Examples: • To subscribe to notiﬁcations of new AMS Amazon Linux AMIs in AWS Region us-east-1, use this Topic ARN = arn:aws:sns:us-east-1:287847593866:customer-ams- amazon1. AMS AMI notiﬁcations with SNS Version May 08, 2025 189 AMS Advanced User Guide AMS Advanced Concepts and Procedures • To subscribe to notiﬁcations of new AMS Window Server 2016 AMIs in AWS Region us- west-2, use this Topic ARN = arn:aws:sns:us-west-2:287847593866:customer- b. c. ams-windows2016 For Protocol, choose Email. For Endpoint, enter an email address that you can use to receive the notiﬁcations. We recommend a distribution list rather than an individual's email. 5. Choose Create subscription. 6. When you receive a conﬁrmation email with the subject line "AWS Notiﬁcation - Subscription Conﬁrmation," open the email and choose Conﬁrm subscription to complete your subscription. Note You are not limited to email for the Protocol. For information on other acceptable protocols and how to use them, see subscribe. To unsubscribe from AMS new AMI notiﬁcations by using the AWS SNS console: 1. Open the Amazon SNS console to the Dashboard. 2. In the navigation bar, change to the AWS Region of your choice. You must use the AWS Region in which you want to receive notiﬁcations for the corresponding AMIs. 3. In the navigation pane, choose Subscriptions, select the subscription, and then choose Actions -> Delete subscriptions. 4. When prompted for conﬁrmation, choose Delete. To subscribe to AMS New AMI notiﬁcations using the Deployment \| Ingestion \| Stack from CloudFormation Template \| Create (ct-36cn2avfrrj9v): 1. To subscribe to the AmazonLinuxSubscription, create and save an execution parameters JSON ﬁle; this example names it CreateSubscribeAmiParams.json: { "AWSTemplateFormatVersion": "2010-09-09", "Resources": { "AmazonLinuxSubscription":{ AMS AMI notiﬁcations with SNS Version May 08, 2025 190 AMS Advanced User Guide AMS Advanced Concepts and Procedures "Type" : "AWS::SNS::Subscription", "Properties": { "TopicArn": "arn:aws:sns:{REGION}:287847593866:{AMS_AMI_NAME}", "Protocol": "email", "Endpoint": "username@yourdomain.com" } } } } 2. Create and save the RFC parameters JSON ﬁle with the following content; this example names it CreateSubscribeAmiRfc.json ﬁle: { "ChangeTypeId": "ct-36cn2avfrrj9v", "ChangeTypeVersion": "1.0", "Title": "cfn-ingest-subscribe-ami" } 3. Create the RFC, specifying the CreateSubscribeAmiRfc ﬁle and the CreateSubscribeAmiParams ﬁle: aws amscm create-rfc --cli-input-json file://CreateSubscribeAmiRfc.json -- execution-parameters file://CreateSubscribeAmiParams.json You receive the ID of the new RFC in the response and can use it to submit and monitor the RFC. Until you submit it, the RFC remains in the editing state and does not start. For examples of creating AMIs, see Create AMI. For information on consuming AMIs programmatically, see EC2 stack: creating. Service notiﬁcations AMS sends outbound service requests, or service
ams-ug-066	ams-ug.pdf	66	the following content; this example names it CreateSubscribeAmiRfc.json ﬁle: { "ChangeTypeId": "ct-36cn2avfrrj9v", "ChangeTypeVersion": "1.0", "Title": "cfn-ingest-subscribe-ami" } 3. Create the RFC, specifying the CreateSubscribeAmiRfc ﬁle and the CreateSubscribeAmiParams ﬁle: aws amscm create-rfc --cli-input-json file://CreateSubscribeAmiRfc.json -- execution-parameters file://CreateSubscribeAmiParams.json You receive the ID of the new RFC in the response and can use it to submit and monitor the RFC. Until you submit it, the RFC remains in the editing state and does not start. For examples of creating AMIs, see Create AMI. For information on consuming AMIs programmatically, see EC2 stack: creating. Service notiﬁcations AMS sends outbound service requests, or service notiﬁcations, when you need to act on, or be aware of, something that might impact your account or resources, including: • Infrastructure impact: AMS sends a service notiﬁcation when there is an underlying AWS service impacting your infrastructure, and you need to take action before a certain date, or you may have an outage. Service notiﬁcations Version May 08, 2025 191 AMS Advanced User Guide AMS Advanced Concepts and Procedures • EC2 Hardware issues: AMS sends service notiﬁcations out for EC2 hardware issues that require you to reboot an EC2 instance before a certain date, or letting you know that AMS will reboot the instance for you. This is an important notice because reboot can cause an outage and you must respond with an acceptable date, or create an RFC with ct-09qbhy7kvtxqw, to reboot the instance yourself. A service notiﬁcation like this automatically closes in ﬁve days if you do not respond. RFC state change notiﬁcations AMS oﬀers notiﬁcations for RFC state changes by email and CloudWatch Events: • Emails by way of the AMS Console: There is an option on the second page of the Create RFC wizard, where you can add up to ﬁve email addresses to be notiﬁed when that RFC state changes. • CloudWatch Events: You can conﬁgure diﬀerent rules and targets for CloudWatch Events to receive notiﬁcations for every RFC state change. Email notiﬁcations You can add email addresses to receive RFC state changes to an RFC that you create in the AMS console, or by using the AMS API/CLI. In the AMS console, use the Email notiﬁcations option, on the second page of the Create RFC wizard: RFC state change notiﬁcations Version May 08, 2025 192 AMS Advanced User Guide AMS Advanced Concepts and Procedures In the AMS API/CLI, add a line like this to the RFC parameters section of your RFC (do not add the line to the run parameters section): --notification "{\"Email\": {\"EmailRecipients\" : [\"email@example.com\"]}}" The behavior of the notiﬁcations varies depending the RFC scheduling type: • Scheduled RFCs receive email notiﬁcations on : Submitted, Scheduled, InProgress, Completed, Rejected, Canceled, Auto-Rejected, or Auto-Canceled. • ASAP RFCs receive email notiﬁcation on: Submitted, InProgress, Completed, Rejected, Canceled, AutoRejected, or Auto-Canceled. Note • Email notiﬁcations are sent from this address: no- reply@managedservices.amazonaws.com. • Special characters and URLs in your RFC title are redacted in the emails we send. This is a security measure. RFC state change notiﬁcations Version May 08, 2025 193 AMS Advanced User Guide AMS Advanced Concepts and Procedures CloudWatch Events notiﬁcations AMS oﬀers push notiﬁcations for the RFC State changes through CloudWatch Events. To get these notiﬁcations: 1. Create a topic and subscription where notiﬁcations will be sent. You can name the topic what you like; for information about doing this, see SNS Topic and Subscription: Creating. 2. Submit an RFC with the Management \| Other \| Other \| Create change type and include the SNS topic and subscription in the request for RFC state change notices. When you submit the Management \| Other \| Other RFC request for this feature, you can specify what RFC state changes you're interested in getting notiﬁed about and what change types, and set other ﬁlters. For example, you may want to request to be notiﬁed only when Admin Access change types are EventType = RfcSubmitted and EventType = RfcUpdated. This is a template of CloudWatch event notiﬁcations that you can receive (with all possible values): { "source ": "aws.managedservices", "detail-type": "AMS RFC State Change", "detail": { "ActionState": "null \| AwsActionPending \| AwsOperatorAssigned \| CustomerActionPending \| NotApplicable \| NoActionPending", "ActualExecutionTimeRange": { "StartTime": "null \| Actual Start Time", "EndTime": "null \| Actual End Time" }, "AutomationStatus": "Automated \| Manual", "AwsAccountId": "AWS Account ID", "AwsApprovalStatus": "null \| SubmissionPending \| NotRequired \| ApprovalPending \| Rejected \| Approved", "ChangeTypeId": "Change_Type_ID", "ChangeTypeVersion": "Change_Type_Version", "CreatedTime": "Created_Time", "CustomerApprovalStatus": "null \| SubmissionPending \| NotRequired \| ApprovalPending \| Rejected \| Approved", "EventType": "RfcActionStateUpdated \| RfcApproved \| RfcAutoRejected \| RfcCanceled \| RfcCompleted \| RfcCreated \| RfcInProgress \| RfcRejected \| RfcSubmitted \| RfcUpdated", "LastModifiedTime": "Last_Updated_Time", "LastSubmittedTime": "null \| Last_Submitted_Time", RFC state change notiﬁcations Version May 08, 2025 194 AMS Advanced User Guide AMS Advanced Concepts and Procedures "RequestedExecutionTimeRange": { "StartTime": "null \| Expected_Start_Time", "EndTime": "null \| Expected_End_Time"
ams-ug-067	ams-ug.pdf	67	Time", "EndTime": "null \| Actual End Time" }, "AutomationStatus": "Automated \| Manual", "AwsAccountId": "AWS Account ID", "AwsApprovalStatus": "null \| SubmissionPending \| NotRequired \| ApprovalPending \| Rejected \| Approved", "ChangeTypeId": "Change_Type_ID", "ChangeTypeVersion": "Change_Type_Version", "CreatedTime": "Created_Time", "CustomerApprovalStatus": "null \| SubmissionPending \| NotRequired \| ApprovalPending \| Rejected \| Approved", "EventType": "RfcActionStateUpdated \| RfcApproved \| RfcAutoRejected \| RfcCanceled \| RfcCompleted \| RfcCreated \| RfcInProgress \| RfcRejected \| RfcSubmitted \| RfcUpdated", "LastModifiedTime": "Last_Updated_Time", "LastSubmittedTime": "null \| Last_Submitted_Time", RFC state change notiﬁcations Version May 08, 2025 194 AMS Advanced User Guide AMS Advanced Concepts and Procedures "RequestedExecutionTimeRange": { "StartTime": "null \| Expected_Start_Time", "EndTime": "null \| Expected_End_Time" }, "RfcId": "RFC_ID", "Status": "Editing \| PendingApproval \| Scheduled \| Rejected \| Canceled \| ExecutionLock \| InProgress \| Success \| Failure", "Title": "Title" } } The supported RFC state changes (EventType), as they appear in the actual CloudWatch Events notiﬁcation are: • RfcActionStateUpdated (no AMS console option): The RFC in one of the states, described later, changed. • RfcApproved (no AMS console option): The RFC passed system and/or AMS operator validation and has been approved for completion. • RfcAutoRejected (Auto-Rejected): The RFC failed system validation or AMS operator and has been rejected. • RfcCanceled (Canceled or Auto-Canceled): The RFC was canceled by either the submitter or an AMS operator. • RfcCompleted (Completed): The RFC run parameters have been completed, including UserData. • RfcCreated (no AMS console option): The RFC was successfully created (the JSON and submitted parameters were valid). • RfcInProgress (InProgress): The RFC run is still in progress. • RfcRejected (Rejected): The RFC failed system or AMS operator validation has been rejected. • RfcSubmitted (Submitted): The RFC has been submitted and is undergoing system validation. • RfcUpdated (no AMS console option): The RFC has been manually updated by an AMS operator. Additionally, you can send CloudWatch Events (CWE) notiﬁcations to any of the supported destinations and build your own systems on top of these automated notiﬁcations: • Amazon EC2 instances • AWS Lambda functions • Streams in Amazon Kinesis Data Streams RFC state change notiﬁcations Version May 08, 2025 195 AMS Advanced User Guide AMS Advanced Concepts and Procedures • Delivery streams in Amazon Data Firehose • Log groups in Amazon CloudWatch Logs • Amazon ECS tasks • Systems Manager Run Command • Systems Manager Automation • AWS Batch jobs • Step Functions state machines • Pipelines in CodePipeline • CodeBuild projects • Amazon Inspector assessment templates • Amazon SNS topics • Amazon SQS queues • Built-in targets: EC2 CreateSnapshot API call, EC2 RebootInstances API call, EC2 StopInstances API call, and EC2 TerminateInstances API call. • The default event bus of another AWS account Note We send CloudWatch Events notiﬁcation for RFC state changes, on a best-eﬀort basis. Setting up private and public DNS During onboarding, AMS sets up a private DNS service for communications between your managed resources and AMS. You can use AMS Route 53 to manage the internal DNS names for your application resources (web servers, application servers, databases, and so forth) without exposing this information to the public Internet. This adds an additional layer of security, and also allows you to fail over from a primary resource to a secondary one (often called a "ﬂip") by mapping the DNS name to a diﬀerent IP address. After you create private DNS resources using the Deployment \| Advanced stack components \| DNS (private) \| Create (ct-0c38gftq56zj6) or Deployment \| Advanced stack components \| DNS Setting up private and public DNS Version May 08, 2025 196 AMS Advanced User Guide AMS Advanced Concepts and Procedures (public) \| Create (ct-0vzsr2nyraedl), you can use the Management \| Advanced stack components \| DNS (private) \| Update (ct-1d55pi44ﬀ21u) and Management \| Advanced stack components \| DNS (public) \| Update (ct-1hzofpphabs3i), CTs to conﬁgure additional, or update existing, record sets. For multi-account landing zone (MALZ) accounts, DNS resources created in the application account VPCs can be shared with the shared services account VPC to maintain centralized DNS using AMS AD. MALZ The following graphic illustrates a possible DNS conﬁguration for Multi-Account Landing Zone AMS. It illustrates a hybrid DNS setup between AMS and a typical customer network. A Canonical Name Record (CNAME) in the customer network DNS server forwards to the AMS AD DNS in the shared services account with a conditional forward that has the CNAME of the AMS FQDN forwarded to the A record. Setting up private and public DNS Version May 08, 2025 197 AMS Advanced User Guide AMS Advanced Concepts and Procedures SALZ The following graphic illustrates a possible DNS conﬁguration for single-account landing zone (SALZ). It shows a hybrid DNS setup between AMS and a typical customer network. A CNAME in the customer network DNS server forwards to the AMS AD DNS with a conditional forward which has the CNAME of the AMS FQDN forwarded to the A
ams-ug-068	ams-ug.pdf	68	DNS in the shared services account with a conditional forward that has the CNAME of the AMS FQDN forwarded to the A record. Setting up private and public DNS Version May 08, 2025 197 AMS Advanced User Guide AMS Advanced Concepts and Procedures SALZ The following graphic illustrates a possible DNS conﬁguration for single-account landing zone (SALZ). It shows a hybrid DNS setup between AMS and a typical customer network. A CNAME in the customer network DNS server forwards to the AMS AD DNS with a conditional forward which has the CNAME of the AMS FQDN forwarded to the A record. Setting up private and public DNS Version May 08, 2025 198 AMS Advanced User Guide AMS Advanced Concepts and Procedures SALZ Route53 DNS The following graphic illustrates a possible DNS conﬁguration for single-account landing zone (SALZ). It shows a hybrid DNS setup between AMS and a typical customer network. A CNAME in the customer network DNS server forwards to the AMS AD DNS with a conditional forward which has the CNAME of the AMS FQDN forwarded to the A record. This also leverages Route53 for outbound network traﬃc so that any application in the account can have DNS Resolution in the account with the highest availability. Route53 enabled Resolution paths: • Instance attempting to resolve AMS MAD name --> VPC +2 (Route53/AmazonProvidedDNS) -- > Conditional Forwarders evaluated --> Route53 MAD Conditional Forwarder rule matched -- > Route53 Outbound resolver --> Managed AD DNS • Instance attempting to resolve customer on-prem name --> VPC +2 (Route53/ AmazonProvidedDNS) --> Conditional Forwarders evaluated --> Route53 On-prem Conditional Forwarder rule matched --> Route53 Outbound resolver --> Customer on-prem DNS • Instance attempting to resolve Internet name --> VPC +2 (Route53/AmazonProvidedDNS) --> Conditional Forwarders evaluated --> No matching forwarder --> Internet DNS Service Setting up private and public DNS Version May 08, 2025 199 AMS Advanced User Guide AMS Advanced Concepts and Procedures For more information, see Using DNS with Your VPC and Working with Private Hosted Zones. AMS egress traﬃc management By default, the route with a destination CIDR of 0.0.0.0/0 for AMS private and customer- applications subnets has a network address translation (NAT) gateway as the target. AMS services, TrendMicro and patching, are components that must have egress access to the Internet so that AMS is able to provide its service, and TrendMicro and operating systems can obtain updates. AMS supports diverting the egress traﬃc to the internet through a customer-managed egress device as long as: • It acts as an implicit (for example, transparent) proxy. and • It allows AMS HTTP and HTTPS dependencies (listed in this section) in order to allow ongoing patching and maintenance of AMS managed infrastructure. Some examples are: AMS egress traﬃc management Version May 08, 2025 200 AMS Advanced User Guide AMS Advanced Concepts and Procedures • The transit gateway (TGW) has a default route pointing to the customer-managed, on-premises ﬁrewall over the AWS Direct Connect connection in the Multi-Account Landing Zone Networking account. • The TGW has a default route pointing to an AWS endpoint in the Multi-Account Landing Zone egress VPC leveraging AWS PrivateLink, pointing to a customer-managed proxy in another AWS account. • The TGW has a default route pointing to a customer-managed ﬁrewall in another AWS account, with site-to-site VPN connection as an attachment to the Multi-Account Landing Zone TGW. AMS has identiﬁed the corresponding AMS HTTP and HTTPS dependencies, and develops and reﬁnes these dependencies on an ongoing basis. See egressMgmt.zip. Along with the JSON ﬁle, the ZIP contains a README. Note • This information isn't comprehensive--some required external sites aren't listed here. • Do not use this list under a deny list or blocking strategy. • This list is meant as a starting point for an egress ﬁltering rule set, with the expectation that reporting tools will be used to determine precisely where the actual traﬃc diverges from the list. To ask for information about ﬁltering egress traﬃc, email your CSDM: ams-csdm@amazon.com. Deploying IAM resources in AMS Advanced AMS deploys IAM resources in your multi-account landing zone (MALZ) Application and single- account landing zone (SALZ) accounts in two ways: • Automated IAM Provisioning: This capability in AMS lets you submit create, update, or delete change types for IAM role or policy provisioning, without operator review, and with IAM and AMS validation checks run automatically. This capability must be explicitly enabled with the Management \| Managed account \| AMS Automated IAM Provisioning with read-write permissions \| Enable (review required) change type (ct-1706xvvk6j9hf). To learn more, see Automated IAM Provisioning AMS. After AMS Automated Deploying IAM resources Version May 08, 2025 201 AMS Advanced User Guide AMS Advanced Concepts and Procedures IAM Provisioning is enabled, you have access to Create, Update, and Delete change types to manage your IAM resources. • Review
ams-ug-069	ams-ug.pdf	69	create, update, or delete change types for IAM role or policy provisioning, without operator review, and with IAM and AMS validation checks run automatically. This capability must be explicitly enabled with the Management \| Managed account \| AMS Automated IAM Provisioning with read-write permissions \| Enable (review required) change type (ct-1706xvvk6j9hf). To learn more, see Automated IAM Provisioning AMS. After AMS Automated Deploying IAM resources Version May 08, 2025 201 AMS Advanced User Guide AMS Advanced Concepts and Procedures IAM Provisioning is enabled, you have access to Create, Update, and Delete change types to manage your IAM resources. • Review required IAM change type: This change type, Deployment \| Advanced stack components \| Identity and Access Management (IAM) \| Create entity or policy (review required) (ct-3dpd8mdd9jn1r), requires an AMS operator review, which can sometimes take a few days to complete if clariﬁcations are needed. Note Whichever method is used, an IAM role is provisioned to the relevant account or accounts and, after the role is provisioned, you must onboard the role in your federation solution. Automated IAM Provisioning AMS AWS Managed Services (AMS) supports automated validation and provisioning for IAM resources including roles and policies using AMS Advanced requests for change (RFCs) and new change types (CTs). Previously, these requests went through a semi-automated process that sometimes resulted in long wait times. Now, you can use AMS Automated IAM Provisioning to provision IAM resources and get the results much more quickly. How Automated IAM Provisioning in AMS works Automated IAM Provisioning relies on automated run-time checks for IAM to validate changes to IAM resources. These automated checks, performed when the Create, Update, or Delete change types are run, prevent IAM resources that are overly-permissive or have insecure patterns from being deployed into your account. This allows you to match the level of rigor in IAM reviews to the expertise of your team. We recommend that teams that are new to cloud services and need manual checks for all IAM resources changes use the existing review-required change type: Deployment \| Advanced stack components \| Identity and Access Management (IAM) \| Create entity or policy (review required), (ct-3dpd8mdd9jn1r). Teams with AWS expertise and control of their environments can use Automated IAM Provisioning to speed up their deployments. You can use this feature to perform validation through automated run-time checks or to perform validation and provisioning of IAM resources after successful validation. Automated IAM Provisioning Version May 08, 2025 202 AMS Advanced User Guide AMS Advanced Concepts and Procedures Important AWS Managed Services has proactively implemented a list of validation runtime checks that prevent the creation of IAM resources or policies with certain permissions and conditions. For a description of these privileges and conditions, see Deploying IAM resources in AMS Advanced. The automated change types ct-1n9gfnog5x7ﬂ, ct-1e0xmuy1diafq, and ct-17cj84y7632o6, allow users who are proﬁcient in managing IAM resouces to provision IAM roles and policies that allow actions beyond Read Only privileges. In addition, you can use the roles created through the automated change types ct-1n9gfnog5x7ﬂ, ct-1e0xmuy1diafq, and ct-17cj84y7632o6 to create the new resources. However, the resources can't follow the AMS naming standard and aren't part of the standard AMS stack. AMS provides the operational and security support of those speciﬁc resources on a best eﬀort basis. While both manual and automated processes aim to uphold our security standards, it's important to note that there are diﬀerences in the checks between the two. The automated provisioning allows for greater ﬂexibility in creating and updating roles and policies; therefore, they are not the same. It's recommended that your organization carefully review the validation runtime checks listed in the AMS User Guide to ensure that they align with your organization's expectations and requirements. Validation ﬂow Automated IAM Provisioning Version May 08, 2025 203 AMS Advanced User Guide AMS Advanced Concepts and Procedures Validation and provisioning ﬂow Note This feature is suitable for teams that are experienced with AWS and IAM resources, and we do not recommend it for teams that are new to AWS. The automated validation process is designed to catch most errors and is helpful for teams to get quick reviews for changes to Automated IAM Provisioning Version May 08, 2025 204 AMS Advanced User Guide AMS Advanced Concepts and Procedures IAM, when they understand the permissions that they need. To use the new change types safely and eﬀectively, we recommend you to have a good understanding of AWS IAM, and the run-time checks oﬀered by the change types to determine whether they are suitable for your team. Onboarding to AMS Automated IAM Provisioning in AMS To use the new change types, ﬁrst enable AMS Automated IAM Provisioning by submitting an RFC using the following change type: Management \| Managed account \| AMS Automated IAM Provisioning with read-write permissions \| Enable (review required) (ct-1706xvvk6j9hf).
ams-ug-070	ams-ug.pdf	70	User Guide AMS Advanced Concepts and Procedures IAM, when they understand the permissions that they need. To use the new change types safely and eﬀectively, we recommend you to have a good understanding of AWS IAM, and the run-time checks oﬀered by the change types to determine whether they are suitable for your team. Onboarding to AMS Automated IAM Provisioning in AMS To use the new change types, ﬁrst enable AMS Automated IAM Provisioning by submitting an RFC using the following change type: Management \| Managed account \| AMS Automated IAM Provisioning with read-write permissions \| Enable (review required) (ct-1706xvvk6j9hf). AWS requires that your organization go through a customer security risk management (CSRM) process to ensure that the use of these change types are aligned with your organizational policies. The AWS operations team works with you to acquire explicit approval from your security team contact in the form of risk acceptance as part of the required review. To learn more, see the RFC customer risk management (CSRM) process. After the RFC for turning on AMS Automated IAM Provisioning with read-write permissions feature is successful, AMS enables the AMS Automated IAM Provisioning change types in the account used to submit the enable RFC. To conﬁrm that an account has AMS Automated IAM Provisioning turned on, check the IAM console for the AWSManagedServicesIAMProvisionAdminRole role. As part of onboarding, AMS provisions IAM Access Analyzer in the same AWS Region of the account to leverage its access preview capability. IAM Access Analyzer helps identify resources in your organization and accounts that are shared with an external entity, validates IAM policies against policy grammar and best practices, and generates IAM policies based on access activity in your AWS CloudTrail logs. To learn more, see Using AWS Identity and Access Management Access Analyzer. Once onboarded, the AWSManagedServicesIAMProvisionAdminRole is deployed to the enabled accounts. If you choose to use this role through SAML federation, then you must onboard the role to your federation solution. As part of onboarding, you can request to update AWSManagedServicesIAMProvisionAdminRole’s trust policy to grant another IAM role ARN to assume this role using AWS Security Token Service. Using AMS Automated IAM Provisioning in AMS You can create RFCs with the following AMS Automated IAM Provisioning change types. Automated IAM Provisioning Version May 08, 2025 205 AMS Advanced User Guide AMS Advanced Concepts and Procedures Note • Only provisioning on roles and policies are supported. While updating roles, the Update CT replaces the existing list of managed policy Amazon resource names (ARNs) and the "assume role" policy document, with the provided list of managed policy ARNs and "assume role" policy document. In a partial update; for example, adding or removing an ARN in the existing list of managed policy ARNs, adding or removing individual policy statements to the "assume role" policy document is not allowed. Similarly, while updating policies, the Update CT replaces the existing policy document and does not allow adding or removing individual policy statement in the existing policy document. • When the “validate only” option is selected, run-time checks are performed without provisioning any IAM entity or policy. Regardless of any ﬁndings, the RFC status is “success”. The "success" status indicates a successful validation against the provided IAM entity or policy. • Deployment \| Advanced Stack Components \| Identity and Access Management (IAM) \| Create entity or policy (read-write permissions)(ct-1n9gfnog5x7ﬂ): A new IAM entity or policy is validated and provisioned automatically. • Management \| Advanced Stack Components \| Identity and Access Management (IAM) \| Update entity or policy (read-write permissions)(ct-1e0xmuy1diafq): An existing IAM entity or policy is updated and validated automatically. • Management \| Advanced Stack Components \| Identity and Access Management (IAM) \| Delete entity or policy (read-write permissions)(ct-17cj84y7632o6): An existing IAM entity or policy that's provisioned using the automated create entity or policy change type is deleted. You can only call the preceding three CTs using a dedicated IAM role: AWSManagedServicesIAMProvisionAdminRole. This role is available only in the accounts that have been onboarded to the feature using the Management \| Managed account \| AMS Automated IAM Provisioning read-write permissions \| Enable (review required) (ct-1706xvvk6j9hf). Automated IAM Provisioning Version May 08, 2025 206 AMS Advanced User Guide AMS Advanced Concepts and Procedures Important The Create, Update, and Delete change types are always visible in your account, but they aren't turned on by default. If you try submit an RFC using one of these change types without ﬁrst enabling the AMS Automated IAM Provisioning feature, then an "unauthorized" error displays. Limitations: • The Create CT might allow you to create an IAM role or policy with permission to create AWS resources. However, AWS resources created by these roles and policies aren't managed by AMS. It's a best practice to adhere to your organizational control to limit creation of such roles or
ams-ug-071	ams-ug.pdf	71	and Procedures Important The Create, Update, and Delete change types are always visible in your account, but they aren't turned on by default. If you try submit an RFC using one of these change types without ﬁrst enabling the AMS Automated IAM Provisioning feature, then an "unauthorized" error displays. Limitations: • The Create CT might allow you to create an IAM role or policy with permission to create AWS resources. However, AWS resources created by these roles and policies aren't managed by AMS. It's a best practice to adhere to your organizational control to limit creation of such roles or policies. • The Update CT can not modify IAM roles and policies created with CFN Ingest, Direct Change Mode, Developer Mode, or, in some cases, through existing AMS Advanced manual or automated CTs. • The Delete CT can not delete existing roles or policies that are not created with the AMS Automated IAM Provisioning Create CT. • The AMS Automated IAM Provisioning with read-write permissions feature isn't supported in Direct Change Mode roles. This means that you can't provision or update IAM roles and policies with read-write permissions using these roles. • AMS Automated IAM Provisioning with read-write permissions Create, Update, and Delete change types are not compatible with the ServiceNow Connector. Runtime checks for AMS Automated IAM Provisioning in AMS Automated IAM Provisioning leverages checks from AWS Identity and Access Management Access Analyzer, and performs additional checks and validations against the AMS boundary policy. AMS deﬁned the additional checks and validations based on IAM best practices, experience operating customer workload in the cloud, and the collective AMS IAM manual evaluation experience. You can view policy run-time check ﬁndings in the request for change (RFC) output. The ﬁndings include the resource identiﬁer, location within the role and/or policy that generated the ﬁndings, and a message outlining the check that the IAM entity or resource failed to pass. These ﬁndings help you author policies that are functional and conform to security best practices. Automated IAM Provisioning Version May 08, 2025 207 AMS Advanced User Guide AMS Advanced Concepts and Procedures Note Automated IAM Provisioning attempts to be speciﬁc about the location within the entity or policy deﬁnition that fails to pass the check. Depending on the type, the location might include the resource name or ARN, or index within an array. For example, a statement to help you adjust the entity or policy for a successful outcome. For a smooth AMS Automated IAM Provisioning experience, it's a best practice to use the “validate only” option to run the validation checks until there are no ﬁndings from the validation checks reported in the RFC outputs. When the validation checks report no ﬁndings, choose Create copy from the AMS Console to quickly create a copy of the existing RFC. When you are ready to provision, in the Parameters section, switch the Validate only value from Yes to No, and then proceed. These are the run-time checks that AMS Automated IAM Provisioning performs to ensure that your IAM resources are secure: Note To provision IAM policies that contain actions denied by these automated change types, you must follow the RFC customer security risk management (CSRM) process. Use the following change type: Deployment \| Advanced stack components \| Identity and Access Management (IAM) \| Create entity or policy (review required) (ct-3dpd8mdd9jn1r). • IAM Access Analyzer policy check and validation: See also Access Analyzer policy check reference and IAM Access Analyzer policy validation. • AMS permissions boundary policy checks: Actions on a set of services that are denied by default. For more information, see Automated IAM Provisioning permission boundary check. • Customer-deﬁned permissions boundary policy checks: Additional restricted actions on a set of services that are denied. For more information, see Automated IAM Provisioning permission boundary check. • AMS-deﬁned custom checks: Checks that identify various insecure and overly permissive policies or access patterns within a requested IAM entity or policy, and denies the request if found one. For for information, see AWS JSON policy elements: Principal. Automated IAM Provisioning Version May 08, 2025 208 AMS Advanced User Guide AMS Advanced Concepts and Procedures Finding Description The role can be accessed from an external account that is outside of your zone of trust. This ﬁnding refers to a principal listed in the role trust policy that is outside of your zone of trust. A zone of trust is deﬁned as the account where the role is being created or the AWS organization that the account belongs to. An entity that does not belong to the account or to the same AWS Organization is an external entity. To resolve the ﬁnding, review the account ID in the principal ARNs and make sure that they belong to you and is an AMS onboarded account. This ﬁnding is generated if
ams-ug-072	ams-ug.pdf	72	outside of your zone of trust. This ﬁnding refers to a principal listed in the role trust policy that is outside of your zone of trust. A zone of trust is deﬁned as the account where the role is being created or the AWS organization that the account belongs to. An entity that does not belong to the account or to the same AWS Organization is an external entity. To resolve the ﬁnding, review the account ID in the principal ARNs and make sure that they belong to you and is an AMS onboarded account. This ﬁnding is generated if the role trust policy includes a principal ARN that has an account ID not owned by you and an AMS onboarded account. To resolve this ﬁnding remove any such principal from the role trust policy. The role can be accessed by an external entity owned by account External_Account_I D that is not owned by the AMS customer- owning account Account_ID . The canonical user ID is not a supported principal in IAM trust policy. Canonical principal IDs are not supported in IAM trust policy. To resolve the ﬁnding remove any such principal from the role trust policy. The role can be accessed by an external web identity that is outside of your zone of trust. This ﬁnding is generated if the role trust policy allows an external Web identity provider The role can be accessed through SAML federation; however, the provided SAML identity provider (IdP) does not exist. (IdP) other than SAML IdP. To resolve this ﬁnding, review the role trust policy and remove statements that allow the sts:Assum eRoleWithWebIdentity operation. This ﬁnding is generated if the role trust policy contains SAML IdP that does not exist in your account. To resolve ensure you all the listed SAML IdP exists in your account. Policy contains privileged actions equivalen t to administrator or power user access. It's a best security practice in AWS Identity and Access Management to grant only the Automated IAM Provisioning Version May 08, 2025 209 AMS Advanced User Guide AMS Advanced Concepts and Procedures Finding Description Consider reducing the permission scope permissions required to perform a task when to a speciﬁc service, action, or resource. If advanced policy elements such as NotAction or NotResource are used, make sure that they are not granting more access than you intend, particularly in Allow statements. you set permissions with IAM policies. Do this by deﬁning the actions that can be taken on speciﬁc resources under speciﬁc conditions, also known as least-privilege permissions. This ﬁnding is generated when automation detects the policy grants broad permissions and does not adhere to the principle of least privilege. To resolve the ﬁnding, review and reduce the permissions. Statement contains privileged actions for Service_Name . Consider excluding these actions with a deny statement. Refer to AMS identiﬁed certain actions for a given service as risky and require further risk review and acceptance by the customer the boundary policy reference in the AMS security team. This ﬁnding is generated when documentation for a list of privileged actions. automation detects the given policy granting such permissions. To resolve this ﬁnding, deny these actions in your policy. For a list of actions refer to the AMS boundary policy. For details on AMS boundary policy, see AMS Automated IAM Provisioning permission boundary check. Statement grants access to privileged RFC Change Types: ct-1n9gfnog5x7ﬂ, ct-1e0xmu This ﬁnding is generated if the policy grants permissions to perform RFC-related actions y1diafq, and ct-17cj84y7632o6 for service Service_Name . Consider scoping the permissions to speciﬁc change types or exclude these change types with a deny statement. using Automated IAM Provisioning change types (CTs). The CTs are subject to risk acceptance and must only be used through onboarded roles. So, you can't granting permission to these CTs. To resolve this ﬁnding, deny RFC actions using these CTs. Automated IAM Provisioning Version May 08, 2025 210 AMS Advanced User Guide AMS Advanced Concepts and Procedures Finding Description Statement contains privileged actions that are not scoped to your resources for service This ﬁnding is generated if the policy grants privileged actions that are not scoped to your Service_Name . Consider scoping the actions to speciﬁc resources or exclude resources of the given service. Wild cards often create overly permissive policies that resources with AMS namespace preﬁxes. If bring a broad set of resources or actions into wildcards are used ensure they restrict the the permission's scope. To resolve the ﬁnding, scope to your resources. either reduce the scope of permissions to resources you own or exclude resources that are in the AMS namespace. For a list of AMS namespace preﬁxes, see the boundary policy in AMS documentation. Note that not all preﬁxes apply to all services. For details on the AMS boundary policy, see AMS Automated IAM Provisioning
ams-ug-073	ams-ug.pdf	73	resources of the given service. Wild cards often create overly permissive policies that resources with AMS namespace preﬁxes. If bring a broad set of resources or actions into wildcards are used ensure they restrict the the permission's scope. To resolve the ﬁnding, scope to your resources. either reduce the scope of permissions to resources you own or exclude resources that are in the AMS namespace. For a list of AMS namespace preﬁxes, see the boundary policy in AMS documentation. Note that not all preﬁxes apply to all services. For details on the AMS boundary policy, see AMS Automated IAM Provisioning permission boundary check. Invalid account Id or Amazon Resource Name (ARN). This ﬁnding is generated if any ARN or account ID speciﬁed in the policy or role trust policy is invalid. To review valid resource ARN's resources for services, see the Service Authorization Reference. Make sure that the account ID is a 12-digit number and that the account is active in AWS. Use of wildcard () for account id in ARN is restricted.. This ﬁnding is generated if a wild card () is speciﬁed in the account ID ﬁeld of an ARN. A wild card in an account ID ﬁeld matches any account and potentially grants unintende d permission to resources. To resolve this, replace the wild card with a speciﬁc account ID. Automated IAM Provisioning Version May 08, 2025 211 AMS Advanced User Guide AMS Advanced Concepts and Procedures Finding Description Speciﬁed resource account not owned by same AMS customer owning account Account_ID . This ﬁnding is generated if an account ID speciﬁed in a resource ARN does not belong The role name is in AMS restricted namespace. The policy name is in AMS restricted namespace. to you and is not managed by AMS. To resolve this, make sure that all resources (as speciﬁed by their ARN in the policy) belong to your accounts that are managed by AMS. This ﬁnding is generated if you try to create a role with a name that starts with an AMS reserved preﬁx. To resolve this, use a name for the role that is speciﬁc to your use case. For a list of AMS reserved preﬁxes, see AMS reserved preﬁxes This ﬁnding is generated if you try to create a policy with a name that starts with an AMS reserved preﬁx. To resolve this, use a name for the policy that is speciﬁc to your use case. For a list of AMS reserved preﬁxes, see AMS reserved preﬁxes. The resource ID in the ARN is in AMS restricted namespace. This ﬁnding is generated if you try to create a policy that grants permission to named resources that are in the AMS namespace . To resolve this, make sure that you scope the permissions to your resources or deny permissions to resources that are in the AMS namespace. For more information on AMS namespaces, see AMS restricted namespaces. Automated IAM Provisioning Version May 08, 2025 212 AMS Advanced User Guide AMS Advanced Concepts and Procedures Finding Description Invalid policy variable case. Update the variable to Variable_Names . This ﬁnding is generated if try to create a policy that contains an IAM global policy variable in the incorrect case. To resolve this, use the correct case for global variables in your policy. For a list of global variables, see AWS global condition context keys. For more information on the policy variables, see IAM policy elements: Variables and tags Statement contains privileged actions that are not scoped to your KMS keys. Consider This ﬁnding is generated if the policy contains permissions that are not scoped to speciﬁc scoping these permissions to speciﬁc keys or exclude AMS owned keys. KMS keys that you own. To resolve this, scope the permission to speciﬁc keys or exclude the keys that are AMS owned. AMS owned keys have speciﬁc alias sets. For a list of AMS owned key aliases, see AMS Automated IAM Provisioning permission boundary check. Statement contains privileged actions that are not scoped to your KMS keys aliases. Consider This ﬁnding is generated if the policy contains permissions that are not scoped to speciﬁc scoping these permissions to your keys or KMS keys alias that you own. To resolve aliases, or exclude AMS-owned key aliases. this, scope the permission to speciﬁc keys or exclude the keys that are AMS owned. AMS owned keys have speciﬁc alias sets. For a list of AMS owned key aliases, see AMS Automated IAM Provisioning permission boundary check. Automated IAM Provisioning Version May 08, 2025 213 AMS Advanced User Guide AMS Advanced Concepts and Procedures Finding Description Statement contains privileged actions that are not adequately scoped to your KMS keys using This ﬁnding is generated if you are scoping permissions to your KMS keys using condition the kms:ResourceAliases condition . Consider using
ams-ug-074	ams-ug.pdf	74	To resolve aliases, or exclude AMS-owned key aliases. this, scope the permission to speciﬁc keys or exclude the keys that are AMS owned. AMS owned keys have speciﬁc alias sets. For a list of AMS owned key aliases, see AMS Automated IAM Provisioning permission boundary check. Automated IAM Provisioning Version May 08, 2025 213 AMS Advanced User Guide AMS Advanced Concepts and Procedures Finding Description Statement contains privileged actions that are not adequately scoped to your KMS keys using This ﬁnding is generated if you are scoping permissions to your KMS keys using condition the kms:ResourceAliases condition . Consider using speciﬁc alias names along s and not using kms:ResourceAliases scope down to aliases for your KMS keys. Or, to with the appropriate set operator for the condition key. If wildcards are used in the if the kms:ResourceAliases key has a value that also includes AMS owned condition alias names ensure they restrict the scope to a limited set of your KMS keys. KMS keys aliases. To resolve this, update the condition to scope down permission only to The role must have customer_deny_policy attached. Include the policy ARN in the list of managed policy ARNs. The AWS managed policy is overly permissiv e or grants permissions restricted by AMS boundary policy. The customer managed policy is in restricted AMS namespace. aliases of your KMS keys or exclude aliases for AMS owned KMS keys. For a list of AMS owned key aliases, see AMS Automated IAM Provision ing permission boundary check. This ﬁnding is generated if the role that you are creating does not have the customer_ deny_policy attached to it. To resolve this, include the customer_deny_policy in the managed policy ARNs list. This ﬁnding is generated if the ManagedPo licyArns value for the role contains any AMS managed policy that provides full or administr ator level access to the relevant service. To resolve this, review use of the AWS managed policy and use a policy that provides scope down permission or deﬁne your own policy that follows the principle of least privilege. This ﬁnding is generated if any customer managed policy with name preﬁxed in the AWS namespace is attached to the role. To resolve this, remove the policy from the ManagedPolicyArn list for the role. Automated IAM Provisioning Version May 08, 2025 214 AMS Advanced User Guide AMS Advanced Concepts and Procedures Finding Description The customer_deny_policy can not be detached from the role. Include the policy ARN in the list of managed policy ARNs. This ﬁnding is generated if the customer_ deny_policy is detached from the role during an update. To resolve this, add the customer_deny_policy ManagedPolicyArns ﬁeld of the role and try again. to the The customer managed policies were provision ed outside AMS Change Management service This ﬁnding is generated if one or more existing customer managed policy ARNs or without prior validation. are attached to a role and the policies are not provisioned through the AMS Change Management service (through an RFC). For example, Developer Mode or Direct Change Mode allow customers to provision IAM policies without an RFC. To resolve this, remove the customer managed policy ARNs from the ManagedPolicyArns list for the role. The count of provided managed policy ARNs exceed attached policy per role quota. This ﬁnding is generated if the total number of managed policies attached to the role The trust policy size ({trust_policy}) exceeds assume role policy size quota of {size}. exceeds the policy per role quota. For more information on IAM quotas, see IAM and AWS STS quotas, name requirements, and character limits. Use this information to reduce the number of policies that you attach to the role. This ﬁnding is generated if the size of the assume role policy document exceeds the policy size quota. For more information on IAM quotas, see IAM and AWS STS quotas, name requirements, and character limits. Automated IAM Provisioning Version May 08, 2025 215 AMS Advanced User Guide AMS Advanced Concepts and Procedures Finding Description Statement contains all mutative actions for Amazon S3. Consider scoping these permissio This ﬁnding is generated if the given policy grants all Amazon Simple Storage Service ns to required actions only. If wild cards are mutative permissions irrespective of one or used ensure they scope limited set of mutative more resources. To resolve this, include only actions. required Amazon S3 mutative actions against your buckets. Statement contains privileged actions that are not allowed against any bucket in Amazon S3. This ﬁnding is generated if the policy grants privileged actions on any bucket. For a list of Consider adding a statement denying these privileged actions, see AMS Automated IAM actions. Provisioning permission boundary check To resolve this ﬁnding, remove, or deny these actions in your policy. Statement contains privileged actions that are not scoped to your buckets in Amazon S3.
ams-ug-075	ams-ug.pdf	75	one or used ensure they scope limited set of mutative more resources. To resolve this, include only actions. required Amazon S3 mutative actions against your buckets. Statement contains privileged actions that are not allowed against any bucket in Amazon S3. This ﬁnding is generated if the policy grants privileged actions on any bucket. For a list of Consider adding a statement denying these privileged actions, see AMS Automated IAM actions. Provisioning permission boundary check To resolve this ﬁnding, remove, or deny these actions in your policy. Statement contains privileged actions that are not scoped to your buckets in Amazon S3. This ﬁnding is generated if the policy grants Amazon S3 actions that are not scoped to your Consider including your buckets or exclude buckets only. This is often occurs if wild cards buckets with AMS namespace preﬁxes. If wild are used when specifying bucket resources. cards are used, make sure that they match To resolve this, specify bucket names or ARNs buckets within your namespaces. that you own or exclude the buckets that have AMS namespace preﬁxes. Statement contains privileged actions that are not scoped to your buckets in Amazon S3. This ﬁnding is generated if the policy grants Amazon S3 actions that are not scoped to your Consider avoiding use of wild cards (*) that bucket. This is often occurs if wild cards are scopes all buckets in the account. used when specifying bucket resources. To resolve this, specify bucket names or ARNs that you own or exclude the buckets that have AMS namespace preﬁxes. Automated IAM Provisioning Version May 08, 2025 216 AMS Advanced User Guide AMS Advanced Concepts and Procedures Finding Description Statement contains a resource wildcard which is scoped to all Amazon S3 buckets, including This ﬁnding is generated if the policy grants permission to buckets speciﬁed using wild non-existent buckets and buckets you do not cards. Use of wild cards often brings non- own . Consider scoping the permissions using existing or non-owner buckets in scope. To a condition and s3:ResourceAccount condition key. resolve this, use condition and the aws:Resou rceAccount permission to buckets within the current condition key to scope the account only. For more details, see Limit access to Amazon S3 buckets owned by speciﬁc AWS accounts. Statement contains a NotResource policy element, which may be scoped to a large number of buckets, including non-existent buckets and buckets you do not own. Consider scoping the permissions using a condition and This ﬁnding is generated if the policy utilizes the NotResources policy element to specify bucket resources. The use of the NotResour ce element might scope a large number of buckets, including non-existent or non-owner s3:ResourceAccount condition key. buckets. To resolve this, use conditions and the aws:ResourceAccount condition key to scope the permission to buckets only within the current account. Statement contains Amazon S3 action to buckets Bucket_Name that either do not exist, are not owned by account Account_I D , or name contains a wild card that might be scoped to a large number of buckets, including non-existent buckets and buckets you do not own. Consider scoping the permissions using a condition and the s3:ResourceAccount condition key This ﬁnding is generated if the policy grants permission to buckets that either do no exist, are not owned by you, or have wild cards in the bucket names covering a large number of buckets and access is not scoped to the current account only. To resolve this, use condition and the aws:ResourceAccoun t condition key to scope the permission to buckets within the current account only. Automated IAM Provisioning Version May 08, 2025 217 AMS Advanced User Guide AMS Advanced Concepts and Procedures Finding Description Statement contains Amazon S3 action to buckets Bucket_Name that either do not exist, not owned by account Account_ID , or the name contains a wild card that might be This ﬁnding is generated if the policy grants permission to buckets that either do no exist, are not owned by you, or have wild cards in the bucket names covering a large number scoped to a large number of buckets, including of buckets and access is scoped to a speciﬁc non-existent buckets and buckets you do not account only. However, the account speciﬁed own. Access is not restricted using s3:Resour ceAccount or speciﬁed resource account in the condition does not belong to you. in the aws:ResourceAccount key does not belong to you and is managed by condition AMS. To resolve this, update the aws:Resou rceAccount appropriate account ID that you own and is condition key and set the managed by AMS. Statement contains privileged actions that are not scoped to your instances for Amazon This ﬁnding is generated if the policy grants privileged actions against Amazon EC2 EC2. Consider scoping the actions to speciﬁc instance ARNs or exclude instances that have
ams-ug-076	ams-ug.pdf	76	account speciﬁed own. Access is not restricted using s3:Resour ceAccount or speciﬁed resource account in the condition does not belong to you. in the aws:ResourceAccount key does not belong to you and is managed by condition AMS. To resolve this, update the aws:Resou rceAccount appropriate account ID that you own and is condition key and set the managed by AMS. Statement contains privileged actions that are not scoped to your instances for Amazon This ﬁnding is generated if the policy grants privileged actions against Amazon EC2 EC2. Consider scoping the actions to speciﬁc instance ARNs or exclude instances that have Name tag key with value in AMS namespace instances that AMS owns. AMS instances are tagged with the Name tag key with values in AMS namespace. To resolve this, specify your preﬁxes. If wild cards are used, ensure they resources or exclude AMS instances with a match namespaces that you own. condition that has the aws:ResourceTag/ Name key that excludes values in the AMS namespace using the StringNotLike operator Statement contains privileged actions that are not scoped to your resources in AWS Systems Manager parameter store. Consider specifying ARNs of your parameters or exclude parameters with AMS namespace preﬁxes. If wild cards are used, ensure they scope only your parameters. This ﬁnding is generated if the policy grants permissions to parameters that you do not own. This is usually when wild cards are used or parameters with AMS namespace preﬁxes are listed under resources in a policy statement. To resolve this, specify parameter s that are within your namespace or exclude AMS parameters with a deny statement. Automated IAM Provisioning Version May 08, 2025 218 AMS Advanced User Guide AMS Advanced Concepts and Procedures Finding Description Statement contains privileged actions against resources in AWS Systems Manager. Consider This ﬁnding is generated if the policy grants permissions other than parameter store or scoping the permissions to read only actions readonly actions against Systems Manager or actions against your resources. resources. To resolve this ﬁnding reduce the permissions to readonly actions or parameter store only. Statement contains privileged actions that are not scoped to {message} in Service_N ame that you own. Consider scoping these permissions to speciﬁc resource types as appropriate or exclude AMS owned resources . If wild cards are used, ensure they match Resources . This ﬁnding is generated if the policy allows privileged actions that are not granted against your resources, especially for named resources . To resolve this ﬁnding review your resource list and see if they only scope resource that is in your namespace. Alternatively exclude resources that are in AMS namespace. Statement contains tagging actions of {Service_Name } that are not scoped to speciﬁc values for Name tag key. Consider scoping these actions by setting aws:Reque condition key with values in stTag/Name your namespace or restrict these actions by This ﬁnding is generated if the policy grants tagging permission for given service and the permission is not scoped to specifc tag keys/ values. To scope down what key or value can be used in tag actions, for example, when making request to perform the actions, use setting aws:RequestTag/Name key with the StringNotLike operator with values in the AMS namespace preﬁxes. condition the aws:RequestTag/tag key condition . So, to resolve this, use this condition key to restrict key or values in your name space. Or, Internal error validating IAM role trust policy. deny the Name tag key (aws:RequestTag/ Name ) with values in AMS namespace. This ﬁnding is generated when CT automatio n encounters an error performing validatio n on the IAM role trust policy through the IAM Access Analyzer service. To resolve this, resubmit the RFC. If the error persists, then contact AMS Operations to troubleshoot the error. Automated IAM Provisioning Version May 08, 2025 219 AMS Advanced User Guide AMS Advanced Concepts and Procedures Finding Description Internal error validating customer managed policy. This ﬁnding is generated when CT automatio n encounters an error performing ovalidation on the customer managed policy through the IAM Access Analyzer service. To resolve this, resubmit the RFC. If the error persists, then contact AMS Operations to troubleshoot the error. Access analyzer not found in AWS Region. Unable to perform access preview check for This ﬁnding is generated when the IAM Access Analyzer resource is not found in the AWS role trust policy. Invalid trust policy for role Role_Name Region. Contact AMS Operations to troublesh oot and create IAM Access Analyzer resource in the AWS Region. This ﬁnding is generated when provided IAM role contains an invalid trust policy. To resolve review the trust policy to verify that it is valid. IAM Access Analyzer encountered an internal error. Failed to create access preview for role This ﬁnding is generated when automation encounters an error while creating an access Role_Name Failed to
ams-ug-077	ams-ug.pdf	77	preview check for This ﬁnding is generated when the IAM Access Analyzer resource is not found in the AWS role trust policy. Invalid trust policy for role Role_Name Region. Contact AMS Operations to troublesh oot and create IAM Access Analyzer resource in the AWS Region. This ﬁnding is generated when provided IAM role contains an invalid trust policy. To resolve review the trust policy to verify that it is valid. IAM Access Analyzer encountered an internal error. Failed to create access preview for role This ﬁnding is generated when automation encounters an error while creating an access Role_Name Failed to create access preview for trust policy of role Role_Name preview for a role through the IAM Access Analyzer. To resolve this, resubmit the RFC. If the error persists, then contact AMS Operation s to troubleshoot the error. This ﬁnding is generated when automation encounters an error while creating an access preview for a role through the IAM Access Analyzer. To resolve this, resubmit the RFC. If the error persists, then contact AMS Operation s to troubleshoot the error. Automated IAM Provisioning Version May 08, 2025 220 AMS Advanced User Guide AMS Advanced Concepts and Procedures Finding Description Internal error validating listed SAML IdP. This ﬁnding is generated when automatio n encounters an error while validating the provided SAML IdPs listed in the role trust policy. To resolve this, resubmit the RFC. If the error persists, then contact AMS Operations to troubleshoot the error. Internal error validating permissions against AWS Key Management Service. This ﬁnding is generated when automation encounters an error while validating the AWS KMS key permissions in the provided policy. To resolve this, resubmit the RFC. If the error persists, then contact AMS Operations to troubleshoot the error. Internal error validating listed managed policy ARNs. This ﬁnding is generated when automatio n encounters an error while validating listed managed policy ARNs. To resolve this, resubmit the RFC. If the error persists, then contact AMS Operations to troubleshoot the error. Internal error validating default customer_ deny_policy attachment. This ﬁnding is generated when automation encounters an error while validating that the Internal error validating managed policy arns for the role Role_Name customer_deny_policy is attached to the role. To resolve this, resubmit the RFC. If the error persists, then contact AMS Operation s to troubleshoot the error. This ﬁnding is generated when automation encounters an error while validating managed policy ARNs for the role. To resolve this, resubmit the RFC. If the error persists, then contact AMS Operations to troubleshoot the error. Automated IAM Provisioning Version May 08, 2025 221 AMS Advanced User Guide AMS Advanced Concepts and Procedures Finding Description Internal error validating Policy_name against customer-deﬁned boundary policy This ﬁnding is generated when automation encounters an error while validating the policy AWSManagedServicesIAMProvis that cotains your custom deny list. To resolve ionCustomerBoundaryPolicy this, resubmit the RFC. If the error persists, then contact AMS Operations to troubleshoot the error. Customer-deﬁned boundary policy AWSManagedServicesIAMProvis This ﬁnding is generated when the policy that contains your custom deny list includes exists ionCustomerBoundaryPolicy in the account. However, the policy contains allow statements that grant permissions. The policy must only contain deny statements. a statement that grants permission. Although the custom deny list exists within your account as an IAM managed policy, it can't be used for permission management. The policy must only contain deny statements that indicate that you want AMS Automated IAM Provisioning to validate and deny those actions in your IAM policies that AMS Automated IAM Provisioning creates. Statement contains privileged actions deﬁned by your organization for Service_Name . Consider excluding these actions with a deny This ﬁnding is generated when automatio n detects any action in your policy that you deﬁned in the custom deny list. To resolve statement. Refer to the policy named in your the ﬁnding, review your policy statement and account for reference to the restricted list of remove any actions that are deﬁned in your actions. custom deny list or add a deny statement that The role must have POLICY_ARN attached. Include the policy ARN in the list of managed policy ARNs. denies those actions. This ﬁnding is generated if the role that you're creating doesn't have the POLICY_ARN attached to it. To resolve this, include the POLICY_ARN in the ManagedPolicyArns ﬁeld of the role and try again. Automated IAM Provisioning Version May 08, 2025 222 AMS Advanced User Guide AMS Advanced Concepts and Procedures Finding Description The POLICY_ARN can not be detached from the role. Include the policy ARN in the list of This ﬁnding is generated if the POLICY_ARN is detached from the role during an update. managed policy ARNs. To resolve this, add the POLICY_ARN to the ManagedPolicyArns ﬁeld of the role and try again. AMS Automated IAM Provisioning permission boundary check AMS permission boundary checks
ams-ug-078	ams-ug.pdf	78	attached to it. To resolve this, include the POLICY_ARN in the ManagedPolicyArns ﬁeld of the role and try again. Automated IAM Provisioning Version May 08, 2025 222 AMS Advanced User Guide AMS Advanced Concepts and Procedures Finding Description The POLICY_ARN can not be detached from the role. Include the policy ARN in the list of This ﬁnding is generated if the POLICY_ARN is detached from the role during an update. managed policy ARNs. To resolve this, add the POLICY_ARN to the ManagedPolicyArns ﬁeld of the role and try again. AMS Automated IAM Provisioning permission boundary check AMS permission boundary checks help you adhere to the default permission boundary policy provided by AMS. This policy is a list of actions denied by AMS Automated IAM Provisioning. Provisioning policies that contain these restricted actions require additional explicit risk acceptance. Download the policy here: boundary-policy.zip. Use customer-deﬁned permission boundary policy checks to customize deny actions beyond the AMS permission boundary policy defaults. When you onboard to AMS Automated IAM Provisioning using the following change type: Management \| Managed account \| AMS Automated IAM Provisioning with read-write permissions \| Enable (review required) (ct-1706xvvk6j9hf), you can include a list of custom deny actions that specify additional restricted actions. You can update the list of deny actions using the change type: Management \| Managed account \| Automated IAM provisioning with read-write permissions \| Update custom deny list (ct-2r9xvd3sdsic0). You must use the dedicated IAM role AWSManagedServicesIAMProvisionAdminRole to run this change type. Note • You must provide a comprehensive list of deny actions for each update. The previous list is replaced by the new list. • The list of deny actions must contain only actions to be denied. Allow actions aren't supported. • The list of deny actions resides within the account as an IAM managed policy named AWSManagedServicesIAMProvisionCustomerBoundaryPolicy. The policy must not be attached to any role. Automated IAM Provisioning Version May 08, 2025 223 AMS Advanced User Guide AMS Advanced Concepts and Procedures • The term permission boundary used to denote denied actions in AMS Automated IAM Provisioning has a diﬀerent contextual meaning compared to the IAM permission boundary. The IAM permission boundary sets the maximum permission that a policy can grant at runtime to an IAM entity. For more information on IAM permission boundary see Policy types in the AWS Identity and Access Management User Guide. The permission boundary in AMS Automated IAM Provisioning prevents you from provisioning an IAM policy that contains a certain set of permissions, for example, a denied list of actions. Troubleshooting AMS Automated IAM Provisioning fndings and errors There are three ways you might run into problems when using AMS Automated IAM Provisioning: • RFC errors: These can happen for a variety of reasons; for example, incorrect input. For more information, see Troubleshooting RFC errors in AMS. • SSM errors: These can happen for a variety of reasons; for example, poor formatting. For more information, see Troubleshooting Systems Manager Automation. • Validation check ﬁndings: These occur when one of the many validation checks that Automated IAM Provisioning runs ﬁnds a problem. For a list of validation checks, and recommended actions to ﬁx, see Runtime checks for AMS Automated IAM Provisioning in AMS. Setting permissions in AMS with IAM roles and proﬁles AMS uses AWS Identity and Access Management (IAM) to manage users, security credentials such as access keys, and permissions that control which AWS resources users and applications can access. AMS provides a default IAM user role and a default Amazon EC2 instance proﬁle (which includes a statement allowing the resource access to the default IAM user role). Requesting a new IAM user role or instance proﬁle AMS uses an IAM role to set user permissions through your federation service and an IAM instance proﬁle as a container for that IAM role. You can request, with an AMS service request, or a Management \| Other \| Other \| Create CT, a custom IAM role or instance proﬁle. See the descriptions of each in this section. Setting permissions with IAM roles and proﬁles Version May 08, 2025 224 AMS Advanced User Guide AMS Advanced Concepts and Procedures Note AMS has an IAM policy, customer_deny_policy that blocks out dangerous namespaces and actions. This policy is attached to all AMS customer roles by default and is rarely a problem for users. Your IAM user and role requests don't include this policy, but automatic inclusion of the customer_deny_policy in requests for IAM roles helps AMS deploy new IAM instance proﬁles more quickly. You can request the exclusion of the customer_deny_policy policy. However, this request will go through a weighty security review and is likely to be declined due to security reasons. Restrict permissions with IAM role policy statements AMS uses an IAM role to set user permissions through your federation service. Single-Account Landing
ams-ug-079	ams-ug.pdf	79	actions. This policy is attached to all AMS customer roles by default and is rarely a problem for users. Your IAM user and role requests don't include this policy, but automatic inclusion of the customer_deny_policy in requests for IAM roles helps AMS deploy new IAM instance proﬁles more quickly. You can request the exclusion of the customer_deny_policy policy. However, this request will go through a weighty security review and is likely to be declined due to security reasons. Restrict permissions with IAM role policy statements AMS uses an IAM role to set user permissions through your federation service. Single-Account Landing Zone AMS: See SALZ: Default IAM User Roles. Multi-Account Landing Zone AMS: See MALZ: Default IAM User Roles. An IAM role is an IAM entity that deﬁnes a set of permissions for making AWS service requests. IAM roles are not associated with a speciﬁc user or group. Instead, trusted entities assume roles, such as IAM users, applications, or AWS services such as Amazon EC2. For more information, see IAM Roles. You can scope down the desired policy for a user assuming the AMS IAM user role by using the AWS Security Token Service (STS) API operation AssumeRole by passing a more restrictive IAM policy under the Policy request ﬁeld. Example policy statements that you can use to restrict CT access are provided next. Using your conﬁgured Active Directory (AD) groups, and the AWS Security Token Service (STS) API operation AssumeRole, you can set permissions for certain users or groups, including restricting access to certain change types (CTs). You can use the policy statements shown below to restrict CT access in various ways. AMS change type statement in the default IAM instance proﬁle that allows access to all AMS API calls (amscm and amsskms) and all change types: { "Sid": "AWSManagedServicesFullAccess", "Effect": "Allow", Restrict permissions with IAM role policy statements Version May 08, 2025 225 AMS Advanced User Guide AMS Advanced Concepts and Procedures "Action": [ "amscm:", "amsskms:" ], "Resource": [ "" ] } 1. Statement to allow access and all actions for only two speciﬁed CTs, where "Action" is the AMS API operations (either amscm or amsskms), and "Resource" represents existing change type IDs and version number: { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action":amscm:, "Resource": [ "arn:aws:amscm:::changetype/ct-ID1:1.0", "arn:aws:amscm:::changetype/ct-ID2:1.0"] } ] } 2. Statement to allow access for CreateRfc, UpdateRfc, and SubmitRfc on only two speciﬁed CTs: { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action":["amscm:CreateRfc", "amscm:UpdateRfc", "amscm:SubmitRfc"], "Resource": ["arn:aws:amscm:::changetype/ct-ID1:1.0", "arn:aws:amscm:::changetype/ct-ID2:1.0"] } ] } 3. Statement to allow access for CreateRfc, UpdateRfc, and SubmitRfc on all available CTs: Restrict permissions with IAM role policy statements Version May 08, 2025 226 AMS Advanced User Guide AMS Advanced Concepts and Procedures { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action":["amscm:CreateRfc", "amscm:UpdateRfc", "amscm:SubmitRfc"], "Resource":"" } ] } 4. Statement to deny access for all actions on restricted CT and allow on other CTs: { "Version": "2012-10-17", "Statement": [ { "Effect": "Deny", "Action":amscm:" "Resource":"arn:aws:amscm:::changetype/ct-RetrictedID:1.0" }, { "Effect": "Allow", "Action":amscm:" "Resource":"" } ] } Restrict permissions with Amazon EC2 IAM instance proﬁles An IAM instance proﬁle is a container for an IAM role that you can use to pass role information to an Amazon EC2 instance when the instance starts. Currently there is one AWS Managed Services (AMS) default instance proﬁle, customer-mc-ec2- instance-profile, that grants permissions to the applications running on the instance, not to users logging into the instance. You might want to modify the default instance proﬁle, or create a new one, if you want to give an instance access to something, without granting other instances Restrict permissions with Amazon EC2 IAM instance proﬁles Version May 08, 2025 227 AMS Advanced User Guide AMS Advanced Concepts and Procedures access as well. You can request a new IAM instance proﬁle with the Management \| Applications \| IAM instance proﬁle \| Create change type (ct-0ixp4ch2tiu04). When submitting the RFC, you could fashion your own instance proﬁle and include that as the InstanceProﬁleDescription, or you could just inform AMS (using the same ﬁeld) of what changes you want. Because this is a Manual CT, AMS must approve the change and will be in contact with you about it. If you're unfamiliar with Amazon IAM policies, see Overview of IAM Policies for important information. There is also a good blog post, Demystifying Amazon EC2 Resource-Level Permissions. Note that AMS does not currently support Resource-based access control, but does support Resource-level controls using IAM role policies (for an explanation of the diﬀerence, see AWS Services That Work with IAM. Single-Account Landing Zone AMS: To see a table of permissions that the default AMS IAM instance proﬁle grants, go to EC2 IAM Instance Proﬁle. AD FS claim rule and SAML settings ActiveDirectory Federation Services (AD FS) claim rule and SAML settings for AWS Managed Services (AMS) For detailed
ams-ug-080	ams-ug.pdf	80	see Overview of IAM Policies for important information. There is also a good blog post, Demystifying Amazon EC2 Resource-Level Permissions. Note that AMS does not currently support Resource-based access control, but does support Resource-level controls using IAM role policies (for an explanation of the diﬀerence, see AWS Services That Work with IAM. Single-Account Landing Zone AMS: To see a table of permissions that the default AMS IAM instance proﬁle grants, go to EC2 IAM Instance Proﬁle. AD FS claim rule and SAML settings ActiveDirectory Federation Services (AD FS) claim rule and SAML settings for AWS Managed Services (AMS) For detailed step-by-step instructions on how to install and conﬁgure AD FS see Enabling Federation to AWS Using Windows Active Directory, ADFS, and SAML 2.0. ADFS claim rule conﬁgurations If you already have an ADFS implementation, conﬁgure following: • Relying party trust • Claims rules The relying party trust and claims rules steps are taken from Enabling Federation to AWS Using Windows Active Directory, AD FS, and SAML 2.0blog • Claims rules: • Nameid: Conﬁguration per blog post • RoleSessionName: Conﬁgure as follows • Claim rule name: RoleSessionName AD FS claim rule and SAML settings Version May 08, 2025 228 AMS Advanced User Guide AMS Advanced Concepts and Procedures • Attribute store: Active Directory • LDAP Attribute: SAM-Account-Name • Outgoing Claim Type: https://aws.amazon.com/SAML/Attributes/ RoleSessionName • Get AD Groups: Conﬁguration per blog post • Role claim: Conﬁgure as follows c:[Type == "http://temp/variable", Value =~ "(?i)^AWS-([^d]{12})-"] => issue(Type = "https://aws.amazon.com/SAML/Attributes/Role", Value = RegExReplace(c.Value, "AWS-([^d]{12})-", "arn:aws:iam::$1:saml-provider/ customer-readonly-saml,arn:aws:iam::$1:role/")); Web console You can access the AWS Web console by using the link below replacing [ADFS-FQDN] with the FQDN of your ADFS implementation. https://[ADFS-FQDN]/adfs/ls/IdpInitiatedSignOn.aspx Your IT department can deploy the above link to the user population via a Group Policy. API and CLI access with SAML How to conﬁgure API and CLI access with SAML. The python packages are sourced from the blog posts below: • NTLM: How to Implement Federated API and CLI Access Using SAML 2.0 and AD FS • Forms: How to Implement a General Solution for Federated API/CLI Access Using SAML 2.0 • PowerShell: How to Set Up Federated API Access to AWS by Using Windows PowerShell Script conﬁguration 1. Using Notepad++, change the default region to the correct region Web console Version May 08, 2025 229 AMS Advanced User Guide AMS Advanced Concepts and Procedures 2. Using Notepad++, disable SSL veriﬁcation for test and dev environments 3. Using Notepad++, conﬁgure idpentryurl https://[ADFS-FDQN]/adfs/ls/IdpInitiatedSignOn.aspx? loginToRp=urn:amazon:webservices Windows conﬁguration The instructions below are for the python packages. The credentials generated will be valid for 1 hour. 1. Download and install python (2.7.11) 2. Download and install AWS CLI tools 3. Install the AMS CLI: a. Download the AMS distributables zip ﬁle provided by your cloud service delivery manager (CSDM) and unzip. Several directories and ﬁles are made available. b. Open either the Managed Cloud Distributables -> CLI -> Windows or the Managed Cloud Distributables -> CLI -> Linux / MacOS directory, depending on your operating system, and: For Windows, execute the appropriate installer (this method only works on Windows 32 or 64 bits systems): • 32 Bits: ManagedCloudAPI_x86.msi • 64 Bits: ManagedCloudAPI_x64.msi For Mac/Linux, execute the ﬁle named: MC_CLI.sh. You can do this by running this command: sh MC_CLI.sh. Note that the amscm and amsskms directories and their contents must be in the same directory as the MC_CLI.sh ﬁle. c. If your corporate credentials are used via federation with AWS (the AMS default conﬁguration) you must install a credential management tool that can access your federation service. For example, you can use this AWS Security Blog How to Implement Federated API and CLI Access Using SAML 2.0 and AD FS for help conﬁguring your credential management tooling. API and CLI access with SAML Version May 08, 2025 230 AMS Advanced User Guide AMS Advanced Concepts and Procedures d. After the installation, run aws amscm help and aws amsskms help to see commands and options. 4. Download the required SAML script Download to c:\aws\scripts 5. Download PIP Download to c:\aws\downloads 6. Using PowerShell, install PIP <pythondir>.\python.exe c:\aws\downloads\get-pip.py 7. Using PowerShell, install boto module <pythondir\scripts>pip install boto 8. Using PowerShell, install requests module <pythondir\scripts>pip install requests 9. Using PowerShell, install requests security module <pythondir\scripts>pip install requests[security] 10. Using PowerShell, install beautifulsoup module <pythondir\scripts>pip install beautifulsoup4 11. Using PowerShell, create a folder called .aws in the users proﬁle (%userproﬁle%\.aws) mkdir .aws 12. Using PowerShell, create a credential ﬁle in the .aws folder New-Item credentials -type ﬁle –force The credentials ﬁle mustn’t have a ﬁle extension The ﬁlename must be all lowercase and have the name credentials 13. Open the credentials ﬁle with notepad and paste in the following data, specifying the correct region [default] API and CLI access with SAML Version May 08, 2025 231 AMS Advanced User Guide AMS
ams-ug-081	ams-ug.pdf	81	install requests security module <pythondir\scripts>pip install requests[security] 10. Using PowerShell, install beautifulsoup module <pythondir\scripts>pip install beautifulsoup4 11. Using PowerShell, create a folder called .aws in the users proﬁle (%userproﬁle%\.aws) mkdir .aws 12. Using PowerShell, create a credential ﬁle in the .aws folder New-Item credentials -type ﬁle –force The credentials ﬁle mustn’t have a ﬁle extension The ﬁlename must be all lowercase and have the name credentials 13. Open the credentials ﬁle with notepad and paste in the following data, specifying the correct region [default] API and CLI access with SAML Version May 08, 2025 231 AMS Advanced User Guide AMS Advanced Concepts and Procedures output = json region = us-east-1 aws_access_key_id = aws_secret_access_key = 14. Using PowerShell, the SAML script and logon <pythondir>.\python.exe c:\aws\scripts\samlapi.py Username: [USERNAME]@upn Choose the role you would like to assume Linux conﬁguration The credentials generated will be valid for 1 hour. 1. Using WinSCP, transfer the SAML script 2. Using WinSCP, transfer the Root CA certiﬁcate (ignore for test and dev) 3. Add the ROOT CA to the trusted root certiﬁcates (ignore for test and dev) $ openssl x509 -inform der -in [certname].cer -out certiﬁcate.pem (ignore for test and dev) Add contents of certiﬁcate.pem to end of /etc/ssl/certs/ca-bundle.crt ﬁle ((ignore for test dev) 4. Create .aws folder in home/ec2-user 5 [default] output = json region = us-east-1 aws_access_key_id = aws_secret_access_key = 5. Using WinSCP, transfer the credentials ﬁle to .aws folder 6. Install boto module $ sudo pip install boto 7. Install requests module $ sudo pip install requests API and CLI access with SAML Version May 08, 2025 232 AMS Advanced User Guide AMS Advanced Concepts and Procedures 8. Install beautifulsoup module $ sudo pip install beautifulsoup4 9. Copy the script to home/ec2-user Set the required permissions Execute the script: samlapi.py Restrict with network ACL A network access control list (NACL) is an optional layer of security for your VPC that acts as a ﬁrewall for controlling traﬃc in and out of one or more subnets. You might set up network ACLs with rules similar to your security groups in order to add an additional layer of security to your VPC. For more information about the diﬀerences between security groups and network ACLs, see Comparison of security groups and network ACLs. However, in AMS Managed Multi-Account Landing Zone, in order for AMS to eﬀectively manage and monitor infrastructure, the use of NACLs is limited to following scope: • NACLs are not supported in the Multi-Account Landing Zone Core accounts, i.e. Management account, Networking, Shared-Services, Logging and Security. • NACLs are supported in Multi-Account Landing Zone Application accounts as long as they are only used as a "Deny" list and have "Allow All" to allow AMS monitoring and management operations. In large scale multi-account environments, you can also leverage features like centralized egress ﬁrewalls to control outbound traﬃc and/or AWS Transit Gateway routing tables in AMS Multi- Account Landing Zone to segregate network traﬃc among VPCs. AMS on Outposts AWS Outposts is a managed hardware solution that extends AMS managed landing zones to customer data centers. With AMS support on AWS Outposts, customers seeking the cloud expertise, cost savings and standardized platform oﬀered by AMS, are no longer limited to hosting resources inside AWS Regions. With AMS on AWS Outposts, customers with on-premise Restrict with network ACL Version May 08, 2025 233 AMS Advanced User Guide AMS Advanced Concepts and Procedures requirements can now modernize on AWS, while enjoying the patching, backup, provisioning, incident management, business continuity, and cost optimization services oﬀered by AMS. Once an AWS Outposts is activated in your AMS Multi-Account Landing Zone or Single-Account Landing Zone account, you can follow existing AMS change management processes to provision and manage AWS resources. AMS-hosted infrastructure can be managed by specifying your AWS Outposts-speciﬁc subnet. AWS Outposts lifecycles can be managed directly in the AWS Outposts console using the AWS Outposts self-provision services role. For information on the role, see AWS Outposts. AWS Outposts installation and operational management The onboarding to AMS on AWS Outposts process is comprised of: 1. Outposts Planning 2. Order Validation 3. Outposts Onboarding to AMS 4. Lifecycle Management AWS Outposts planning During AWS Outposts planning, you identify AMS on AWS Outposts use cases and engage key stakeholders, including your AMS account team and AWS Outposts representatives, to align on capacity strategy. 1. Once use cases requiring AMS on AWS Outposts have been identiﬁed, engage your AMS account team to discuss capacity planning. 2. Once your AWS Outposts capacity requirements have been determined, your AMS account team engages the AWS Outposts service team to discuss AWS Outposts onboarding plan, roles and responsibilities. During this time an AWS Outposts single point of contact (SPOC) is assigned to you. The AWS Outposts SPOC assists in ﬁnalizing AWS Outposts sizing requirements. AWS Outposts order
ams-ug-082	ams-ug.pdf	82	Outposts use cases and engage key stakeholders, including your AMS account team and AWS Outposts representatives, to align on capacity strategy. 1. Once use cases requiring AMS on AWS Outposts have been identiﬁed, engage your AMS account team to discuss capacity planning. 2. Once your AWS Outposts capacity requirements have been determined, your AMS account team engages the AWS Outposts service team to discuss AWS Outposts onboarding plan, roles and responsibilities. During this time an AWS Outposts single point of contact (SPOC) is assigned to you. The AWS Outposts SPOC assists in ﬁnalizing AWS Outposts sizing requirements. AWS Outposts order validation During order validation, you create an AWS Outposts site, and order your required capacity directly in the AWS Outposts console or through your AWS Outposts account representative. AWS Outposts installation and operational management Version May 08, 2025 234 AMS Advanced User Guide AMS Advanced Concepts and Procedures Once you, the AMS account team, the AWS Outposts team are aligned, you can request the AWS Outposts self-provisioned service role using change type ID ct-3qe6io8t6jtny, to create your site and AWS Outposts order directly in the AWS Outposts console. Alternatively, you can work through the AWS Outposts SPOC to create Outpost Sites and orders. Your AWS Outposts SPOC remains to provide status updates to you and the AMS account team during site and order validation, and AWS Outposts installation. AWS Outposts onboarding to AMS Once your AWS Outposts unit is activated in your AMS managed VPC, you can request that monitors be created to track availability, capacity, exceptions and network connectivity for your Outposts hardware. By following the monitoring deployment steps described next, your AWS Outposts hardware is actively monitored by AMS. 1. Once your AWS Outposts has been installed and activated, you can request AWS Outposts- speciﬁc monitoring by submitting the following template with an RFC using the Management \| Other \| Other \| Create (ct-1e1xtak34nx76) change type. AMS operations ensures that the AWS Outposts subnet is tracked in AMS internal tooling. • AWS Outposts ID • Subnet CIDR • Recommended AWS Outposts alarms: • InstanceFamilyCapacityAvailabilityAlert • InstanceTypeCapacityAvailabilityAlert • EBSVolumeTypeCapacityAvailabilityAlert • CapacityExceptionsAlert • Direct Connect ConnectionAlert • For each of the above alerts, specify the following parameters: • Statistic ("Average" is recommended. Other options include sum, maximum, minimum, sample count and p90) • Period ("5 minutes" is recommended. Other options include 10 and 30 seconds, 1, 5, and 15 minutes, 1 and 6 hours, and 1 day) • Threshold type ("Static" is recommended. "Anomaly" are also options.) • Condition ("Whenever call count is greater than", "equal to", "less than" are also options.) AWS Outposts installation and operational management Version May 08, 2025 235 AMS Advanced User Guide AMS Advanced Concepts and Procedures • Condition Value ("25%" is conﬁgured by default. Another other positive integer is allowable.) • Notiﬁcation topic (AMS operations topics are automatically assigned. However any other, or custom, topic can also be added.) 2. Monitoring and operations Support • AMS operations monitors AWS Outposts metrics for network disconnection or component failures. AMS operations provides ﬁrst response services for AWS Outposts issues, and escalates, if needed, to Premium support or EC2 support. • AMS operations is available to address issues related to your AWS Outposts unit. 3. When EC2 instance status or system status checks fail, AMS operations follows existing processes to bring the instance back online. If the restart fails or AWS Outposts capacity is insuﬃcient, then an AMS operations team member notiﬁes you directly to determine next steps. AWS Outposts life cycle management Once AWS Outposts has been onboarded to your AMS account, you are notiﬁed if any availability, capacity, or network exceptions, occur. You can decommission AWS Outposts directly through the AWS Outposts console or the AWS Outposts SPOC. You can manage AWS Outposts directly in the AWS Outposts console using the AWS Outposts self- service provisioning service role or developer mode. You can also request AWS Outposts through your CSDM, or AWS Outposts single point of contact, (SPOC). High-availability on AWS Outposts can be achieved by deploying two or more AWS Outposts. Conﬁguring two or more AWS Outposts enables the multi-availability zone option for your Amazon Relational Database Service instances. Provisioning AMS managed resources on AWS Outposts Provisioning AWS resources hosted on AWS Outposts (for example, Amazon EC2, Amazon EMR, Amazon EKS, Amazon ECS, Amazon EBS, and Amazon S3) in AMS accounts (Single-Account Landing Zone, Multi-Account Landing Zone, and Accelerate accounts) are subject to the same AMS support levels as resources in AWS Regions. You can use AMS change management, self-service provisioning services, or developer mode to create and modify the resources created on AWS Outposts. Provisioning AMS managed resources on AWS Outposts Version May 08, 2025 236 AMS Advanced User Guide AMS Advanced Concepts and Procedures Currently, all instance types (M5/M5d, C5/C5d, R5/R5d, I3en,
ams-ug-083	ams-ug.pdf	83	AWS Outposts Provisioning AWS resources hosted on AWS Outposts (for example, Amazon EC2, Amazon EMR, Amazon EKS, Amazon ECS, Amazon EBS, and Amazon S3) in AMS accounts (Single-Account Landing Zone, Multi-Account Landing Zone, and Accelerate accounts) are subject to the same AMS support levels as resources in AWS Regions. You can use AMS change management, self-service provisioning services, or developer mode to create and modify the resources created on AWS Outposts. Provisioning AMS managed resources on AWS Outposts Version May 08, 2025 236 AMS Advanced User Guide AMS Advanced Concepts and Procedures Currently, all instance types (M5/M5d, C5/C5d, R5/R5d, I3en, G4dn), Amazon Elastic Block Store, Amazon Elastic Container Service, Amazon Elastic Kubernetes Service, Amazon EMR, Amazon Relational Database Service DBs, Application Load Balancers, and App Mesh Envoy proxy are available directly on AWS Outposts. These resources are eligible for the same AMS operations support as resources in existing regions. Limitations of AMS on AWS Outposts • Operational support for AWS Outposts-hosted resources is dependent on consistent network connectivity. AWS Outposts network disconnection prevents AMS operations from being able to troubleshoot any incidents or problems that occur on the disconnected AWS Outposts unit. For AMS on AWS Outposts service level contingencies, see the updated AWS Service Level Agreements (SLAs). • Amazon Relational Database Service: • The create RDS change type (ct-2z60dyvto9g6c), by default, enables multi-AZ and requires a DB subnet group. DB subnet groups require two subnets in two separate Availability Zones (AZ). If you have only one AWS Outposts, creating a DB subnet group is an issue since AWS Outposts are only assigned to a single AZ. To circumvent this limitation, follow these instructions: 1. Request a DB subnet group through an RFC with a Management \| Other \| Other CT, and specify the subnet on the AWS Outposts. 2. Create a custom CFN template to deploy RDS on AWS Outposts, and specify the subnet group created in the previous step. To learn more about doing this, see Custom resources. 3. Request that AMS deploy the CFN template containing the target RDS instance through the AMS CFN ingest CT (ct-36cn2avfrrj9v). 4. Note that currently, RDS for AWS Outposts does not provide metrics and logs due to a limitation of RDS Service. • Workload ingest (WIGs): Linux WIGs only works if the pre-WIGs EC2 instance is on a non-AWS Outposts subnet. The reason is because Linux WIGs creates a WIGs node in the subnet of the ﬁrst EC2 instance using m4.large, by default. As AWS Outposts doesn't have that instance type, WIGs is not able to launch its worker node. The workaround for this is to create the initial EC2 instance in a non-AWS Outposts subnet, then the target instance can be created on AWS Outposts. Moreover, currently, only Nitro-based EC2 instance types including C5, C5d, M5, M5d, R5, R5d, G4, and I3en are supported on AWS Outposts. Limitations of AMS on AWS Outposts Version May 08, 2025 237 AMS Advanced User Guide AMS Advanced Concepts and Procedures • Amazon Elastic Block Store (EBS): Create EBS Volume CT (ct-16xg8qguovg2w) does not work, as volumes get created in AWS instead of AWS Outposts as we do not provide the AWS Outposts Amazon resource number (ARN) as an input parameter to the CT. • Network connectivity: Network connectivity is your responsibility per the AWS Outposts team. • Brownﬁeld and account takeover: AWS Outposts activated in non-AMS accounts cannot be transitioned into AMS, due to the nature of AWS Outposts billing and enterprise support requirements. AMS on AWS Outposts compliance AMS on AWS Outposts compliance attestation AWS Outposts control plane has been attested to HIPAA eligible, PCI and ISO compliance. However, AMS on AWS Outposts control plane has not been attested for AWS Outposts. For this reason, customers are encouraged to pursue compliance attestation AMS on AWS Outposts environment. For controlling resource creation on the Outpost unit, customers are encouraged to segregate developer access to the Outpost, to prevent excess developer access in standard AMS managed accounts. AMS Managed Workloads requiring FedRAMP compliance Foremost, AMS management accounts must ﬁrst be assessed for regulatory compliance, since control plane data would ﬂow out of the AWS Outposts to AMS management accounts. If FedRAMP certiﬁcation is required and the AMS account structure is compliant, then it is recommended that you either utilize a datacenter vendor that already has the required certiﬁcation and owns all of the service link appliance (or already encrypts egress data). Finally, additional data protection can be put in place by working with your account team to deploy an SCP that restricts data to the AWS Outposts and prevents the creation of any in- region resources in the account hosting the Outpost. Impact on existing compliance for AMS accounts An account utilizing AWS Outposts does not need to be retested for compliance as long
ams-ug-084	ams-ug.pdf	84	and the AMS account structure is compliant, then it is recommended that you either utilize a datacenter vendor that already has the required certiﬁcation and owns all of the service link appliance (or already encrypts egress data). Finally, additional data protection can be put in place by working with your account team to deploy an SCP that restricts data to the AWS Outposts and prevents the creation of any in- region resources in the account hosting the Outpost. Impact on existing compliance for AMS accounts An account utilizing AWS Outposts does not need to be retested for compliance as long as no regulated data is being consumed and the account is logically separated. AMS management accounts can manage non-regulated and regulated accounts as long as cross account authentication/authorization and ingress/ egress data ﬂows are segregated between VPCs. AMS on AWS Outposts compliance Version May 08, 2025 238 AMS Advanced User Guide AMS Advanced Concepts and Procedures Therefore, even though both the non-compliant Outpost account and existing compliant application accounts are in the same organization (including shared services, networking, logging, master, security AMS services), the compliance application account still retains compliance since data is logically separated. AMS on AWS Outposts FAQs Which use cases qualify for AMS support on AWS Outposts? AMS on AWS Outposts can be leveraged by enterprises needing a proven cloud operating model have workloads requiring low latency (e.g., factory robot management and mainframe migration), edge computing (e.g., remote workstations and edge data streamlining), and large data transfer loads. Why should I use this feature? AMS provides monitoring of AWS Outposts hardware and ﬁrst response to any AWS Outposts hardware issue. Moreover, the following support features for all managed resources hosted on AWS Outposts: • Logging, Monitoring, Guardrails, and Event Management • Continuity Management • Security and Access Management • Patch Management • Change Management • Automated and Self-Service Provisioning Management • Incident and Problem Management • Reporting (Reporting for AWS Outposts hardware will not be initially supported with AMS on AWS Outposts) • Service Request Management • Developer Mode • Enterprise Support How do I use this feature? AWS Outposts planning: During AWS Outposts planning, you have identiﬁed AMS on AWS Outposts use cases and will engage key stakeholders, including the AMS account team and AWS Outposts representatives, to align on capacity strategy. AMS on AWS Outposts FAQs Version May 08, 2025 239 AMS Advanced User Guide AMS Advanced Concepts and Procedures Order validation: During order validation, you create an AWS Outposts site, and order your required capacity directly in the AWS Outposts console, or through your AWS Outposts account representative. AWS Outposts onboarding to AMS: Once your AWS Outposts unit is activated in your AMS managed VPC, you can request that your AWS Outposts be onboarded to your AMS account by submitting a request for change (RFC) using the template in the AMS User Guide (AWS Outposts). AMS operations then creates a subnet and monitors for your Outpost using the inputs provided on the RFC. Lifecycle management: Once AWS Outposts has been onboarded to your AMS account, you are notiﬁed of any availability, capacity, or network exceptions. You can decommission AWS Outposts directly through the AWS Outposts console or your AWS Outposts single point of contact (SPOC). What are the limitations of AMS on AWS Outposts? Data residency (e.g., country-speciﬁc data localization laws, etc.) use cases have not yet been validated for AMS on AWS Outposts. AWS Outposts activated in non-AMS accounts cannot be transitioned into AMS, due to the nature of AWS Outposts billing and Enterprise Support requirements. AWS Outposts control plane has been attested to HIPAA eligible, PCI and ISO compliance. However, AMS on AWS Outposts control plane has not been attested for AWS Outposts. For this reason, customers are encouraged to pursue compliance attestation AMS on AWS Outposts environment. Can I opt out of this feature? Provisioning AWS Outposts into your AMS environment is optional. Once deployed into your AMS account, AWS Outposts can be deprovisioned via the AWS Outposts console at any time, if no longer needed. How will AMS on AWS Outposts be billed? AMS uplift on AWS Outposts charges will be applied at the Group B tier. How will the AMS Service Level Agreement change to accommodate AWS Outposts? Incident management will be contingent on AWS Outposts availability. AWS Outposts availability is subject to customer network availability, which is the responsibility of the AMS on AWS Outposts FAQs Version May 08, 2025 240 AMS Advanced User Guide AMS Advanced Concepts and Procedures customer. AWS Outposts availability is also subject to AWS Outposts hardware uptime, which is dependent on AWS Outposts Service Level Agreements. See also AWS Outposts FAQs. Using tags in AMS Topics • AMS infrastructure automatic tagging • AMS recommended tags • Tag bulk update notes Providing tags can
ams-ug-085	ams-ug.pdf	85	AMS Service Level Agreement change to accommodate AWS Outposts? Incident management will be contingent on AWS Outposts availability. AWS Outposts availability is subject to customer network availability, which is the responsibility of the AMS on AWS Outposts FAQs Version May 08, 2025 240 AMS Advanced User Guide AMS Advanced Concepts and Procedures customer. AWS Outposts availability is also subject to AWS Outposts hardware uptime, which is dependent on AWS Outposts Service Level Agreements. See also AWS Outposts FAQs. Using tags in AMS Topics • AMS infrastructure automatic tagging • AMS recommended tags • Tag bulk update notes Providing tags can be of great value. For in-depth information, read Tagging Your Amazon EC2 Resources. RFCs that create instances, such as an Amazon S3 bucket or an AWS Elastic Load Balancer (ELB), generally provide a schema that enables you to add up to seven tags (key/value pairs); you can add more tags to your S3 bucket by submitting a Management \| Advanced stack components \| Amazon S3 storage \| Update CT. Amazon EC2, Amazon EFS, Amazon RDS, and the multi-tiered (HA Two-Tiered and HA One-Tiered) schemas allow up to ﬁfty tags. Tags are speciﬁed in the ExecutionParameters part of the schema. When using the AMS console, you must enable the Additional conﬁguration view in order to add tags. Tip Many CT schemas have a Description and Name ﬁeld near the top of the schema. Those ﬁelds are used to name the stack or stack component, they do not name the resource you are creating. Some schemas oﬀer a parameter to name the resource you are creating, and some do not. For example, the CT schema for Create Amazon EC2 stack does not oﬀer a parameter to name the Amazon EC2 instance. In order to do so, you must create a tag with the key "Name" and the value of what you want the name to be. If you do not create such a tag, your Amazon EC2 instance displays in the Amazon EC2 console without a name attribute. Using tags Version May 08, 2025 241 AMS Advanced User Guide AMS Advanced Concepts and Procedures Are there tag restrictions? Yes: • Tags are case sensitive. • The maximum key length is 128 Unicode characters. • The maximum value length is 256 Unicode characters. • The maximum number of tags per resource is 50. • The reserved preﬁx is aws:. • AWS-generated tag names and values are automatically assigned the aws: preﬁx, which you can't assign. User-deﬁned tag names have the preﬁx user: in the cost allocation report. • Use each key only once for each resource. If you attempt to use the same key twice on the same resource, your request is rejected. • Allowed characters are Unicode letters, white space, numbers, and the following special characters: + - = . _ : / Which AWS resource types support tags? See Now Organize Your AWS Resources by Using up to 50 Tags per Resource. AMS infrastructure automatic tagging AMS can tag all resources created by AMS for management purposes, in your multi-account landing zone (MALZ) and single-account landing zone (SALZ) accounts through a request for change (RFC) with the Management \| Other \| Other \| Create change type (ct-1e1xtak34nx76). This can help you in identifying resources created by AMS for management purposes. AMS can automatically identify AMS-created resources based on the naming standards and check if the resource has the following tag keys and values - "AppName", "AppId", "AMSResource", and "EnvironmentType". If the tag key does not exist, or the value is empty, those tag-keys can be created automatically by AMS with tag-value "AMSInfrastructure". You can customize the tags you want on AMS-created resources based on your organization's tagging standards. You can include your own tag-keys and tag-values when you submit the request to AMS. Follow these AWS tag naming standards: Tagging Best Practices Note For MALZ accounts, custom tagging of AMS infrastructure is supported on Application accounts only. Custom tagging on core accounts is currently not supported. AMS infrastructure automatic tagging Version May 08, 2025 242 AMS Advanced User Guide AMS Advanced Concepts and Procedures If the tag-key name you provide in your RFC, already exists on the resource, then the tag- value gets replaced with the new tag-value that you provided in the RFC. Total length of tag key:value pairs must not exceed 256 characters. Include the following information in your RFC with the Management \| Other \| Other \| Create change type (ct-1e1xtak34nx76) for tagging AMS-created resources. 1. List of multi-account landing zone or single-account landing zone accounts where you would like to tag AMS-created resources for management purposes. 2. Required tag-key name and tag-value (if needed). By default, AMS can tag with tag-key name as "EnvironmentType" and tag-value as "AMSInfrastructure". If you need a custom tag-key name and tag-value,
ams-ug-086	ams-ug.pdf	86	value gets replaced with the new tag-value that you provided in the RFC. Total length of tag key:value pairs must not exceed 256 characters. Include the following information in your RFC with the Management \| Other \| Other \| Create change type (ct-1e1xtak34nx76) for tagging AMS-created resources. 1. List of multi-account landing zone or single-account landing zone accounts where you would like to tag AMS-created resources for management purposes. 2. Required tag-key name and tag-value (if needed). By default, AMS can tag with tag-key name as "EnvironmentType" and tag-value as "AMSInfrastructure". If you need a custom tag-key name and tag-value, follow AWS tag naming standards: Tagging Best Practices These resources are currently supported by AMS infrastructure tagging: API Gateway Amazon CloudFront Amazon DynamoDB Amazon EBS Amazon EC2 Amazon OpenSearch Service Amazon Quantum Ledger Database (QLDB) Amazon Redshift Amazon RDS Amazon S3 (specific buckets only) Amazon Simple Queue Service (SQS) Amazon Simple Notification Service (SNS) Amazon VPC AWS Certificate Manager AWS CloudFormation AWS CloudTrail AWS CodeBuild AWS CodePipeline AWS Elastic Beanstalk AWS Lambda AWS Secrets Manager AWS Service Catalog AWS Systems Manager AWS WAF Regional AMS infrastructure automatic tagging Version May 08, 2025 243 AMS Advanced User Guide AMS Advanced Concepts and Procedures Elastic Load Balancing "arn:aws:s3:::awsms-a-patch-data-", "arn:aws:s3:::ams-a-log-management-", "arn:aws:s3:::cf- templates-", "arn:aws:s3:::mc-a", "arn:aws:s3:::ams-a-backup-reports-", "arn:aws:s3:::ams- a-patch-data-customer-reports-", "arn:aws:s3:::ams-a-patch-data-raw-", "arn:aws:s3:::ams- a-patch-data-reporting-", "arn:aws:s3:::ams-a-release-assets-", "arn:aws:s3:::ams-cfn-drift- remediation-", "arn:aws:s3:::ams-reporting-data-a" AMS recommended tags AMS recommends the following tags on supported resources. Starred () tags are highly recommended. Note You can use tags to schedule patching. For information, see AMS Advanced Patch Orchestrator: a tag-based patching model. AMS reserved preﬁxes AMS resource attributes must comply with certain patterns; for example, IAM instance proﬁle names, BackupVault names, tag names, and so forth, must not start with AMS reserved preﬁxes. Those reserved preﬁxes are: /aws_reserved/* ams-* /ams/* ams* AMS* Ams* aws* AWS* AWS_* AWSManagedServices* codedeploy_service_role CloudTrail* Cloudtrail* customer-mc-* eps AMS recommended tags Version May 08, 2025 244 AMS Advanced Concepts and Procedures AMS Advanced User Guide EPSDB* IAMPolicy* INGEST* LandingZone* Managed_Services* managementhost mc* MC* Mc* MMS* ms- NewAMS* Root* sentinel* Sentinel* sentinel.int. StackSet-ams* StackSet-AWS-Landing-Zone StateMachine* TemplateId* VPC_* UnhealthyInServiceBastion AMS recommended tags Supported values Notes Unconstrained. Tag key AppName* AppId* EnvironmentType * OwnerTeamEmail * Distribution list email address Identify the applications that will reside on, or require access to, the resource. This facilitates tracking and communications between AMS and you. Distinguish between development, test, and production infrastructure as the environment for the resource. Identify the distribution list email address for the team responsible for the resource. The email should not be a personal email; it must be an AMS recommended tags Version May 08, 2025 245 AMS Advanced User Guide AMS Advanced Concepts and Procedures Tag key Supported values Notes ComplianceFramewor Unconstrained k CostCenter Customer DataClassification HoursOfOperation OwnerTeam anonymous email like a distribution list. Identify which controls and policies should be applied to the resource. Identify the cost center or business unit associated with a resource (typically for cost allocation and tracking). Used by AMS customers that have resources from multiple customers (AMS sub-customers). To group resources in the managed environme nt into the speciﬁc customer they are serving. Identify a speciﬁc client on a particular group of resources or services. Identify the speciﬁc data-confidentiali ty level a resource supports. Identify which controls and policies should be applied to the resource. Identify the date or time a resource should be started, stopped, deleted, or rotated. Identify the team responsible for the resource. Facilitates communication with the team responsible for the resource. AMS recommended tags Version May 08, 2025 246 AMS Advanced User Guide AMS Advanced Concepts and Procedures Tag key Supported values Notes Patch Group You have two options: What resources to include in an automated patching maintenance • You can submit window. a service request with the informati on outlined in AMS Advanced Patch Orchestrator: a tag- based patching model, and AMS creates on your speciﬁed resources, and using the information you provide, a Patch Group tag for you. • If you have already created a Patch Group tag on your resources, the supported values are unconstrained. ProjectId Unconstrained Identify the projects the resource supports. AMS recommended tags Version May 08, 2025 247 AMS Advanced User Guide AMS Advanced Concepts and Procedures Tag key Supported values Notes SupportPriority One of six possible acronyms for Conﬁdent Identify which type of support should be priority: Conﬁdentiality, Integrity, or iality, Integrity, or Availability. Availability; the order of the acronym is the priority. For example, I.C.A. would mean the order is Integrity, Conﬁdentiality, Availabil ity. Other acceptable values are C.I.A., C.A.I., I.A.C., A.C.I., and A.I.C. Tag bulk update notes These notes are for use with the Tag \| Bulk Update and Tag \| Bulk Update (Review Required) change type example walkthroughs. Notes on bulk update tags: • Supported services: • For Tag \| Bulk Update (Review
ams-ug-087	ams-ug.pdf	87	Tag key Supported values Notes SupportPriority One of six possible acronyms for Conﬁdent Identify which type of support should be priority: Conﬁdentiality, Integrity, or iality, Integrity, or Availability. Availability; the order of the acronym is the priority. For example, I.C.A. would mean the order is Integrity, Conﬁdentiality, Availabil ity. Other acceptable values are C.I.A., C.A.I., I.A.C., A.C.I., and A.I.C. Tag bulk update notes These notes are for use with the Tag \| Bulk Update and Tag \| Bulk Update (Review Required) change type example walkthroughs. Notes on bulk update tags: • Supported services: • For Tag \| Bulk Update (Review Required): All. • For Tag \| Bulk Update: • Auto Scaling • Amazon EC2 • Elastic Load Balancing • Amazon RDS • Amazon S3 buckets • To generate the comma-separated values (CSV) ﬁle, log in to Resource Groups > Tag Editor in the AWS console, ﬁnd the resources you want to tag, and then export them to a CSV ﬁle. For more information, see Export Results to CSV. NOTE: We recommend using an S3 pre-signed URL for providing the CSV object location. Tag bulk update notes Version May 08, 2025 248 AMS Advanced User Guide AMS Advanced Concepts and Procedures • There must be columns with the headers Service, Type, and Identiﬁer. These columns are mandatory. • Rename the column Identiﬁer to ID. • The values for columns Service, Type, and Identiﬁer (changed to ID) are as provided by the Tag Editor under Resource Groups. • If a resource to be tagged is not available under the Tag Editor, use the Amazon Resource Name (ARN) of the resource for the column Identiﬁer (changed to ID) and keep Service and Type blank. • The column headers of the tags to be added or modiﬁed must have the format Tag: TagKey. • The column headers of the tags to be deleted must have the format Untag: TagKey. • Each row is for a resource to be tagged or untagged. • If a tag is to be added to a resource, specify the value of the tag under the appropriate Tag: TagKey column. • If a tag is to be deleted from a resource, specify True under the appropriate Untag: TagKey column. • If a Tag: TagKey or Untag: TagKey is not applicable for a resource, add a dash (-) to the respective column or keep it blank. NOTE: The Untag overrides the Tag - this is because, unlike Tag, Untag needs to be manually added to the CSV ﬁle, so we assume the intention was to remove, not modify, the tag. • Any additional columns that don't ﬁt the criteria are ignored. Important The Tag Editor export populates a matrix of all tags against all resources, missing tags are populated with a value of 'not tagged'. Re-using this export CSV as input to the RFC results in all the previously missing tags being created, with literal values of 'not tagged'. Tag bulk update notes Version May 08, 2025 249 AMS Advanced User Guide AMS Advanced Concepts and Procedures Note For information about exporting tags to a CSV ﬁle, see Find Resources to Tag -> Export Results to CSV. AWS Managed Services Resource Scheduler Use AWS Managed Services (AMS) Resource Scheduler to schedule the automatic start and stop of AutoScaling groups, Amazon EC2 instances, and RDS instances in your account. This helps reduce infrastructure costs where the resources are not meant to be running 24/7. The solution is built on top of Instance Scheduler on AWS, but contains additional features and customizations speciﬁc to AMS needs. Note By default, AMS Resource Scheduler doesn't interact with resources that aren't part of an AWS CloudFormation stack. The resource must be part of a stack that starts with "stack-" , "sc-" or "SC-". To schedule the resources that are not part of a CloudFormation stack, you can update the Resource Scheduler stack parameter ScheduleNonStackResources to Yes. AMS Resource Scheduler uses periods and schedules: • Periods deﬁne the times when Resource Scheduler runs, such as start time, end time, and days of the month. • Schedules contain your deﬁned periods, along with additional conﬁgurations, such as SSM maintenance window, timezone, hibernate setting, and so forth; and specify when resources should run, given the conﬁgured period rules. You can conﬁgure these periods and schedules using AMS Resource Scheduler's automated change types (CTs). For full details on the settings available for AMS Resource Scheduler, see the corresponding AWS Instance Scheduler documentation at Solution components. For an architectural view of Resource Scheduler Version May 08, 2025 250 AMS Advanced User Guide AMS Advanced Concepts and Procedures the solution, see the corresponding AWS Instance Scheduler documentation at Architecture overview.html. Deploying AMS Resource Scheduler To deploy AMS Resource Scheduler, use the automated change type (CT) : Deployment \| AMS Resource Scheduler \|
ams-ug-088	ams-ug.pdf	88	when resources should run, given the conﬁgured period rules. You can conﬁgure these periods and schedules using AMS Resource Scheduler's automated change types (CTs). For full details on the settings available for AMS Resource Scheduler, see the corresponding AWS Instance Scheduler documentation at Solution components. For an architectural view of Resource Scheduler Version May 08, 2025 250 AMS Advanced User Guide AMS Advanced Concepts and Procedures the solution, see the corresponding AWS Instance Scheduler documentation at Architecture overview.html. Deploying AMS Resource Scheduler To deploy AMS Resource Scheduler, use the automated change type (CT) : Deployment \| AMS Resource Scheduler \| Solution \| Deploy (ct-0ywnhc8e5k9z5) to raise an RFC that then deploys the solution in your account. Once the RFC is executed, a CloudFormation stack containing AMS Resource Scheduler resources with default conﬁguration, is automatically provisioned into your account. For more on Resource Scheduler change types, see AMS Resource Scheduler. Note To ﬁnd out if AMS Resource Scheduler is already deployed in your account, check the AWS Lambda console for that account and look for the AMSResourceScheduler function. After the AMS Resource Scheduler is provisioned in your account, we recommend you review the default conﬁguration and, if required, customize conﬁgurations such as tag key, timezone, scheduled services, and so forth, based on your preferences. For details on the recommended customizations, see Customizing AMS Resource Scheduler, next. To make the custom conﬁgurations, or just conﬁrm the Resource Scheduler conﬁguration, Customizing AMS Resource Scheduler We recommend you customize the following properties of AMS Resource Scheduler using the update AMS Resource Scheduler change types, see AMS Resource Scheduler. • Tag name: The name of the tag that Resource Scheduler will use to associate instance schedules with resources. The default value is Schedule. • Scheduled Services: A comma-separated list of services that Resource Scheduler can manage. The default value is "ec2,rds,autoscaling". Valid values are "ec2", "rds" and "autoscaling" • Default timezone: Specify the default time zone for the Resource Scheduler to use. The default value is UTC. • Use CMK: A comma-separated list of Amazon KMS Customer Managed Key (CMK) ARNs that Resource Scheduler can be granted permissions to. Deploying Resource Scheduler Version May 08, 2025 251 AMS Advanced User Guide AMS Advanced Concepts and Procedures • Use LicenseManager: A comma-separated list of AWS Licence Manager ARNs to that Resource Scheduler can be granted permissions to. Note AMS may, time to time, release features and ﬁxes to keep AMS Resource Scheduler up to date in your account. When this happens, any customization that you make to the AMS Resource Scheduler are preserved. Using AMS Resource Scheduler To conﬁgure AMS Resource Scheduler after the solution is deployed, use the automated Resource Scheduler CTs to create, delete, update, and describe (get details on) AMS Resource Scheduler periods (the times when Resource Scheduler runs) and schedules (the conﬁgured periods and other options). For an example of using the AMS Resource Scheduler change types, see AMS Resource Scheduler. To select resources to be managed by AMS Resource Scheduler, following deployment and schedule creation, you use the AMS Tag Create CTs to tag Auto Scaling groups, Amazon RDS stacks, and Amazon EC2 resources with that tag key you provided during deployment, and the deﬁned schedule as the tag value. After the resources are tagged, the resources are scheduled for start or stop per your deﬁned Resource Scheduler schedule. There is no additional cost to using AMS Resource Scheduler. However the solution makes use of several AWS services and you're charged for these resources as they are used. For more details, see Architecture overview. To opt out temporarily or completely of AMS Resource Scheduler, submit a Management \| Other \| Other \| Update RFC requesting to disable or remove the solution from our release automation system. AMS Resource Scheduler cost estimator In order to track cost savings, AMS Resource Scheduler features a component that hourly calculates the estimated cost savings for Amazon EC2 and RDS resources that are managed by scheduler. This cost savings data is then published as a CloudWatch metric (AMS/ResourceScheduler) to help Using Resource Scheduler Version May 08, 2025 252 AMS Advanced User Guide AMS Advanced Concepts and Procedures you track it. The cost savings estimator only estimates savings on instance running hours. It does not account any other cost, such as data transfer costs associated with a resource. The cost savings estimator is enabled with Resource Scheduler. It runs hourly and retrieves cost and usage data from AWS Cost Explorer. From that data it calculates the average cost per hour for each instance type and then projects the cost for a full day if it was running without being scheduled. The cost savings is the diﬀerence between the projected cost and the actual reported cost from Cost Explorer for a given day. For example, if instance A
ams-ug-089	ams-ug.pdf	89	savings on instance running hours. It does not account any other cost, such as data transfer costs associated with a resource. The cost savings estimator is enabled with Resource Scheduler. It runs hourly and retrieves cost and usage data from AWS Cost Explorer. From that data it calculates the average cost per hour for each instance type and then projects the cost for a full day if it was running without being scheduled. The cost savings is the diﬀerence between the projected cost and the actual reported cost from Cost Explorer for a given day. For example, if instance A is conﬁgured with Resource Scheduler to run from 9 a.m. to 5 p.m., that is eight hours on a given day. Cost Explorer reports the cost as $1 and usage as 8. The average cost per hour is therefore $0.125. If the instance was not scheduled with Resource Scheduler, then the instance would run 24 hours on that day. In that case, the cost would have been 24x0.125 = $3. Resource Scheduler helped you achieve a cost savings of $2. In order for the cost savings estimator to retrieve cost and usage only for resources managed by Resource Scheduler from Cost Explorer, the tag key that Resource Scheduler uses to target resources needs to be activated as the Cost allocation tag in the Billing Dashboard. If the account belongs to an organization, the tag key needs to be activated in the Management account of the organization. For information on doing this, see Activating User-Deﬁned Cost Allocation Tags and User-Deﬁned Cost Allocation Tags After the tag key is activated as Cost Allocation Tag, AWS billing starts tracking cost and usage for resources managed by Resource Scheduler, and after that data is available, the cost savings estimator starts to calculate the cost savings and publish the data under the AMS/ ResourceScheduler metric namespace in CloudWatch. Cost estimator tips Cost Savings Estimator does not accept discounts such as reserved instances, savings plans, and so forth, into consideration in its calculation. The Estimator takes usage costs from Cost Explorer and calculates the average cost per hour for the resources. For more details, see Understanding your AWS Cost Datasets: A Cheat Sheet In order for the cost savings estimator to retrieve cost and usage only for resources managed by Resource Scheduler from Cost Explorer, the tag key that Resource Scheduler uses to target resources needs to be activated as the Cost Allocation tag in the Billing Dashboard. If the account belongs to an organization, the tag key needs to be activated in the management account of the organization. For information on doing this, see User-Deﬁned Cost Allocation Tags. If the cost AMS Resource Scheduler cost estimator Version May 08, 2025 253 AMS Advanced User Guide AMS Advanced Concepts and Procedures allocation tag is not activated, the estimator is not able to calculate the savings and publish the metric, even if it is enabled. AMS Resource Scheduler best practices Scheduling Amazon EC2 Instances • Instance shut down behavior must be set to stop and not to terminate. This is pre-set to stop for instances that are created with the AMS Amazon EC2 Create automated change type (ct-14027q0sjyt1h) and can be set for Amazon EC2 instances created with AWS CloudFormation ingestion, by setting the InstanceInitiatedShutdownBehavior property to stop. If instances have shut down behavior set to terminate, then the instances will end when the Resource Scheduler stops them and the scheduler won't be able to start them back up. • Amazon EC2 instances that are part of an Auto Scaling group aren't processed individually by AMS Resource Scheduler, even if they are tagged. • If the target instance root volume is encrypted with a KMS customer master key (CMK), an additional kms:CreateGrant permission needs to be added to your Resource Scheduler IAM role, for the scheduler to be able to start such instances. This permission is not added to the role by default for improved security. If you require this permission, submit an RFC with the Management \| AMS Resource Scheduler \| Solution \| Update change type, and specify a comma separated list of ARNs of the KMS CMKs. Scheduling Auto Scaling groups • AMS Resource Scheduler starts or stops the auto scaling of Auto Scaling groups, not individual instances in the group. That is, the scheduler restores the size of the Auto Scaling group (start) or sets the size to 0 (stop). • Tag AutoScaling group with the speciﬁed tag and not the instances within the group. • During stop, AMS Resource Scheduler stores the Auto Scaling group's Minimum, Desired, and Maximum capacity values and sets the Minimum and Desired Capacity to 0. During start, the scheduler restores the Auto Scaling group size as it was during the stop. Therefore, Auto Scaling group instances must use
ams-ug-090	ams-ug.pdf	90	starts or stops the auto scaling of Auto Scaling groups, not individual instances in the group. That is, the scheduler restores the size of the Auto Scaling group (start) or sets the size to 0 (stop). • Tag AutoScaling group with the speciﬁed tag and not the instances within the group. • During stop, AMS Resource Scheduler stores the Auto Scaling group's Minimum, Desired, and Maximum capacity values and sets the Minimum and Desired Capacity to 0. During start, the scheduler restores the Auto Scaling group size as it was during the stop. Therefore, Auto Scaling group instances must use an appropriate capacity conﬁguration so that the instances' termination and relaunch don't aﬀect any application running in the Auto Scaling group. • If the Auto Scaling group is modiﬁed (the minimum or maximum capacity) during a running period, the scheduler stores the new Auto Scaling group size and uses it when restoring the group at the end of a stop schedule. AMS Resource Scheduler best practices Version May 08, 2025 254 AMS Advanced User Guide AMS Advanced Concepts and Procedures Scheduling Amazon RDS instances • The scheduler can take a snapshot before stopping the RDS instances (does not apply to Aurora DB cluster). This feature is turned on by default with the Create RDS Instance Snapshot AWS CloudFormation template parameter set to true. The snapshot is kept until the next time the Amazon RDS instance is stopped and a new snapshot is created. Scheduler can start/stop Amazon RDS instance that are part of a cluster or Amazon RDS Aurora database or in a multi availability zone (Multi-AZ) conﬁguration. However, check Amazon RDS limitation when the scheduler won't be able to stop the Amazon RDS instance, especially Multi- AZ instances. To schedule Aurora Cluster for start or stop use the Schedule Aurora Clusters template parameter (default is true). The Aurora cluster (not the individual instances within the cluster) must be tagged with the tag key deﬁned during initial conﬁguration and the schedule name as the tag value to schedule that cluster. Every Amazon RDS instance has a weekly maintenance window during which any system changes are applied. During the maintenance window, Amazon RDS will automatically start instances that have been stopped for more than seven days to apply maintenance. Note that Amazon RDS will not stop the instance once the maintenance event is complete. The scheduler allows specifying whether to add the preferred maintenance window of an Amazon RDS instance as a running period to its schedule. The solution will start the instance at the beginning of the maintenance window and stop the instance at the end of the maintenance window if no other running period speciﬁes that the instance should run, and if the maintenance event is completed. If the maintenance event is not completed by the end of the maintenance window, the instance will run until the scheduling interval after the maintenance event is completed. Note The Scheduler doesn't validate that a resource is started or stopped. It makes the API call and moves on. If the API call fails, it logs the error for investigation. AMS Resource Scheduler best practices Version May 08, 2025 255 AMS Advanced User Guide AMS Advanced Concepts and Procedures AWS Systems Manager in AMS Advanced An AWS Systems Manager document (SSM document) deﬁnes the actions that Systems Manager performs on your AWS resources. Systems Manager includes more than a dozen pre-conﬁgured documents that you can use by specifying parameters at runtime. Documents use JavaScript Object Notation (JSON) or YAML, and they include steps and parameters that you specify. AWS Managed Services (AMS) is a trusted publisher for SSM documents. SSM documents owned by AMS are shared only with onboarded AMS accounts, always begin with a reserved preﬁx (AWSManagedServices-*), and show up in the Systems Manager console, as owned by AWS. The AMS process for SSM document development and publishing follows AWS best practices and requires multiple peer reviews throughout the document life cycle. For more information on AWS best practices for sharing SSM documents, see Best practices for shared SSM documents. Available AMS Advanced SSM documents AMS Advanced SSM documents are available exclusively to AMS Advanced customers, and are used to automate operational workﬂow to operate your account. To see the available AMS Advanced SSM documents from the AWS Management Console: 1. Open the Systems Managerconsole at AWS Systems Manager console. 2. Choose Shared with me. 3. In the search bar, ﬁlter by Document name preﬁx, then Equals, and set the value to AWSManagedServices-. For AWS CLI instructions, see Using shared SSM documents. AMS Advanced SSM document versions SSM documents support versioning. AMS Advanced SSM documents can't be modiﬁed from the customer’s account and can't be re-shared. They're centrally managed and maintained by AMS Advanced in order to operate the account. Version numbers
ams-ug-091	ams-ug.pdf	91	workﬂow to operate your account. To see the available AMS Advanced SSM documents from the AWS Management Console: 1. Open the Systems Managerconsole at AWS Systems Manager console. 2. Choose Shared with me. 3. In the search bar, ﬁlter by Document name preﬁx, then Equals, and set the value to AWSManagedServices-. For AWS CLI instructions, see Using shared SSM documents. AMS Advanced SSM document versions SSM documents support versioning. AMS Advanced SSM documents can't be modiﬁed from the customer’s account and can't be re-shared. They're centrally managed and maintained by AMS Advanced in order to operate the account. Version numbers are incremented with each document update in a speciﬁc AWS Region. As new Regions become available, the same document content in two Regions can have diﬀerent version numbers; this is typical and doesn't mean their behavior will be diﬀerent. If you want to compare two AMS Advanced SSM documents, we recommend comparing their hashes with the AWS CLI: AWS Systems Manager in AMS Advanced Version May 08, 2025 256 AMS Advanced User Guide AMS Advanced Concepts and Procedures aws ssm describe-document \ --name AWSManagedServices-DOCUMENTNAME \ --output text --query "Document.Hash" Two SSM documents are identical if their hashes match. Systems Manager pricing in AMS There is no cost associated with AMS Advanced SSM document access. Runtime cost varies based on the type of SSM document, its steps, and runtime duration. For more information, refer to AWS Systems Manager pricing. Oﬀboard AMS accounts AMS oﬀers oﬀ-boarding assistance for single-account landing zone and multi-account landing zone accounts. AMS does not unshare any AMIs from you during oﬀboarding to avoid impact for any of your depedencies. If you want to remove AMS AMIs from your account, you can use the cancel- image-launch-permission API to hide speciﬁc AMIs. For example, you can use the script below to hide all of the AMS AMIs that were shared with your account earlier: for ami in $(aws ec2 describe-images --executable-users self --owners 027415890775 -- query 'Images[].ImageId' --output text) ; do aws ec2 cancel-image-launch-permission --image-id $ami ; done You must have the AWS CLI v2 installed for the script to execute without any errors. For AWS CLI installation steps, see Installing or updating the latest version of the AWS CLI. For details on the cancel-image-launch-permission command, see cancel-image-launch-permission. Note The service termination date is the last day of the calendar month following the end of the 30 days requisite termination notice period. If the end of the requisite termination notice period falls after the 20th day of the calendar month, then the service termination date Systems Manager pricing Version May 08, 2025 257 AMS Advanced User Guide AMS Advanced Concepts and Procedures is the last day of the following calendar month. The following are example scenarios for termination dates. • If the termination notice is provided on April 12, then the 30 days notice ends on May 12. The service termination date is May 31. • If a termination notice is provided on April 29, then the 30 days notice ends on May 29. The service termination date is June 30. Topics • Oﬀboard from AMS single-account landing zone accounts • Oﬀboard from AMS multi-account landing zone accounts Oﬀboard from AMS single-account landing zone accounts AMS oﬀers oﬀ-boarding assistance within 30 days prior to termination of AMS. You must request oﬀ-boarding assistance at least 7 days before such assistance can be provided. Oﬀ-boarding assistance can be oﬀered in two forms: • Control hand-over: AMS transfers account control back to you along with access credentials for all AMS-managed applications, or • Resource termination for account closure: AMS deletes all of the data in your AMS-managed environment and de-provisions any active resources in the account. When submitting the oﬀboarding request, customers can request that AMS: • Delete or retain the data objects (including logs) that are stored on Amazon S3 buckets • Remove or retain Amazon S3 buckets • Remove or retain AWS Backup restore points Important Any other speciﬁc requests (subject to plausibility) must be communicated to AMS before initialization of oﬀboarding. Optional Prerequisites (if required): Oﬀboard from single-account landing zone accounts Version May 08, 2025 258 AMS Advanced User Guide AMS Advanced Concepts and Procedures Note Prior to the oﬀboarding request, customers can request AMS assistance to transfer your data in the existing format using AWS Snowball Edge or any other media that AWS interfaces with. In addition to data backups, the following customer data can be provided as part of oﬀ-boarding assistance: • Data stored in storage services including logs • Customer-speciﬁc change type schemas • CloudFormation templates for change type schemas If oﬀ-boarding activities are not completed upon the termination of AMS, we hand over the controls of the account(s) to enable you to complete any pending activity. Function What was removed Impact Actions needed Monitoring, Logging,
ams-ug-092	ams-ug.pdf	92	oﬀboarding request, customers can request AMS assistance to transfer your data in the existing format using AWS Snowball Edge or any other media that AWS interfaces with. In addition to data backups, the following customer data can be provided as part of oﬀ-boarding assistance: • Data stored in storage services including logs • Customer-speciﬁc change type schemas • CloudFormation templates for change type schemas If oﬀ-boarding activities are not completed upon the termination of AMS, we hand over the controls of the account(s) to enable you to complete any pending activity. Function What was removed Impact Actions needed Monitoring, Logging, Alerting AMS Monitoring removed AMS no longer has access or visibility Contingencies for removed and into your resources unsubscribed services and environment. are owned by you. MMS (Managed Monitoring System) unsubscribed Resource Tagger and Alarm Manager removed Baseline CloudWatc h alerts remain on existing resources GuardDuty and Macie: Ownership reverts to you Oﬀboard from single-account landing zone accounts Version May 08, 2025 259 AMS Advanced User Guide AMS Advanced Concepts and Procedures Function What was removed Impact Actions needed Backup management AMS Backup automation is AMS no longer monitors the backup AMS Backup Plans must be reconﬁgu removed although jobs or performs red. All monitorin the AWS Backup restoration actions g and remediation service remains during incidents. ownership returns to available for use. Alarms and alerts are you. Backup vaults and disabled. Deletion of data are retained the IAM backup role unless deletion is and KMS keys render requested. your AMS backups inoperable. AMS automations for service management AMS-curated AWS SSM automation No AMS access to your accounts. All All automation including SSM, runbooks, Amazon automation disabled. SNS, and Lambda Simple Notiﬁcat ion Service (SNS), and AWS Lambda functions are no longer available. functions need to be recreated, if required. Compliance AMS visibility into and monitoring for All monitoring, reporting, and Monitoring and remediation for all GuardDuty and remediation from all security and AWS Conﬁg rules Amazon GuardDuty compliance tools to removed, although these rules remain on the accounts. and AWS Conﬁg Rules is no longer managed by AMS. be assumed by you. Oﬀboard from single-account landing zone accounts Version May 08, 2025 260 AMS Advanced User Guide AMS Advanced Concepts and Procedures Function What was removed Impact Actions needed On-instance agents Access to Resource Scheduler, Resource CloudWatch and SSM Agents on instances You manage tagging and on-instance Tagger or automated are left in place with CloudWatch and SSM instance conﬁgura existing conﬁgura agent conﬁgurations. tion to install tions however, AMS required agents in no longer assists with your EC2 instances is these conﬁgurations. removed. Patch and reporting infrastructure AMS no longer manages pre- and AMS no longer creates a snapshot You retain the Patch baselines and post- patching activities, and access of the instance prior to patching, no snapshots created in the past. Additionally, and visibility to these longer installs and the conﬁguration of services are removed. monitors the patch the patch maintenan installation, and ce windows remains no longer notiﬁes but the patches are you of the outcome. no longer installed Reports and "audit" or remediated by S3 buckets are left AMS. All reporting in your accounts on infrastructure at your request. operational metrics AMS no longer generates service metric reports. are now your responsibility. Oﬀboard from single-account landing zone accounts Version May 08, 2025 261 AMS Advanced User Guide AMS Advanced Concepts and Procedures Function What was removed Impact Actions needed Process management All accounts are oﬀboarded from the All service disruptio n formerly remediate You regain full ownership of all service managemen d by AMS through process management. t provided for incidents and incidents, including service requests, service requests, and changes to the problem, and change, environment, as management. well as Root Cause investigations, are longer managed by AMS. Oﬀboard from AMS multi-account landing zone accounts There are two types of AWS accounts that you can oﬀboard from AMS Advanced multi-account landing zone: • Application accounts • Core accounts To oﬀboard all accounts from your AMS Multi-account landing zone, you must oﬀboard all Application accounts before you oﬀboard Core accounts. To take over and continue operating workloads in oﬀboarded Application or Core accounts, make sure that you review this documentation with your AMS account team. This documentation outlines the changes that AMS performs during the oﬀboard process. Tasks to complete for continued operation of oﬀboarded accounts The following tasks are required for continued operation of accounts that you oﬀboarded from AMS multi-account landing zone: • Turn on Developer mode: To gain more permission to your accounts, turn on Developer mode before you oﬀboard Application accounts from AMS. When you turn on Developer mode, you can more easily make the necessary changes to prepare for oﬀboarding. Don’t try to remove Oﬀboard from multi-account landing zone accounts Version
ams-ug-093	ams-ug.pdf	93	you review this documentation with your AMS account team. This documentation outlines the changes that AMS performs during the oﬀboard process. Tasks to complete for continued operation of oﬀboarded accounts The following tasks are required for continued operation of accounts that you oﬀboarded from AMS multi-account landing zone: • Turn on Developer mode: To gain more permission to your accounts, turn on Developer mode before you oﬀboard Application accounts from AMS. When you turn on Developer mode, you can more easily make the necessary changes to prepare for oﬀboarding. Don’t try to remove Oﬀboard from multi-account landing zone accounts Version May 08, 2025 262 AMS Advanced User Guide AMS Advanced Concepts and Procedures or modify AMS infrastructure resources. If you delete AMS infrastructure resources, then AMS might not be able to successfully oﬀboard your account. For information about how to enable Developer mode, see Getting started with AMS Advanced Developer mode. If you can’t complete the necessary changes to prepare for oﬀboarding after you turn on Developer mode, then contact your AMS account team to discuss your requirements. • Choose an alternate method for EC2 stack access: After you oﬀboard Application accounts from AMS, you can’t use RFCs to access your stack resources. Review Oﬀboarding changes, and then choose an alternate access method so that you retain access to your stacks. For more information, see Access Alternatives. Oﬀboard AMS Application accounts To oﬀboard Application accounts from your multi-account landing zone environment, complete the following steps for each account: 1. Verify that there are no open RFCs in the account. For more information, see Create, clone, update, ﬁnd, and cancel RFCs. 2. Verify that you can access the primary or root user email address for the account. 3. From the Application account, submit an RFC with the Application Account \| Conﬁrm oﬀboarding (ct-2wlfo2jxj2rkj) change type. In the RFC, specify the Application account to oﬀboard. 4. From the Management account, submit an RFC with the Management account \| Oﬀboard Application Account (ct-0vdiy51oyrhhm) change type. In the RFC, specify the Application account to oﬀboard. Also, indicate if you want to delete or retain the transit gateway attachment to the landing zone. 5. To make sure that AMS billing is stopped, notify your CSDM that you oﬀboarded the account. The following occurs after the Application account is oﬀboarded: • All components are disassociated from AMS services, but your created resources remain in the account. You can choose to keep or close the AMS oﬀboarded account. • Core accounts and other remaining Application accounts function normally after an Application account is oﬀboarded. • AMS billing is stopped, but AWS billing isn’t stopped until you close the account. For more information, see What you need to know before closing your account. Oﬀboard from multi-account landing zone accounts Version May 08, 2025 263 AMS Advanced User Guide AMS Advanced Concepts and Procedures • If an account is closed, then the account is visible in your organization in the suspended state for 90 days. After 90 days, the closed account is permanently removed and no longer visible in your organization. • After the account is closed, you can still sign in and ﬁle a support case or contact Support for 90 days. • After 90 days, any content that remains in the account is permanently deleted and the remaining AWS services are terminated. Application account oﬀboarding FAQ Q: Can I use my federated IAM roles to continue to access an Application account that I oﬀboarded from my AMS multi-account landing zone? Yes. AMS created default AWS Identity and Access Management (IAM) roles remain available in the account after AMS oﬀboarding. However, these roles and policies are designed for use with AMS access management. To provide the necessary access for your users, you might need to deploy your own IAM resources. Q: How do I gain full access to an Application account that I oﬀboarded from my AMS multi- account landing zone? Oﬀboarded Application accounts are moved to the Deprecated Organizational Unit (OU) in the AWS Organizations account structure. This move lifts SCP access restrictions that previously blocked root user access. For information about how to reset root user credentials, see Resetting a lost or forgotten root user password. Q: What changes are made during Application account oﬀboarding? For information about actions that AMS takes when the service oﬀboards accounts, see Oﬀboarding changes. Q: Can I oﬀboard an Application account without detaching it from the transit gateway? Yes. Use the Management account \| Oﬀboard Application Account (ct-0vdiy51oyrhhm) change type to submit the RFC, and specify the DeleteTransitGatewayAttachment parameter as False. Q: How long does it take to oﬀboard an Application account? When you use the Management account \| Oﬀboard Application Account (ct-0vdiy51oyrhhm) change type, RFCs complete within 1 hour. Oﬀboard from multi-account landing zone accounts Version May 08, 2025
ams-ug-094	ams-ug.pdf	94	Q: What changes are made during Application account oﬀboarding? For information about actions that AMS takes when the service oﬀboards accounts, see Oﬀboarding changes. Q: Can I oﬀboard an Application account without detaching it from the transit gateway? Yes. Use the Management account \| Oﬀboard Application Account (ct-0vdiy51oyrhhm) change type to submit the RFC, and specify the DeleteTransitGatewayAttachment parameter as False. Q: How long does it take to oﬀboard an Application account? When you use the Management account \| Oﬀboard Application Account (ct-0vdiy51oyrhhm) change type, RFCs complete within 1 hour. Oﬀboard from multi-account landing zone accounts Version May 08, 2025 264 AMS Advanced User Guide AMS Advanced Concepts and Procedures Q: Is it mandatory that I close the oﬀboarded account? No. Account closure after AMS oﬀboarding isn’t mandatory. During the oﬀboarding process, AMS removes its access and management of your AWS account, but your account and your resources within the account remain. It's important to note that after AMS oﬀboarding, you’re solely responsible for managing and maintaining your AWS account and resources. AMS isn’t responsible for any issues, incidents, or service disruptions that might occur in your account after the oﬀboarding process is complete. For more information, see How do I close my AWS account?. Q: If I submit an account closure request, are all existing resources deleted immediately? No. Account closure doesn’t terminate your resources. Resources in the account automatically terminate 90 days after the closure request. AMS billing stops, but AWS resource billing doesn’t stop until you close the account. For more information, see What you need to know before closing your account. Q: Can I schedule the oﬀboarding of an Application account? Yes. You can schedule the RFCs to run at a speciﬁc time. However, the Application Account \| Conﬁrm oﬀboarding RFC must complete before you can schedule the Management account \| Oﬀboard Application Account RFC. For more information, see RFC scheduling. Application account oﬀboarding RACI • R: Responsible party. The party responsible for completing the listed task. • A: Accountable party. The party that approves the completed task. • C: Consulted party. A party whose opinions are sought, typically as subject matter experts, and with whom there is bilateral communication. • I: Informed party. A party that’s informed on progress, often only on completion of the task or deliverable. Activity Prerequisites CustomerAWS Managed Services (AMS) Oﬀboard from multi-account landing zone accounts Version May 08, 2025 265 AMS Advanced User Guide AMS Advanced Concepts and Procedures Activity CustomerAWS Managed Services (AMS) Verify access to the root email address for each AWS account ID that will be oﬀboarded Review AMS documentation on recommended customer actions and prepare accounts for AMS oﬀboarding If needed, submit an RFC to enable Developer mode to prepare accounts for AMS oﬀboarding If needed, choose an alternate method for EC2 stack access. Oﬀboarding Submit RFCs to conﬁrm and request oﬀboarding of Application accounts Oﬀboard AMS components from Application accounts Notify AMS CSDM of oﬀboarded accounts to stop AMS billing Post-oﬀboarding Reset root user account password and verify root access in oﬀboarded accounts Close the account or follow AMS guidance on recommended customer actions in the AMS oﬀboarding documentation to continue operating the accounts R R R R R I R R R C C I I I R I C C Oﬀboard Core accounts To oﬀboard multi-account landing zone Core accounts, complete the following steps: 1. Verify that all Application accounts in the landing zone were oﬀboarded from AMS. Oﬀboard from multi-account landing zone accounts Version May 08, 2025 266 AMS Advanced User Guide AMS Advanced Concepts and Procedures 2. Verify that you have no open RFCs in the accounts. For more information, see Create, clone, update, ﬁnd, and cancel RFCs. 3. Verify that you can access the primary or root user email address for all Core accounts. For more information, see Multi-Account Landing Zone accounts. 4. Verify that you can access the primary or root user phone number for the management account. Use the AWSManagedServicesBillingRole IAM role to update the phone number. For more information, see How do I update my telephone number that's associated with my AWS account?. 5. Log in to your AMS landing zone management account and submit an AMS service request. In the service request, specify to oﬀboard your entire landing zone. The following occurs after the Core accounts are oﬀboarded: • All components are disassociated from AMS services, but some AWS resources remain in the account. You can choose to keep or close the AMS oﬀboarded Core accounts. • AMS billing is stopped, but AWS billing isn’t stopped until you close the account. For more information, see What you need to know before closing your account. • If an account is closed, then the account is visible in your organization in the suspended state for 90 days. After

Subsets and Splits

No community queries yet

The top public SQL queries from the community will appear here once available.