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-ct-769	ams-ct.pdf	769	Managed landing zone \| Management account \| Oﬀboard applicati on account Note added: After conﬁrming the oﬀboarding you have 48 hours to run the oﬀboarding change type. If not run in 48 hours, the conﬁrmation is dropped and the process must be restarted. Management \| Custom Stack \| Stack from CloudForm ation Template \| Remediate drift The list of resources supported for this CT was added. Management \| Host security \| Trend Micro DSM \| Update agent status (review required). Management \| Host security \| Trend Micro \| Add User (review required). February 20, 2025 February 20, 2025 February 20, 2025 February 20, 2025 Version April 22, 2025 3012 AMS Advanced Change Type Reference AMS Advanced Change Type Details Updated change type: Deployment \| Standalon A note was added that, in order to use the AWS e resources \| EC2 instance Marketplace AMI you must \| Create for WIGS (Review subscribe to the AMI from January 23, 2025 Required) that account, and then agree to the terms of the AMI. AMS can not perform these actions for you because as a buyer you perform these actions yourself. New change type: Management \| Monitorin Change type for requesting that AMS update an SNS topic January 23, 2025 g and notiﬁcation \| SNS \| in your account for you. Use Update (Review Required) this when you need extra help or communications about the SNS topic to update. New change type: Management \| Advanced Change type for requestin g that AMS delete EBS stack components \| EBS snapshots for you. Use this snapshot \| Delete (Review when you need extra help or Required) communications about the snapshots to delete. January 23, 2025 New change type: Deploymen t \| Advanced stack component Change type for creating an S3 access point. January 23, 2025 s \| S3 access point \| Create New change type parameter January 23, 2025 Deployment \| Advanced stack components \| S3 storage \| Create and Management \| Advanced stack component s \| S3 storage \| Update Change types for creating and updating S3 storage, new parameter for tags. Version April 22, 2025 3013 AMS Advanced Change Type Reference AMS Advanced Change Type Details Updated change type: Deployment \| Advanced stack components \| RDS database stack \| Create DB subnet group "pattern" is removed from the December 19, 2024 Keys and Tags sections of the CT schema. Updated change type: Deployment \| AMS Resource Scheduler \| Solution \| Deploy Parameters MemorySize and SchedulerFrequency added to the CT schemas. December 19, 2024 Default values are 512MB and 10 mins, respectively. A new version of this change type is now available. November 21, 2024 A new version of this change type is now available. November 21, 2024 Updated change type: Management \| Advanced stack components \| Target group \| Detach instances Updated change type: Management \| Advanced stack components \| S3 storage \| Update Updated change type: Deployment \| Advanced stack A new version of this change type is now available. November 21, 2024 components \| S3 storage \| Create Version April 22, 2025 3014 AMS Advanced Change Type Reference AMS Advanced Change Type Details Updated change type November 21, 2024 The ExpectedExecutionD was urationInMinutes updated from 60 to 240 for the following 35 change types: • ct-3dpd8mdd9jn1r • ct-2epp05svrlwod (v1, v2, v3) • ct-220bdb8blaixf • ct-1oxx2g2d7hc90 (v1, v2) • ct-2jndrh7uit8uf • ct-1urj94c3hdfu5 • ct-08avsj2e9mc7g • ct-25v6r7t8gvkq5 • ct-36emj2uapfbu8 (v1, v2) • ct-211l2gxvsrrhy • ct-2aaaqid7asjy6 • ct-30j78u6li9aqr • ct-27tuth19k52b4 • ct-2zxya20wmf5bf (v1, v2) • ct-05yb337abq3x5 • ct-3ovo7px2vsa6n (v1, v2, v3) • ct-27jjy5wnrfef2 • ct-31eyj2hlvqjwu • ct-0ttx8eh3ice91 • ct-0fpjlxa808sh2 (v1, v2) • ct-3cp96z7r065e4 • ct-3memthlcmvc1b • ct-0ixp4ch2tiu04 • ct-1ay83wy4vxa3k Version April 22, 2025 3015 AMS Advanced Change Type Reference AMS Advanced Change Type Details • ct-3qe6io8t6jtny • ct-1pybwg08h8qsz • ct-1706xvvk6j9hf • ct-2r9xvd3sdsic0 • ct-3gjfayulf5hhs • ct-2tqi3kjcusen4 • ct-1b8fudnqq7m8r • ct-07jzw8bzd2on7 • ct-2qjqju7h67s7w • ct-2rnjx5yd6jgpt • ct-34sxfo53yuzah Change Type description is updated to reﬂect that this CT is used to update read-only access. Change Type description is updated to reﬂect that this CT is used to update stack admin access. The restriction to delete snapshots creates less than 60 days ago is changed to less than 30 days ago. Added an optional parameter for S3 URI of a bucket that belongs to the same AWS account. The invalid snapshots report is uploaded to this bucket. October 24, 2024 October 24, 2024 October 24, 2024 Updated change type Updated change type Updated change type Version April 22, 2025 3016 AMS Advanced Change Type Reference AMS Advanced Change Type Details New change type New change type to create a custom RDS parameter group and optionally attach it to an existing RDS instance. August 30, 2024 Updated change type Updated the change type description. August 9, 2024 Update change type Version two of this change type is now available.
ams-ct-770	ams-ct.pdf	770	of a bucket that belongs to the same AWS account. The invalid snapshots report is uploaded to this bucket. October 24, 2024 October 24, 2024 October 24, 2024 Updated change type Updated change type Updated change type Version April 22, 2025 3016 AMS Advanced Change Type Reference AMS Advanced Change Type Details New change type New change type to create a custom RDS parameter group and optionally attach it to an existing RDS instance. August 30, 2024 Updated change type Updated the change type description. August 9, 2024 Update change type Version two of this change type is now available. May 22, 2024 New change type Deprecated change type Earlier updates May 22, 2024 April 8, 2024 New change type to add an event notiﬁcation to the speciﬁed S3 bucket through direct API calls. Deployment \| Advanced stack components \| AWS Identity and Access Management (IAM) \| Create Entity or Policy (Read Permissions) The following table describes the important changes to the documentation of the AMS Change Type Reference Guide prior to March 2024. • API version: 2019-05-21 Change Description New CT Management \| Managed account \| Automated IAM provisioning with read-write permissions \| Update custom deny list (review required). New CT. Link(s) ct-2r9xvd 3sdsic0 Earlier updates Version April 22, 2025 3017 AMS Advanced Change Type Reference AMS Advanced Change Type Details Change Description Link(s) Updated CT Management \| Managed landing zone \| Management account \| Oﬀboard application account. ct-0vdiy5 1oyrhhm Updated CT. New CT Management \| Managed Account \| DNS \| Migrate to Route 53. ct-2tqi3k jcusen4 New CT. Updated CT Management \| Advanced Stack Components \| EBS Volume \| Delete. ct-3e3h8u 0sp5z80 Updated CT. Updated CT Deployment \| Managed landing zone \| Networking account \| Add static route. ct-3r2ckz nmt0a59 Updated Additional Information section. Updated CT Deployment \| Advanced Stack Components \| Identity and Access Management (IAM) \| Create Service-Linked role. ct-2eof6j 3mlcwhf Added CustomSuffix input parameter. Updated CT Deployment \| Managed Landing Zone \| Management Account \| Create Custom SCP (review required). ct-33ste5 yc7hprs Added a note in the Tips section. New CT Management \| Advanced Stack Components \| Route 53 Resolver \| Disassociate resolver rules from VPC. ct-2pfarp vczsstr New CT. Updated CT Management \| Patching \| Patch window \| Update. Updated CT. ct-2utx36 abv83pv Earlier updates Version April 22, 2025 3018 AMS Advanced Change Type Reference AMS Advanced Change Type Details Change Description Link(s) Updated CT Management \| Advanced Stack Components \| RDS database stack \| Update deletion protection. ct-2syhk4 sr7cvyw Updated CT. New CT Management \| Advanced Stack Components \| RDS database stack \| Update enhanced monitoring. ct-3jx80f quylzhf New CT. Updated CT Deployment \| Directory Service \| DNS \| Create Group Managed Service Account. ct-2qhl8j 1pjnbgn Updated CT. Updated CT Management \| AWS Backup \| Backup plan \| Update. ct-1ay83w y4vxa3k Updated CT. Updated CT Management \| Advanced Stack Components \| RDS database stack \| Update master password. ct-2052mi u12d8fn Updated CT. Updated CT Deployment \| Advanced Stack Components \| ACM \| Create private certiﬁcate. ct-3ll9hn adql9s1 Updated CT. Updated CT Deployment \| Advanced Stack Components \| EC2 stack \| Create (with additional volumes). ct-1aqsjf 86w6vxg Updated Tips section. Earlier updates Version April 22, 2025 3019 AMS Advanced Change Type Reference AMS Advanced Change Type Details Change Description Updated CT Deployment \| Advanced Stack Components \| Database Migration Service (DMS) \| Create Source Endpoint. Updated Tips section. New CT Management \| Advanced Stack Components \| Route 53 Resolver \| Associate VPC with Resolver Rule. New CT Link(s) Database Migration Service (DMS) \| Create Source Endpoint ct-2pbqof fhclpek Updated CT Management \| Advanced Stack Components \| KMS key \| Update. ct-3ovo7p x2vsa6n New CT Updated CT Management \| Advanced Stack Components \| Security group \| Associate. ct-12lyw7 otiyr6f New CT Updated CT Management \| Advanced Stack Components \| Security group \| Disassociate. ct-13lk0n oacn6ua New CT Updated CT Management \| Advanced Stack Components \| S3 storage \| Update policy (review required). ct-0fpjlx a808sh2 New CT Updated CT Management \| Advanced Stack Components \| RDS database stack \| Rotate DB certiﬁcate. ct-1ezarc 5xph3tq New CT Earlier updates Version April 22, 2025 3020 AMS Advanced Change Type Reference AMS Advanced Change Type Details Change Description Link(s) Updated CT Management \| Advanced Stack Components \| Tag \| Update (review required). ct-0zko7t 3rk2efb New CT New CT Management \| Advanced stack components \| KMS key \| Share (review required). ct-05yb33 7abq3x5 New CT Updated CT Management \| Advanced stack components \| KMS key \| Update (review required). ct-3ovo7p x2vsa6n New version New CT Management \| Directory Service \| Directory \| Create AD trust. Updated CT Deployment \| Advanced stack components \| Identity and Access Management (IAM) \| Create access key. Version 2. ct-0x6dyl rnfjgz5 ct-2hhqzg xvkcig8 Updated CT Deployment \| Advanced stack components \| Redshift \| Create (cluster
ams-ct-771	ams-ct.pdf	771	Updated CT Management \| Advanced Stack Components \| Tag \| Update (review required). ct-0zko7t 3rk2efb New CT New CT Management \| Advanced stack components \| KMS key \| Share (review required). ct-05yb33 7abq3x5 New CT Updated CT Management \| Advanced stack components \| KMS key \| Update (review required). ct-3ovo7p x2vsa6n New version New CT Management \| Directory Service \| Directory \| Create AD trust. Updated CT Deployment \| Advanced stack components \| Identity and Access Management (IAM) \| Create access key. Version 2. ct-0x6dyl rnfjgz5 ct-2hhqzg xvkcig8 Updated CT Deployment \| Advanced stack components \| Redshift \| Create (cluster subnet group). ct-0q43l4 0hxrzum New required parameterSubnetGroupDescription. Updated CTs Deployment \| Advanced stack components \| EC2 Stack \| Create. Deployment \| Ingestion \| Stack from migration partner migrated instance \| Create. New optional parameter EnforceIMDSv2. ct-14027q 0sjyt1h ct-257p9z jk14ija New CT Management \| Managed account \| Stack access duration \| Override (review required). ct-0jb01c ofkhwk1 Earlier updates Version April 22, 2025 3021 AMS Advanced Change Type Reference AMS Advanced Change Type Details Change Description New CTs Deployment \| Advanced Stack Components \| Identity and Access Management (IAM) \| Create entity or policy (read-write permissions). Management \| Advanced Stack Components \| Identity and Access Management (IAM) \| Update entity or policy (read-write permissions). Management \| Advanced Stack Components \| Identity and Access Management (IAM) \| Delete entity or policy (read-write permissions). Management \| Managed account \| Automated IAM provisioning with read-write permissions \| Enable (review required) New CTs Deployment \| Managed landing zone \| Management account \| Create stacksets stack, ct-16pknsfa8lul7. Management \| Managed landing zone \| Management account \| Delete stacksets stack, ct-1yqy4frl5s8y8. Management \| Managed landing zone \| Management account \| Update stacksets stack, ct-1v9g9n30woc8h. Link(s) ct-1n9gfn og5x7ﬂ ct-1e0xmu y1diafq ct-17cj84 y7632o6 ct-1706xv vk6j9hf ct-16pkns fa8lul7 ct-1yqy4f rl5s8y8 ct-1v9g9n 30woc8h Updated CT Management \| Access \| Stack admin access \| Grant, ct-1dmlg9 g1l91h6. ct-1dmlg9 g1l91h6 Version 3.0 adds support for a custom maximum stack access time. Submit an RFC with the Management \| Other \| Other \| Update (review required) (ct-0xdawir96cy7k) change type in the SALZ account or MALZ Shared Services account to customize this value. Earlier updates Version April 22, 2025 3022 AMS Advanced Change Type Reference AMS Advanced Change Type Details Change Description Link(s) Updated CT Management \| Access \| Stack admin access \| Update, ct-0ikpop 8zqhkxg. ct-0ikpop 8zqhkxg Version 3.0 adds support for a custom maximum stack access time. Submit an RFC with the Management \| Other \| Other \| Update (review required) (ct-0xdawir96cy7k) change type in the SALZ account or MALZ Shared Services account to customize this value. Updated CT Management \| Access \| Stack read-only access \| Grant, ct-199h35t7uz6jl. ct-199h35 t7uz6jl Version 3.0 adds support for a custom maximum stack access time. Submit an RFC with the Management \| Other \| Other \| Update (review required) (ct-0xdawir96cy7k) change type in the SALZ account or MALZ Shared Services account to customize this value. Updated CT Management \| Access \| Stack read-only access \| Update, ct-3kh1wiizlne1i. ct-3kh1wi izlne1i Version 3.0 adds support for a custom maximum stack access time. Submit an RFC with the Management \| Other \| Other \| Update (review required) (ct-0xdawir96cy7k) change type in the SALZ account or MALZ Shared Services account to customize this value. Updated CT Management \| Access \| Stack admin access \| Grant, ct-1dmlg9 g1l91h6. ct-1dmlg9 g1l91h6 Version 3.0 is the default version, adding support for multiple usernames and access times up to 12 hours (previously 8). Earlier updates Version April 22, 2025 3023 AMS Advanced Change Type Reference AMS Advanced Change Type Details Change Description Link(s) Updated CT Management \| Access \| Stack admin access \| Update, ct-0ikpop 8zqhkxg. ct-0ikpop 8zqhkxg Version 3.0 is the default version, adding support for multiple usernames and access times up to 12 hours (previously 8). Updated CT Management \| Access \| Stack read-only access \| Grant, ct-199h35t7uz6jl. ct-199h35 t7uz6jl Version 3.0 is the default version, adding support for multiple usernames and access times up to 12 hours (previously 8). Updated CT Management \| Access \| Stack read-only access \| Update, ct-3kh1wiizlne1i. ct-3kh1wi izlne1i New CT New CT New CT New CT New CT Version 3.0 is the default version, adding support for multiple usernames and access times up to 12 hours (previously 8). Management \| Advanced stack components \| Bastions \| Update bastion instance size (review required), ct-0tmpmp1wpgkr9. ct-0tmpmp 1wpgkr9 Management \| Advanced stack components \| Bastions \| Update bastion instance or session counts (review required) ct-1962s5 ct-1962s5 oczal9z oczal9z. Management \| Advanced stack components \| Bastions \| Add CIDR Ingress (review required) ct-36zubwzxp44a4. ct-36zubw zxp44a4 Management \| Advanced stack components \| EC2 instance stack \| Associate private ip addresses (review required), ct-1pvlhug439gl2. Management \| Advanced stack components \| EC2 instance stack \| Update instance detailed monitoring, ct-0tmpmp 1wpgkr9. ct-1pvlhu g439gl2 ct-0tmpmp
ams-ct-772	ams-ct.pdf	772	multiple usernames and access times up to 12 hours (previously 8). Management \| Advanced stack components \| Bastions \| Update bastion instance size (review required), ct-0tmpmp1wpgkr9. ct-0tmpmp 1wpgkr9 Management \| Advanced stack components \| Bastions \| Update bastion instance or session counts (review required) ct-1962s5 ct-1962s5 oczal9z oczal9z. Management \| Advanced stack components \| Bastions \| Add CIDR Ingress (review required) ct-36zubwzxp44a4. ct-36zubw zxp44a4 Management \| Advanced stack components \| EC2 instance stack \| Associate private ip addresses (review required), ct-1pvlhug439gl2. Management \| Advanced stack components \| EC2 instance stack \| Update instance detailed monitoring, ct-0tmpmp 1wpgkr9. ct-1pvlhu g439gl2 ct-0tmpmp 1wpgkr9 New CT Deployment \| Advanced stack components \| VPC \| Add static route (review required), ct-06bwg93ukgg8t. ct-06bwg9 3ukgg8t Earlier updates Version April 22, 2025 3024 AMS Advanced Change Type Reference AMS Advanced Change Type Details Change Description Link(s) Updated CT Management \| Advanced stack components \| AMI \| Deregister (multiple), ct-26vhhlj9jmlpf ct-26vhhl j9jmlpf Version 2.0 supports deregistering multiple AMIs in one request. Updated CT Management \| Advanced stack components \| Security group \| Authorize ingress rule, ct-3j2zstluz6dxq. ct-3j2zst luz6dxq Updated to version 3.0. Updated CT Management \| Advanced stack components \| Security group \| Revoke ingress rule, ct-1vjbacfr4ufdv. ct-1vjbac fr4ufdv Updated to version 3.0. Updated CT Deployment \| AMS Resource Scheduler \| Solution \| Deploy, ct-0ywnhc8e5k9z5. ct-0ywnhc 8e5k9z5 Version 2 requires the Action (deploy or update) parameter. Updated CT Management \| AMS Resource Scheduler \| Solution \| Update, ct-2c7ve50jost1v. ct-2c7ve5 0jost1v Version 2 requires the Action (deploy or update) parameter. Updated CT Deployment \| Advanced stack components \| Auto Scaling group \| Create, ct-2tylseo8rxfsc. ct-2tylse o8rxfsc New optional parameter EnforceIMDSv2. Updated CT Deployment \| Standard stacks \| High availability two-tier stack \| Create, ct-06mjngx5ﬂwto. ct-06mjng x5ﬂwto New optional parameter EnforceIMDSv2. New CT Management \| Directory Service \| Directory \| Share Directory, ct-369odosk0pd9w. ct-369odo sk0pd9w Earlier updates Version April 22, 2025 3025 AMS Advanced Change Type Reference AMS Advanced Change Type Details Change Description Link(s) New CT Management \| Directory Service \| Directory \| Unshare Directory , ct-2xd2anlb5hbzo. ct-2xd2an lb5hbzo Updated CT Management \| Host security \| Trend Micro DSM \| Add login (read-only) , ct-0wspy4o646g9p. ct-0wspy4 o646g9p Version 2 has new parameters and examples. It does not require a review. Updated CT Management \| Advanced stack components \| AMI \| Deregister, ct-26vhhlj9jmlpf. ct-26vhhl j9jmlpf Version 2 supports deleting or deregistering multiple AMIs. Updated CT Deployment \| Directory Service \| DNS \| Create conditional forwarder, ct-3nba0wtdugnan. ct-3nba0w tdugnan Conditional forwarder now supports up to 5 IP addresses. Updated CT Management \| Directory Service \| DNS \| Update conditional forwarder, ct-2fqmbyud166z9. ct-2fqmby ud166z9 Conditional forwarder now supports up to 5 IP addresses. Updated CT Management \| Advanced stack components \| EC2 instance stack \| Change hostname (Linux), ct-2781aqd6f6svs. ct-2781aq d6f6svs Version 2 does not require a review. Updated CT Deployment \| Advanced stack components \| Auto Scaling group \| Create, ct-2tylseo8rxfsc. ct-2tylse o8rxfsc Version 3 has new parameter descriptions. Updated CT walkthrough Management \| Managed landing zone \| Application account \| Conﬁrm oﬀboarding, ct-2wlfo2jxj2rkj. ct-2wlfo2 jxj2rkj Added tips. Earlier updates Version April 22, 2025 3026 AMS Advanced Change Type Reference AMS Advanced Change Type Details Change Description Updated CT walkthroughs Management \| Advanced stack components \| DNS (private) \| Update, ct-1d55pi44ﬀ21u and Deployment \| Advanced stack components \| DNS (private) \| Create, ct-0c38gftq56zj6. New CT New CT New CT New CT New CT New CT Added tips about 500 limit on RRs. Deployment \| Advanced stack components \| VPCEndpoint (Interface) \| Create, ct-3oafsdbzjtuqp. Deployment \| Advanced stack components \| S3 storage \| Update encryption, ct-128svy9nn2yj8. Deployment \| Advanced stack components \| S3 storage \| Update versioning, ct-2hh93eyzmwbkd. Deployment \| Advanced stack components \| RDS database stack \| Update instance type, ct-13swbwdxg106z. ct-13swbw dxg106z Deployment \| Advanced stack components \| RDS database stack \| Update MultiAZ setting, ct-36jq7gvwyty8h. Deployment \| Advanced stack components \| RDS database stack \| Update storage, ct-0loed9dzig1ze. ct-36jq7g vwyty8h ct-0loed9 dzig1ze Link(s) ct-1d55pi 44ﬀ21u and ct-0c38gf tq56zj6 ct-3oafsd bzjtuqp ct-128svy 9nn2yj8 ct-2hh93e yzmwbkd Updated CT Deployment \| Advanced stack components \| RDS snapshot \| Copy, ct-1c0jrxd3su5oe. ct-1c0jrx d3su5oe Added support for multi-region (MRK) KMS keys. Updated CT Management \| Advanced stack components \| EC2 instance stack \| Replace instance proﬁle, ct-37kcp2v1mriu6. ct-37kcp2 v1mriu6 Updated to version 2.0 with new parameters. Updated CT Deployment \| Advanced stack components \| EC2 stack \| Create (with additional volumes), ct-1aqsjf86w6vxg. ct-1aqsjf 86w6vxg Added support for specifying core count and threads per core. Earlier updates Version April 22, 2025 3027 AMS Advanced Change Type Reference AMS Advanced Change Type Details Change Description Link(s) Updated CT Deployment \| Advanced stack components \| KMS key \| Create, ct-1d84keiri1jhg. ct-1d84ke iri1jhg Added guidance for deleting a key, and a warning that deletion does not occur automatically. Updated CTs Deployment \| Advanced stack components \| Tag \|
ams-ct-773	ams-ct.pdf	773	instance proﬁle, ct-37kcp2v1mriu6. ct-37kcp2 v1mriu6 Updated to version 2.0 with new parameters. Updated CT Deployment \| Advanced stack components \| EC2 stack \| Create (with additional volumes), ct-1aqsjf86w6vxg. ct-1aqsjf 86w6vxg Added support for specifying core count and threads per core. Earlier updates Version April 22, 2025 3027 AMS Advanced Change Type Reference AMS Advanced Change Type Details Change Description Link(s) Updated CT Deployment \| Advanced stack components \| KMS key \| Create, ct-1d84keiri1jhg. ct-1d84ke iri1jhg Added guidance for deleting a key, and a warning that deletion does not occur automatically. Updated CTs Deployment \| Advanced stack components \| Tag \| Create, ct-3cx7we852p3af. ct-3cx7we 852p3af Updated parameters, description, and console screenshot. Updated CTs Management \| Advanced stack components \| Tag \| Update, ct-0xqwmtn1hfh8u. ct-0xqwmt n1hfh8u Updated parameters, description, and console screenshot. Updated CTs Management \| Advanced stack components \| Tag \| Delete, ct-2zebb2czoxpjd. ct-2zebb2 czoxpjd Updated parameters, description, and console screenshot. Updated CTs Management \| Standalone resources \| EC2 instance \| Terminate , ct-3dfubbpesm2v9. ct-3dfubb pesm2v9 Updated parameters, description, and console screenshot. Updated CT Management \| Advanced stack components \| EC2 instance stack \| Update DeleteOnTermination (review required), ct-2aaaqid7asjy6. ct-2aaaqi d7asjy6 Updated description of the DeleteOnTermination parameter. Updated CT Management \| Advanced stack components \| KMS key \| Update, ct-3ovo7px2vsa6n. ct-3ovo7p x2vsa6n Updated the description of the KeyRotation parameter. Earlier updates Version April 22, 2025 3028 AMS Advanced Change Type Reference AMS Advanced Change Type Details Change Description Link(s) Updated CT Management \| Advanced stack components \| RDS database stack \| Update master user password, ct-2052miu12d8fn. ct-2052mi u12d8fn Updated examples and tips with additional guidance for using SSM Parameter Store or AWS Secrets Manager Updated CT Management \| Advanced stack components \| Target group \| Detach instances, ct-37bq2l9c8fzxv. ct-37bq2l 9c8fzxv Updated description of InstancesIds parameter. Updated CTs Added support for GP3 storage, and choice of SQL character sets to: • Deployment \| Advanced stack components \| RDS database stack \| Create • Management \| Advanced stack components \| RDS database stack \| Update Updated CTs Added support for multi-Region KMS keys (MRK) to: • Deployment \| Advanced stack components \| S3 storage \| Create • Management \| Advanced stack components \| S3 storage \| Update ct-2z60dy vto9g6c and ct-12w49b oaiwtzp ct-1a68ck 03fn98r and ct-1gi93j hvj28eg CT Name Change Deployment \| Advanced stack components \| OpenSearch \| Create domain, ct-0azen3a9anxzj is removed and replaced with Deployment \| Advanced stack components \| OpenSearch \| Create domain, ct-281et7bs9ep4s. ct-281et7 bs9ep4s This update included a change to the OpenSearch \| Create domain schema. New CT Management \| Managed landing zone \| Networking account \| Remove TGW static route, ct-0rmgrnr9w8mzh. ct-0rmgrn r9w8mzh Earlier updates Version April 22, 2025 3029 AMS Advanced Change Type Reference AMS Advanced Change Type Details Change Description Link(s) New CT Deployment \| AMS Resource Scheduler \| Solution \| Deploy, ct-2c7ve50jost1v. ct-0ywnhc 8e5k9z5 Updated CTs Management \| Advanced stack components \| DNS (private) \| Create, ct-0c38gftq56zj6. Management \| Advanced stack components \| DNS (private) \| Update, ct-1d55pi44ﬀ21u. Management \| Advanced stack components \| DNS (public) \| Create, ct-0vzsr2nyraedl. Management \| Advanced stack components \| DNS (public) \| Update, ct-1hzofpphabs3i. Parameters and CLI examples have changed for version 2.0. Updated CTs Deployment \| Advanced stack components \| RDS database stack \| Create (for Aurora), ct-2jvzjwunghrhy. Deployment \| Advanced stack components \| RDS database stack \| Create from backup (for Aurora), ct-2wllq61djysxz. Management \| Advanced stack components \| RDS database stack \| Update (for Aurora), ct-2dphvdy1krpj6. Updated descriptions, added min/max parameters serverless scaling, and added InstanceType values. ct-0c38gf tq56zj6, ct-1d55pi 44ﬀ21u, ct-0vzsr2 nyraedl, and ct-1hzofp phabs3i ct-2jvzjw unghrhy, ct-2wllq6 1djysxz, and ct-2dphvd y1krpj6 Updated CT Management \| Advanced stack components \| EC2 instance stack \| Resize, ct-15mazjj88xc69. ct-15mazj j88xc69 Updated description, parameters, and CLI examples for version 2.0. New CT Management \| AMS Resource Scheduler \| Solution \| Update, ct-2c7ve50jost1v. ct-2c7ve5 0jost1v Earlier updates Version April 22, 2025 3030 AMS Advanced Change Type Reference AMS Advanced Change Type Details Change Description Link(s) Updated CT Management\| AMS Resource Scheduler \| Solution \| Deploy, ct-0ywnhc8e5k9z5. ct-0ywnhc 8e5k9z5 Removed SALZ restriction and added Action parameter. New CT Deployment \| Advanced stack components \| Identity and Access Management (IAM) \| Create access key, ct-2hhqzg ct-2hhqzg xvkcig8 xvkcig8. New CT Management \| Advanced stack components \| Identity and Access Management (IAM) \| Deleate or deactivate access key, ct-37qquo 9wbpa8x ct-37qquo9wbpa8x. Updated CT Deployment \| Advanced stack components \| Application Load Balancer \| Create, ct-111r1yayblnw4. ct-111r1y ayblnw4 Added parameter TargetGroup to optionally specify a load balancer TargetGroup. Updated CT Management \| Managed landing zone \| Application account \| Conﬁrm Oﬀboarding, ct-2wlfo2jxj2rkj. ct-2wlfo2 jxj2rkj Added a tip not to use this for Customer Managed application accounts. Updated CT Management \| Managed landing zone \| Management account \| Oﬀboard application account, ct-0vdiy51oyrhhm. ct-0vdiy5 1oyrhhm Added a tip: when applied to Customer Managed application
ams-ct-774	ams-ct.pdf	774	Management \| Advanced stack components \| Identity and Access Management (IAM) \| Deleate or deactivate access key, ct-37qquo 9wbpa8x ct-37qquo9wbpa8x. Updated CT Deployment \| Advanced stack components \| Application Load Balancer \| Create, ct-111r1yayblnw4. ct-111r1y ayblnw4 Added parameter TargetGroup to optionally specify a load balancer TargetGroup. Updated CT Management \| Managed landing zone \| Application account \| Conﬁrm Oﬀboarding, ct-2wlfo2jxj2rkj. ct-2wlfo2 jxj2rkj Added a tip not to use this for Customer Managed application accounts. Updated CT Management \| Managed landing zone \| Management account \| Oﬀboard application account, ct-0vdiy51oyrhhm. ct-0vdiy5 1oyrhhm Added a tip: when applied to Customer Managed application accounts, there is no conﬁrmation step. Updated CT Deployment \| Advanced stack components \| KMS alias \| Create, ct-2svg4k2fqi4ak. ct-2svg4k 2fqi4ak Updated the AliasName pattern to reject names with prohibite d preﬁxes. Earlier updates Version April 22, 2025 3031 AMS Advanced Change Type Reference AMS Advanced Change Type Details Change Description Link(s) New Content The What Are AMS Change Types? ﬁle now has a link to a zip ﬁle with a current comma-separated value (CSV) ﬁle of change Change type CSV output types. ﬁle New CT New CT New CT New CT New CT New CT New CT Management \| Advanced stack components \| EBS snapshot \| Archive, ct-059ewa92tc2i1. ct-059ewa 92tc2i1 Management \| Advanced stack components \| Identity and Access Management (IAM) \| Update max session duration, ct-1fzddq rr20c2i ct-1fzddqrr20c2i. Deployment \| Advanced stack components \| RDS snapshot \| Create (Cluster), ct-2zqwr34epwzx1. ct-2zqwr3 4epwzx1 Management \| Standalone resources \| RDS instance \| Terminate , ct-3glr80c15rp7z. ct-3glr80 c15rp7z Management \| Advanced stack components \| RDS snapshot \| Delete, ct-0idxb0xsg1ui6. ct-0idxb0 xsg1ui6 Deployment \| Managed landing zone \| Networking account \| Create transit gateway route table, ct-3dscwaeyi6cup. ct-3dscwa eyi6cup Management \| Advanced stack components \| S3 storage \| Manage lifecycle conﬁguration, ct-1ax768xtu8c9q. ct-1ax768 xtu8c9q Updated CT Deployment \| Advanced stack components \| EC2 stack \| Create, ct-14027q0sjyt1h. ct-14027q 0sjyt1h Added a tip not to select instance types that are too small. Updated CT Management \| Advanced stack components \| Application Load Balancer \| Update, ct-1a1zzgi2nb83d. ct-1a1zzg i2nb83d Updated the description of the LoadBalancerSubnetIds parameter. Earlier updates Version April 22, 2025 3032 AMS Advanced Change Type Reference AMS Advanced Change Type Details Change Description Link(s) Updated CT Deployment \| Patching \| SSM patch window \| Create, ct-0el2j0 7llrxs7. ct-0el2j0 7llrxs7 Replaced references to Route 53 hosted zones with SSM window creation. Updated CT Management \| AWS service \| Self-provisioned service \| Add, ct-1w8z66n899dct. ct-1w8z66 n899dct List of service names updated to include AWS Private Certiﬁca te Authority (PCA) Updated CT Management \| AWS service \| Self-provisioned service \| Add (review required), ct-3qe6io8t6jtny. ct-3qe6io 8t6jtny List of service names updated to include AWS Private Certiﬁca te Authority (PCA) Updated CT Management \| Patching \| On demand patching \| Run, ct-3oy53m1qzl2s5. ct-3oy53m 1qzl2s5 Added a note regarding the StartInactiveInstances parameter. Inactive instances return to their inactive state after patching. Updated CT Management \| Advanced stack components \| Tag \| Bulk update, ct-3047c34zuvswh. ct-3047c3 4zuvswh Added Supported Resources section and a link to Tag bulk update notes. Updated CT Management \| Advanced stack components \| Tag \| Bulk update (review required), ct-0k4b96aatyqgl. ct-0k4b96 aatyqgl Added Supported Resources section and a link to Tag bulk update notes. New CT Deployment \| Advanced stack components \| RDS snapshot \| Copy (for Aurora), ct-19fdy7np55xiu. ct-19fdy7 np55xiu Earlier updates Version April 22, 2025 3033 AMS Advanced Change Type Reference AMS Advanced Change Type Details Change Description Link(s) New CT New CT Management \| Advanced stack components \| RDS database stack \| Start Aurora Cluster, ct-02ocqy2i0jx3t. ct-02ocqy 2i0jx3t Management \| Advanced stack components \| RDS database stack \| Stop Aurora Cluster, ct-37vqa0oggka3q. ct-37vqa0 oggka3q Updated CT schema Management \| AWS service \| Self-provisioned service \| Add, ct-1w8z66n899dct. ct-1w8z66 n899dct The AWS Codepipeline service was removed from the possible services you could add with this CT. Updated CT schema Deployment \| Advanced stack components \| AMI \| Copy, ct-046aizcwg5idf. ct-046aiz cwg5idf The Region parameter was updated to add: "This must be the account onboarded Region." Updated CT schemas Management \| Directory Service \| DNS \| Add A record, ct-2w3rbmnny1qpo ct-2w3rbm nny1qpo Management \| Directory Service \| DNS \| Add CNAME record, ct-2murl5 ct-2murl5xzbxoxf Management \| Directory Service \| DNS \| Remove record, ct-1icrtx8ydvdwe Improved examples. xzbxoxf ct-1icrtx 8ydvdwe Updated CT tips Deployment \| Advanced stack components \| RDS database stack \| Create from snapshot, ct-20san5sgtwd9e. ct-20san5 sgtwd9e Added a note: "You can't restore a DB instance from a DB snapshot that is both shared and encrypted. Instead, you can make a copy of the DB snapshot and restore the DB instance from the copy. To copy the shared snapshot, please use the following CT: RDS Snapshot \| Copy". Earlier updates Version April 22, 2025 3034 AMS Advanced Change Type Reference AMS Advanced
ams-ct-775	ams-ct.pdf	775	ct-2murl5xzbxoxf Management \| Directory Service \| DNS \| Remove record, ct-1icrtx8ydvdwe Improved examples. xzbxoxf ct-1icrtx 8ydvdwe Updated CT tips Deployment \| Advanced stack components \| RDS database stack \| Create from snapshot, ct-20san5sgtwd9e. ct-20san5 sgtwd9e Added a note: "You can't restore a DB instance from a DB snapshot that is both shared and encrypted. Instead, you can make a copy of the DB snapshot and restore the DB instance from the copy. To copy the shared snapshot, please use the following CT: RDS Snapshot \| Copy". Earlier updates Version April 22, 2025 3034 AMS Advanced Change Type Reference AMS Advanced Change Type Details Change Description Updated CT schemas Deployment/Advanced stack components/Tag/Create, ct-3cx7we852p3af. Management/Advanced stack components/Tag/Delete, ct-2zebb2czoxpjd. Management/Advanced stack components/Tag/Update, ct-0xqwmtn1hfh8u. For all three, the ResourceArns parameter description was updated. Link(s) ct-3cx7we 852p3af ct-2zebb2 czoxpjd ct-0xqwmt n1hfh8u Updated CT tips Management \| Directory Service \| DNS \| Add A record, ct-2w3rbmnny1qpo. ct-2w3rbm nny1qpo Management \| Directory Service \| DNS \| Add CNAME record, ct-2murl5 ct-2murl5xzbxoxf. xzbxoxf Added a note: "For multi-account landing zone (MALZ), use this change type in the shared services account." Updated content Updated Tips section with information on "Linux Preparation for AMI Create," "Windows Preparation for AMI Create," and AMI \| Create. "UserData for AMI Create." New content Example walkthroughs for each change type have been moved here from the retired AMS Advanced Change Management Change Types by Guide. Classiﬁcation. All change types with execution mode=manual are now appended with "(review required)" to the Operation name. All change types with execution mode=automated are now appended with nothing (any cases of "(auto)" or "(no review required)" are removed). New CT Management \| Managed account \| Direct Change mode \| Enable, CT ID: ct-3rd4781c2nnhp. ct-3rd478 1c2nnhp Earlier updates Version April 22, 2025 3035 AMS Advanced Change Type Reference AMS Advanced Change Type Details Change Description Change types that included "Master account" in their classiﬁc ation have all been updated to "Management account." Removed the space in pattern for parameter: IpProtocol . Updated CTs Management \| Advanced stack components \| EC2 instance stack \| Change time zone (ct-3g9dbtun44mal) Link(s) Managed Landing Zone Subcategory ct-3j2zst luz6dxq ct-0lqrua jvhwsbk ct-111fhp lhx9axe ct-1vjbac fr4ufdv ct-3g9dbt un44mal New CTs: Management \| Advanced stack components \| RDS database stack \| Update deletion protection ct-2syhk4 sr7cvyw Deployment \| Advanced stack components \| Identity and Access Management (IAM) \| Create service-speciﬁc credentials ct-2ni31o yto1i5k Management \| Advanced stack components \| Identity and Access Management (IAM) \| Reset service-speciﬁc credentials ct-22cbvc 1yujhec Deployment\| Managed landing zone \| Management Account \| Create custom SCP (review required) (ct-33ste5yc7hprs) and Updated CTs: Deployment\| Managed landing zone \| Networking account \| Create application route table (review required) (ct-1urj9 4c3hdfu5) ct-33ste5 yc7hprs and ct-1urj94 c3hdfu5 Change classiﬁcation to include "(review required)" appended to the Operation name. Earlier updates Version April 22, 2025 3036 AMS Advanced Change Type Reference AMS Advanced Change Type Details Change Description Deployment \| Advanced stack components \| Database Migration Service (DMS) \| Start replication task (ct-1yq7h hqse71yg) Updated to indicate the DocumentName and Region are required parameters; previously, they were erroneously listed as optional. Link(s) ct-1yq7hh qse71yg Deployment \| AWS Backup \| Backup plan \| Create (ct-2hyoz bpa0sx0m) ct-2hyozb pa0sx0m Added note to warn that not all resources types supported by AWS Backup are enabled by default. Find which services are in Getting Started 1: Service Opt-In. If changes need to be made, open an RFC using CT ct-1e1xtak34nx76. Deployment \| Advanced stack components \| Identity and Access Management (IAM) \| Create EC2 instance proﬁle ct-117rmp 64d5mvb (ct-117rmp64d5mvb) and Deployment \| Advanced stack and components \| Identity and Access Management (IAM) \| Create ct-1k3oui Lambda execution role (ct-1k3oui719dcju) 719dcju New Version: 2.0. Updated to make JSON copy-paste easier. Deployment \| Advanced stack components \| RDS database stack \| Create (ct-2z60dyvto9g6c) ct-2z60dy vto9g6c Added a new value for the RDSDBEngine parameter: mariadb. Deployment \| Advanced stack components \| RDS database stack \| Update (ct-12w49boaiwtzp) ct-12w49b oaiwtzp Extended the expected duration time to 360 minutes from 60 minutes. Earlier updates Version April 22, 2025 3037 AMS Advanced Change Type Reference AMS Advanced Change Type Details Change Description Link(s) Updated CTs "Additional Information" Added an important note about limitations on the resources that can be remediated. ct-34sxfo 53yuzah Management \| AWS service \| Self-provisioned service \| Add Self-Service Provisioning service (no review required) ct-1w8z66 n899dct Deployment \| Advanced stack components \| Identity and Access Management (IAM) \| Create service-linked role ct-2eof6j 3mlcwhf Management \| Advanced stack components \| ACM \| Delete certiﬁcate ct-1q8q56 cmwqj9m Management \| Managed landing zone \| Application account \| Conﬁrm oﬀboarding ct-2wlfo2 jxj2rkj Management \| Managed landing zone \| Application account \| Oﬀboard application account ct-0vdiy5 1oyrhhm Deployment \| Managed landing zone \| Management account \| Create Accelerate account ct-0vdiy5 1oyrhhm New CTs: Updated CTs: Earlier updates Version April
ams-ct-776	ams-ct.pdf	776	can be remediated. ct-34sxfo 53yuzah Management \| AWS service \| Self-provisioned service \| Add Self-Service Provisioning service (no review required) ct-1w8z66 n899dct Deployment \| Advanced stack components \| Identity and Access Management (IAM) \| Create service-linked role ct-2eof6j 3mlcwhf Management \| Advanced stack components \| ACM \| Delete certiﬁcate ct-1q8q56 cmwqj9m Management \| Managed landing zone \| Application account \| Conﬁrm oﬀboarding ct-2wlfo2 jxj2rkj Management \| Managed landing zone \| Application account \| Oﬀboard application account ct-0vdiy5 1oyrhhm Deployment \| Managed landing zone \| Management account \| Create Accelerate account ct-0vdiy5 1oyrhhm New CTs: Updated CTs: Earlier updates Version April 22, 2025 3038 AMS Advanced Change Type Reference AMS Advanced Change Type Details Change Description Link(s) ct-2bxelbn765ive and ct-3u61cd4edns0x Managemen t \| AMS Resource Scheduler \| Schedule \| Add (ct-2bxel bn765ive) and Managemen t \| AMS Resource Scheduler \| Schedule \| Update (ct-3u61c d4edns0x) The SSMMainte nanceWind ow can now take a list of AWS Systems Manager existing maintenence windows. New CTs: Deployment \| Advanced stack components \| Identity and Access Managment (IAM) \| Create OpenID Connect provider ct-30ecvf i3tq4k3 Earlier updates Version April 22, 2025 3039 AMS Advanced Change Type Reference AMS Advanced Change Type Details Change Description Link(s) Updated CTs: Deployment \| Advanced stack components \| RDS database stack \| Create ct-2z60dy vto9g6c This update adds performance insights options. Updated CTs "Additional Many CTs had non-standard "Additional Information" sections without links to the corresponding walkthrough, this has been January 27, 2022 Information" ﬁxed. Management \| Advanced stack components \| Application Load Balancer \| Add listener certiﬁcate ct-3g6fq83nxg1a7 Management \| Advanced stack components \| Application Load Balancer \| Remove listener certiﬁcate ct-0tpbr6lfa3zng Management \| Advanced stack components \| Load Balancer (ELB) stack \| Replace listener certiﬁcate January 13, 2022 ct-0aqx5t0pgfzbg New CTs: Management \| Advanced stack components \| Network Load Balancer \| Add listener certiﬁcate ct-35p977vul06df Management \| Advanced stack components \| Network Load Balancer \| Remove listener certiﬁcate ct-3929xwf222jri Management \| Managed landing zone \| Networking account \| Disable TGW propagation ct-2pxyajek47am2 Earlier updates Version April 22, 2025 3040 AMS Advanced Change Type Reference AMS Advanced Change Type Details Change Description Link(s) Management \| Managed landing zone \| Networking account \| Enable TGW propagation ct-1f9hi4bephqa9 Management \| Standalone resources \| EC2 instance \| Terminate ct-3dfubbpesm2v9 Management \| Advanced stack components \| EC2 Instance Stack \| Gather log4j information (v2.0) ct-19f40lfm5umy8 Management \| Advanced stack components \| Database Migration Service (DMS) \| Start replication task and Management \| Advanced stack components \| Database Migration Service (DMS) \| Stop replication task Updated CTs: ct-1yq7hhqse71yg and ct-1vd3y4ygbqmfk Management \| Advanced stack components \| EC2 instance stack \| Change hostname (Linux) ct-2781aqd6f6svs This update provides an option to target all instances in the region. This change updates the task ARN regular expressio n to the allow tasks containing the a dash ( - ). Automated , with additional parameters, and moved to version 2.0. Earlier updates Version April 22, 2025 3041 AMS Advanced Change Type Reference AMS Advanced Change Type Details Change Description Management \| Advanced stack components \| EC2 instance stack \| Restore volumes ct-0ﬀvihqwjvqj1 Link(s) This update adds two optional parameters, RootVolum eType and VolumeTyp es. Earlier updates Version April 22, 2025 3042 AMS Advanced Change Type Reference AMS Advanced Change Type Details Change Description Link(s) A Priority parameter has been added to all execution mode=manual change types (CTs). The changed CTs are: For additional information, see RFC scheduling. Deploymen t/ Monitor ing and notificat ion/ Guard Duty IP set/ Create Deploym ent/ Monit oring and notificat ion/ Guard Duty threat intel set/ Create Managem ent/ Monit oring and notificat ion/ Guard Duty IP set/ Delete Managem ent/ Monit oring Earlier updates Version April 22, 2025 3043 AMS Advanced Change Type Reference AMS Advanced Change Type Details Change Description Link(s) and notificat ion/ Guard Duty IP set/ Update Managem ent/ Monit oring and notificat ion/ Guard Duty threat intel set/ Delete Managem ent/ Monit oring and notificat ion/ Guard Duty threat intel set/ Update Managem ent/ Other/ Other/Cr eate Mana gement/ Other/ Earlier updates Version April 22, 2025 3044 AMS Advanced Change Type Reference AMS Advanced Change Type Details Change Description Link(s) Other/ Update D eployment /Managed landing zone/ Mana gement account/ Create Custom SCP Deplo yment/ Managed landing zone/ Netw orking account/ Create applicati on route table Dep loyment/ Advanced stack component s/ Identit y and Access Managemen t (IAM)/ Create entity or policy De ployment/ Earlier updates Version April 22, 2025 3045 AMS Advanced Change Type Reference AMS Advanced Change Type Details Change Description Link(s) Advanced stack component s/KMS key/ Create (review required) (1.0 and 2.0) Depl oyment/ Advanced stack component s/S3 storage/ Create policy De ployment/ Advanced stack component s/ Securit y group/ Create (review required) Deployme nt/ Advanc ed stack component s/Tag/ Create (review required) Manageme
ams-ct-777	ams-ct.pdf	777	gement account/ Create Custom SCP Deplo yment/ Managed landing zone/ Netw orking account/ Create applicati on route table Dep loyment/ Advanced stack component s/ Identit y and Access Managemen t (IAM)/ Create entity or policy De ployment/ Earlier updates Version April 22, 2025 3045 AMS Advanced Change Type Reference AMS Advanced Change Type Details Change Description Link(s) Advanced stack component s/KMS key/ Create (review required) (1.0 and 2.0) Depl oyment/ Advanced stack component s/S3 storage/ Create policy De ployment/ Advanced stack component s/ Securit y group/ Create (review required) Deployme nt/ Advanc ed stack component s/Tag/ Create (review required) Manageme nt/AWS service/ Earlier updates Version April 22, 2025 3046 AMS Advanced Change Type Reference AMS Advanced Change Type Details Change Description Link(s) Self- provi sioned service/ Add Manage ment/ Advanced stack component s/EC2 instance stack/ Change hostname (Linux) (1.0) Manag ement/ Advanced stack component s/ Identit y and Access Managemen t (IAM)/ Delete entity or policy Ma nagement/ Advanced stack component s/ Identit y and Access Managemen Earlier updates Version April 22, 2025 3047 AMS Advanced Change Type Reference AMS Advanced Change Type Details Change Description Link(s) t (IAM)/ Update entity or policy Ma nagement/ Advanced stack component s/KMS key/ Delet e(1.0 and 2.0) Mana gement/ Advanced stack component s/KMS key/ Updat e(1.0 and 2.0) Mana gement/ Advanced stack component s/S3 storage/ Delete policy Ma nagement/ Advanced stack component s/S3 storage/ Earlier updates Version April 22, 2025 3048 AMS Advanced Change Type Reference AMS Advanced Change Type Details Change Description Link(s) Update policy Ma nagement/ Advanced stack component s/ Securit y group/ Delete Manag ement/ Advanced stack component s/ Securit y group/ Update Manag ement/ Advanced stack component s/Tag/ Bulk update (review required) Manageme nt/ Advanc ed stack component s/Tag/ Delete (review required) Manageme nt/ Advanc Earlier updates Version April 22, 2025 3049 AMS Advanced Change Type Reference AMS Advanced Change Type Details Change Description Link(s) ed stack component s/Tag/ Update (review required) Manageme nt/ Managed account/ D eveloper mode/ Enable Manage ment/ Standard stacks/ Stack/ Remed iate drift Man agement/ A pplicatio ns/IAM instance profile/ Create Man agement/ Host security/ Malware full system scan/ Disable Earlier updates Version April 22, 2025 3050 AMS Advanced Change Type Reference AMS Advanced Change Type Details Change Description Link(s) New CTs: Management \| Advanced Stack Components \| EC2 Instance Stack \| Gather log4j information December 20, 2021 Single instance scan use v1.0, Multi instance scan use v2.0. ct-19f40lfm5umy8 New CTs: Management \| Directory service \| DNS \| Delete conditional forwarder December 17, 2021 ct-1icghmq38rnsn Management \| Directory service \| DNS \| Update conditional forwarder December 17, 2021 ct-2fqmbyud166z9 New CTs: Deployment \| Directory service \| DNS \| Create conditional forwarder November 30, 2021 ct-3nba0wtdugnan Deployment \| Directory service \| DNS \| Create group managed service account November 30, 2021 ct-2qhl8j1pjnbgn Management \| Directory service \| DNS \| Update record permission November 30, 2021 ct-1eft8s6vdhz0w Management \| Directory service \| DNS \| Update cluster permissions November 30, 2021 ct-03ytgoevfebjr Earlier updates Version April 22, 2025 3051 AMS Advanced Change Type Reference AMS Advanced Change Type Details Change Description Deployment \| Advanced stack components \| Identity and Access Management (IAM) \| Create EC2 instance proﬁle ct-117rmp64d5mvb Link(s) November 30, 2021 Deployment \| Advanced stack components \| Identity and Access Management (IAM) \| Create Lambda execution role November 30, 2021 ct-1k3oui719dcju New CTs: Management \| Managed landing zone \| Management account \| Move Account to OU October 28, 2021 ct-1vq0f289r36ay Deployment \| AWS Backup \| Backup plan \| Create ct-2hyozbpa0sx0m. Additional parameters were for creating backup copies across accounts. Management \| Advanced stack components \| EBS snapshot \| Delete ct-30bﬁwxjku1nu. The CT description was expanded to mention some cavaets. Updated CTs: Management \| Advanced stack components \| EC2 instance \| Start ct-03t7kvuwx6rgr. The CT schema was updated so you can start mulitple EC2 instances. Management \| Advanced stack components \| EC2 instance \| Stop ct-3mvvt2zkyveqj. The CT schema was updated so you can stop mulitple EC2 instances. There's also a new parameter, ForceStop. November 11, 2021 October 28, 2021 Earlier updates Version April 22, 2025 3052 AMS Advanced Change Type Reference AMS Advanced Change Type Details Change Description Link(s) Management \| AWS Backup \| Recovery point \| Delete ct-1r1vbr8ahr156. The CT schema was updated so you can delete mulitple recovery points. Updated CTs: Deployment \| Advanced stack components \| Redshift \| Create (cluster from snapshot) version 1.0 October 14, 2021 ct-3jrqmeq7j0wke. A new parameter, NodeType, was added. Many change type examples were missing, this has been ﬁxed. September 30, 2021 Missing Examples Management \| Directory Service \| Computer object \| Remove SPN September 30, 2021 ct-1078jhyxq32dp Deployment \| Managed landing zone \| Networking account \| Disassociate TGW attachment September 30, 2021 ct-3jo8yccbin4it Deployment \| Managed landing zone \| Networking account \| Associate TGW attachment September 30,
ams-ct-778	ams-ct.pdf	778	\| Delete ct-1r1vbr8ahr156. The CT schema was updated so you can delete mulitple recovery points. Updated CTs: Deployment \| Advanced stack components \| Redshift \| Create (cluster from snapshot) version 1.0 October 14, 2021 ct-3jrqmeq7j0wke. A new parameter, NodeType, was added. Many change type examples were missing, this has been ﬁxed. September 30, 2021 Missing Examples Management \| Directory Service \| Computer object \| Remove SPN September 30, 2021 ct-1078jhyxq32dp Deployment \| Managed landing zone \| Networking account \| Disassociate TGW attachment September 30, 2021 ct-3jo8yccbin4it Deployment \| Managed landing zone \| Networking account \| Associate TGW attachment September 30, 2021 New CTs: ct-3nmhh0qr338q6 Deployment \| Managed landing zone \| Networking account \| Add static route September 30, 2021 ct-3r2ckznmt0a59 Deployment \| Managed landing zone \| Management account \| Create Developer Mode account (with VPC) September 30, 2021 ct-38xcr0q86k9lh Earlier updates Version April 22, 2025 3053 AMS Advanced Change Type Reference AMS Advanced Change Type Details Change Description Link(s) Management \| Advanced stack components \| Security Group \| Delete (no review required) September 30, 2021 ct-18r16ldqil6w9 Management \| Advanced stack components \| Security Group \| Disassociate (no review required) September 30, 2021 Updated CTs: ct-13lk0noacn6ua Management \| Advanced stack components \| AMI \| Deregister ct-26vhhlj9jmlpf This CT has a new parameter "DeleteSn apshots" to allow deleting snapshots associated with AMI. Management \| Advanced stack components \| AMI \| Deregister ct-2r2bﬀv9u6q4m A note was added that you cannot use the CT with Aurora MySQL or Aurora PostgreSQL. Classiﬁcation (two): Management \| Standard stacks \| Stack \| Remediate drift (auto) Management \| Custom stack \| Stack \| Remediate drift (auto) New CTs: ct-3kinq0u4l33zf. Management \| AWS Backup \| Backup plan \| Enable cross account copy (Management account) ct-2yja7ihh30ply. Management \| Advanced stack components \| EC2 instance stack \| Encrypt instance volumes ct-0hahohe17csnc. Updated CTs: Deployment \| Advanced stack components \| Database Migration Service (DMS) \| Create replication subnet group This CT (ct-2q5azjd8p1ag5) will fail if the 'dms-vpc-role' IAM role doesn't exist in the account. ct-2q5azjd8p1ag5. September 30, 2021 September 30, 2021 September 16, 2021 September 16, 2021 September 16, 2021 September 16, 2021 Earlier updates Version April 22, 2025 3054 AMS Advanced Change Type Reference AMS Advanced Change Type Details Link(s) September 16, 2021 Change Description Deployment \| Advanced stack components \| EC2 stack \| Create The note for InstanceType has been updated to this "Any EC2 instance created within AMS environments have pre-conﬁgured AMS components and agents like EPS, SSM, Cloudwatch etc., which occupy the resource’s capacity along with the applicati on workload. Therefore AMS does not recommend using the t2.micro/t3.micro and t2.nano/t3.nano instance types as they can impact the performance of the application and AMS tooling running on the instances. For more information, see Choosing the Right EC2 Instance Type for Your Application. ct-14027q0sjyt1h. Deployment \| Advanced stack components \| EC2 stack \| Create (with additional volumes) September 16, 2021 The note for InstanceType has been updated to this "Any EC2 instance created within AMS environments have pre-conﬁgured AMS components and agents like EPS, SSM, Cloudwatch etc., which occupy the resource’s capacity along with the applicati on workload. Therefore AMS does not recommend using the t2.micro/t3.micro and t2.nano/t3.nano instance types as they can impact the performance of the application and AMS tooling running on the instances. For more information, see Choosing the Right EC2 Instance Type for Your Application. ct-1aqsjf86w6vxg. Management \| Advanced stack components \| Security Group \| Associate September 16, 2021 There is a new version and support for additional resource types. ct-12lyw7otiyr6f. Earlier updates Version April 22, 2025 3055 AMS Advanced Change Type Reference AMS Advanced Change Type Details Change Description Link(s) Deployment \| AMS Resource Scheduler \| Solution \| Deploy ct-0ywnhc8e5k9z5. August 26, 2021 Management \| AMS Resource Scheduler \| State \| Enable ct-2wrvu4kca9xky. Management \| AMS Resource Scheduler \| State \| Disable ct-14v49adibs4db. New information, a note about the diﬀerenc e in usage for the change types if using a single- account landing zone or multi- account landing zone account. Management \| Patching \| Patch window \| Update ct-2utx36 abv83pv. August 26, 2021 Management \| Advanced stack components \| KMS key \| Enable rotation ct-2lt0jeydeumpe. August 26, 2021 Management \| Directory Service \| Users and groups \| Add group to group ct-1i20abktsm05v. August 26, 2021 New CTs: Management \| Directory Service \| Users and groups \| Add user to group ct-24pi85mjtza8k. August 26, 2021 Management \| Directory Service \| Users and groups \| Add group ct-3eutt7grkict4. August 26, 2021 Management \| Directory Service \| Users and groups \| Remove user from group ct-2019s9y3nfml4. August 26, 2021 Management \| Directory Service \| DNS \| Remove record ct-1icrtx8ydvdwe. August 26, 2021 Earlier updates Version April 22, 2025 3056 AMS Advanced Change Type Reference AMS Advanced Change Type Details Change Description Management \| Directory Service \| DNS \|
ams-ct-779	ams-ct.pdf	779	groups \| Add group to group ct-1i20abktsm05v. August 26, 2021 New CTs: Management \| Directory Service \| Users and groups \| Add user to group ct-24pi85mjtza8k. August 26, 2021 Management \| Directory Service \| Users and groups \| Add group ct-3eutt7grkict4. August 26, 2021 Management \| Directory Service \| Users and groups \| Remove user from group ct-2019s9y3nfml4. August 26, 2021 Management \| Directory Service \| DNS \| Remove record ct-1icrtx8ydvdwe. August 26, 2021 Earlier updates Version April 22, 2025 3056 AMS Advanced Change Type Reference AMS Advanced Change Type Details Change Description Management \| Directory Service \| DNS \| Add CNAME record ct-2murl5xzbxoxf. Management \| Directory Service \| DNS \| Add A record ct-2w3rbmnny1qpo. Management \| Advanced stack components \| EC2 instance stack \| Restore volumes The schema is updated with new parameters and the version is now 3.0. ct-2z60dyvto9g6c. Link(s) August 26, 2021 August 26, 2021 August 26, 2021 Deployment \| Advanced stack components \| DNS (private) \| Create August 26, 2021 The schema is updated with new parameters: AliasTarg etDnsName, AliasTargetHostedZoneId, and AliasTarg etEvaluatedTargetHealth to support "A" record to route traﬃc to AWS resource such as CloudFront distribution or an Amazon Updated CTs: S3 bucket, by providing the DNSName and HostedZoneID associated with the AWS resource. ct-0c38gftq56zj6 . Deployment \| Advanced stack components \| DNS (public) \| Create August 26, 2021 The schema is updated with new parameters: AliasTarg etDnsName, AliasTargetHostedZoneId, and AliasTarg etEvaluatedTargetHealth to support "A" record to route traﬃc to AWS resource such as CloudFront distribution or an Amazon S3 bucket, by providing the DNSName and HostedZoneID associated with the AWS resource. ct-0vzsr2nyraedl . Earlier updates Version April 22, 2025 3057 AMS Advanced Change Type Reference AMS Advanced Change Type Details Change Description Link(s) Management \| Advanced stack components \| DNS (private) \| Update August 26, 2021 The schema is updated with new parameters: AliasTarg etDnsName, AliasTargetHostedZoneId, and AliasTarg etEvaluatedTargetHealth to support "A" record to route traﬃc to AWS resource such as CloudFront distribution or an Amazon S3 bucket, by providing the DNSName and HostedZoneID associated with the AWS resource. ct-1d55pi44ﬀ21u. Management \| Advanced stack components \| DNS (public) \| Update August 26, 2021 The schema is updated with new parameters: AliasTarg etDnsName, AliasTargetHostedZoneId, and AliasTarg etEvaluatedTargetHealth to support "A" record to route traﬃc to AWS resource such as CloudFront distribution or an Amazon S3 bucket, by providing the DNSName and HostedZoneID associated with the AWS resource. ct-1hzofpphabs3i. Updated CTs: Deployment \| Advanced stack components \| RDS database stack \| Create The RDSDBEngine parameter has a new value available: mariadb. ct-2z60dyvto9g6c. August 12, 2021 New CTs: Deployment \| Advanced stack components \| Identity and Access Management (IAM) \| Create SAML identity provider July 29, 2021 ct-3hox8uwjgze1f. Management \| Advanced stack components \| Identity and Access Management (IAM) \| Delete SAML identity provider ct-01zl37gmuk4q2. Management \| Advanced stack components \| Identity and Access Management (IAM) \| Update SAML identity provider ct-379uwo67vbvng. July 29, 2021 July 29, 2021 Earlier updates Version April 22, 2025 3058 AMS Advanced Change Type Reference AMS Advanced Change Type Details Change Description New CTs: Deployment \| Advanced stack components \| VPNGateway \| Create ct-0qbikxr9okwvy. Link(s) July 15, 2021 Management \| Advanced stack components \| AMI \| Create from Auto Scaling group ct-3e3prksxmdhw8. July 15, 2021 Management \| Advanced stack components \| EBS Volume \| Attach ct-34jldf2qihaic. July 15, 2021 Management \| Advanced stack components \| EBS Volume \| Detach ct-2d55p1d7z6w3d. July 15, 2021 Managed ﬁrewall, Outbound (Palo Alto): Create allow list ct-309eozh6lpkr8. Managed ﬁrewall, Outbound (Palo Alto): Delete allow list ct-2fzh1wckpl7f5. July 15, 2021 July 15, 2021 Managed ﬁrewall, Outbound (Palo Alto): Create security policy ct-281dpwh9tqnan. July 15, 2021 Managed ﬁrewall, Outbound (Palo Alto): Delete security policy ct-1taxucdyi84iy. July 15, 2021 Managed ﬁrewall, Outbound (Palo Alto): Update security policy ct-0mss4i7neuj7f. July 15, 2021 Updated CTs: Management \| Managed ﬁrewall \| Outbound (Palo Alto) \| Add URLs and Management \| Managed ﬁrewall \| Outbound (Palo Alto) \| Remove URLs. New schemas. ct-2b9q8339bj2sa and ct-2mf36chtp1ejh. July 15, 2021 Management \| AWS service \| Self-provisioned service \| Add. New parameter, SAMLProviders. ct-3qe6io8t6jtny. July 15, 2021 Earlier updates Version April 22, 2025 3059 AMS Advanced Change Type Reference AMS Advanced Change Type Details Change Description Management \| Advanced stack components \| AMI \| Encrypt. Note warning not to try to encrypt AMIs that are already encrypted. ct-3u9yd8jznb2zd. Link(s) July 15, 2021 Earlier updates Version April 22, 2025 3060 AMS Advanced Change Type Reference AMS Advanced Change Type Details AWS Glossary For the latest AWS terminology, see the AWS glossary in the AWS Glossary Reference. Version April 22, 2025 3061
ams-og-001	ams-og.pdf	1	AMS Advanced Account Onboarding Information AMS Advanced Onboarding Guide Version May 08, 2024 Copyright © 2025 Amazon Web Services, Inc. and/or its aﬃliates. All rights reserved. AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information AMS Advanced Onboarding Guide: AMS Advanced Account Onboarding Information 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 Onboarding Guide AMS Advanced Account Onboarding Information Table of Contents AWS Managed Services Onboarding Introduction ........................................................................ 1 Learning about AMS .................................................................................................................................... 1 Key terms ....................................................................................................................................................... 2 AMS modes .................................................................................................................................................... 8 AMS modes and applications or workloads ...................................................................................... 9 AMS post-account prescriptive guidance .............................................................................................. 17 What we do, what we do not do ........................................................................................................... 17 AMS egress traﬃc management ............................................................................................................. 18 IAM user role ............................................................................................................................................... 19 MALZ: Default IAM User Roles ........................................................................................................... 20 SALZ: Default IAM User Role .............................................................................................................. 35 Default Access Firewall Rules .................................................................................................................. 47 Linux Stack Instance Ports .................................................................................................................. 47 Windows Stack Instance Ports ........................................................................................................... 48 Service management ..................................................................................................................... 49 Account governance ................................................................................................................................... 49 Service commencement ............................................................................................................................ 50 Customer relationship management (CRM) .......................................................................................... 50 CRM Process ........................................................................................................................................... 51 CRM meetings ........................................................................................................................................ 52 CRM Meeting Arrangements ............................................................................................................... 53 CRM monthly reports ........................................................................................................................... 54 Cost optimization ....................................................................................................................................... 55 Cost optimization framework ............................................................................................................. 55 Cost optimization responsibility matrix ........................................................................................... 57 Service hours ............................................................................................................................................... 59 Getting help ................................................................................................................................................ 60 Change management modes ........................................................................................................ 61 Modes overview .......................................................................................................................................... 62 Types of modes and accounts in AMS ............................................................................................. 62 AMS modes and applications or workloads .................................................................................... 67 Real world use cases for AMS modes ............................................................................................... 75 RFC mode ..................................................................................................................................................... 79 Learn about RFCs .................................................................................................................................. 79 Version May 08, 2024 iii AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information What are change types? .................................................................................................................... 125 Troubleshooting RFC errors .............................................................................................................. 137 Direct Change mode ............................................................................................................................... 148 Getting Started with Direct Change mode ................................................................................... 149 Security and compliance ................................................................................................................... 151 Change management in Direct Change mode ............................................................................. 156 Creating stacks using Direct Change mode .................................................................................. 159 Direct Change Mode use cases ........................................................................................................ 162 Developer mode ....................................................................................................................................... 163 Getting started with Developer mode ........................................................................................... 164 Security and compliance ................................................................................................................... 166 Change management ......................................................................................................................... 168 Provisioning infrastructure ............................................................................................................... 173 Detective controls ............................................................................................................................... 174 Logging, monitoring, and event management ............................................................................. 174 Incident management ........................................................................................................................ 174 Patch management ............................................................................................................................ 174 Continuity management ................................................................................................................... 175 Security and access management ................................................................................................... 175 Self-Service Provisioning mode in AMS .............................................................................................. 175 Getting started with SSP mode in AMS ........................................................................................ 176 Amazon API Gateway ........................................................................................................................ 177 Alexa for Business .............................................................................................................................. 178 Amazon AppStream 2.0 .................................................................................................................... 179 Amazon Athena ................................................................................................................................... 182 Amazon Bedrock ................................................................................................................................. 182 Amazon CloudSearch ......................................................................................................................... 184 Amazon CloudWatch Synthetics ...................................................................................................... 185 Amazon Cognito ................................................................................................................................. 186 Amazon Comprehend ........................................................................................................................ 187 Amazon Connect ................................................................................................................................. 188 Amazon Data Firehose ...................................................................................................................... 190 Amazon DevOps Guru ........................................................................................................................ 191 Amazon DocumentDB (with MongoDB compatibility) ................................................................ 192 Amazon DynamoDB ........................................................................................................................... 193 Amazon Elastic Container Registry ................................................................................................. 194 Version May 08, 2024 iv AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information EC2 Image Builder .............................................................................................................................. 195 Amazon ECS on AWS Fargate .......................................................................................................... 197 Amazon EKS on AWS Fargate .......................................................................................................... 199 Amazon EMR ....................................................................................................................................... 202 Amazon EventBridge .......................................................................................................................... 205 Amazon Forecast ................................................................................................................................ 207 Amazon FSx ......................................................................................................................................... 210 Amazon FSx for OpenZFS ................................................................................................................. 211 Amazon FSx for NetApp ONTAP ..................................................................................................... 213 Amazon Inspector Classic ................................................................................................................. 214 Amazon Kendra ................................................................................................................................... 215 Amazon Kinesis Data Streams ......................................................................................................... 216 Amazon Kinesis Video Streams ....................................................................................................... 217 Amazon Lex ......................................................................................................................................... 218 Amazon MQ ......................................................................................................................................... 218 Amazon Managed Service for Apache Flink ................................................................................. 219 Amazon Managed Streaming for Apache Kafka .......................................................................... 221 Amazon Managed Service for Prometheus ................................................................................... 222 Amazon Personalize ........................................................................................................................... 223 Amazon QuickSight ............................................................................................................................ 225 Amazon Rekognition .......................................................................................................................... 227 Amazon SageMaker AI ....................................................................................................................... 228 Amazon Simple Email Service ......................................................................................................... 231 Amazon Simple Workﬂow Service .................................................................................................. 232 Amazon Textract ................................................................................................................................. 233 Amazon Transcribe ............................................................................................................................. 234 Amazon WorkDocs ............................................................................................................................. 235 Amazon WorkSpaces .......................................................................................................................... 236 AMS Code services ............................................................................................................................. 238 AWS Amplify ........................................................................................................................................ 241 AWS AppSync ...................................................................................................................................... 242 AWS App Mesh .................................................................................................................................... 243 AWS Audit Manager ........................................................................................................................... 243 AWS Batch ............................................................................................................................................ 245 AWS Certiﬁcate Manager .................................................................................................................. 246 AWS Private Certiﬁcate Authority ................................................................................................... 247 Version May 08, 2024 v AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information AWS CloudEndure ............................................................................................................................... 250 AWS CloudHSM ................................................................................................................................... 251 AWS CodeBuild ................................................................................................................................... 252 AWS CodeCommit .............................................................................................................................. 254 AWS CodeDeploy ................................................................................................................................ 255 AWS CodePipeline .............................................................................................................................. 256 AWS Compute Optimizer .................................................................................................................. 258 AWS DataSync ..................................................................................................................................... 259 AWS Device Farm ............................................................................................................................... 261 AWS Elastic Disaster Recovery ......................................................................................................... 261 AWS Elemental MediaConvert ......................................................................................................... 263 AWS Elemental MediaLive ................................................................................................................ 263 AWS Elemental
ams-og-002	ams-og.pdf	2	241 AWS AppSync ...................................................................................................................................... 242 AWS App Mesh .................................................................................................................................... 243 AWS Audit Manager ........................................................................................................................... 243 AWS Batch ............................................................................................................................................ 245 AWS Certiﬁcate Manager .................................................................................................................. 246 AWS Private Certiﬁcate Authority ................................................................................................... 247 Version May 08, 2024 v AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information AWS CloudEndure ............................................................................................................................... 250 AWS CloudHSM ................................................................................................................................... 251 AWS CodeBuild ................................................................................................................................... 252 AWS CodeCommit .............................................................................................................................. 254 AWS CodeDeploy ................................................................................................................................ 255 AWS CodePipeline .............................................................................................................................. 256 AWS Compute Optimizer .................................................................................................................. 258 AWS DataSync ..................................................................................................................................... 259 AWS Device Farm ............................................................................................................................... 261 AWS Elastic Disaster Recovery ......................................................................................................... 261 AWS Elemental MediaConvert ......................................................................................................... 263 AWS Elemental MediaLive ................................................................................................................ 263 AWS Elemental MediaPackage ........................................................................................................ 264 AWS Elemental MediaStore .............................................................................................................. 265 AWS Elemental MediaTailor ............................................................................................................. 266 AWS Global Accelerator .................................................................................................................... 267 AWS Glue .............................................................................................................................................. 268 AWS Lake Formation ......................................................................................................................... 269 AWS Lambda ....................................................................................................................................... 271 AWS License Manager ....................................................................................................................... 272 AWS Migration Hub ........................................................................................................................... 273 AWS Outposts ..................................................................................................................................... 273 AWS Resilience Hub ........................................................................................................................... 274 AWS Secrets Manager ........................................................................................................................ 275 AWS Security Hub .............................................................................................................................. 278 AWS Service Catalog AppRegistry .................................................................................................. 279 AWS Shield ........................................................................................................................................... 280 AWS Snowball Edge ........................................................................................................................... 281 AWS Step Functions ........................................................................................................................... 283 AWS Systems Manager Parameter Store ....................................................................................... 284 AWS Systems Manager Automation ............................................................................................... 285 AWS Transfer Family .......................................................................................................................... 288 AWS Transit Gateway ......................................................................................................................... 289 AWS WAF .............................................................................................................................................. 291 AWS Well-Architected Tool .............................................................................................................. 292 AWS X-Ray ........................................................................................................................................... 292 Version May 08, 2024 vi AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information VM Import/Export .............................................................................................................................. 294 Customer Managed mode ...................................................................................................................... 295 Getting started with Customer Managed mode .......................................................................... 296 AMS and AWS Service Catalog ............................................................................................................. 296 Getting started with Service Catalog ............................................................................................. 296 Service Catalog in AMS before you begin ..................................................................................... 297 AMS Multi-account landing zone (MALZ) onboarding .............................................................. 301 MALZ network architecture ................................................................................................................... 301 About multi-account landing zone network architecture .......................................................... 301 Choosing single MALZ or multiple MALZs .................................................................................... 304 Multi-Account Landing Zone accounts ........................................................................................... 309 MALZ: Core account onboarding .......................................................................................................... 354 Create an AWS multi-account landing zone core account ......................................................... 355 Create an IAM role for AMS to access your account ................................................................... 356 Secure the new account with multi-factor authentication (MFA) for the root user ............... 359 Subscribe to AWS Marketplace for EPS ......................................................................................... 359 Set up networking .............................................................................................................................. 361 Set up access management .............................................................................................................. 365 MALZ: Application account onboarding .............................................................................................. 370 Requesting a new application account .......................................................................................... 370 Setting up Active Directory to federate access to AMS IAM roles ............................................ 372 Setting up networking with the new Application account ........................................................ 375 Setting up additional VPCs in the Application account .............................................................. 376 Appendix: multi-account landing zone (MALZ) onboarding consideration list ............................ 377 Account conﬁguration ....................................................................................................................... 377 AMS multi-account landing zone monitoring alerts ................................................................... 378 Network conﬁguration ...................................................................................................................... 378 Active Directory conﬁguration ......................................................................................................... 380 Trend Micro Endpoint Protection (EPS) ......................................................................................... 380 Access: Bastions, SSH and RDP ........................................................................................................ 380 Federation ............................................................................................................................................ 381 AMS Single-account landing zone (SALZ) onboarding .............................................................. 383 AMS SALZ onboarding process ............................................................................................................. 383 SALZ network architecture .................................................................................................................... 384 AMS Single-account landing zone shared services ...................................................................... 386 SALZ: Create a new AWS account for AMS ........................................................................................ 387 Version May 08, 2024 vii AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Create an AWS account ..................................................................................................................... 388 Set up consolidated billing–link new account to Payer account ............................................... 390 Conﬁgure your AWS account for AMS access ............................................................................... 391 Subscribe to AWS Marketplace for EPS ......................................................................................... 394 Subscribe to AWS Marketplace for CentOS 7.6 ........................................................................... 396 Secure the new account with multi-factor authentication (MFA) for the root user ............... 396 SALZ: Set up networking ....................................................................................................................... 396 Allocate IP Space for your AMS Environment .............................................................................. 396 Establish Private Network Connectivity to AWS .......................................................................... 398 Set up your Firewall ........................................................................................................................... 399 AMS Bastion Options during Application Migrations/Onboarding .......................................... 399 SALZ: Set up access management ....................................................................................................... 404 Establish an Active Directory (AD) trust ........................................................................................ 405 Federate your Active Directory with the AMS AWS Identity and Access Management roles ....................................................................................................................................................... 411 SALZ: Default settings ............................................................................................................................ 417 Endpoint Security (EPS) .................................................................................................................... 417 Security groups ................................................................................................................................... 421 EC2 IAM instance proﬁle ................................................................................................................... 426 Monitored metrics defaults .............................................................................................................. 433 Log retention and rotation defaults ............................................................................................... 448 Continuity management defaults ................................................................................................... 449 Patching defaults ................................................................................................................................ 450 Validate the AMS service (SALZ) .......................................................................................................... 451 Find account settings ......................................................................................................................... 451 Finding an instance ID or IP address .............................................................................................. 455 DNS friendly bastion names ............................................................................................................ 458 Finding bastion IP addresses ........................................................................................................... 459 EC2 instances: Creating ..................................................................................................................... 460 Access, requesting .............................................................................................................................. 469 Other \| Other RFC, creating (CLI) .................................................................................................... 477 Any stack: deleting, rebooting, starting, stopping ...................................................................... 480 Access examples .................................................................................................................................. 493 Reporting an incident ........................................................................................................................ 504 Creating a service request ................................................................................................................ 509 Post-onboarding steps ...................................................................................................................... 514 Version May 08, 2024 viii AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Tutorials ................................................................................................................................................ 514 Appendix: SALZ onboarding questionnaire ........................................................................................ 542 Deployment summary ....................................................................................................................... 542 Environment architecture considerations ...................................................................................... 542 Single-Account Landing Zone Monitoring Alerts ......................................................................... 543 Maintenance Window ........................................................................................................................ 544 Next Steps ............................................................................................................................................ 544
ams-og-003	ams-og.pdf	3	names ............................................................................................................ 458 Finding bastion IP addresses ........................................................................................................... 459 EC2 instances: Creating ..................................................................................................................... 460 Access, requesting .............................................................................................................................. 469 Other \| Other RFC, creating (CLI) .................................................................................................... 477 Any stack: deleting, rebooting, starting, stopping ...................................................................... 480 Access examples .................................................................................................................................. 493 Reporting an incident ........................................................................................................................ 504 Creating a service request ................................................................................................................ 509 Post-onboarding steps ...................................................................................................................... 514 Version May 08, 2024 viii AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Tutorials ................................................................................................................................................ 514 Appendix: SALZ onboarding questionnaire ........................................................................................ 542 Deployment summary ....................................................................................................................... 542 Environment architecture considerations ...................................................................................... 542 Single-Account Landing Zone Monitoring Alerts ......................................................................... 543 Maintenance Window ........................................................................................................................ 544 Next Steps ............................................................................................................................................ 544 Appendix: ActiveDirectory Federation Services (ADFS) claim rule and SAML settings ............ 545 ADFS claim rule conﬁgurations ............................................................................................................ 545 Web console .............................................................................................................................................. 546 API and CLI access with SAML .............................................................................................................. 546 Script conﬁguration ........................................................................................................................... 546 Windows conﬁguration ..................................................................................................................... 546 Linux conﬁguration ............................................................................................................................ 548 Document history ........................................................................................................................ 550 AWS Glossary ............................................................................................................................... 552 Version May 08, 2024 ix AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information AWS Managed Services Onboarding Introduction Welcome to AWS Managed Services (AMS). AMS is an enterprise service that provides ongoing management of your AWS infrastructure. This guide is designed to help you get started using AMS, including how to set up a new account for AMS, set up networking and access to AMS, and validate your onboarding setup. It is intended for IT administrators tasked with preparing for and carrying out the tasks required to onboard the AMS service to a new AWS account. Onboarding the AMS service requires special privileges to set up Active Directory trusts and complete other networking-level tasks. To get help in deciding whether to use multi-account landing zone accounts or single-account landing zone accounts, visit Choosing single MALZ or multiple MALZs . Important This guide is divided into two parts after this introduction: One for multi-account landing zone accounts and one for single-account landing zone accounts. The onboarding is quite diﬀerent for the two, please go next to the section of the guide that applies to your situation. Topics • Learning about AMS • AMS key terms • AMS modes • AMS post-account prescriptive guidance • What we do, what we do not do • AMS egress traﬃc management • IAM user role in AMS • Default Access Firewall Rules Learning about AMS To understand AMS better, refer to these AMS User Guide sections: Learning about AMS Version May 08, 2024 1 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information • What Is AWS Managed Services introduces the AMS service and describes the key features, operations, and interfaces as well as a typical AMS-managed network architecture. This chapter also provides information on access management including how to access your AMS-managed resources and using bastions. • Key Terms provides deﬁnitions and explanations for AMS terminology. • Understanding AMS Defaults provides the default values AMS uses, including the defaults for basic environment components, IAM and EC2, proxies, monitored metrics, logging, endpoint security (EPS), backups, and patching. • Change Management provides details on how requests for change (RFCs) and change types (CTs) work and includes examples of using AMS RFCs. • Several additional chapters cover accessing the AWS console, the AMS CLI, using the AMS change management system, the AMS SKMS, security, service requests, incidents, monitoring, logs, EPS, backups, and patch management. To learn more about AMS multi-account landing zone architecture, see Multi-Account Landing Zone network architecture To learn more about AMS single-account landing zone architecture, see Single-Account Landing Zone network architecture 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. Key terms Version May 08, 2024 2 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information • 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
ams-og-004	ams-og.pdf	4	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. Key terms Version May 08, 2024 2 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information • 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. 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 Key terms Version May 08, 2024 3 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information 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. • 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
ams-og-005	ams-og.pdf	5	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. Key terms Version May 08, 2024 4 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information • 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. • 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. Key terms Version May 08, 2024 5 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information • 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: • 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
ams-og-006	ams-og.pdf	6	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. Key terms Version May 08, 2024 6 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information • 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: • 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 Key terms Version May 08, 2024 7 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information 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. AMS modes Use this to help you select the appropriate AWS Managed Services (AMS) mode for hosting your applications, based on your desired combination of ﬂexibility and prescriptive governance to achieve your business outcomes. The intended audience for this information is: • Customer teams responsible for the strategy and governance of their landing zone. This information will help the team lay out the foundation of an AMS-managed landing zone, with the AMS modes they’d like to oﬀer to their internal and external customers. • Business and application owners tasked with migrating their application to AMS. This information will help with planning application migration, with the appropriate AMS mode to migrate/host their application. Note, the same application can be hosted
ams-og-007	ams-og.pdf	7	based on your desired combination of ﬂexibility and prescriptive governance to achieve your business outcomes. The intended audience for this information is: • Customer teams responsible for the strategy and governance of their landing zone. This information will help the team lay out the foundation of an AMS-managed landing zone, with the AMS modes they’d like to oﬀer to their internal and external customers. • Business and application owners tasked with migrating their application to AMS. This information will help with planning application migration, with the appropriate AMS mode to migrate/host their application. Note, the same application can be hosted in more than one AMS mode during diﬀerent phases of its Software Development Life Cycle (SDLC) lifecycle. • AMS partners tasked with guiding customers on the diﬀerent options to build and migrate to AMS. AMS modes Version May 08, 2024 8 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information This information assumes that you have already made the decision to leverage AMS to accelerate your journey to the cloud. Refer to this paper at two points in your cloud migration journey: First, during the foundation phase of setting up the AMS-managed platform. Second, when you are transitioning from the foundation to the migration phase of your cloud adoption journey, just after onboarding to AMS is complete and you're focusing on application governance and operations. AMS modes and applications or workloads Consider operational and governance requirements for your applications when selecting the right mode, either by requesting a new application account or hosting the application in an existing application account. The selection of the appropriate AMS mode for each application or workload depends on the following factors: • The type of SDLC lifecycle function that the environment will provide (e.g., sandbox with unmoderated changes, UAT with some frequent changes, production with minimal changes and highly regulated) • The governance policies needed (enforced through SCPs at the OU level) • Operational Model (if you want to own the operational responsibility or want to outsource that to AMS) • The desired business outcomes, like time to operate in the cloud, and cost of operations. Note For a descriptions of the mode types per AMS service, see Types of modes and accounts in AMS. For real-world use cases of the diﬀerent modes, see Real world use cases for AMS modes The following table outlines key considerations for application owners to help decide on the most suitable AMS mode. Application owners should include an assessment phase ahead of application migration to fully understand which mode applies to their speciﬁc application. Example: For applications based on cloud-native services or serverless architecture, the best option could be to start building and iterating in Developer mode and deploy the ﬁnal Infrastructure as Code using AMS Managed – SSP mode. In this case light re-factoring may be required to ensure that any CloudFormation templates created for automated deployment meet the ingest guidelines laid out by AMS. Additionally, any IAM permissions need to be approved by AMS Security to ensure they follow the least privilege model. AMS modes and applications or workloads Version May 08, 2024 9 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information The AMS mode selected to host the application, can help enable you to build towards you desired cloud operating model. Note More than one cloud operating model can existing in a single AMS Managed Landing Zone based on the diﬀerent AMS modes selected to host the applications. Decision issues Standard CM mode / OOD* AWS Service Catalog Direct Change mode Self- service provision ing Developer mode Customer Managed Operational readiness Logging, Monitorin g and Event Managemen t AMS responsible for all managed infrastructure Continuit y Managemen t AMS responsibility to execute backup plan selected by customer Customer responsib Customer le for responsib resources le for Self- provision Service ed using Provision developer ed Services IAM role (SSP) Customer responsib le for Self- Service Provision ed Services (SSP) outside AMS CM system Customer responsib le for resources provision ed using developer IAM role outside Customer responsible AMS modes and applications or workloads Version May 08, 2024 10 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Decision issues Standard CM mode / OOD* AWS Service Catalog Direct Change mode Self- service provision ing Developer mode Customer Managed AMS CM system Customer responsib le for resources provision ed using developer IAM role outside AMS CM system Customer responsib le for resources AMS-managed through one-way AD trust with on-prem domain. Requires Not managed infrastructure to join AMS applicable domain AMS Instance Level Access Managemen t Security Managemen t and Account AMS responsibility for all managed accounts Level Access Managemen t responsib provision le for all ed using managed developer accounts IAM role outside AMS CM system AMS modes and applications or workloads Version May 08, 2024
ams-og-008	ams-og.pdf	8	Service Catalog Direct Change mode Self- service provision ing Developer mode Customer Managed AMS CM system Customer responsib le for resources provision ed using developer IAM role outside AMS CM system Customer responsib le for resources AMS-managed through one-way AD trust with on-prem domain. Requires Not managed infrastructure to join AMS applicable domain AMS Instance Level Access Managemen t Security Managemen t and Account AMS responsibility for all managed accounts Level Access Managemen t responsib provision le for all ed using managed developer accounts IAM role outside AMS CM system AMS modes and applications or workloads Version May 08, 2024 11 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Decision issues Standard CM mode / OOD* AWS Service Catalog Direct Change mode Self- service provision ing Developer mode Customer Managed Patch Managemen t AMS responsibility for all managed accounts Change Managemen t AMS responsibility for all managed accounts Customer responsib Customer le for responsib resources le for Self- provision Service ed using Provision developer ed Services IAM role (SSP) outside AMS CM system Customer responsib Customer le for responsib resources le for Self- provision Service ed using Provision developer ed Services IAM role (SSP) outside AMS CM system AMS modes and applications or workloads Version May 08, 2024 12 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Decision issues Standard CM mode / OOD* AWS Service Catalog Direct Change mode Self- service provision ing Developer mode Customer Managed Prescript ive and Provision standardi ing zed for the Managemen provision t ing options oﬀered in AMS Flexibility to directly use AWS service API for AWS Service Catalog following AMS prescript ive standards Flexibility to directly use AWS Flexibility service to directly API use AWS following service APIs AMS for SSP prescript services ive standards Flexibility to directly use AWS service API for provision ing Incident Managemen t and Audit AMS responsibile for all managed accounts Customer responsib le for resources provision ed using developer IAM role outside AMS Change Managemen t System AMS modes and applications or workloads Version May 08, 2024 13 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Decision issues Standard CM mode / OOD* AWS Service Catalog Direct Change mode Self- service provision ing Developer mode Customer Managed GuardRail s and Shared infrastru cture Prescriptive and standardized leveraging AMS Core Accounts Flexible and bespoke leveraging AMS Core Accounts (Network) and Security Framework Applicati on refactori ng Support for AWS services Application readiness Light refactoring is needed Light refactori ng is needed (if No need for provisioned refactoring using AMS Standard CM) Limited to what is supported by AMS Not limited Business considerations AMS modes and applications or workloads Version May 08, 2024 14 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Decision issues Standard CM mode / OOD* AWS Service Catalog Direct Change mode Self- service provision ing Developer mode Customer Managed Time to operation al readiness Three to six months 6-18 months dependent on 6 months + dependent customer on customer application infrastru operations competencies cture and application operations competenc ies $ De-centra lized accounts/ applicati ons like sandbox, third party managed applicati ons Costs $$$$ $$$ $$ Applicati Webserver with 3 tier stack, apps with on compliance and regulatory requireme examples nts Webserver using API Gateway, container ized application leveraging ECS/EKS Iterating /optimizi ng on Data Lake application that uses Lambda, Glue, Athena, etc *Operations On Demand (OOD) has an oﬀering for customers using the Standard CM mode to manage their changes through dedicated resourcing. For more details, see the Operations on Demand catalog of oﬀerings and talk to your cloud service delivery manager (CSDM). AMS modes and applications or workloads Version May 08, 2024 15 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Note The price comparison between SSP mode and Developer mode assumes that the same AWS services are provisioned. Comparing AMS Modes against business and IT objectives As shown, if you are looking for a highly controlled and standardized governance model for you applications, then AMS-managed Standard Change, AWS Service Catalog, or Direct Change modes are the best ﬁt. If you require a bespoke governance model with a focus on application innovation without the need for operational readiness, select Customer Managed mode. With Customer Managed mode, it could take you a longer time to operationalize you applications as you bear the responsibility to establish people, processes, and tools to support operational capabilities such as Incident Management, Conﬁguration Management, Provisioning Management, Security Management, Patch Management, etc. AMS modes and applications or workloads Version May 08, 2024 16 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information AMS post-account prescriptive guidance As organizations adopt distributed operations and DevOps practices, there are a core set of operational capabilities that should be applied to every account prior to deployment of workloads
ams-og-009	ams-og.pdf	9	readiness, select Customer Managed mode. With Customer Managed mode, it could take you a longer time to operationalize you applications as you bear the responsibility to establish people, processes, and tools to support operational capabilities such as Incident Management, Conﬁguration Management, Provisioning Management, Security Management, Patch Management, etc. AMS modes and applications or workloads Version May 08, 2024 16 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information AMS post-account prescriptive guidance As organizations adopt distributed operations and DevOps practices, there are a core set of operational capabilities that should be applied to every account prior to deployment of workloads to meet the pillars of Well Architected. This link downloads a ZIP ﬁle containing a Word document, and a ZIP ﬁle with scripts and examples. Automated Account Setup is a set of scripts to automate, or bootstrap, the setup of a new application account. Once a new account is vended, and before any workloads are deployed, in order to make the account ready from an operational, security and management point of view, you setup default backup plans, patch windows, and encryption (and more). To help improve the agility, consistency, and responsiveness for application account setup, the following sample "How To" is provided for your reference. Automated Account Setup. 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. 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. AMS post-account prescriptive guidance Version May 08, 2024 17 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information 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 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, 2024 18 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information • 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
ams-og-010	ams-og.pdf	10	• 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. IAM user role in AMS An IAM role is similar to an IAM user, in that it is an AWS identity with permission policies that determine what the identity can and can't do in AWS. However, instead of being uniquely associated with one person, a role is intended to be assumable by anyone who needs it. Currently there is one AMS default user role, Customer_ReadOnly_Role, for standard AMS accounts and an additional role, customer_managed_ad_user_role for AMS accounts with Managed Active Directory. The role policies set permissions for CloudWatch and Amazon S3 log actions, AMS console access, read-only restrictions on most AWS services, restricted access to account S3 console, and AMS change-type access. IAM user role Version May 08, 2024 19 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Additionally, the Customer_ReadOnly_Role has mutative, reserved-instances permissions that allow you to reserve instances. It has some cost-saving values, so, if you know that you're going to need a certain number of Amazon EC2 instances for a long period of time, you can call those APIs. To learn more, see Amazon EC2 Reserved Instances. Note The AMS service level objective (SLO) for creating custom IAM policies for IAM users is four business days, unless an existing policy is going to be reused. If you want to modify the existing IAM user role, or add a new one, submit an IAM: Update Entity or IAM: Create Entity RFC, respectively. If you're unfamiliar with Amazon IAM roles, see IAM Roles for important information. Multi-Account Landing Zone (MALZ): To see the AMS multi-account landing zone default, un- customized, user role policies, see MALZ: Default IAM User Roles, next. MALZ: Default IAM User Roles JSON policy statements for the default multi-account AMS multi-account landing zone user roles. Note The user roles are customizable and may diﬀer on a per-account basis. Instructions on ﬁnding your role are provided. These are examples of the default MALZ user roles. To make sure that you have the policies set that you need, run the AWS command get-role or sign in to the AWS Management -> IAM console and choose Roles in the navigation pane. Core OU account roles A core account is an MALZ-managed infrastructure account. AMS multi-account landing zone Core accounts include a management account and a networking account. MALZ: Default IAM User Roles Version May 08, 2024 20 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Core OU account: Common roles and policies Role Policy or policies AWSManagedServicesReadOnlyRole ReadOnlyAccess (Public AWS Managed Policy). AWSManagedServicesCaseRole ReadOnlyAccess AWSSupportAccess (Public AWS Managed Policy). AWSManagedServicesChangeManagementRo le (Core account version) ReadOnlyAccess AWSSupportAccess AMSChangeManagementReadOnlyPolicy AMSChangeManagementInfrastructurePolicy Core OU account: Management account roles and policies Role Policy or policies AWSManagedServicesBillingRole AMSBillingPolicy (AMSBillingPolicy). AWSManagedServicesReadOnlyRole ReadOnlyAccess (Public AWS Managed Policy). AWSManagedServicesCaseRole ReadOnlyAccess AWSSupportAccess (Public AWS Managed Policy). AWSManagedServicesChangeManagementRo le (Management account version) ReadOnlyAccess AWSSupportAccess AMSChangeManagementReadOnlyPolicy AMSChangeManagementInfrastructurePolicy MALZ: Default IAM User Roles Version May 08, 2024 21 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Role Policy or policies AMSMasterAccountSpecificCha ngeManagementInfrastructure Policy Core OU Account: Networking account roles and policies Role Policy or policies AWSManagedServicesReadOnlyRole ReadOnlyAccess (Public AWS Managed Policy). AWSManagedServicesCaseRole ReadOnlyAccess AWSSupportAccess (Public AWS Managed Policy). AWSManagedServicesChangeManagementRo le (Networking account version) ReadOnlyAccess AWSSupportAccess AMSChangeManagementReadOnlyPolicy AMSChangeManagementInfrastructurePolicy AMSNetworkingAccountSpeciﬁcChangeMa nagementInfrastructurePolicy Application Account Roles Application account roles are applied to your application-speciﬁc accounts. Application account: Roles and policies Role Policy or policies AWSManagedServicesReadOnlyRole ReadOnlyAccess (Public AWS Managed Policy). AWSManagedServicesCaseRole ReadOnlyAccess MALZ: Default IAM User Roles Version May 08, 2024 22 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Role Policy or policies AWSSupportAccess (Public AWS Managed Policy). This policy provides access to all support operations and resources. For information, see Getting Started with AWS Support. AWSManagedServicesSecurityOpsRole ReadOnlyAccess AWSSupportAccess Example This policy provides access to all support operations and resources. AWSCertificateManagerFullAccess information, (Public AWS Managed Policy) AWSWAFFullAccess information, (Public AWS Managed policy). This policy grants full access to AWS WAF resources. AMSSecretsManagerSharedPolicy AWSManagedServicesChangeManagementRo le (Application account version) ReadOnlyAccess AWSSupportAccess (Public AWS Managed Policy). This policy provides access to all support operations and resources. For information, see Getting
ams-og-011	ams-og.pdf	11	08, 2024 22 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Role Policy or policies AWSSupportAccess (Public AWS Managed Policy). This policy provides access to all support operations and resources. For information, see Getting Started with AWS Support. AWSManagedServicesSecurityOpsRole ReadOnlyAccess AWSSupportAccess Example This policy provides access to all support operations and resources. AWSCertificateManagerFullAccess information, (Public AWS Managed Policy) AWSWAFFullAccess information, (Public AWS Managed policy). This policy grants full access to AWS WAF resources. AMSSecretsManagerSharedPolicy AWSManagedServicesChangeManagementRo le (Application account version) ReadOnlyAccess AWSSupportAccess (Public AWS Managed Policy). This policy provides access to all support operations and resources. For information, see Getting Started with AWS Support. AMSSecretsManagerSharedPolicy AMSChangeManagementPolicy AMSReservedInstancesPolicy MALZ: Default IAM User Roles Version May 08, 2024 23 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Role Policy or policies AMSS3Policy AWSManagedServicesAdminRole ReadOnlyAccess AWSSupportAccess AMSChangeManagementInfrastructurePolicy AWSMarketplaceManageSubscriptions AMSSecretsManagerSharedPolicy AMSChangeManagementPolicy AWSCertificateManagerFullAccess AWSWAFFullAccess AMSS3Policy AMSReservedInstancesPolicy Policy Examples Examples are provided for most policies used. To view the ReadOnlyAccess policy (which is pages long as it provides read-only access to all AWS services), you can use this link, if you have an active AWS account: ReadOnlyAccess. Also, a condensed version is included here. AMSBillingPolicy AMSBillingPolicy The new Billing role can be used by your accounting department to view and change billing information or account settings in the Management account. To access information such as Alternate Contacts, view the account resources usage, or keep a tab of your billing or even modify your payment methods, you use this role. This new role comprises of all the permissions listed in the AWS Billing IAM actions web page. { MALZ: Default IAM User Roles Version May 08, 2024 24 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information "Version": "2012-10-17", "Statement": [ { "Action": [ "aws-portal:ViewBilling", "aws-portal:ModifyBilling" ], "Resource": "", "Effect": "Allow", "Sid": "AllowAccessToBilling" }, { "Action": [ "aws-portal:ViewAccount", "aws-portal:ModifyAccount" ], "Resource": "", "Effect": "Allow", "Sid": "AllowAccessToAccountSettings" }, { "Action": [ "budgets:ViewBudget", "budgets:ModifyBudget" ], "Resource": "", "Effect": "Allow", "Sid": "AllowAccessToAccountBudget" }, { "Action": [ "aws-portal:ViewPaymentMethods", "aws-portal:ModifyPaymentMethods" ], "Resource": "", "Effect": "Allow", "Sid": "AllowAccessToPaymentMethods" }, { "Action": [ "aws-portal:ViewUsage" ], "Resource": "", "Effect": "Allow", MALZ: Default IAM User Roles Version May 08, 2024 25 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information "Sid": "AllowAccessToUsage" }, { "Action": [ "cur:DescribeReportDefinitions", "cur:PutReportDefinition", "cur:DeleteReportDefinition", "cur:ModifyReportDefinition" ], "Resource": "", "Effect": "Allow", "Sid": "AllowAccessToCostAndUsageReport" }, { "Action": [ "pricing:DescribeServices", "pricing:GetAttributeValues", "pricing:GetProducts" ], "Resource": "", "Effect": "Allow", "Sid": "AllowAccessToPricing" }, { "Action": [ "ce:", "compute-optimizer:" ], "Resource": "", "Effect": "Allow", "Sid": "AllowAccessToCostExplorerComputeOptimizer" }, { "Action": [ "purchase-orders:ViewPurchaseOrders", "purchase-orders:ModifyPurchaseOrders" ], "Resource": "", "Effect": "Allow", "Sid": "AllowAccessToPurchaseOrders" }, { "Action": [ "redshift:AcceptReservedNodeExchange", MALZ: Default IAM User Roles Version May 08, 2024 26 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information "redshift:PurchaseReservedNodeOffering" ], "Resource": "", "Effect": "Allow", "Sid": "AllowAccessToRedshiftAction" }, { "Action": "savingsplans:", "Resource": "", "Effect": "Allow", "Sid": "AWSSavingsPlansFullAccess" } ] } AMSChangeManagementReadOnlyPolicy AMSChangeManagementReadOnlyPolicy Permissions to see all AMS change types, and the history of requested change types. { "Version": "2012-10-17", "Statement": [{ "Sid": "AMSCoreAccountsCMAndSKMSReadOnlyAccess", "Effect": "Allow", "Action": [ "amscm:GetChangeTypeVersion", "amscm:GetRfc", "amscm:ListChangeTypeCategories", "amscm:ListChangeTypeClassificationSummaries", "amscm:ListChangeTypeItems", "amscm:ListChangeTypeOperations", "amscm:ListChangeTypeSubcategories", "amscm:ListChangeTypeVersionSummaries", "amscm:ListRestrictedExecutionTimes", "amscm:ListRfcSummaries", "amsskms:GetStack", "amsskms:GetSubnet", "amsskms:GetVpc", "amsskms:ListAmis", "amsskms:ListStackSummaries", "amsskms:ListSubnetSummaries", "amsskms:ListVpcSummaries" MALZ: Default IAM User Roles Version May 08, 2024 27 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information ], "Resource": "" }] } AMSMasterAccountSpeciﬁcChangeManagementInfrastructurePolicy AMSMasterAccountSpecificChangeManagementInfrastructurePolicy Permissions to request the Deployment \| Managed landing zone \| Management account \| Create application account (with VPC) change type. { "Version": "2012-10-17", "Statement": [{ "Sid": "AMSMasterAccountAccess", "Effect": "Allow", "Action": [ "amscm:ApproveRfc", "amscm:CancelRfc", "amscm:CreateRfc", "amscm:RejectRfc", "amscm:SubmitRfc", "amscm:UpdateRfc", "amscm:UpdateRfcActionState", "amscm:UpdateRestrictedExecutionTimes" ], "Resource": [ "arn:aws:amscm:global::changetype/ct-1zdasmc2ewzrs:" ] }] } AMSNetworkingAccountSpeciﬁcChangeManagementInfrastructurePolicy AMSNetworkingAccountSpecificChangeManagementInfrastructurePolicy Permissions to request the Deployment \| Managed landing zone \| Networking account \| Create application route table change type. { "Version": "2012-10-17", MALZ: Default IAM User Roles Version May 08, 2024 28 AMS Advanced Account Onboarding Information AMS Advanced Onboarding Guide "Statement": [{ "Sid": "AMSNetworkingAccountAccess", "Effect": "Allow", "Action": [ "amscm:ApproveRfc", "amscm:CancelRfc", "amscm:CreateRfc", "amscm:RejectRfc", "amscm:SubmitRfc", "amscm:UpdateRfc", "amscm:UpdateRfcActionState", "amscm:UpdateRestrictedExecutionTimes" ], "Resource": [ "arn:aws:amscm:global::changetype/ct-1urj94c3hdfu5:" ] }] } AMSChangeManagementInfrastructurePolicy AMSChangeManagementInfrastructurePolicy (for Management \| Other \| Other CTs) Permissions to request the Management \| Other \| Other \| Create, and Management \| Other \| Other \| Update change types. { "Version": "2012-10-17", "Statement": [{ "Sid": "AMSCoreAccountsAccess", "Effect": "Allow", "Action": [ "amscm:CancelRfc", "amscm:CreateRfc", "amscm:SubmitRfc", "amscm:UpdateRfc", "amscm:UpdateRfcActionState", "amscm:UpdateRestrictedExecutionTimes", ], "Resource": [ "arn:aws:amscm:global::changetype/ct-1e1xtak34nx76:", "arn:aws:amscm:global::changetype/ct-0xdawir96cy7k:", ] MALZ: Default IAM User Roles Version May 08, 2024 29 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information }] } AMSSecretsManagerSharedPolicy AMSSecretsManagerSharedPolicy Permissions to view secret passwords/hashes shared by AMS through AWS Secrets Manager (e.g. passwords to infrastructure for auditing). Permissions to create secret password/hashes to share with AMS. (for example, license keys for products that need to be deployed). { "Version": "2012-10-17", "Statement": [{ "Sid": "AllowAccessToSharedNameSpaces", "Effect": "Allow", "Action": "secretsmanager:", "Resource": [ "arn:aws:secretsmanager:::secret:ams-shared/", "arn:aws:secretsmanager:::secret:customer-shared/" ] }, { "Sid": "DenyGetSecretOnCustomerNamespace", "Effect": "Deny", "Action": "secretsmanager:GetSecretValue", "Resource": "arn:aws:secretsmanager:::secret:customer-shared/" }, { "Sid": "AllowReadAccessToAMSNameSpace", "Effect": "Deny", "NotAction": [ "secretsmanager:Describe", "secretsmanager:Get", "secretsmanager:List"
ams-og-012	ams-og.pdf	12	"arn:aws:amscm:global::changetype/ct-0xdawir96cy7k:", ] MALZ: Default IAM User Roles Version May 08, 2024 29 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information }] } AMSSecretsManagerSharedPolicy AMSSecretsManagerSharedPolicy Permissions to view secret passwords/hashes shared by AMS through AWS Secrets Manager (e.g. passwords to infrastructure for auditing). Permissions to create secret password/hashes to share with AMS. (for example, license keys for products that need to be deployed). { "Version": "2012-10-17", "Statement": [{ "Sid": "AllowAccessToSharedNameSpaces", "Effect": "Allow", "Action": "secretsmanager:", "Resource": [ "arn:aws:secretsmanager:::secret:ams-shared/", "arn:aws:secretsmanager:::secret:customer-shared/" ] }, { "Sid": "DenyGetSecretOnCustomerNamespace", "Effect": "Deny", "Action": "secretsmanager:GetSecretValue", "Resource": "arn:aws:secretsmanager:::secret:customer-shared/" }, { "Sid": "AllowReadAccessToAMSNameSpace", "Effect": "Deny", "NotAction": [ "secretsmanager:Describe", "secretsmanager:Get", "secretsmanager:List" ], "Resource": "arn:aws:secretsmanager:::secret:ams-shared/" } ] } MALZ: Default IAM User Roles Version May 08, 2024 30 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information AMSChangeManagementPolicy AMSChangeManagementPolicy Permissions to request and view all AMS change types, and the history of requested change types. { "Version": "2012-10-17", "Statement": [{ "Sid": "AMSFullAccess", "Effect": "Allow", "Action": [ "amscm:", "amsskms:" ], "Resource": [ "" ] }] } AMSReservedInstancesPolicy AMSReservedInstancesPolicy Permissions to manage Amazon EC2 reserved instances; for pricing information, see Amazon EC2 Reserved Instances. { "Version": "2012-10-17", "Statement": [{ "Sid": "AllowReservedInstancesManagement", "Effect": "Allow", "Action": [ "ec2:ModifyReservedInstances", "ec2:PurchaseReservedInstancesOffering" ], "Resource": [ "" ] }] } MALZ: Default IAM User Roles Version May 08, 2024 31 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information AMSS3Policy AMSS3Policy Permissions to create and delete ﬁles from existing Amazon S3 buckets. Note These permissions do not grant the ability to create S3 buckets; that must be done with the Deployment \| Advanced stack components \| S3 storage \| Create change type. { "Version": "2012-10-17", "Statement": [{ "Effect": "Allow", "Action": [ "s3:AbortMultipartUpload", "s3:DeleteObject", "s3:PutObject", ], "Resource": "" }] } AWSSupportAccess AWSSupportAccess Full access to Support. For information, see Getting Started with Support. For Premium Support information, see Support. { "Version": "2012-10-17", "Statement": [{ "Effect": "Allow", "Action": [ "support:" ], "Resource": "" }] } MALZ: Default IAM User Roles Version May 08, 2024 32 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information AWSMarketplaceManageSubscriptions AWSMarketplaceManageSubscriptions (Public AWSManaged Policy) Permissions to subscribe, unsubscribe, and view AWS Marketplace subscriptions. { "Version": "2012-10-17", "Statement": [{ "Action": [ "aws-marketplace:ViewSubscriptions", "aws-marketplace:Subscribe", "aws-marketplace:Unsubscribe" ], "Effect": "Allow", "Resource": "" }] } AWSCertiﬁcateManagerFullAccess AWSCertificateManagerFullAccess Full access to AWS Certiﬁcate Manager. For more information, see AWS Certiﬁcate Manager. AWSCertificateManagerFullAccess information, (Public AWS Managed Policy). { "Version": "2012-10-17", "Statement": [{ "Effect": "Allow", "Action": [ "acm:" ], "Resource": "" }] } AWSWAFFullAccess AWSWAFFullAccess Full access to AWS WAF. For more information, see AWS WAF - Web Application Firewall. MALZ: Default IAM User Roles Version May 08, 2024 33 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information AWSWAFFullAccess information, (Public AWS Managed policy). This policy grants full access to AWS WAF resources. { "Version": "2012-10-17", "Statement": [{ "Action": [ "waf:", "waf-regional:", "elasticloadbalancing:SetWebACL" ], "Effect": "Allow", "Resource": "" }] } ReadOnlyAccess ReadOnlyAccess Read-only access to all AWS services and resources on the AWS console. When AWS launches a new service, AMS updates the ReadOnlyAccess policy to add read-only permissions for the new service. The updated permissions are applied to all principal entities that the policy is attached to. This doesn't grant the ability to log into EC2 hosts or database hosts. If you have an active AWS account, then you can use this link ReadOnlyAccess to view the entire ReadOnlyAccess policy. The whole ReadOnlyAccess policy is very long as it provides read-only access to all AWS services. The following is a partial excerpt of the ReadOnlyAccess policy. {{ "Version": "2012-10-17", "Statement": [ { "Sid": "ReadOnlyActions", "Effect": "Allow", "Action": [ "a4b:Get", "a4b:List", "a4b:Search", "access-analyzer:GetAccessPreview", "access-analyzer:GetAnalyzedResource", ...{truncated} MALZ: Default IAM User Roles Version May 08, 2024 34 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information } Single-Account Landing Zone (SALZ): To see the AMS single-account landing zone default, uncustomized, user role policies, see SALZ: Default IAM User Role, next. SALZ: Default IAM User Role JSON policy statements for the default AMS single-account landing zone user role. Note The SALZ default user role is customizable and may diﬀer on a per-account basis. Instructions on ﬁnding your role are provided. This is an example of the default SALZ user role, but to make sure that you have the policies set for you, run the AWS command get-role or sign in to the AWS Management -> IAM console at https://console.aws.amazon.com/iam/. In the IAM console, in the navigation pane, choose Roles. The customer read-only role is a combination of multiple policies. A breakdown of the role (JSON) follows. Managed Services Audit Policy: {"Version": "2012-10-17", "Statement": [ { "Sid": "BasicConsoleAccess", "Effect": "Allow", "Action": [ "aws-portal:View", "ec2-reports:View", "support:" ], "Resource": [ "" ] }, { "Sid": "AuditAccessToAWSServices", "Effect": "Allow", "Action": [ SALZ: Default IAM User Role Version May 08, 2024 35 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information "acm:Describe", "acm:List", "appstream:Get", "autoscaling:Describe", "cloudformation:Describe", "cloudformation:Get", "cloudformation:List", "cloudformation:ValidateTemplate", "cloudfront:Get", "cloudfront:List*",
ams-og-013	ams-og.pdf	13	get-role or sign in to the AWS Management -> IAM console at https://console.aws.amazon.com/iam/. In the IAM console, in the navigation pane, choose Roles. The customer read-only role is a combination of multiple policies. A breakdown of the role (JSON) follows. Managed Services Audit Policy: {"Version": "2012-10-17", "Statement": [ { "Sid": "BasicConsoleAccess", "Effect": "Allow", "Action": [ "aws-portal:View", "ec2-reports:View", "support:" ], "Resource": [ "" ] }, { "Sid": "AuditAccessToAWSServices", "Effect": "Allow", "Action": [ SALZ: Default IAM User Role Version May 08, 2024 35 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information "acm:Describe", "acm:List", "appstream:Get", "autoscaling:Describe", "cloudformation:Describe", "cloudformation:Get", "cloudformation:List", "cloudformation:ValidateTemplate", "cloudfront:Get", "cloudfront:List", "cloudsearch:Describe", "cloudsearch:List", "cloudtrail:DescribeTrails", "cloudtrail:GetTrailStatus", "cloudtrail:LookupEvents", "cloudwatch:Describe", "cloudwatch:Get", "cloudwatch:List", "codecommit:Get", "codecommit:List", "codedeploy:BatchGet", "codedeploy:Get", "codedeploy:List", "codepipeline:Get", "codepipeline:List", "config:Describe", "config:Get", "datapipeline:Describe", "datapipeline:EvaluateExpression", "datapipeline:GetPipelineDefinition", "datapipeline:ListPipelines", "datapipeline:ValidatePipelineDefinition", "directconnect:Describe", "ds:Describe", "dynamodb:Describe", "dynamodb:List", "ec2:Describe", "ec2:Get", "ecs:Describe", "ecs:List", "elasticache:Describe", "elasticache:List", "elasticbeanstalk:Check", "elasticbeanstalk:Describe", SALZ: Default IAM User Role Version May 08, 2024 36 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information "elasticbeanstalk:List", "elasticbeanstalk:RequestEnvironmentInfo", "elasticbeanstalk:RetrieveEnvironmentInfo", "elasticfilesystem:Describe", "elasticloadbalancing:Describe", "elasticmapreduce:Describe", "elasticmapreduce:List", "elastictranscoder:List", "events:Describe", "events:Get", "events:List", "guardduty:Get", "guardduty:List", "kinesis:Describe", "kinesis:List", "kms:List", "lambda:Get", "lambda:List", "macie:Describe", "macie:Get", "macie:List", "opsworks:Describe", "opsworks:Get", "rds:Describe", "rds:Download", "rds:List", "redshift:Describe", "redshift:View", "route53:Get", "route53:List", "route53domains:CheckDomainAvailability", "route53domains:Get", "route53domains:List", "sdb:Get", "sdb:List", "ses:Get", "ses:List", "sns:Get", "sns:List", "sqs:Get", "sqs:List", "ssm:ListCommands", "ssm:ListCommandInvocations", "storagegateway:Describe", SALZ: Default IAM User Role Version May 08, 2024 37 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information "storagegateway:List", "swf:Count", "swf:Describe", "swf:Get", "swf:List", "tag:get", "trustedadvisor:Describe", "waf:Get", "waf:List", "waf-regional:Get", "waf-regional:List" ], "Resource": [ "" ] }, { "Sid": "AWSManagedServicesFullAccess", "Effect": "Allow", "Action": [ "amscm:", "amsskms:" ], "Resource": [ "" ] } ] } Managed Services IAM ReadOnly Policy { "Statement": [ { "Action": [ "iam:GenerateCredentialReport", "iam:GetAccountAuthorizationDetails", "iam:GetAccountPasswordPolicy", "iam:GetAccountSummary", "iam:GetCredentialReport", "iam:GetGroup", "iam:GetGroupPolicy", SALZ: Default IAM User Role Version May 08, 2024 38 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information "iam:GetInstanceProfile", "iam:GetPolicy", "iam:GetPolicyVersion", "iam:GetRole", "iam:GetRolePolicy", "iam:GetUser", "iam:GetUserPolicy", "iam:ListAccountAliases", "iam:ListAttachedRolePolicies", "iam:ListEntitiesForPolicy", "iam:ListGroupPolicies", "iam:ListGroups", "iam:ListGroupsForUser", "iam:ListInstanceProfiles", "iam:ListInstanceProfilesForRole", "iam:ListMFADevices", "iam:ListPolicies", "iam:ListPolicyVersions", "iam:ListRolePolicies", "iam:ListRoles", "iam:ListSAMLProviders", "iam:ListUsers", "iam:ListVirtualMFADevices" ], "Effect": "Allow", "Resource": [ "" ], "Sid": "IAMReadOnlyAccess" }, { "Action": [ "iam:" ], "Effect": "Deny", "Resource": [ "arn:aws:iam:::group/mc-", "arn:aws:iam:::group/mc_", "arn:aws:iam:::policy/mc-", "arn:aws:iam:::policy/mc_", "arn:aws:iam:::role/mc-", "arn:aws:iam:::role/mc_", "arn:aws:iam:::role/Sentinel-", "arn:aws:iam:::role/Sentinel_", SALZ: Default IAM User Role Version May 08, 2024 39 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information "arn:aws:iam:::user/mc-", "arn:aws:iam:::user/mc_" ], "Sid": "DenyAccessToIamRolesStartingWithMC" } ], Managed Services User Policy "Version": "2012-10-17" } { "Version": "2012-10-17", "Statement": [ { "Sid": "AllowCustomerToListTheLogBucketLogs", "Effect": "Allow", "Action": [ "s3:ListBucket" ], "Resource": [ "arn:aws:s3:::mc-a-logs-" ], "Condition": { "StringLike": { "s3:prefix": [ "aws/", "app/", "encrypted", "encrypted/", "encrypted/app/" ] } } }, { "Sid": "BasicAccessRequiredByS3Console", "Effect": "Allow", "Action": [ "s3:ListAllMyBuckets", "s3:GetBucketLocation" ], "Resource": [ SALZ: Default IAM User Role Version May 08, 2024 40 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information "arn:aws:s3:::" ] }, { "Sid": "AllowCustomerToGetLogs", "Effect": "Allow", "Action": [ "s3:GetObject" ], "Resource": [ "arn:aws:s3:::mc-a-logs-/aws/", "arn:aws:s3:::mc-a-logs-/encrypted/app/" ] }, { "Sid": "AllowAccessToOtherObjects", "Effect": "Allow", "Action": [ "s3:DeleteObject", "s3:Get", "s3:List", "s3:PutObject" ], "Resource": [ "" ] }, { "Sid": "AllowCustomerToListTheLogBucketRoot", "Effect": "Allow", "Action": [ "s3:ListBucket" ], "Resource": [ "arn:aws:s3:::mc-a-logs-" ], "Condition": { "StringEquals": { "s3:prefix": [ "", "/" ] } } SALZ: Default IAM User Role Version May 08, 2024 41 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information }, { "Sid": "AllowCustomerCWLConsole", "Effect": "Allow", "Action": [ "logs:DescribeLogStreams", "logs:DescribeLogGroups" ], "Resource": [ "arn:aws:logs:::log-group:" ] }, { "Sid": "AllowCustomerCWLAccessLogs", "Effect": "Allow", "Action": [ "logs:FilterLogEvents", "logs:GetLogEvents" ], "Resource": [ "arn:aws:logs:::log-group:/aws/", "arn:aws:logs:::log-group:/infra/", "arn:aws:logs:::log-group:/app/", "arn:aws:logs:::log-group:RDSOSMetrics::" ] }, { "Sid": "AWSManagedServicesFullAccess", "Effect": "Allow", "Action": [ "amscm:", "amsskms:" ], "Resource": [ "" ] }, { "Sid": "ModifyAWSBillingPortal", "Effect": "Allow", "Action": [ "aws-portal:Modify" ], "Resource": [ SALZ: Default IAM User Role Version May 08, 2024 42 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information "" ] }, { "Sid": "DenyDeleteCWL", "Effect": "Deny", "Action": [ "logs:DeleteLogGroup", "logs:DeleteLogStream" ], "Resource": [ "arn:aws:logs:::log-group:" ] }, { "Sid": "DenyMCCWL", "Effect": "Deny", "Action": [ "logs:CreateLogGroup", "logs:CreateLogStream", "logs:DescribeLogStreams", "logs:FilterLogEvents", "logs:GetLogEvents", "logs:PutLogEvents" ], "Resource": [ "arn:aws:logs:::log-group:/mc/" ] }, { "Sid": "DenyS3MCNamespace", "Effect": "Deny", "Action": [ "s3:" ], "Resource": [ "arn:aws:s3:::mc-a-logs-/encrypted/mc/", "arn:aws:s3:::mc-a-logs-/mc/", "arn:aws:s3:::mc-a-logs--audit/", "arn:aws:s3:::mc-a-internal-/", "arn:aws:s3:::mc-a-internal-" ] }, { SALZ: Default IAM User Role Version May 08, 2024 43 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information "Sid": "ExplicitDenyS3CfnBucket", "Effect": "Deny", "Action": [ "s3:" ], "Resource": [ "arn:aws:s3:::cf-templates-" ] }, { "Sid": "DenyListBucketS3LogsMC", "Action": [ "s3:ListBucket" ], "Effect": "Deny", "Resource": [ "arn:aws:s3:::mc-a-logs-" ], "Condition": { "StringLike": { "s3:prefix": [ "auditlog/", "encrypted/mc/", "mc/" ] } } }, { "Sid": "DenyS3LogsDelete", "Effect": "Deny", "Action": [ "s3:Delete", "s3:Put" ], "Resource": [ "arn:aws:s3:::mc-a-logs-/" ] }, { "Sid": "DenyAccessToKmsKeysStartingWithMC", "Effect": "Deny", "Action": [ "kms:" SALZ: Default IAM User Role Version May 08, 2024 44 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information ], "Resource": [ "arn:aws:kms:::key/mc-", "arn:aws:kms:::alias/mc-" ] }, { "Sid": "DenyListingOfStacksStartingWithMC", "Effect": "Deny", "Action": [ "cloudformation:" ], "Resource": [ "arn:aws:cloudformation:::stack/mc-" ] }, { "Sid": "AllowCreateCWMetricsAndManageDashboards", "Effect": "Allow", "Action": [ "cloudwatch:PutMetricData" ], "Resource": [ "" ] }, { "Sid": "AllowCreateandDeleteCWDashboards", "Effect": "Allow", "Action": [ "cloudwatch:DeleteDashboards", "cloudwatch:PutDashboard" ], "Resource": [ "*" ] } ] } Customer
ams-og-014	ams-og.pdf	14	"mc/" ] } } }, { "Sid": "DenyS3LogsDelete", "Effect": "Deny", "Action": [ "s3:Delete", "s3:Put" ], "Resource": [ "arn:aws:s3:::mc-a-logs-/" ] }, { "Sid": "DenyAccessToKmsKeysStartingWithMC", "Effect": "Deny", "Action": [ "kms:" SALZ: Default IAM User Role Version May 08, 2024 44 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information ], "Resource": [ "arn:aws:kms:::key/mc-", "arn:aws:kms:::alias/mc-" ] }, { "Sid": "DenyListingOfStacksStartingWithMC", "Effect": "Deny", "Action": [ "cloudformation:" ], "Resource": [ "arn:aws:cloudformation:::stack/mc-" ] }, { "Sid": "AllowCreateCWMetricsAndManageDashboards", "Effect": "Allow", "Action": [ "cloudwatch:PutMetricData" ], "Resource": [ "" ] }, { "Sid": "AllowCreateandDeleteCWDashboards", "Effect": "Allow", "Action": [ "cloudwatch:DeleteDashboards", "cloudwatch:PutDashboard" ], "Resource": [ "" ] } ] } Customer Secrets Manager Shared Policy { SALZ: Default IAM User Role Version May 08, 2024 45 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information "Version": "2012-10-17", "Statement": [ { "Sid": "AllowSecretsManagerListSecrets", "Effect": "Allow", "Action": "secretsmanager:listSecrets", "Resource": "" }, { "Sid": "AllowCustomerAdminAccessToSharedNameSpaces", "Effect": "Allow", "Action": "secretsmanager:", "Resource": [ "arn:aws:secretsmanager:::secret:ams-shared/", "arn:aws:secretsmanager:::secret:customer-shared/" ] }, { "Sid": "DenyCustomerGetSecretCustomerNamespace", "Effect": "Deny", "Action": "secretsmanager:GetSecretValue", "Resource": "arn:aws:secretsmanager:::secret:customer-shared/" }, { "Sid": "AllowCustomerReadOnlyAccessToAMSNameSpace", "Effect": "Deny", "NotAction": [ "secretsmanager:Describe", "secretsmanager:Get", "secretsmanager:List" ], "Resource": "arn:aws:secretsmanager:::secret:ams-shared/" } ] } Customer Marketplace Subscribe Policy { "Version": "2012-10-17", "Statement": [ { "Sid": "AllowMarketPlaceSubscriptions", SALZ: Default IAM User Role Version May 08, 2024 46 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information "Effect": "Allow", "Action": [ "aws-marketplace:ViewSubscriptions", "aws-marketplace:Subscribe" ], "Resource": [ "*" ] } ] } Default Access Firewall Rules These are the default ﬁrewall rules required to access your instances. Note For information on ﬁrewall rules and ports required for establishing an AD one-way trust, see the AMS Security Guide by going to the AWS Artifact console -> Reports tab and search for AWS Managed Services. Linux Stack Instance Ports These rules are required for your authentication into AMS Linux stacks. Linux Instance Ports Rules FROM: Linux Stack Instance TO: CORP Domain Controller Port 389 389 88 88 Protocol Service Direction TCP UDP TCP UDP LDAP LDAP Kerberos Kerberos Ingress Ingress Ingress Ingress Default Access Firewall Rules Version May 08, 2024 47 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Windows Stack Instance Ports These rules are required for your authentication into AMS Windows stacks. FROM: Windows Stack Instance TO: CORP Domain Controller Port 88 135 389 Protocol Service TCP \| UDP Kerberos TCP \| UDP DCE/RPC Locator service TCP \| UDP LDAP Direction Ingress and Egress Ingress and Egress Ingress and Egress 3268 TCP \| UDP 445 TCP 49152 - 65535 TCP msft-gc, Microsoft Global Catalog (LDAP service which contains data Ingress and Egress from Active Directory forests) Microsoft-DS Active Directory, Windows shares Dynamic or private ports that cannot be registered with IANA. This range is used for private, or customized services or temporary purposes and for automatic allocatio n of ephemeral ports. Ingress and Egress Ingress and Egress Windows Stack Instance Ports Version May 08, 2024 48 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information 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, 2024 49 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information 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
ams-og-015	ams-og.pdf	15	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 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, 2024 50 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information • 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, 2024 51 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information CRM meetings 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, 2024 52 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information 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, 2024 53 AMS Advanced Onboarding Guide AMS
ams-og-016	ams-og.pdf	16	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, 2024 53 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information 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, 2024 54 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information 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, 2024 55 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information • 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
ams-og-017	ams-og.pdf	17	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 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, 2024 56 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information • 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, 2024 57 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information 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, 2024 58 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information 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, 2024 59 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information 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, 2024 60 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Change management modes AWS Managed Services (AMS) uses change management mode to guardrail changes in AMS Advanced. The
ams-og-018	ams-og.pdf	18	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, 2024 60 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Change management modes AWS Managed Services (AMS) uses change management mode to guardrail changes in AMS Advanced. The change management modes help you maintain high operational standards for the environment, and to control risk and prevent adverse impact. AMS Advanced has diﬀerent modes that provide diﬀerent levels of control and risk. All modes, except for Customer-Managed mode, are managed by AMS. The following are the available change management modes: • RFC mode (formerly Standard CM mode): Provides a "request for change" (RFC) system and AMS- custom change types (CTs) • Direct Change mode: Same as RFC mode plus use of AWS APIs and consoles to create AMS- managed resources • AWS Service Catalog on AMS: Similar to Direct Change mode, but instead of using the AMS change management system (RFCs), you use AWS Service Catalog to create resources that AMS then manages. • Developer mode: Same as Direct Change mode only the resources you create with AWS APIs and consoles are not AMS-managed—you are responsible for their management • Self Service Provisioning (SSP) mode: Same as Developer mode except there is no access to the AMS change management system (no RFCs) • Customer Managed mode: AMS provides you with a multi-account landing zone landing zone but all resource management is your responsibility The AWS Managed Services (AMS) change management system, using the change management (CM) API, provides operations to create and manage requests for change (RFCs) for both multi- account landing zone (MALZ) and single-account landing zone (SALZ) accounts. A request for change (RFC) is a request created by either you or AMS through the AMS interface to make a change to your managed environment and includes a change type (CT) ID for a particular operation. The AMS change management (CM) API provides operations to create and manage requests for change (RFCs). You can create, update, submit, approve, reject, and cancel RFCs. The AMS operators can create, update, submit, approve, reject, cancel, and mark RFCs as closed. For a list of AMS reserved preﬁxes not to be used in tag or other names, see Reserved preﬁxes. Version May 08, 2024 61 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information For information on each change type, including schemas and examples, see the AMS Change Type Reference. Note All change management API calls are recorded in AWS CloudTrail. For more information, see Accessing your logs. Modes overview Use this information to help you select the appropriate AWS Managed Services (AMS) mode for hosting your applications, based on your desired combination of ﬂexibility and prescriptive governance to achieve your business outcomes. The intended audience for this information is: • Customer teams responsible for the strategy and governance of their landing zone. This information will help the team lay out the foundation of an AMS-managed landing zone, with the AMS modes they’d like to oﬀer to their internal and external customers. • Business and application owners tasked with migrating their application to AMS. This information will help with planning application migration, with the appropriate AMS mode to migrate/host their application. Note, the same application can be hosted in more than one AMS mode during diﬀerent phases of its Software Development Life Cycle (SDLC) lifecycle. • AMS partners tasked with guiding customers on the diﬀerent options to build and migrate to AMS. This information is most useful during the foundation phase of setting up your AMS-managed platform, and when you are transitioning from the foundation to the migration phase of your cloud adoption journey, just after onboarding to AMS is complete and you're focusing on application governance and operations. Types of modes and accounts in AMS AWS Managed Services (AMS) modes can be deﬁned as the ways of interacting with the AMS service under the speciﬁc governance framework for each mode. The landing zone diﬀerences, multi-account landing zone or MALZ and single-account landing zone or SALZ are noted. Modes overview Version May 08, 2024 62 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Note For details about application deployment and choosing the right AMS mode, see AMS modes and applications or workloads. For real-world use cases of the diﬀerent modes, see Real world use cases for AMS modes The following table provides descriptions of the modes per AMS service. AMS feature RFC mode (formerly Direct Change Standard mode CM mode) /
ams-og-019	ams-og.pdf	19	service under the speciﬁc governance framework for each mode. The landing zone diﬀerences, multi-account landing zone or MALZ and single-account landing zone or SALZ are noted. Modes overview Version May 08, 2024 62 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Note For details about application deployment and choosing the right AMS mode, see AMS modes and applications or workloads. For real-world use cases of the diﬀerent modes, see Real world use cases for AMS modes The following table provides descriptions of the modes per AMS service. AMS feature RFC mode (formerly Direct Change Standard mode CM mode) / OOD* Landing Zone MALZ and MALZ and Conﬁgura SALZ SALZ tion Change Managemen t Change schedulin g, review Same as RFC mode for high- of manual risk changes changes, like IAM and change or security record groups AWS Service Catalog Self-service provisioning / Customer Managed Developer mode MALZ and SALZ None Logging, Monitoring, Guardrails, and Event Managemen t Yes (supported resources) No Types of modes and accounts in AMS Version May 08, 2024 63 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information AMS feature Continuity managemen t Security managemen t Patch managemen t Incident and problem managemen t Reporting Service request managemen t RFC mode (formerly Direct Change Standard mode CM mode) / OOD* Yes (supported resources) AWS Service Catalog Self-service provisioning / Customer Managed Developer mode No Not applicable / No Instance level security controls and account level controls Account level controls AWS Org level controls Yes Response and resolution SLA Not applicable / No Response SLA for resulting for AMS supported resources resources No No Yes Yes No Support requests only No *Operations On Demand (OOD) has an oﬀering for customers using the RFC mode to manage their changes through dedicated resourcing. For more details, see the Operations on Demand catalog of oﬀerings and talk to your cloud service delivery manager (CSDM). Note Self-Service Provisioning mode in AMS and AMS Advanced Developer mode may both appear to be a suitable ﬁt for an application that has complex architecture rooted in native Types of modes and accounts in AMS Version May 08, 2024 64 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information AWS Services. When architecting workloads, you make trade-oﬀs between operational excellence and agility, based on your business context. This is a good way to think about selecting SSP mode or Developer mode for your application. The selection may also change based on the SDLC phase of the application. For example: When the application is production-ready, then SSP mode maybe a more appropriate option due to stricter AMS guardrails in this mode. The guardrails are enforced in the form of preventative controls like RFC-based change control for IAM updates and SCPs at the application OU level. These business decisions can drive your engineering priorities. You might optimize to increase ﬂexibility for application owners in "pre-prod" phase at the expense of governance and operational support. MALZ architecture and associated AMS modes AMS multi-account landing zone (MALZ) gives you the option to automatically provision application accounts (or resource accounts) under the default Organizational Units (OU): Customer Managed OU, Managed OU, or Development OU. The infrastructure provisioned in the application accounts created under each of these OUs is subject to the speciﬁc AMS mode oﬀered by those foundational OUs. It is common to ﬁnd a mix of two or more modes in the same application account. For example: RFC mode and SSP mode can coexist in an AMS managed account that hosts pipeline architecture consisting of API Gateway and Lambda for trigger functions, and EC2, S3, and SQS for ingestion and orchestration. In this case, SSP mode would apply to Lambda and API Gateway. Figure 1 presents how diﬀerent modes are oﬀered through the foundational OUs in AMS. When requesting a new application account in AMS, you must select the OU for the account. MALZ architecture and associated AMS modes Types of modes and accounts in AMS Version May 08, 2024 65 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information AMS leverages the foundational OUs based on AWS best practices as a way to logically manage accounts using Service Control Policies (SCPs). This serves as a way to enforce the governance framework with each AMS mode. Any governance and security guardrails (in the form of SCPs) applied to the foundational OUs also get applied to the custom/child OUs automatically. Additional SCPs can be requested for the child OUs. It is important to understand that application accounts are not the same as modes. Modes are applied to the infrastructure provisioned within the accounts and deﬁne the operational responsibilities between AMS and customers. Figure 1: MALZ architecture and associated AMS modes Types of modes and accounts in AMS Version May 08, 2024 66 AMS Advanced Onboarding Guide AMS Advanced Account
ams-og-020	ams-og.pdf	20	enforce the governance framework with each AMS mode. Any governance and security guardrails (in the form of SCPs) applied to the foundational OUs also get applied to the custom/child OUs automatically. Additional SCPs can be requested for the child OUs. It is important to understand that application accounts are not the same as modes. Modes are applied to the infrastructure provisioned within the accounts and deﬁne the operational responsibilities between AMS and customers. Figure 1: MALZ architecture and associated AMS modes Types of modes and accounts in AMS Version May 08, 2024 66 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Note "Restrictive" implies that you can request custom policies for these OUs, they are approved by AMS on a case-by-case basis to ensure they don’t interfere in AMS's capabilities to provide operational excellence. For a detailed list of AMS guardrails see AMS Guardrails in the user guide. AMS modes and applications or workloads Consider operational and governance requirements for your applications when selecting the right mode, either by requesting a new application account or hosting the application in an existing application account. The selection of the appropriate AMS mode for each application or workload depends on the following factors: • The type of SDLC lifecycle function that the environment will provide (e.g., sandbox with unmoderated changes, UAT with some frequent changes, production with minimal changes and highly regulated) AMS modes and applications or workloads Version May 08, 2024 67 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information • The governance policies needed (enforced through SCPs at the OU level) • Operational Model (if you want to own the operational responsibility or want to outsource that to AMS) • The desired business outcomes, like time to operate in the cloud, and cost of operations. Note For a descriptions of the mode types per AMS service, see Types of modes and accounts in AMS. For real-world use cases of the diﬀerent modes, see Real world use cases for AMS modes The following table outlines key considerations for application owners to help decide on the most suitable AMS mode. Application owners should include an assessment phase ahead of application migration to fully understand which mode applies to their speciﬁc application. Example: For applications based on cloud-native services or serverless architecture, the best option could be to start building and iterating in Developer mode and deploy the ﬁnal Infrastructure as Code using AMS Managed – SSP mode. In this case light re-factoring may be required to ensure that any CloudFormation templates created for automated deployment meet the ingest guidelines laid out by AMS. Additionally, any IAM permissions need to be approved by AMS Security to ensure they follow the least privilege model. The AMS mode selected to host the application, can help enable you to build towards you desired cloud operating model. Note More than one cloud operating model can existing in a single AMS Managed Landing Zone based on the diﬀerent AMS modes selected to host the applications. AMS modes and applications or workloads Version May 08, 2024 68 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Decision issues Standard CM mode / OOD* AWS Service Catalog Direct Change mode Self- service provision ing Developer mode Customer Managed Operational readiness Logging, Monitorin g and Event Managemen t AMS responsible for all managed infrastructure Customer responsib Customer le for responsib resources le for Self- provision Service Provision ed using developer ed Services IAM role (SSP) outside AMS CM system Customer responsib Continuit y AMS responsibility to execute backup Managemen plan selected by customer t Customer le for Customer responsib resources responsible le for Self- provision Service ed using Provision developer ed Services IAM role (SSP) Instance Level Access Managemen t AMS-managed through one-way AD trust with on-prem domain. Requires managed infrastructure to join AMS domain Not applicable outside AMS CM system Customer responsib le for resources provision ed using AMS modes and applications or workloads Version May 08, 2024 69 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Decision issues Standard CM mode / OOD* AWS Service Catalog Direct Change mode Self- service provision ing Developer mode Customer Managed Security Managemen t and Account AMS responsibility for all managed accounts Level Access Managemen t Patch Managemen t AMS responsibility for all managed accounts developer IAM role outside AMS CM system Customer responsib le for resources AMS responsib provision le for all ed using managed developer accounts IAM role outside AMS CM system Customer responsib Customer le for responsib resources le for Self- Service Provision provision ed using developer ed Services IAM role (SSP) outside AMS CM system AMS modes and applications or workloads Version May 08, 2024 70 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Decision issues Standard CM mode / OOD* AWS Service Catalog Direct Change
ams-og-021	ams-og.pdf	21	accounts Level Access Managemen t Patch Managemen t AMS responsibility for all managed accounts developer IAM role outside AMS CM system Customer responsib le for resources AMS responsib provision le for all ed using managed developer accounts IAM role outside AMS CM system Customer responsib Customer le for responsib resources le for Self- Service Provision provision ed using developer ed Services IAM role (SSP) outside AMS CM system AMS modes and applications or workloads Version May 08, 2024 70 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Decision issues Standard CM mode / OOD* AWS Service Catalog Direct Change mode Self- service provision ing Developer mode Customer Managed Change Managemen t AMS responsibility for all managed accounts Customer responsib Customer le for responsib resources le for Self- provision Service ed using Provision developer ed Services IAM role (SSP) outside AMS CM system Prescript ive and Provision standardi ing zed for the Managemen provision t ing options oﬀered in AMS Flexibility to directly use AWS service API for AWS Service Catalog following AMS prescript ive standards Flexibility to directly use AWS Flexibility service to directly API use AWS following service APIs AMS for SSP prescript services ive standards Flexibility to directly use AWS service API for provision ing AMS modes and applications or workloads Version May 08, 2024 71 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Decision issues Standard CM mode / OOD* AWS Service Catalog Direct Change mode Self- service provision ing Developer mode Customer Managed Customer responsib le for resources provision ed using developer IAM role outside AMS Change Managemen t System AMS responsibile for all managed accounts Incident Managemen t and Audit GuardRail s and Shared infrastru cture Prescriptive and standardized leveraging AMS Core Accounts (Network) and Security Framework Application readiness Flexible and bespoke leveraging AMS Core Accounts AMS modes and applications or workloads Version May 08, 2024 72 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Decision issues Standard CM mode / OOD* AWS Service Catalog Direct Change mode Self- service provision ing Developer mode Customer Managed Light refactoring is needed Light refactori ng is needed (if No need for provisioned refactoring using AMS Standard CM) Limited to what is supported by AMS Not limited Applicati on refactori ng Support for AWS services Business considerations 6-18 months dependent on 6 months + dependent customer on customer application infrastru operations competencies cture and Time to operation al readiness Three to six months Costs $$$$ $$$ $$ application operations competenc ies $ AMS modes and applications or workloads Version May 08, 2024 73 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Decision issues Standard CM mode / OOD* AWS Service Catalog Direct Change mode Applicati Webserver with 3 tier stack, apps with on compliance and regulatory requireme examples nts Self- service provision ing Webserver using API Gateway, container ized application leveraging ECS/EKS Developer mode Customer Managed Iterating /optimizi ng on Data Lake application that uses Lambda, Glue, Athena, etc De-centra lized accounts/ applicati ons like sandbox, third party managed applicati ons *Operations On Demand (OOD) has an oﬀering for customers using the Standard CM mode to manage their changes through dedicated resourcing. For more details, see the Operations on Demand catalog of oﬀerings and talk to your cloud service delivery manager (CSDM). Note The price comparison between SSP mode and Developer mode assumes that the same AWS services are provisioned. Comparing AMS Modes against business and IT objectives AMS modes and applications or workloads Version May 08, 2024 74 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information As shown, if you are looking for a highly controlled and standardized governance model for you applications, then AMS-managed Standard Change, AWS Service Catalog, or Direct Change modes are the best ﬁt. If you require a bespoke governance model with a focus on application innovation without the need for operational readiness, select Customer Managed mode. With Customer Managed mode, it could take you a longer time to operationalize you applications as you bear the responsibility to establish people, processes, and tools to support operational capabilities such as Incident Management, Conﬁguration Management, Provisioning Management, Security Management, Patch Management, etc. Real world use cases for AMS modes Examine these to help determine how to use AMS modes. • Use Case 1, business imperative to lower costs with a time-sensitive data center exit: An enterprise with a compelling business event, like a data center exit, is interested in re-hosting their on-prem applications on the cloud. Most of the on-prem inventory consists of Windows and Linux servers with a mix of operating system versions. In doing so, the customer also wants to take advantage of cost savings that moving to the cloud oﬀers and improving the technical and security posture of their applications. The customer wants to move fast but
ams-og-022	ams-og.pdf	22	these to help determine how to use AMS modes. • Use Case 1, business imperative to lower costs with a time-sensitive data center exit: An enterprise with a compelling business event, like a data center exit, is interested in re-hosting their on-prem applications on the cloud. Most of the on-prem inventory consists of Windows and Linux servers with a mix of operating system versions. In doing so, the customer also wants to take advantage of cost savings that moving to the cloud oﬀers and improving the technical and security posture of their applications. The customer wants to move fast but does not have the in- house cloud operations expertise built out yet. The customer has to ﬁnd a balance of refactoring, too much refactoring can be risky against a tight timeline. However, with some refactoring, Real world use cases for AMS modes Version May 08, 2024 75 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information like updating OS versions and optimizing databases, applications can achieve the next level of performance. In this example, the customer can select AMS-managed RFC mode to re-host most of their applications. AMS provides infrastructure operations, while also guiding the customer operations teams on best practices on securely operating in the cloud. AMS-managed AWS Service Catalog and AMS-managed Direct Change mode gives the customer an extra ﬂexibility while achieving the same business outcomes and objectives. In addition, the customer can use the AMS Operations On Demand (OOD) oﬀering to have dedicated AMS operations engineers to prioritize the execution of requests for change (RFCs). While oﬄoading the undiﬀerentiated infrastructure operational tasks (patching, backups, account management, etc) to AMS, the customer can continue to focus on optimizing their application and ramp-up their internal teams on cloud operations. AMS provides monthly reports to the customer on cost savings, and makes recommendations on resource optimizations. In this use case, if there were end-of-life applications hosted on legacy OS versions like Windows 2003 and 2008, that the customer decided not to re-factor, those can also be migrated to AMS and hosted in an account that leverages Customer Managed mode. • Use Case 2, building a data lake with Lambda, Glue, Athena within the secure AMS boundary: An enterprise is looking to set up a Data Lake to meet the reporting needs for multiple applications in AMS. The customer wants to use S3 buckets for the storage of datasets and AWS Athena to query against the dataset for each report. S3 and AWS Athena will be deployed in separate AMS Managed accounts. The account with S3 also has other services like Glue, Lambda, and Step Functions to build a data ingestion pipeline. Glue, Lambda, Athena, and Step Functions are considered Self-Service Provisioning (SSP) services in this case. The customer also deployed an EC2 instance in the account that acts as an ad hoc tooling/scripting server. The customer starts by requesting AMS to enable the SSP services in their AMS Managed account. AMS provisions an IAM role for each service that the customer can assume, once the role is onboarded to the customer's federation solution. For ease of management, the customer can also combine the policies for the separate IAM roles into one custom role, alleviating the need to switch roles when working between the AWS services. Once the role is enabled in the account, the customer is able to conﬁgure the services as per their requirements. However, the customer must work with the AMS change management system to request additional permissions, depending on their use case. For example, for access to Glue Crawlers, additional permissions are needed by Glue. Additional permissions will also be needed to create event sources for Lambda. The customer will work with AMS to update IAM roles to allow cross-account access for Athena to query S3 buckets. Updates Real world use cases for AMS modes Version May 08, 2024 76 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information to service roles or service-linked roles will also be needed through AMS change management for Lambda to call the Step Functions service, and Glue to read and write to all S3 buckets. AMS works with customers to ensure that the least-privilege access model is followed and the IAM changes requested are not overly permissive and opening up the environment to unnecessary risk. The customer’s data lake team spends time planning for all IAM permissions needed for the services speciﬁc to the customer’s architecture and requests AMS to enable them. This is because all IAM changes are processed manually and undergo review from the AMS Security team. Time to process these requests should be accounted for in the application deployment schedule. As the SSP services are operational in the account, the customer can request support and report issues through AMS incident management and service requests. However, AMS will not
ams-og-023	ams-og.pdf	23	changes requested are not overly permissive and opening up the environment to unnecessary risk. The customer’s data lake team spends time planning for all IAM permissions needed for the services speciﬁc to the customer’s architecture and requests AMS to enable them. This is because all IAM changes are processed manually and undergo review from the AMS Security team. Time to process these requests should be accounted for in the application deployment schedule. As the SSP services are operational in the account, the customer can request support and report issues through AMS incident management and service requests. However, AMS will not actively monitor performance and concurrency metrics for Lambda, or job metrics for Glue. It is the customer’s responsibility to ensure appropriate logging and monitoring is enabled for SSP services. The EC2 instance and S3 bucket in the account are fully managed by AMS. • Use Case 3, quick and ﬂexible set up of a CICD deployment pipeline in AMS: A customer is looking to set up a Jenkins-based CICD pipeline to deploy code pipeline to all application accounts in AMS. The customer may ﬁnd it most suitable to host this CICD pipeline in the AMS-managed Direct Change mode (DCM) or AMS-managed Developer mode because it gives them ﬂexibility to set up the Jenkins server with required custom conﬁguration on EC2, with the desired IAM permissions to access CloudFormation and S3 buckets that host the artifact repository. While this can also be done in the AMS-managed RFC mode, the customer team would need to create multiple manual RFCs for IAM roles to iterate on the least permissive set of approved permissions, which are manually reviewed by AMS. DCM allows the customers to achieve their operational goals on AWS while avoiding the need to create multiple manual RFCs for IAM roles, when using AMS-managed RFC mode, to iterate on the least permissive set of approved permissions, which are manually reviewed by AMS. This would take time as well as education on the customer’s part to ramp up AMS processes and tools. Working with Developer mode, the customer can start with a "developer role" to provision infrastructure using native AWS APIs. The quickest and most ﬂexible way to set up this pipeline would be to use AMS Managed-Developer mode. Developer mode gives the quickest and easiest way, while compromising on operational integration, while DCM is less ﬂexible but does provide the same level of operational support as RFC mode. • Use Case 4, bespoke operating model within the AMS foundation: A customer is looking at a deadline-driven data center exit and one of their enterprise applications is fully managed by a third party MSP, including application operations and infrastructure operations. Assuming that the customer does not have time in the schedule to re-factor this application so that it Real world use cases for AMS modes Version May 08, 2024 77 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information can be operated by AMS, Customer Managed mode is a suitable option. The customer can take advantage of the automated and quick set up of AMS managed Landing Zone. They can leverage the centralized account management that controls account vending and connectivity through the centralized networking account. It also simpliﬁes their billing by consolidating charges for all customer managed accounts through the AMS Payer account. The customer has ﬂexibility to set up their bespoke access management model with the MSP separate from standard access management used for AMS Managed accounts. This way, using Customer Managed mode, they can set up an AMS managed environment while meeting their business requirement of vacating their on-prem environment. In this case, if the customer also has Windows-based applications that they are migrating to the cloud, and choose to move them to a Customer Managed account, the customer is responsible for creating a cloud operating model. This can be complex, expensive, and time consuming depending on the customer's ability to transform traditional IT processes and train people. The customer can save time and cost by "lift and shift" of such workloads to an AMS Managed account and oﬄoad infrastructure operations to AMS. Note Customers may sometimes feel the need to move application accounts between the governance framework of RFC or SSP mode and Developer mode. For example, customers may host an application in AMS-managed mode as part of initial lift and shift migration, but overtime want to re-write the application to optimize it for cloud- native AWS services. They could change the mode of the pre-prod account from AMS- managed RFC to AMS-managed Developer mode, giving them the ﬂexibility and agility for provisioning infrastructure. However, once infrastructure provisioning changes have been made using the "developer role", the same infrastructure cannot be moved back to AMS-managed RFC mode. This is because AMS cannot guarantee operations of infrastructure that was provisioned
ams-og-024	ams-og.pdf	24	or SSP mode and Developer mode. For example, customers may host an application in AMS-managed mode as part of initial lift and shift migration, but overtime want to re-write the application to optimize it for cloud- native AWS services. They could change the mode of the pre-prod account from AMS- managed RFC to AMS-managed Developer mode, giving them the ﬂexibility and agility for provisioning infrastructure. However, once infrastructure provisioning changes have been made using the "developer role", the same infrastructure cannot be moved back to AMS-managed RFC mode. This is because AMS cannot guarantee operations of infrastructure that was provisioned outside of the AMS change management system. Customers may need to create a new application account that oﬀers AMS-managed RFC mode and then re-deploy the "optimized" infrastructure conﬁguration through CloudFormation templates or custom AMIs ingested into an AMS-managed account. This is a clean way to deploy a production ready conﬁguration. Once deployed, the application will be under prescriptive AMS governance and operations. The same applies to switching modes between Customer Managed mode and AMS-managed. Real world use cases for AMS modes Version May 08, 2024 78 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information RFC mode RFC mode is the default mode for AMS Advanced operations plan customers. It includes a change management system with requests for change or RFCs and a catalog of change types to use to request the addition or change that you need to your accounts. This change management system provides a level of security in limiting who can make changes to your accounts. For details on AMS Advanced change types, see What Are AMS Change Types?. For details about onboarding to AMS Advanced, see AWS Managed Services Onboarding Introduction. For change type example walkthroughs, see the "Additional Information" section for the relevant change type in the AMS Advanced Change Type Reference Change Types by Classiﬁcation section. Note RFC mode was previously called "Change Management mode" or "Standard CM mode." Topics • Learn about RFCs • What are change types? • Troubleshooting RFC errors in AMS Learn about RFCs Requests for change, or RFCs, work in a two-fold manner. First, there are parameters required for the RFC itself. These are the options in the CreateRfc API. And second, there are parameters required for the action of the RFC (the execution parameters). To learn about the CreateRfc options, see the CreateRfc section of the AMS API Reference. These options typically appear in the Additional conﬁgurations area of the Create RFC pages. You can create and submit an RFC with the CreateRfc API, aws amscm create-rfc CLI, or using the AMS console Create RFC pages. For a tutorial on creating an RFC, see Create an RFC. Topics RFC mode Version May 08, 2024 79 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information • What are RFCs? • Authenticate when using the AMS API/CLI • Understand RFC security reviews • Understand RFC change type classiﬁcations • Understand RFC action and activity states • Understand RFC status codes • Understand RFC update CTs and CloudFormation template drift detection • Schedule RFCs • Approve or reject RFCs • Request RFC restricted run periods • Create, clone, update, ﬁnd, and cancel RFCs • Use the AMS console with RFCs • Learn about common RFC parameters • Sign up for the RFC daily email What are RFCs? A request for change, or RFC, is how you make a change in your AMS-managed environment, or ask AMS to make a change on your behalf. To create an RFC, you choose from AMS change types, choose RFC parameters (such as schedule), and then submit the request using either the AMS console or the API commands CreateRfc and SubmitRfc. An RFC contain two speciﬁcations, one for the RFC itself, and one for the change type (CT) parameters. At the command line, you can use an Inline RFC command, or a standard CreateRfc template in JSON format, that you ﬁll out and submit along with the CT JSON schema ﬁle that you create (based on the CT parameters). The CT name is an informal description of the CT. A CSIO (category, subcategory, item, operation) is a more formal description of a CT. Only the CT ID must be speciﬁed when creating an RFC. AMS notiﬁes you when the change has completed successfully (Success) or unsuccessfully (Failure). Note For information about troubleshooting RFC failures, see Troubleshooting RFC errors in AMS. Learn about RFCs Version May 08, 2024 80 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information The following graphic depicts the workﬂow of an RFC submitted by you. Authenticate when using the AMS API/CLI When you use the AMS API/CLI, you must authenticate with temporary credentials. To request temporary security credentials for federated users, cal GetFederationToken, AssumeRole, AssumeRoleWithSAML, or AssumeRoleWithWebIdentity AWS security token service (STS)
ams-og-025	ams-og.pdf	25	ID must be speciﬁed when creating an RFC. AMS notiﬁes you when the change has completed successfully (Success) or unsuccessfully (Failure). Note For information about troubleshooting RFC failures, see Troubleshooting RFC errors in AMS. Learn about RFCs Version May 08, 2024 80 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information The following graphic depicts the workﬂow of an RFC submitted by you. Authenticate when using the AMS API/CLI When you use the AMS API/CLI, you must authenticate with temporary credentials. To request temporary security credentials for federated users, cal GetFederationToken, AssumeRole, AssumeRoleWithSAML, or AssumeRoleWithWebIdentity AWS security token service (STS) APIs. A common choice is SAML. After set up, you add an argument to each operation that you call. For example: aws --profile saml amscm list-change-type-categories. A shortcut for SAML 2.0 proﬁles is to set the proﬁle variable at the start of each API/CLI with set AWS_DEFAULT_PROFILE=saml (for Windows; for Linux it would be export AWS_DEFAULT_PROFILE=saml). For information about setting CLI environment variables, see Conﬁguring the AWS Command Line Interface, Environment Variables. Learn about RFCs Version May 08, 2024 81 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Understand RFC security reviews The AWS Managed Services (AMS) change management approval process ensures that we perform a security review of changes we make in your accounts. AMS evaluates all the requests for change (RFCs) against AMS technical standards. Any change that might lower your account's security posture by deviating from the technical standards, goes through a security review. Duringthe security review, AMS highlights relevant risk and, in cases of high or very high security risk, your authorized security personnel accepts or rejects the RFC. All changes are also evaluated to assess for adverse impact on AMS's ability to operate. If potential adverse impacts are found, then additional reviews and approvals are required within AMS. AMS technical standards AMS Technical Standards deﬁne the minimum security criteria, conﬁgurations, and processes to establish the baseline security of your accounts. These standards must be followed by both AMS and you. Any change that could potentially lower the security posture of your account by deviating from the technical standards, goes through a Risk Acceptance process, where relevant risk is highlighted by AMS and accepted or rejected by the authorized security personnel from your end. All such changes are also evaluated to assess if there would be any adverse impact on AMS's ability to operate the account and, if so, additional reviews and approvals are required within AMS. RFC customer security risk management (CSRM) process When someone from your organization requests a change to your managed environment, AMS reviews the change to determine whether the request might deteriorate the security posture of your account by falling outside the technical standards. If the request does lower the security posture of the account, AMS notiﬁes your security team contact with the relevant risk, and executes the change; or, if the change introduces high or very high security risk in the environment, AMS seeks explicit approval from your security team contact in the form of risk acceptance (explained next). The AMS Customer Risk Acceptance process is designed to: • Ensure risks are clearly identiﬁed and communicated to the right owners • Minimize identiﬁed risks to your environment • Obtain and document approval from the designated security contacts who understand your organization's risk proﬁle Learn about RFCs Version May 08, 2024 82 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information • Reduce ongoing operational overhead for identiﬁed risks How to access technical standards and high or very high risks We have made AMS Technical Standards documentation available for your reference in the https:// console.aws.amazon.com/artifact/ as a report. Use the AMS Technical Standards documentation to understand whether a change would require risk acceptance from your authorized security contact prior to submitting a request for change (RFC). Find the Technical Standards report by searching on "AWS Managed Services (AMS) Technical Standards" in the AWS Artifact Reports tab search bar after logging in with the default AWSManagedServicesChangeManagementRole. Note The AMS technical standard document is accessible for the Customer_ReadOnly_Role in single-account landing zone. In multi-account landing zone, the AWSManagedServicesAdminRole used by security admins and AWSManagedServicesChangeManagementRole used by application teams, can be used to access the document. If your team uses a custom role, create an Other \| Other RFC to request access and we will update the speciﬁed custom role. Understand RFC change type classiﬁcations The change types that you use when submitting an RFC are divided into two broad categories: • Deployment: This classiﬁcation is for creating resources. • Management: This classiﬁcation is for updating or deleting resources. The Management category also contains change types for accessing instances, encrypting or sharing AMIs, and starting,stopping,rebooting, or deleting stacks. Understand RFC action and activity states RfcActionState (API) / Activity State (console) help you understand
ams-og-026	ams-og.pdf	26	access the document. If your team uses a custom role, create an Other \| Other RFC to request access and we will update the speciﬁed custom role. Understand RFC change type classiﬁcations The change types that you use when submitting an RFC are divided into two broad categories: • Deployment: This classiﬁcation is for creating resources. • Management: This classiﬁcation is for updating or deleting resources. The Management category also contains change types for accessing instances, encrypting or sharing AMIs, and starting,stopping,rebooting, or deleting stacks. Understand RFC action and activity states RfcActionState (API) / Activity State (console) help you understand the status of human intervention, or action, on an RFC. Used primarily for manual RFCs, the RfcActionState helps you understand when there is action needed by either you or AMS operations, and helps you see Learn about RFCs Version May 08, 2024 83 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information when AMS Operations is actively working on your RFC. This provides increased transparency into the actions being taken on an RFC during its lifecycle. RfcActionState (API) / Activity State (console) deﬁnitions: • AwsOperatorAssigned: An AWS operator is actively working on your RFC. • AwsActionPending: A response or action from AWS is expected. • CustomerActionPending: A response or action from the customer is expected. • NoActionPending: No action is required from either AWS or the customer. • NotApplicable: This state can't be set by AWS operators or customers, and is used only for RFCs that were created prior to this functionality being released. RFC action states diﬀer depending on whether the change type submitted requires manual review and has scheduling set to ASAP or not. • RFC ActionState changes during the review, approval, and start of a manual change type with deferred scheduling: • After you submit a manual, scheduled, RFC, the ActionState automatically changes to AwsActionPending to indicate that an operator needs to review and approve the RFC. • When an operator begins actively reviewing your RFC, the ActionState changes to AwsOperatorAssigned. • When the operator approves your RFC, the RFC Status changes to Scheduled, and the ActionState automatically changes to NoActionPending. • When the scheduled start time of the RFC is reached, the RFC Status changes to InProgress, and the ActionState automatically changes to AwsActionPending to indicate that an operator needs to be assigned for review of the RFC. • When an operator begins actively running the RFC, they change the ActionState to AwsOperatorAssigned. • Once completed, the Operator closes the RFC. This automatically changes the ActionState to NoActionPending. Learn about RFCs Version May 08, 2024 84 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Important • Action states can't be set by you. They are either set automatically based on changes in the RFC, or set manually by AMS operators. • If you add correspondence to an RFC, the ActionState is automatically set to AwsActionPending. • When an RFC is created, the ActionState is automatically set to NoActionPending. • When an RFC is submitted, the ActionState is automatically set to AwsActionPending. • When an RFC is Rejected, Canceled, or completed with a status of Success or Failure, the ActionState is automatically reset to NoActionPending. • Action states are enabled for both automated and manual RFCs, but mostly matter for manual RFCs because those type of RFCs often require communications. Review RFC action states use case examples Use Case: Visibility on Manual RFC Process • Once you submit a manual RFC, the RFC action state automatically changes to AwsActionPending to indicate that an operator needs to review and approve the RFC. When an operator begins actively reviewing your RFC, the RFC action state changes to AwsOperatorAssigned. • Consider a manual RFC that has been approved and scheduled and is ready to begin running. Once the RFC status changes to InProgress, the RFC action state automatically changes to AwsActionPending. It changes again to AwsOperatorAssigned once an operator starts actively running the RFC. • When a manual RFC is completed (closed as "Success" or "Failure"), the RFC Action state changes to NoActionPending to indicate that no further actions are necessary from either the customer or operator. Use case: RFC correspondence • When a manual RFC is Pending Approval, an AMS Operator might need further information from you. Operators will post a correspondence to the RFC and change the RFC action state to Learn about RFCs Version May 08, 2024 85 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information CustomerActionPending. When you respond by adding a new RFC correspondence, the RFC action state automatically changes to AwsActionPending. • When an automated or manual RFC has failed, you can add a correspondence to the RFC details, asking the AMS Operator why the RFC failed. When your correspondence is added, the RFC action state is automatically set to AwsActionPending. When
ams-og-027	ams-og.pdf	27	an AMS Operator might need further information from you. Operators will post a correspondence to the RFC and change the RFC action state to Learn about RFCs Version May 08, 2024 85 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information CustomerActionPending. When you respond by adding a new RFC correspondence, the RFC action state automatically changes to AwsActionPending. • When an automated or manual RFC has failed, you can add a correspondence to the RFC details, asking the AMS Operator why the RFC failed. When your correspondence is added, the RFC action state is automatically set to AwsActionPending. When the AMS operator picks up the RFC to view your correspondence, the RFC action state changes to AwsOperatorAssigned. When the operator responds by adding a new RFC correspondence, the RFC action state may be set to CustomerActionPending, indicating that there is another response from the customer expected, or to NoActionPending, indicating that no response from the customer is needed or expected. Understand RFC status codes RFC status codes help you track your requests. You can observe these status codes during an RFC run in the CLI output, or by refreshing the RFC list page in the console. You can also see the codes for an RFC on the details page for that RFC, which might look like this: You might see an RFC in your list that you didn't submit. When AMS operators use an internal-only CT, they submit it in an RFC and it displays in your RFC list. For more information, see Internal-only change types. Important You can request notiﬁcations of RFC state changes. For details, see RFC State Change Notiﬁcations. Learn about RFCs Version May 08, 2024 86 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information RFC status codes Success Failure Editing: the RFC has been created but not submitted Rejected: RFCs are rejected typically because they fail validation; for example, an unusable PendingApproval / Submitted: The RFC has resource, i.e. a subnet, is speciﬁed been submitted and the system is determini Canceled: RFCs are canceled typically because ng if it requires approval, and obtaining that they do not pass validation before the approval, if required conﬁgured start time has passed Approved by AWS / Approved by customer: Failure: The RFC has failed; see the StatusRea the RFC has been approved. Automated son in the output for failure reasons, and AMS RFCs are approved by AWS, manual RFCs operations automatically creates a trouble are approved by Operators and, sometimes, ticket and communicates with you as needed customers Scheduled: the RFC has passed syntax and requirement checks and is scheduled for running InProgress: the RFC is being run, note that RFCs that provision multiple resources or have long-running UserData, take longer to run Executed: The RFC has been run Success / Succeeded: The RFC has been successfully completed Note Canceled or rejected RFCs can be re-submitted using UpdateRfc; see also Update RFCs. If the RFC passes all the necessary conditions (for example, all required parameters are speciﬁed), the status changes to PendingApproval (even automated CTs require approval, which happens automatically if syntax and parameter checks pass). If it does not pass, the status changes to Learn about RFCs Version May 08, 2024 87 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Rejected. The StatusReason provides information about rejections; the ExecutionOutput ﬁelds provide information about approval and completion. Error codes include: • InvalidRfcStateException: The RFC is in a status that doesn't allow the operation that was called. For example, if the RFC has moved to the Submitted state, it can no longer be modiﬁed. • InvalidRfcScheduleException: The StartTime, EndTime, or TimeoutInMinutes parameters were breached. • InternalServerError: A diﬃculty with the system was encountered. • InvalidArgumentException: A parameter is incorrectly speciﬁed; for example, an unacceptable value is used. • ResourceNotFoundException: A value, such as the stack ID, cannot be found. If the scheduled requested start and end times (also known as the change run window) occur before the change is approved, the RFC status changes to Canceled. If the change is approved, the RFC status changes to Scheduled. The change run window for ASAP RFCs is the submitted time plus the ExpectedExecutionDuration value for the CT. At any time before the arrival of the change run window, a scheduled change (submitted with a RequestedStartTime in the CLI) can be modiﬁed or canceled. If the scheduled change is modiﬁed, it must then be re-submitted. When the change start time arrives (scheduled or ASAP) and after approvals are complete, the status changes to InProgress and no modiﬁcations can be made. If the change is completed within the speciﬁed change run window, the status changes to Success. If any part of the change fails, or if the change is still in progress when the change run window ends, the status changes
ams-og-028	ams-og.pdf	28	time before the arrival of the change run window, a scheduled change (submitted with a RequestedStartTime in the CLI) can be modiﬁed or canceled. If the scheduled change is modiﬁed, it must then be re-submitted. When the change start time arrives (scheduled or ASAP) and after approvals are complete, the status changes to InProgress and no modiﬁcations can be made. If the change is completed within the speciﬁed change run window, the status changes to Success. If any part of the change fails, or if the change is still in progress when the change run window ends, the status changes to Failure. Note During the InProgress, Success, or Failure change states, the RFC cannot be modiﬁed or canceled. The following diagram illustrates the RFC statuses from the CreateRFC call through to resolution. Learn about RFCs Version May 08, 2024 88 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Learn about RFCs Version May 08, 2024 89 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Understand RFC update CTs and CloudFormation template drift detection Resources provisioned in AMS use a modiﬁed AWS CloudFormation template. If a resource has a parameter changed directly through a service's AWS Management Console, then the CloudFormation creation record of that resource becomes out of sync. If this happens and you attempt to use an AMS update change type to update the resource in AMS, then AMS references the original resource conﬁguration and potentially resets changed parameters. This reset might be damaging, so AMS disallows RFCs with update change types if any extra AMS conﬁguration changes are detected. For a list of update change types, use the console ﬁlter. Drift remediation FAQs Questions and answers on AMS drift remediation. There are two change types that you can use to initiate drift remediation, one is execution mode=manual or "review required," the other is execution mode=automated. Drift remediation supported resources (ct-3kinq0u4l33zf) These are the resources that are supported by the drift remediation change type, (ct-3kinq0u4l33zf). For remediation of any resource, use the "review required" (ct-34sxfo53yuzah) change type instead. AWS::EC2::Instance AWS::EC2::SecurityGroup AWS::EC2::VPC AWS::EC2::Subnet AWS::EC2::NetworkInterface AWS::EC2::EIP AWS::EC2::InternetGateway AWS::EC2::NatGateway AWS::EC2::NetworkAcl AWS::EC2::RouteTable AWS::EC2::Volume AWS::AutoScaling::AutoScalingGroup AWS::AutoScaling::LaunchConfiguration AWS::AutoScaling::LifecycleHook AWS::AutoScaling::ScalingPolicy AWS::AutoScaling::ScheduledAction AWS::ElasticLoadBalancing::LoadBalancer AWS::ElasticLoadBalancingV2::Listener Learn about RFCs Version May 08, 2024 90 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information AWS::ElasticLoadBalancingV2::ListenerRule AWS::ElasticLoadBalancingV2::LoadBalancer AWS::CloudWatch::Alarm Drift remediation change types Questions and answers on using the AMS drift remediation change types. For a list of supported resources for the drift remediation feature, see Drift remediation supported resources (ct-3kinq0u4l33zf). Important Drift remediation modiﬁes the stack template and/or parameters and it is mandatory to update your local template repositories or any automation that is updating these stacks to use the latest stack template and parameters. Using old template and/or parameters without syncing can cause damaging changes to underlying resources. The no review required, automated, CT (ct-3kinq0u4l33zf) supports remediating only 10 resources per RFC. To remediate remaining resources in batches of 10 create new RFCs until all resources are remediated. Which drift remediation change type should I use? We recommend using the no review required, automated CT (ct-3kinq0u4l33zf) when: • You attempt to perform an update to an existing stack resource using an automated CT and the RFC gets rejected as the stack is DRIFTED. • You used an Update CT in the past and it failed as the stack was DRIFTED. You do not need to attempt an update again and can use the review required, manual, CT instead. We recommend using the review required, manual CT (ct-34sxfo53yuzah) only when drifted resource types are not supported by the drift remediation no review required, automated, CT (ct-3kinq0u4l33zf), or when the drift remediation no review required, automated, CT fails. What changes are performed to the stack during remediation? Remediation requires updates to the stack template and/or parameters depending on the properties that are drifted. Remediation also updates the stack policy of the stack during remediation and restores the stack policy to its previous value once remediation is completed. Learn about RFCs Version May 08, 2024 91 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information How can we see the changes performed to the stack template and/or parameters? In the response to the RFC, a change summary is provided with the following information: • ChangeSummaryJson: Contains change summary of Stack Template and/or Parameters as part of drift remediation. Remediation is performed in multiple phases. This change summary consists of changes for individual phases. If Remediation is successful check changes of the last phase. See ExecutionPlan in the JSON for phases executed in order. For example, RestoreReferences section when present is always executed at the end and contains JSON for post remediation changes. If remediation is run in DryRun mode none of these changes would have been applied to the stack. • PreRemediationStackTemplateAndConfigurationJson: Contains conﬁguration snapshot of CloudFormation Stack including Template, Parameters,
ams-og-029	ams-og.pdf	29	following information: • ChangeSummaryJson: Contains change summary of Stack Template and/or Parameters as part of drift remediation. Remediation is performed in multiple phases. This change summary consists of changes for individual phases. If Remediation is successful check changes of the last phase. See ExecutionPlan in the JSON for phases executed in order. For example, RestoreReferences section when present is always executed at the end and contains JSON for post remediation changes. If remediation is run in DryRun mode none of these changes would have been applied to the stack. • PreRemediationStackTemplateAndConfigurationJson: Contains conﬁguration snapshot of CloudFormation Stack including Template, Parameters, Outputs, StackPolicyBody before remediation was triggered on the stack. What do I need to do once remediation is performed? Important You need to update your local template repositories, or any automation, that would be updating the remediated stack, with the latest template and parameters provided in the RFC summary. It is very important to do this because using the old template and/or parameters can cause further destructive changes on the stack resources. Will my application be eﬀected during this remediation? Remediation is an oﬄine process that is performed only on the CloudFormation stack conﬁguration. No updates are performed on the underlying resource. Can I continue using Management \| Other \| Other RFCs to perform updates to resources after remediation? We recommend that you always perform updates to stack resources using the available automated Update CTs. When the available Update CTs do not support your use case, use Management \| Other \| Other requests. Does remediation create any new resources in the stack? Remediation does not create any new resources in the stack. However, remediation creates new outputs and updates the stack template metadata section to store the remediation summary for your reference. Learn about RFCs Version May 08, 2024 92 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Will remediation always be successful? Remediation requires careful analysis and validation of the template conﬁguration to determine if it can be performed. In scenarios where these validations fail, the remediation process is stopped and no changes are performed to the stack template or parameters. Also, remediation can only be performed on supported resource types. How can I perform updates to stack resources if remediation is not successful? You can use the Management \| Other \| Other \| Update CT (ct-0xdawir96cy7k) to request changes. AMS monitors such scenarios and works towards improving the remediation solution. Can I remediate stacks that have both supported and unsupported resource types? Yes. However, remediation is performed only if the supported resource types are found DRIFTED in the stack. If any unsupported resource types are DRIFTED, remediation does not continue. Can I request remediation for stacks created through non-CFN Ingest CTs? Yes. Remediation can be performed on stacks irrespective of the change type used for creating the stack. Can I know the changes that would be performed to the stack before remediation? Yes. Both change types provide a DryRun option that you can use to request changes that would be performed if the stack was remediated. However, the ﬁnal remediation changes may diﬀer depending on the drift present on the stack at the time of remediation. Schedule RFCs The Scheduling feature allows you to choose a start time for RFCs. The following options are available in the Scheduling feature: • Execute this change ASAP: AMS runs the RFC as soon as it's approved. Most CTs are automatically approved. Use this option if don't want the RFC to start at a speciﬁc time. • Schedule this change: Set a day, time, and time zone for the RFC to run. For automated change types, it's a best practice to request a start time that's at least 10 minutes after you plan to submit the RFC. For review required change types, it's required that you request a start time that's at least 24 hours after you plan to submit the RFC. If the RFC isn't approved by the conﬁgured start time, then the RFC is rejected. Learn about RFCs Version May 08, 2024 93 AMS Advanced Onboarding Guide Set an RFC schedule AMS Advanced Account Onboarding Information To schedule an RFC, use one of the following methods: Execute this change ASAP: • Console: Do nothing. This uses the default RFC schedule. • API or CLI: Remove the RequestedStartTime and RequestedEndTime options in the Create RFC operation. ASAP "review required" RFCs are auto-rejected if they are not approved within thirty days of submission. Schedule this change: • Console: Select the Schedule this change radio button. A Start time area opens. Manually type in a day or use the calendar widget to pick a day. Enter a time, in UTC, expressed in ISO 8601 format, and use the drop-down list to pick a location. By default, AMS uses the ISO 8601 format
ams-og-030	ams-og.pdf	30	ASAP: • Console: Do nothing. This uses the default RFC schedule. • API or CLI: Remove the RequestedStartTime and RequestedEndTime options in the Create RFC operation. ASAP "review required" RFCs are auto-rejected if they are not approved within thirty days of submission. Schedule this change: • Console: Select the Schedule this change radio button. A Start time area opens. Manually type in a day or use the calendar widget to pick a day. Enter a time, in UTC, expressed in ISO 8601 format, and use the drop-down list to pick a location. By default, AMS uses the ISO 8601 format YYYYMMDDThhmmssZ or YYYY-MM-DDThh:mm:ssZ, either format is accepted. Note The Default End Time is 4 hours from the Start time that you enter. To set the End Time of your scheduled change beyond 4 hours, use the API or CLI to run the change. • API or CLI: Submit values for the RequestedStartTime and RequestedEndTime parameters in the Create RFC operation. Passing a conﬁgured RequestedEndTime doesn't stop the run for an automated change type that has already started. For a "review required" change type, if the RequestedEndTime is reached while AMS Operations research is still ongoing, and you're in communication with AMS, then you can request an extension, or you might be asked to re- submit the RFC. Tip For an example of a UTC time readout, see UTC on the Time-is website. Example ISO 8601 format for a date/time value of 2016-12-05 at 2:20pm: 2016-12-05T14:20:00Z or 20161205T142000Z. Learn about RFCs Version May 08, 2024 94 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information If you provide... • only a RequestedStartTime, the RFC is considered scheduled and the RequestedEndTime is populated using the ExecutionDurationInMinutes value. • only a RequestedEndTime, we throw an InvalidArgumentException. • both RequestedStartTime and RequestedEndTime, we overwrite the RequestedEndTime with the speciﬁed start time plus the ExecutionDurationInMinutes value. • neither RequestedStartTime nor RequestedEndTime, we keep those values as null and the RFC is treated as an ASAP RFC. Note For all scheduled RFCs, an unspeciﬁed end time is written to be the time of the speciﬁed RequestedStartTime plus the ExpectedExecutionDurationInMinutes attribute of the submitted change type. For example, if the ExpectedExecutionDurationInMinutes is "60" (minutes), and the speciﬁed RequestedStartTime is 2016-12-05T14:20:00Z (December 5, 2016 at 4:20 AM), the actual end time would be set to December 5, 2016 at 5:20 AM. To ﬁnd the ExpectedExecutionDurationInMinutes for a speciﬁc change type, run this command: aws amscm --profile saml get-change-type-version -- change-type-id CHANGE_TYPE_ID --query "ChangeTypeVersion. {ExpectedDuration:ExpectedExecutionDurationInMinutes}" Use the RFC Priority option Use the Priority option in execution mode = manual change types to alert AMS Operations to the urgency of the request. Priority option in execution mode = manual: Specify the priority of a manual RFC as High, Medium, or Low. RFCs classiﬁed as High are reviewed and approved prior to RFCs classiﬁed as Medium, subject to RFC service level objectives (SLOs) and their submission times. RFCs with Low priority or no priority speciﬁed are processed in the order they are submitted. Learn about RFCs Version May 08, 2024 95 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Approve or reject RFCs RFCs submitted with approval-required (manual) CTs must be approved by you or AMS. Pre- approved CTs are automatically processed. For more information, see CT approval requirements. Note When using "review required" CTs, AMS recommends that you use the ASAP Scheduling option (choose ASAP in the console, leave start and end time blank in the API/CLI) as these CTs require an AMS operator to examine the RFC, and possibly communicate with you before it can be approved and run. If you schedule these RFCs, be sure to allow at least 24 hours. If approval does not happen before the scheduled start time, the RFC is rejected automatically. If an approval-required RFC is successfully submitted by AMS, then it must be explicitly approved by you. Or, iﬀ you submit an approval-required RFC, then it must be approved by AMS. If you're required to approve an RFC that AMS submitted, then an email or other predetermined communication is sent to you requesting the approval. The communication includes the RFC ID. After the communication is sent, do one of the followings: • Console Approve or Reject: Use the RFC details page for the relevant RFC: Learn about RFCs Version May 08, 2024 96 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information • API / CLI Approve: ApproveRfc marks a change as approved. The action must be taken by both the owner and operator, if both are required. The following is an example CLI approve command. In the following example, replace RFC_ID with the appropriate RFC ID. aws amscm approve-rfc --rfc-id RFC_ID • API / CLI Reject: RejectRfc marks a change as rejected. The following is an example CLI reject command.
ams-og-031	ams-og.pdf	31	• Console Approve or Reject: Use the RFC details page for the relevant RFC: Learn about RFCs Version May 08, 2024 96 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information • API / CLI Approve: ApproveRfc marks a change as approved. The action must be taken by both the owner and operator, if both are required. The following is an example CLI approve command. In the following example, replace RFC_ID with the appropriate RFC ID. aws amscm approve-rfc --rfc-id RFC_ID • API / CLI Reject: RejectRfc marks a change as rejected. The following is an example CLI reject command. In the following example, replace RFC_ID with the appropriate RFC ID. aws amscm reject-rfc --rfc-id RFC_ID --reason "no longer relevant" Request RFC restricted run periods Formerly known as blackout days, you can request to restrict certain time periods. No changes can be run during those times. To set a restricted run period, use the UpdateRestrictedExecutionTimes API operation and set a speciﬁc time period, in UTC. The period that you specify overrides any previous periods that were speciﬁed. If you submit an RFC during the speciﬁed restricted run time, submission fails with the error Invalid RFC Schedule. You can specify up to 200 restricted time periods. By default, no restricted period is set. The following is an example request command (with SAML authentication conﬁgured): aws amscm --profile saml update-restricted-execution-times --restricted-execution- times="[{\"TimeRange\":{\"StartTime\":\"2018-01-01T12:00:00Z\",\"EndTime\": \"2018-01-01T12:00:01Z\"}}]" You can also view your current RestrictedExecutionTimes setting by running the ListRestrictedExecutionTimes API operation. Example: aws amscm --profile saml list-restricted-execution-times If you want to submit an RFC during a speciﬁed restricted execution time, then add the RestrictedExecutionTimesOverrideId with the value of OverrideRestrictedTimeRanges, and then submit the RFC as you normally would. It's a best practice to only use this method for a critical or emergency RFC. For more information, see the API reference for SubmitRfc. Learn about RFCs Version May 08, 2024 97 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Create, clone, update, ﬁnd, and cancel RFCs The following examples walk you through various RFC operations. Topics • Create an RFC • Clone RFCs (re-create) with the AMS console • Update RFCs • Find RFCs • Cancel RFCs Create an RFC Creating an RFC with the console The following is the ﬁrst page of the RFC Create process in the AMS console, with Quick cards open and Browse change types active: The following is the ﬁrst page of the RFC Create process in the AMS console, with Select by category active: Learn about RFCs Version May 08, 2024 98 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information How it works: 1. Navigate to the Create RFC page: In the left navigation pane of the AMS console click RFCs to open the RFCs list page, and then click Create RFC. 2. Choose a popular change type (CT) in the default Browse change types view, or select a CT in the Choose by category view. • Browse by change type: You can click on a popular CT in the Quick create area to immediately open the Run RFC page. Note that you cannot choose an older CT version with quick create. To sort CTs, use the All change types area in either the Card or Table view. In either view, select a CT and then click Create RFC to open the Run RFC page. If applicable, a Create with older version option appears next to the Create RFC button. • Choose by category: Select a category, subcategory, item, and operation and the CT details box opens with an option to Create with older version if applicable. Click Create RFC to open the Run RFC page. Learn about RFCs Version May 08, 2024 99 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information 3. On the Run RFC page, open the CT name area to see the CT details box. A Subject is required (this is ﬁlled in for you if you choose your CT in the Browse change types view). Open the Additional conﬁguration area to add information about the RFC. In the Execution conﬁguration area, use available drop-down lists or enter values for the required parameters. To conﬁgure optional execution parameters, open the Additional conﬁguration area. 4. When ﬁnished, click Run. If there are no errors, the RFC successfully created page displays with the submitted RFC details, and the initial Run output. 5. Open the Run parameters area to see the conﬁgurations you submitted. Refresh the page to update the RFC execution status. Optionally, cancel the RFC or create a copy of it with the options at the top of the page. Creating an RFC with the CLI How it works: 1. Use either the Inline Create (you issue a create-rfc command with all RFC and execution parameters included), or Template Create (you create two JSON ﬁles,
ams-og-032	ams-og.pdf	32	When ﬁnished, click Run. If there are no errors, the RFC successfully created page displays with the submitted RFC details, and the initial Run output. 5. Open the Run parameters area to see the conﬁgurations you submitted. Refresh the page to update the RFC execution status. Optionally, cancel the RFC or create a copy of it with the options at the top of the page. Creating an RFC with the CLI How it works: 1. Use either the Inline Create (you issue a create-rfc command with all RFC and execution parameters included), or Template Create (you create two JSON ﬁles, one for the RFC parameters and one for the execution parameters) and issue the create-rfc command with the two ﬁles as input. Both methods are described here. 2. Submit the RFC: aws amscm submit-rfc --rfc-id ID command with the returned RFC ID. Monitor the RFC: aws amscm get-rfc --rfc-id ID command. To check the change type version, use this command: aws amscm list-change-type-version-summaries --filter Attribute=ChangeTypeId,Value=CT_ID Note You can use any CreateRfc parameters with any RFC whether or not they are part of the schema for the change type. For example, to get notiﬁcations when the RFC status changes, add this line, --notification "{\"Email\": {\"EmailRecipients \" : [\"email@example.com\"]}}" to the RFC parameters part of the request (not Learn about RFCs Version May 08, 2024 100 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information the execution parameters). For a list of all CreateRfc parameters, see the AMS Change Management API Reference. INLINE CREATE: Issue the create RFC command with execution parameters provided inline (escape quotes when providing execution parameters inline), and then submit the returned RFC ID. For example, you can replace the contents with something like this:: aws amscm create-rfc --change-type-id "CT_ID" --change-type-version "VERSION" --title "TITLE" --execution-parameters "{\"Description\": \"example\"}" TEMPLATE CREATE: Note This example of creating an RFC uses the Load Balancer (ELB) stack change type. 1. Find the relevant CT. The following command searches CT classiﬁcation summaries for those that contain "ELB" in the Item name and creates output of the Category, Item, Operation, and ChangeTypeID in table form (Subcategory for both is Advanced stack components). aws amscm list-change-type-classification-summaries --query "ChangeTypeClassificationSummaries[?contains(Item,'ELB')]. [Category,Item,Operation,ChangeTypeId]" --output table --------------------------------------------------------------------- \| CtSummaries \| +-----------+---------------------------+---------------------------+ \| Deployment\| Load balancer (ELB) stack \| Create \| ct-123h45t6uz7jl \| \| Management\| Load balancer (ELB) stack \| Update \| ct-0ltm873rsebx9 \| +-----------+---------------------------+---------------------------+ 2. Find the most current version of the CT: ChangeTypeId and ChangeTypeVersion: The change type ID for this walkthrough is ct-123h45t6uz7jl (create ELB), to ﬁnd out the latest version, run this command: Learn about RFCs Version May 08, 2024 101 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information aws amscm list-change-type-version-summaries --filter Attribute=ChangeTypeId,Value=ct-123h45t6uz7jl 3. Learn the options and requirements. The following command outputs the schema to a JSON ﬁle named CreateElbParams.json. aws amscm get-change-type-version --change-type-id "ct-123h45t6uz7jl" --query "ChangeTypeVersion.ExecutionInputSchema" --output text > CreateElbParams.json 4. Modify and save the execution parameters JSON ﬁle. This example names the ﬁle CreateElbParams.json. For a provisioning CT, the StackTemplateId is included in the schema and must be submitted in the execution parameters. For TimeoutInMinutes, how many minutes are allowed for the creation of the stack before the RFC is failed, this setting will not delay the RFC execution, but you must give enough time (for example, don't specify "5"). Valid values are "60" up to "360," for CTs with long-running UserData: Create EC2 and Create ASG. We recommend the max allowed "60" for all other provisioning CTs. Provide the ID of the VPC where you want the stack to be created; you can get the VPC ID with the CLI command aws amsskms list-vpc-summaries. { "Description": "ELB-Create-RFC", "VpcId": "VPC_ID", "StackTemplateId": "stm-sdhopv00000000000", "Name": "MyElbInstance", "TimeoutInMinutes": 60, "Parameters": { "ELBSubnetIds": ["SUBNET_ID"], "ELBHealthCheckHealthyThreshold": 4, "ELBHealthCheckInterval": 5, "ELBHealthCheckTarget": "HTTP:80/", "ELBHealthCheckTimeout": 60, "ELBHealthCheckUnhealthyThreshold": 5, "ELBScheme": false } } Learn about RFCs Version May 08, 2024 102 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information 5. Output the RFC JSON template to a ﬁle in your current folder named CreateElbRfc.json: aws amscm create-rfc --generate-cli-skeleton > CreateElbRfc.json 6. Modify and save the CreateElbRfc.json ﬁle. Because you created the execution parameters in a separate ﬁle, remove the ExecutionParameters line. For example, you can replace the contents with something like this: { "ChangeTypeVersion": "2.0", "ChangeTypeId": "ct-123h45t6uz7jl", "Title": "Create ELB" } 7. Create the RFC. The following command speciﬁes the execution parameters ﬁle and the RFC template ﬁle: aws amscm create-rfc --cli-input-json file://CreateElbRfc.json --execution- parameters file://CreateElbParams.json You receive the ID of the new RFC in the response and can use it to submit and monitor the RFC. Until you submit it, the RFC remains in the editing state and does not start. Tips Note You can use the AMS API/CLI to create an RFC without creating an RFC JSON ﬁle or a CT execution parameters JSON ﬁle. To do this, you
ams-og-033	ams-og.pdf	33	this: { "ChangeTypeVersion": "2.0", "ChangeTypeId": "ct-123h45t6uz7jl", "Title": "Create ELB" } 7. Create the RFC. The following command speciﬁes the execution parameters ﬁle and the RFC template ﬁle: aws amscm create-rfc --cli-input-json file://CreateElbRfc.json --execution- parameters file://CreateElbParams.json You receive the ID of the new RFC in the response and can use it to submit and monitor the RFC. Until you submit it, the RFC remains in the editing state and does not start. Tips Note You can use the AMS API/CLI to create an RFC without creating an RFC JSON ﬁle or a CT execution parameters JSON ﬁle. To do this, you use the create-rfc command and add the required RFC and execution parameters to the command, this is called "Inline Create". Note that all provisioning CTs have contained within the execution-parameters block a Parameters array with the parameters for the resource. The parameters must have quote marks escaped with a back slash (\). The other documented method of creating an RFC is called "Template Create." This is where you create a JSON ﬁle for the RFC parameters and another JSON ﬁle for the execution parameters, and submit the two ﬁles with the create-rfc command. These ﬁles can serve as templates and be re-used for future RFCs. Learn about RFCs Version May 08, 2024 103 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information When creating RFCs with templates, you can use a command to create the JSON ﬁle with the contents you want by issuing a command as shown. The commands create a ﬁle named "parameters.json" with the shown content; you could also use these commands to create the RFC JSON ﬁle. Clone RFCs (re-create) with the AMS console You can use the AMS console to clone an existing RFC. To clone, or recreate, an RFC by using the AMS console, follow these steps: 1. Find the relevant RFC. From the left navigation, click RFCs. The RFCs dashboard opens. 2. Scroll through the pages until you ﬁnd the RFC you want to clone. Use the Filter option to narrow the list. Choose the RFC that you want to clone. The RFC details page opens. 3. Click Create a Copy. The Create a request for change page opens with all options set as in the original RFC. 4. Make the changes you want. To set additional options, change the Basic option to Advanced. After you have set all options, choose Submit. The active RFC details page opens with a new RFC ID for the cloned RFC and the cloned RFC appears in the RFC dashboard. Update RFCs You can resubmit an RFC that has been rejected or that has not yet been submitted, by updating the RFC and then submitting it, or re-submitting it. Note that most RFCs are rejected because the speciﬁed RequestedStartTime has passed before submission or the speciﬁed TimeoutInMinutes is inadequate to run the RFC (since TimeoutInMinutes does not prolong a successful RFC, we recommend always setting this to at least "60" and up to "360" for an Amazon EC2 or an Amazon EC2 Auto Scaling group with long-running UserData). This section describes how to use the CLI version of the UpdateRfc command to update an RFC with a new RFC parameter, or new parameters using either stringiﬁed JSON or an updated parameters ﬁle. Learn about RFCs Version May 08, 2024 104 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information This example describes using the CLI version of the AMS UpdateRfc API (see Update RFC). While there are change types for updating some resources (DNS private and public, load balancer stacks, and stack patching conﬁguration), there is no CT to update an RFC. We recommend that you submit one UpdateRfc operation at a time. If you submit multiple updates, for example on a DNS stack, the updates might fail attempting to update the DNS at the same time. REQUIRED DATA: RfcId: The RFC you're updating. OPTIONAL DATA: ExecutionParameters: Unless you're updating a non-required ﬁeld, like Description, you would submit modiﬁed execution parameters to address the issues that caused the RFC to be rejected or canceled. All submitted non-null values overwrite those values in the original RFC. 1. Find the relevant rejected or canceled RFC, you can use this command (you can substitute the value with Canceled): aws amscm list-rfc-summaries --filter Attribute=RfcStatusId,Value=Rejected 2. You can modify any of the following RFC parameters : { "Description": "string", "ExecutionParameters": "string", "ExpectedOutcome": "string", "ImplementationPlan": "string", "RequestedEndTime": "string", "RequestedStartTime": "string", "RfcId": "string", "RollbackPlan": "string", "Title": "string", "WorstCaseScenario": "string"} Example command updating the Description ﬁeld: aws amscm update-rfc --description "AMSTestNoOpsActionRequired" --rfc-id "RFC_ID" --region us-east-1 Example command updating the ExecutionParameters VpcId ﬁeld: Learn about RFCs Version May 08, 2024 105 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information aws amscm update-rfc --execution-parameters "{\"VpcId\":\"VPC_ID\"}" --rfc-id "RFC_ID" --region us-east-1 Example command updating the RFC with an
ams-og-034	ams-og.pdf	34	command (you can substitute the value with Canceled): aws amscm list-rfc-summaries --filter Attribute=RfcStatusId,Value=Rejected 2. You can modify any of the following RFC parameters : { "Description": "string", "ExecutionParameters": "string", "ExpectedOutcome": "string", "ImplementationPlan": "string", "RequestedEndTime": "string", "RequestedStartTime": "string", "RfcId": "string", "RollbackPlan": "string", "Title": "string", "WorstCaseScenario": "string"} Example command updating the Description ﬁeld: aws amscm update-rfc --description "AMSTestNoOpsActionRequired" --rfc-id "RFC_ID" --region us-east-1 Example command updating the ExecutionParameters VpcId ﬁeld: Learn about RFCs Version May 08, 2024 105 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information aws amscm update-rfc --execution-parameters "{\"VpcId\":\"VPC_ID\"}" --rfc-id "RFC_ID" --region us-east-1 Example command updating the RFC with an execution parameters ﬁle that contains the updates; see example execution parameters ﬁle in step 2 of: EC2 stack \| Create: aws amscm update-rfc --execution-parameters file://CreateEc2ParamsUpdate.json -- rfc-id "RFC_ID" --region us-east-1 3. Resubmit the RFC using submit-rfc and the same RFC ID that you have from when the RFC was ﬁrst created: aws amscm submit-rfc --rfc-id RFC_ID If the RFC succeeds, you receive no conﬁrmation or error messages at the command line. 4. To monitor the status of the request and to view Execution Output, run the following command. aws amscm get-rfc --rfc-id RFC_ID Find RFCs Find a request for change (RFC) with the console To ﬁnd an RFC by using the AMS console, follow these steps. Note This procedure applies only to scheduled RFCs, that is, RFCs that did not use the ASAP option. 1. From the left navigation, click RFCs. The RFCs dashboard opens. 2. Scroll through the list or use the Filter option to reﬁne the list. Learn about RFCs Version May 08, 2024 106 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information The RFC list changes per ﬁlter criteria. 3. Choose the Subject link for the RFC you want. The RFC details page opens for that RFC with information including RFC ID. 4. If there are many RFCs in the dashboard, you can use the Filter option to search by RFC: • Subject: The subject line, or title (in the API/CLI) given to the RFC when it was created. • RFC ID: The identiﬁer for the RFC. • Activity state: If you know the RFC state, you can choose between AwsOperatorAssigned meaning an operator is currently looking at the RFC, AwsActionPending meaning that an AMS operator must perform something before the RFC execution can proceed or CustomerActionPending meaning that you need to take some action before the RFC execution can proceed. • Status: If you know the RFC status, you can choose between: • Scheduled: RFCs that were scheduled. • Canceled: RFCs that were canceled. • In progress: RFCs in progress. • Success: RFCs that executed successfully. • Rejected: RFCs that were rejected. • Editing: RFCs that are being edited. • Failure: RFCs that failed. • Pending approval: RFCs that cannot proceed until either AMS or you approve. Typically, this indicates that you need to approve the RFC. You will have gotten a service notiﬁcation of this in your Service Requests list. • Change type: Pick the Category, Subcategory, Item, and Operation, and the change type ID is retrieved for you. • Requested start time or Requested end time: This ﬁlter option lets you choose Before or After, and then enter a Date and, optionally, a Time (hh:mm and time zone). This ﬁlter operates successfully only on scheduled RFCs (not ASAP RFCs). • Status: Either Scheduled, Canceled, In progress, Success, Rejected, Editing, or Failure. • Subject: The subject (or title, if the RFC was created with the API/CLI) that you gave the RFC. • Change type ID: Use the identiﬁer for the change type submitted with the RFC. Learn about RFCs Version May 08, 2024 107 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information The search allows you to add the ﬁlters, as shown in the following screenshot. 5. Click on the Subject link for the RFC you want. The RFC details page opens for that RFC with information including RFC ID. Finding a request for change (RFC) with the CLI You can use multiple ﬁlters to ﬁnd an RFC. To check the change type version, use this command: aws amscm list-change-type-version-summaries --filter Attribute=ChangeTypeId,Value=CT_ID Note You can use any CreateRfc parameters with any RFC whether or not they are part of the schema for the change type. For example, to get notiﬁcations when the RFC status changes, add this line, --notification "{\"Email\": {\"EmailRecipients \" : [\"email@example.com\"]}}" to the RFC parameters part of the request (not the execution parameters). For a list of all CreateRfc parameters, see the AMS Change Management API Reference. Learn about RFCs Version May 08, 2024 108 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information If you don’t write down the RFC ID, and need to ﬁnd it later, you can use the AMS change management (CM) system to search for
ams-og-035	ams-og.pdf	35	or not they are part of the schema for the change type. For example, to get notiﬁcations when the RFC status changes, add this line, --notification "{\"Email\": {\"EmailRecipients \" : [\"email@example.com\"]}}" to the RFC parameters part of the request (not the execution parameters). For a list of all CreateRfc parameters, see the AMS Change Management API Reference. Learn about RFCs Version May 08, 2024 108 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information If you don’t write down the RFC ID, and need to ﬁnd it later, you can use the AMS change management (CM) system to search for it and narrow the results with a ﬁlter or query. 1. The CM API ListRfcSummaries operation has ﬁlters. You can Filter results based on an Attribute and Value combined in a logical AND operation, or based on an Attribute, a Condition, and Values. RFC ﬁltering Attribute Valid values Valid condition Default condition Notes s ActualEndTime Any string represent ing an ISO8601 datetime (for Before, After, Between None example, “20170101 T000000Z”) The Before or After condition only accepts one value in the Values ﬁeld. The Between condition must have exactly two values in the Values ﬁeld, where the ﬁrst value should represent a date that happens before the second value Learn about RFCs Version May 08, 2024 109 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Attribute Valid values Valid condition Default condition Notes s ActualStartTime Any string represent ing an ISO8601 datetime (for Before, After, Between None example, “20170101 T000000Z”) AutomationStatusId Manual, Automated Equals Equals The Before or After condition only accepts one value in the Values ﬁeld. The Between condition must have exactly two values in the Values ﬁeld, where the ﬁrst value should represent a date that happens before the second value There are only two automation statuses Finding a Change Type or CSIO ChangeTypeId ChangeTypeVersion CreatedBy Any valid change type ID; for example, ct-123h45t6uz7jl Any valid change type ID; for example, 1.0 Any string (maximum allowed length is 2048 characters) Equals Equals Equals Equals Finding a Change Type or CSIO Contains Contains The CreatedBy ﬁeld of the RFC contains the ARN of the user who created it Learn about RFCs Version May 08, 2024 110 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Attribute Valid values Valid condition Default condition Notes s CreatedTime Any string represent ing an ISO8601 datetime (for Before, After, Between None example, “20170101 T000000Z”) LastModifiedTime Any string represent ing an ISO8601 datetime (for Before, After, Between None example, “20170101 T000000Z”) The Before or After condition only accepts one value in the Values ﬁeld. The Between condition must have exactly two values in the Values ﬁeld, where the ﬁrst value should represent a date that happens before the second value The Before or After condition only accepts one value in the Values ﬁeld. The Between condition must have exactly two values in the Values ﬁeld, where the ﬁrst value should represent a date that happens before the second value Learn about RFCs Version May 08, 2024 111 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Attribute Valid values Valid condition Default condition Notes s LastSubmittedTime Any string represent ing an ISO8601 datetime (for Before, After, Between None example, “20170101 T000000Z”) RequestedEndTime Any string represent ing an ISO8601 datetime (for Before, After, Between None example, “20170101 T000000Z”) The Before or After condition only accepts one value in the Values ﬁeld. The Between condition must have exactly two values in the Values ﬁeld, where the ﬁrst value should represent a date that happens before the second value The Before or After condition only accepts one value in the Values ﬁeld. The Between condition must have exactly two values in the Values ﬁeld, where the ﬁrst value should represent a date that happens before the second value Learn about RFCs Version May 08, 2024 112 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Attribute Valid values Valid condition Default condition Notes s RequestedStartTime Any string represent ing an ISO8601 datetime (for Before, After, Between None example, “20170101 T000000Z”) RfcStatusId Equals Equals Canceled, Editing, Failure, InProgress, PendingApproval, Rejected, Scheduled , Success Title Any valid RFC title Contains Contains The Before or After condition only accepts one value in the Values ﬁeld. The Between condition must have exactly two values in the Values ﬁeld, where the ﬁrst value should represent a date that happens before the second value Refresh the RFC list in the AMS console or run GetRfc Regular expressio ns in each individua l ﬁeld are not supported. Case insensitive search Examples: To ﬁnd the IDs of all the RFCs related to SQS (where SQS is contained in the Item portion of the CT), you can use this command: list-rfc-summaries --query 'RfcSummaries[?contains(Item.Name,`SQS`)]. [Category.Id,Subcategory.Id,Type.Id,Item.Id,RfcId]' --output table Learn about RFCs Version May 08, 2024 113
ams-og-036	ams-og.pdf	36	accepts one value in the Values ﬁeld. The Between condition must have exactly two values in the Values ﬁeld, where the ﬁrst value should represent a date that happens before the second value Refresh the RFC list in the AMS console or run GetRfc Regular expressio ns in each individua l ﬁeld are not supported. Case insensitive search Examples: To ﬁnd the IDs of all the RFCs related to SQS (where SQS is contained in the Item portion of the CT), you can use this command: list-rfc-summaries --query 'RfcSummaries[?contains(Item.Name,`SQS`)]. [Category.Id,Subcategory.Id,Type.Id,Item.Id,RfcId]' --output table Learn about RFCs Version May 08, 2024 113 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Which returns something like this: ---------------------------------------------------------------------------- \| ListRfcSummaries \| +----------+--------------------------------+-------+-------+----------------+ \|Deployment\| Advanced Stack Components \|SQS \|Create \|ct-123h45t6uz7jl\| \|Management\| Monitoring & Notification \|SQS \|Update \|ct-123h45t6uz7jl\| +----------+--------------------------------+-------+-------+----------------+ Another ﬁlter available for list-rfc-summaries is AutomationStatusId, to look for RFCs that are automated or manual: aws amscm list-rfc-summaries --filter Attribute=AutomationStatusId,Value=Automated Another ﬁlter available for list-rfc-summaries is Title (Subject in the console): Attribute=Title,Value=RFC-TITLE Example of the new request structure in JSON that returns RFCs where: • (Title CONTAINS the phrase "Windows 2012" OR "Amazon Linux") AND • (RfcStatusId EQUALS "Success" OR "InProgress") AND • (20170101T000000Z <= RequestedStartTime <= 20170103T000000Z) AND (ActualEndTime <= 20170103T000000Z) { "Filters": [ { "Attribute": "Title", "Values": ["Windows 2012", "Amazon Linux"], "Condition": "Contains" }, { "Attribute": "RfcStatusId", "Values": ["Success", "InProgress"], "Condition": "Equals" }, { Learn about RFCs Version May 08, 2024 114 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information "Attribute": "RequestedStartTime", "Values": ["20170101T000000Z", "20170103T000000Z"], "Condition": "Between" }, { "Attribute": "ActualEndTime", "Values": ["20170103T000000Z"], "Condition": "Before" } ] } Note With more advanced Filters, AMS intends to deprecate the following ﬁelds in an upcoming release: • Value: The Value ﬁeld is part of the Filters ﬁeld. Use the Values ﬁeld that supports more advanced functionality. • RequestedEndTimeRange: Use the RequestedEndTime inside the Filters ﬁeld that supports more advanced functionality • RequestedStartTimeRange: Use the RequestedStartTime inside the Filters ﬁeld that supports more advanced functionality. For information about using CLI queries, see How to Filter the Output with the --query Option and the query language reference, JMESPath Speciﬁcation. 2. If you're using the AMS console: Go to the RFCs list page. If needed, you can ﬁlter on the RFC Subject, which is what you entered as the RFC Title when you created it. Tips Note This procedure applies only to scheduled RFCs, that is, RFCs that did not use the ASAP option. Learn about RFCs Version May 08, 2024 115 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Cancel RFCs You can cancel an RFC using the Console or the AMS API/CLI. To cancel an RFC with the console, ﬁnd the RFC in your RFC list, open it, click Cancel. Required Data: • Reason: Why you are canceling the RFC. • RfcId: The RFC you are canceling. 1. Typically you would cancel an RFC right after submitting it (so the RFC ID should be handy); otherwise, you would not be able to cancel it unless you scheduled it and it's before the speciﬁed start time. If you need to ﬁnd the RFC ID, you can use this command (you can substitute the Value with PendingApproval for an RFC that is manually approved): aws amscm list-rfc-summaries --filter Attribute=RfcStatusId,Value=Scheduled 2. Example command to cancel an RFC: aws amscm cancel-rfc --reason "Bad Stack ID" --rfc-id "RFC_ID" --profile saml -- region us-east-1 Use the AMS console with RFCs The AMS console provides features to help you succeed with creating and submitting RFCs. Use the RFC List page (Console) The AMS console RFCs list page provides you with the following options: • Advanced RFC search through a Filter. For information, see Find RFCs. • Finding the last time the RFC was Modiﬁed. This value represents that last time that the RFC status was changed. • Viewing RFC details with the RFC Subject. Choosing this link opens the details page for that RFC. • Viewing RFC status. For information, see Understand RFC status codes Learn about RFCs Version May 08, 2024 116 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Use RFC quick create (console) Use the RFC quick create cards, or list table, or choose change types for RFCs by classiﬁcation. To learn more, see Create an RFC. Add RFC correspondence and attachments (console) You can add correspondence to an RFC after it has been submitted and before it is approved; for example, while it's in the state of "PendingApproval". After an RFC is approved (in a state of "Scheduled" or "InProgress"), correspondence cannot be added, because it could be construed as a change to the request. After an RFC is completed (in a state of "Canceled", "Rejected", "Success", or "Failure"), correspondence is once again enabled, though correspondence is disabled once an RFC is closed for more than
ams-og-037	ams-og.pdf	37	RFCs by classiﬁcation. To learn more, see Create an RFC. Add RFC correspondence and attachments (console) You can add correspondence to an RFC after it has been submitted and before it is approved; for example, while it's in the state of "PendingApproval". After an RFC is approved (in a state of "Scheduled" or "InProgress"), correspondence cannot be added, because it could be construed as a change to the request. After an RFC is completed (in a state of "Canceled", "Rejected", "Success", or "Failure"), correspondence is once again enabled, though correspondence is disabled once an RFC is closed for more than 30 days. Note Each correspondence is limited to 5,000 characters. Limitations for attachments: • Only three attachments per correspondence. • Limit ﬁfty attachments per RFC. • Each attachment must be less than 5 MB in size. • Only text ﬁles are accepted such as plaintext (.txt), comma-separated values (.csv), JSON (.json), or YAML (.yaml). In the case of YAML format, the ﬁle must be attached using ﬁle extension .yaml. Learn about RFCs Version May 08, 2024 117 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Note Text ﬁles that have XML content are prohibited. If you have XML content to share with AMS, use a service request. • File names are limited to 255 characters, with only numbers, letters, spaces, dashes (-), underscores (_), and dots (.). • Updating and deleting attachments on an RFC is not currently supported. To add correspondence and attachments to an RFC, follow these steps: 1. In the AMS console, on the RFC details page for an RFC, ﬁnd the Correspondence section at the bottom of the page. Before any correspondence: After some correspondence: Learn about RFCs Version May 08, 2024 118 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information 2. To add a new correspondence, type your message in the Reply text box. To attach ﬁles related to the correspondence, choose Add Attachment, and then choose the ﬁles you want. 3. When you're ﬁnished, choose Submit. The new correspondence, along with links to the attached ﬁles, appear in the correspondence list on the RFC details page. Learn about RFCs Version May 08, 2024 119 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Conﬁgure RFC email notiﬁcations (console) The AMS console Requests for Change create page provides you with an option to add email addresses to receive notiﬁcations of RFC state changes: Additionally, you can add email addresses for notiﬁcations to any change type, for example: aws amscm create-rfc --change-type-id ct-1e1xtak34nx76 Learn about RFCs Version May 08, 2024 120 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information --change-type-version 1.0 --title "TITLE" --notification "{\"Email\": {\"EmailRecipients\" : [\"email@example.com\"]}}" Add a similar line (--notification "{\"Email\": {\"EmailRecipients\" : [\"email@example.com\"]}}") to any change type inline or template request in the RFC parameters part of the request, not the parameters part. Learn about common RFC parameters The following are RFC parameters that you are required to submit, and parameters that are commonly used in RFCs: • Change type information: ChangeTypeId and ChangeTypeVersion. Ror a list of change type IDs and version numbers, see Change Type Reference. Run list-change-type-classification-summaries in the CLI with the query argument to narrow the results. For example, narrow results to change types that contain "Access" in the Item name. aws amscm list-change-type-classification-summaries --query "ChangeTypeClassificationSummaries [?contains (Item, 'access')]. [Category,Subcategory,Item,Operation,ChangeTypeId]" --output table Run get-change-type-version and specify the change type ID. The following command gets the CT version for ct-2tylseo8rxfsc. aws amscm get-change-type-version --change-type-id ct-2tylseo8rxfsc • Title: A name for the RFC; this becomes the Subject of the RFC in the AMS console RFC list and you can search on it with the GetRfc command and a ﬁlter on Title • Scheduling: If you want a scheduled RFC, you must include the RequestedStartTime and RequestedEndTime parameters, or use the Schedule this change console option. For an ASAP RFC (that runs as soon as it's approved), when using the CLI, leave RequestedStartTime and RequestedEndTime null. When using the console, accept the ASAP option. If the RequestedStartTime is missed, the RFC is rejected. • Provisioning CTs: The execution parameters, or Parameters are the speciﬁc settings that are required to provision the resource. They vary widely depending on the CT. Learn about RFCs Version May 08, 2024 121 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information • Non-provisioning CTs: CTs that do not provision a resource, such as access CTs or Other \| Other, or delete stack, have minimal execution parameters and no Parameters block. • Some RFCs also require that you specify a TimeoutInMinutes, or how many minutes are allowed for the creation of the stack before the RFC is failed. Valid values are 60 (minutes) up to 360, for long-running UserData. If the execution can't be completed before the TimeoutInMinutes is exceeded, the RFC fails. However,
ams-og-038	ams-og.pdf	38	CT. Learn about RFCs Version May 08, 2024 121 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information • Non-provisioning CTs: CTs that do not provision a resource, such as access CTs or Other \| Other, or delete stack, have minimal execution parameters and no Parameters block. • Some RFCs also require that you specify a TimeoutInMinutes, or how many minutes are allowed for the creation of the stack before the RFC is failed. Valid values are 60 (minutes) up to 360, for long-running UserData. If the execution can't be completed before the TimeoutInMinutes is exceeded, the RFC fails. However, this setting doesn't delay the execution of the RFC. • RFCs that create instances, such as an S3 bucket or an ELB, generally provide a schema that allows you to add up to seven tags (key/value pairs). You can add more tags to your S3 bucket by submitting a service request or a Management \| Other \| Other \| Update CT. EC2, EFS, 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. Providing tags can be of great value. For more information, see Tagging Your Amazon EC2 Resources. When using the AMS console, you must open the Additional conﬁguration area 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 don't name the resource you're creating. Some schemas oﬀer a parameter to name the resource you're creating, and some do not. For example, the CT schema for Create EC2 stack doesn't oﬀer a parameter to name the 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 EC2 instance displays in the EC2 console without a name attribute. Use the RFC AWS Region option The AMS API and CLI (amscm and amsskms) endpoints are in us-east-1. If you federate with Security Assertion Markup Language (SAML), then scripts are provided to you at onboarding that set your AWS Region to us-east-1. If you use SAML, then you don't need to specify the --region option when you issue a command. If your SAML is conﬁgured to use us-east-1 but your account isn't in that AWS Region, then you must specify your account-onboarded Region when you issue other AWS commands (for example, aws s3). Learn about RFCs Version May 08, 2024 122 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Note Most of the command examples provided in this guide don't include the --region option. Sign up for the RFC daily email You can sign up for a daily email summarizing the RFC activity in your account over the last 24 hours using the RFC digest feature. The RFC digest feature is a streamlined process that reduces the number of email notiﬁcations you receive regarding your account's RFCs. The RFC digest might reduce the likelihood that you miss actions that are pending your response. To turn on the RFC digest feature, contact your AMS Cloud Service Delivery Manager (CSDM). The CSDM subscribes you. You can request up to 20 email addresses (or aliases) to include on your RFC digest email list. The current email schedule is ﬁxed at 09:00 UTC-8. To turn oﬀ the RFC digest feature, contact your CSDM with your request. If you don't set up RFC digest and want notiﬁcations regarding your RFCs, or if you want more detailed information on your RFCs than what the RFC digest provides, then use the Change Management System to set up CloudWatch Events notiﬁcations or email notiﬁcations for every individual RFC that you want information on. For information on setting up RFC notiﬁcations, see RFC State Change Notiﬁcations. The topics contained in the RFC digest include the following: • Pending Customer Approval: Lists RFCs that are in PendingApproval status, awaiting your approval • Pending Customer Reply: Lists RFCs that are awaiting your reply on RFC correspondence • Pending AWS Approval or Reply: Lists RFCs that are waiting on AMS for reply or approval • Completed: Lists RFCs in Success, Failure, Cancelled and Rejected status The following is an example RFC digest: Learn about RFCs Version May 08, 2024 123 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Learn about RFCs Version May 08, 2024 124 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information What are change types? Change type refers to the action that an AWS Managed Services (AMS) request for change (RFC) performs and encompasses the change action itself, and the type of change – manual vs automated. AMS has a large collection of
ams-og-039	ams-og.pdf	39	on AMS for reply or approval • Completed: Lists RFCs in Success, Failure, Cancelled and Rejected status The following is an example RFC digest: Learn about RFCs Version May 08, 2024 123 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Learn about RFCs Version May 08, 2024 124 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information What are change types? Change type refers to the action that an AWS Managed Services (AMS) request for change (RFC) performs and encompasses the change action itself, and the type of change – manual vs automated. AMS has a large collection of change types not used by other Amazon web services. You use these change types when submitting a request for change (RFC) to deploy, or manage, or gain access to, resources. Topics • Automated and manual CTs • CT approval requirements • Change type versions • Create change types • Update change types • Internal-only change types • Change type schemas • Managing permissions for change types • Redacting sensitive information from change types • Finding a change type, using the query option Automated and manual CTs A constraint on change types is whether they are automated or manual, this is the change type AutomationStatusId attribute, called the Execution mode in the AMS console. Automated change types have expected results and execution times and run through the AMS automated system, generally within an hour or less (this largely depends on what resources the CT is provisioning). Manual change types are uncommon, but they are treated diﬀerently because they require that an AMS operator act on the RFC before it can be run. That sometimes means communicating with the RFC submitter, so, manual change types require varying lengths of time to complete. For all scheduled RFCs, an unspeciﬁed end time is written to be the time of the speciﬁed RequestedStartTime plus the ExpectedExecutionDurationInMinutes attribute of the submitted change type. For example, if the ExpectedExecutionDurationInMinutes is "60" (minutes), and the speciﬁed RequestedStartTime is 2016-12-05T14:20:00Z (December What are change types? Version May 08, 2024 125 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information 5, 2016 at 4:20 AM), the actual end time would be set to December 5, 2016 at 5:20 AM. To ﬁnd the ExpectedExecutionDurationInMinutes for a speciﬁc change type, run this command: aws amscm --profile saml get-change-type-version --change-type-id CHANGE_TYPE_ID -- query "ChangeTypeVersion.{ExpectedDuration:ExpectedExecutionDurationInMinutes}" Note Scheduled RFCs with Execution mode= Manual, in the Console, must be set to run at least 24 hours in the future. This caveat does not apply to the AMS API/CLI, but it is still important to schedule manual RFCs at least 8 hours ahead. Note When using "review required" CTs, AMS recommends that you use the ASAP Scheduling option (choose ASAP in the console, leave start and end time blank in the API/CLI) as these CTs require an AMS operator to examine the RFC, and possibly communicate with you before it can be approved and run. If you schedule these RFCs, be sure to allow at least 24 hours. If approval does not happen before the scheduled start time, the RFC is rejected automatically. AMS aims to respond to a manual CT within four hours, and will correspond as soon as possible, but it could take much longer for the RFC to actually be run. For a list of the CTs that are Manual and require AMS review, see the Change Type CSV ﬁle, available on the Developer's Resources page of the Console. YouTube Video: How can I ﬁnd automated change types for AMS RFCs? To ﬁnd the Execution mode for a CT in the AMS console, you must use the Browse change types search option. The results show the execution mode of the matching change type or change types. To ﬁnd the AutomationStatus for a speciﬁc change type by using the AMS CLI, run this command: aws amscm --profile saml get-change-type-version --change-type-id CHANGE_TYPE_ID -- query "ChangeTypeVersion.{AutomationStatus:AutomationStatus.Name}" What are change types? Version May 08, 2024 126 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information You can also look up change types in the AMS Change Type Reference, which provides information about all AMS change types. Note The AMS API/CLI are not currently part of the AWS API/CLI. To access the AMS API/CLI, you download the AMS SDK through the AMS console. CT approval requirements AMS CTs always have two approval conditions, AwsApprovalId and CustomerApprovalId that indicate whether the RFC requires AMS or you, or anyone, to approve the execution. The approval condition is somewhat related to the execution mode; for details, see Automated and manual CTs. To ﬁnd out the approval condition for a CT, you can look in the AMS Change Type Reference, or run GetChangeTypeVersion. Both will also give you the CT AutomationStatusId or Execution mode. You can approve RFCs by using the AMS console
ams-og-040	ams-og.pdf	40	To access the AMS API/CLI, you download the AMS SDK through the AMS console. CT approval requirements AMS CTs always have two approval conditions, AwsApprovalId and CustomerApprovalId that indicate whether the RFC requires AMS or you, or anyone, to approve the execution. The approval condition is somewhat related to the execution mode; for details, see Automated and manual CTs. To ﬁnd out the approval condition for a CT, you can look in the AMS Change Type Reference, or run GetChangeTypeVersion. Both will also give you the CT AutomationStatusId or Execution mode. You can approve RFCs by using the AMS console or with the following command: aws amscm approve-rfc --rfc-id RFC_ID CT approval condition If the CT approval condition is It requires approval from And AwsApprovalId: Required AwsApprovalId: NotRequir edIfSubmitter No action is required. This condition is typical for automated CTs. No action is required. This condition is typical for manual CTs because they will always be reviewed by AMS operators. The AMS change type system, The AMS change type system and no one else, if the submitted RFC is for the What are change types? Version May 08, 2024 127 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information If the CT approval condition is CustomerApprovalId: NotRequired CustomerApprovalId: Required It requires approval from account it was submitted against, The AMS change type system, The AMS change type system and you, And If the RFC passes syntax and parameter checks, it is auto approved. A notiﬁcation is sent to you, and you must explicitly approve the RFC, either by responding to the notice, or running the ApproveRfc operation. CustomerApprovalId: NotRequiredIfSubmitter The AMS change type If the RFC passes syntax and parameter checks, it is auto approved. system and no one else, if you submitted the RFC. Urgent Security Incident or Patch AMS Is auto approved and implemented. Change type versions Change types are versioned and the version changes when a major update is made to the change type. After selecting a change type using the AMS console, you have the option of opening the Additional conﬁguration area and selecting a change type version. You can also specify a change type version at the API/CLI command line. You might want to do this for various reasons, including: • You know that the version of the Update change type that you want must match the version of the Create change type that you used to create the resource that you now want to update. For example, you might have an Elastic Load Balancer (ELB) instance that you created with ELB Create change type version 1. To update it, choose ELB Update version 1. What are change types? Version May 08, 2024 128 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information • You want to use a change type version that has diﬀerent options in it than the most recent change type. We don't recommend this because AMS updates change types mainly for security reasons and we recommend that you always choose the most recent version. Create change types Create change types are matched version-to-version with the Update change types. That is, the change type version that you use to provision a resource must match the version of the Update change type that you would use later to modify that resource. For example, if you create an S3 bucket with the Create S3 Bucket change type version 2.0, and later want to submit an RFC to modify that S3 bucket, you must use the Update S3 Bucket change type version 2.0 as well, even if there is an Update S3 Bucket change type with version 3.0. We recommend keeping a record of the change type ID and version that you use when provisioning a resource with a Create change type in case you later want to use an Update change type to modify it. Update change types AMS provides Update change types to update resources that were created with Create change types. The Update change types must be matched version-to-version with the Create change type originally used to provision the resource. We recommend keeping a record of the change type ID and version that you use when provisioning a resource to make it easy to update it. YouTube Video: How do I use update CTs to change resources in an AWS Managed Services (AMS) account? Internal-only change types You can see change types that are for internal use only. This is so you know what actions AMS can, or does, take. If there is an internal-only change type that you would like to have available for your use, submit a service request. For example, there is a Management \| Monitoring and notiﬁcation \| CloudWatch alarm suppression \| Update CT that is internal-only. AMS uses it to deploy infrastructure updates (such as patching) to
ams-og-041	ams-og.pdf	41	easy to update it. YouTube Video: How do I use update CTs to change resources in an AWS Managed Services (AMS) account? Internal-only change types You can see change types that are for internal use only. This is so you know what actions AMS can, or does, take. If there is an internal-only change type that you would like to have available for your use, submit a service request. For example, there is a Management \| Monitoring and notiﬁcation \| CloudWatch alarm suppression \| Update CT that is internal-only. AMS uses it to deploy infrastructure updates (such as patching) to turn oﬀ alarm notiﬁcations that the updates might erroneously trigger. When this CT is submitted, you will notice the RFC for the CT in your RFC list. Any internal-only CT that is deployed in an RFC appears in your RFC list. What are change types? Version May 08, 2024 129 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Change type schemas All change types provide a JSON schema for your input in the creation, modiﬁcation, or access, of resources. The schema provides the parameters, and their descriptions, for you to create a request for change (RFC). The successful execution of an RFC results in execution output. For provisioning RFCs, the execution output includes a "stack_id" that represents the stack in CloudFormation and can be searched in the CloudFormation console. The execution output sometimes includes output of the ID of the instance created and that ID can be used to search for the instance in the corresponding AWS console. For example, the Create ELB CT execution output includes a "stack_id" that is searchable in CloudFormation and outputs a key=ELB value=<stack-xxxx> that is searchable in the Amazon EC2 console for Elastic Load Balancing. Let's examine a CT schema. This is the schema for CodeDeploy Application Create, a fairly small schema. Some schemas have very large Parameter areas. { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Create CodeDeploy application", "description": "Use to create an AWS CodeDeploy applicati on resource with the specified name.", The ﬁrst part of the schema provides information to AMS about the requested change type. "type": "object", "properties": { "Description": { "description": "The reason for the request.", "type": "string", "minLength": 1, "maxLength": 500 }, "VpcId": { "description": "ID of the vpc to use, in the form vpc-0123abcd or vpc-01234567890abcdef.", "type": "string", "pattern": "^vpc-[a-z0-9]{8}$" }, "StackTemplateId": { "description": "Must be stm-sft6rv00000000000", "type": "string", "enum": ["stm-sft6rv00000000000"] What are change types? Version May 08, 2024 130 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information }, "Name":{ "description": "A name for the stack or stack component ; this becomes the Stack Name.", "type": "string", "minLength": 1, "maxLength": 255 }, "Tags": { "description": "Up to seven tags (key/value pairs) to categorize the resource.", "type": "array", "items": { "type": "object", "properties": { "Key": { "type": "string", "minLength": 1, "maxLength": 127 }, "Value": { "type": "string", "minLength": 1, "maxLength": 255 } }, "additionalProperties": false, "required": [ "Key", "Value" ] }, "minItems": 1, "maxItems": 7 }, "TimeoutInMinutes": { "description": "The maximum amount of time, in minutes, to allow for execution of the change. This will not prolong execution, but the RFC fails if the change is not completed in the specified time. The TimeoutIn Minutes parameter allows you to indicate a boundary time for running the change type. Valid values are 60 up to 360, for long-running UserData. The Parameters section is where you specify settings for the resource you are creating, or the action you are requesting. What are change types? Version May 08, 2024 131 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Valid values are 60 up to 360, for long-running UserData.", "type": "number", "minimum": 0, "maximum": 60 }, "Parameters": { "description": "Specifications for the stack.", "type": "object", "properties": { "CodeDeployApplicationName": { "description": "The name of an AWS CodeDeploy application.", "type": "string", "minLength": 1, "maxLength": 100, "pattern": "^[a-zA-Z0-9._+=,@-]{1,100}$" The "additional properties" sections let you know what parameters are required and which are optional. } }, "additionalProperties": false, "required": [ "CodeDeployApplicationName" ] } }, "additionalProperties": false, "required": [ "Description", "VpcId", "StackTemplateId", "Name", "TimeoutInMinutes", "Parameters" ] } Note This schema allows up to seven tags; however, EC2, EFS, RDS, and the multi-tier create schemas allow up to 50 tags. What are change types? Version May 08, 2024 132 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Managing permissions for change types You can use a custom policy to restrict which change types (CTs) are available to diﬀerent groups or users. To learn more about doing this, see the AMS User Guide section Setting Permissions. Redacting sensitive information from change types AMS change type schemas oﬀer a parameter attribute, "metadata":"ams:sensitive":"true" that is used for parameters that would contain sensitive information, such as a password. When this attribute is set, the input provided is obscured. Note that you cannot
ams-og-042	ams-og.pdf	42	tags. What are change types? Version May 08, 2024 132 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Managing permissions for change types You can use a custom policy to restrict which change types (CTs) are available to diﬀerent groups or users. To learn more about doing this, see the AMS User Guide section Setting Permissions. Redacting sensitive information from change types AMS change type schemas oﬀer a parameter attribute, "metadata":"ams:sensitive":"true" that is used for parameters that would contain sensitive information, such as a password. When this attribute is set, the input provided is obscured. Note that you cannot set this parameter attribute; however, if you are working with AMS to create a change type and have a parameter that you would like obscured at input, you can request this. Finding a change type, using the query option This example demonstrates how to use the AMS Console to ﬁnd the appropriate change type for the RFC that you want to submit. You can use the console or the API/CLI to ﬁnd a change type ID (CT) or version. There are two methods, either a search or choosing the classiﬁcation. For both selection types, You can sort the search by choosing either Most frequently used, Most recently used, or Alphabetical. YouTube Video: How do I create an RFC using the AWS Managed Services CLI and where can I ﬁnd the CT Schema? In the AMS console, on the RFCs -> Create RFC page: • With Browse by change type selected (the default), either: • Use the Quick create area to select from AMS's most popular CTs. Click on a label and the Run RFC page opens with the Subject option auto-ﬁlled for you. Complete the remaining options as needed and click Run to submit the RFC. • Or, scroll down to the All change types area and start typing a CT name in the option box, you don't have to have the exact or full change type name. You can also search for a CT by change type ID, classiﬁcation, or execution mode (automated or manual) by entering the relevant words. What are change types? Version May 08, 2024 133 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information With the default Cards view selected, matching CT cards appear as you type, select a card and click Create RFC. With the Table view selected, choose the relevant CT and click Create RFC. Both methods open the Run RFC page. • Alternatively, and to explore change type choices, click Choose by category at the top of the page to open a series of drop-down option boxes. • Choose Category, a Subcategory, an Item, and an Operation. The information box for that change type appears a panel appears at the bottom of the page. • When you're ready, press Enter, and a list of matching change types appears. • Choose a change type from the list. The information box for that change type appears at the bottom of the page. • After you have the correct change type, choose Create RFC. 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. Note The AMS API/CLI (amscm and amsskms) endpoints are in the AWS N. Virginia Region, us-east-1. Depending on how your authentication is set, and what AWS Region your account and resources are in, you may need to add --region us-east-1 when issuing commands. You may also need to add --profile saml, if that is your authentication method. To search for a change type using the AMS CM API (see ListChangeTypeClassiﬁcationSummaries) or CLI: What are change types? Version May 08, 2024 134 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information You can use a ﬁlter or query to search. The ListChangeTypeClassiﬁcationSummaries operation has Filters options for Category, Subcategory, Item, and Operation, but the values must match the existing values exactly. For more ﬂexible results when using the CLI, you can use the --query option. Change type ﬁltering with the AMS CM API/CLI Attribute Valid values ChangeTypeId Any string represent ing a ChangeTypeId (For ex: ct-abc123 xyz7890) Valid/Default condition Equals Category Any free-form text Contains Subcategory Item Operation 1. Here are some examples of listing change type classiﬁcations: The following command lists all change type categories. aws amscm list-change-type-categories Notes For change type IDs, see the Change Type Reference. For change type
ams-og-043	ams-og.pdf	43	operation has Filters options for Category, Subcategory, Item, and Operation, but the values must match the existing values exactly. For more ﬂexible results when using the CLI, you can use the --query option. Change type ﬁltering with the AMS CM API/CLI Attribute Valid values ChangeTypeId Any string represent ing a ChangeTypeId (For ex: ct-abc123 xyz7890) Valid/Default condition Equals Category Any free-form text Contains Subcategory Item Operation 1. Here are some examples of listing change type classiﬁcations: The following command lists all change type categories. aws amscm list-change-type-categories Notes For change type IDs, see the Change Type Reference. For change type IDs, see Finding a Change Type or CSIO. Regular expressio ns in each individua l ﬁeld are not supported. Case insensitive search The following command lists the subcategories belonging to a speciﬁed category. aws amscm list-change-type-subcategories --category CATEGORY The following command lists the items belonging to a speciﬁed category and subcategory. aws amscm list-change-type-items --category CATEGORY --subcategory SUBCATEGORY What are change types? Version May 08, 2024 135 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information 2. Here are some examples of searching for change types with CLI queries: The following command searches CT classiﬁcation summaries for those that contain "S3" in the Item name and creates output of the category, subcategory, item, operation, and change type ID in table form. aws amscm list-change-type-classification-summaries --query "ChangeTypeClassificationSummaries [?contains(Item, 'S3')]. [Category,Subcategory,Item,Operation,ChangeTypeId]" --output table +---------------------------------------------------------------+ \| ListChangeTypeClassificationSummaries \| +----------+-------------------------+--+------+----------------+ \|Deployment\|Advanced Stack Components\|S3\|Create\|ct-1a68ck03fn98r\| +----------+-------------------------+--+------+----------------+ 3. You can then use the change type ID to get the CT schema and examine the parameters. The following command outputs the schema to a JSON ﬁle named CreateS3Params.schema.json. aws amscm get-change-type-version --change-type-id "ct-1a68ck03fn98r" --query "ChangeTypeVersion.ExecutionInputSchema" --output text > CreateS3Params.schema.json For information about using CLI queries, see How to Filter the Output with the --query Option and the query language reference, JMESPath Speciﬁcation. 4. After you have the change type ID, we recommend verifying the version for the change type to make sure it's the latest version. Use this command to ﬁnd the version for a speciﬁed change type: aws amscm list-change-type-version-summaries --filter Attribute=ChangeTypeId,Value=CHANGE_TYPE_ID To ﬁnd the AutomationStatus for a speciﬁc change type, run this command: aws amscm --profile saml get-change-type-version --change-type-id CHANGE_TYPE_ID -- query "ChangeTypeVersion.{AutomationStatus:AutomationStatus.Name}" To ﬁnd the ExpectedExecutionDurationInMinutes for a speciﬁc change type, run this command: What are change types? Version May 08, 2024 136 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information aws amscm --profile saml get-change-type-version --change-type-id ct-14027q0sjyt1h --query "ChangeTypeVersion.{ExpectedDuration:ExpectedExecutionDurationInMinutes}" Troubleshooting RFC errors in AMS Many AMS provisioning RFC failures can be investigated through the CloudFormation documentation. See Troubleshooting AWS CloudFormation: Troubleshooting Errors Additional troubleshooting suggestions are provided in the following sections. "Management" RFC errors in AMS AMS "Management" Category change types (CTs) allow you to request access to resources as well as manage existing resources. This section describes some common issues. RFC access errors • Make sure the Username and FQDN you speciﬁed in the RFC are correct and exist in the domain. For help ﬁnding your FQDN, see Finding your FQDN. • Make sure the stack ID you speciﬁed for access is an EC2-related stack. Stacks such as ELB and Amazon Simple Storage Service (S3) are not candidates for access RFCs, instead, use your read only access role to get access these stacks resources. For help ﬁnding a stack ID, see Finding stack IDs • Make sure the stack ID you provided is correct and belongs to the relevant account. For help with other access RFC failures, see Access management. YouTube Video: How do I raise a Request for Change (RFC) properly to avoid rejections and failures? RFC (manual) CT scheduling errors Most change types are ExecutionMode=Automated, but some are ExecutionMode=Manual and that aﬀects how you should schedule them to avoid RFC failure. Scheduled RFCs with ExecutionMode=Manual, must be set to execute at least 24 hours in the future if you are using the AMS Console to create the RFC. This caveat does not apply to the AMS API/CLI, but it is still important to schedule Manual RFCs at least 8 hours ahead. Troubleshooting RFC errors Version May 08, 2024 137 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information AMS aims to respond to a manual CT within four hours, and will correspond as soon as possible, but it could take much longer for the RFC to actually be executed. Using RFCs with manual update CTs AMS Operations reject Management \| Other \| Other RFCs for updates to stacks, when there is an Update change type for the type of stack that you want to update. RFC delete stack errors RFC delete stack failures: If you use the Management \| Standard stacks \| Stack \| Delete CT, you will see the detailed events in the AWS CloudFormation Console for the stack with the AMS stack name. You can identify your stack
ams-og-044	ams-og.pdf	44	will correspond as soon as possible, but it could take much longer for the RFC to actually be executed. Using RFCs with manual update CTs AMS Operations reject Management \| Other \| Other RFCs for updates to stacks, when there is an Update change type for the type of stack that you want to update. RFC delete stack errors RFC delete stack failures: If you use the Management \| Standard stacks \| Stack \| Delete CT, you will see the detailed events in the AWS CloudFormation Console for the stack with the AMS stack name. You can identify your stack by checking it against the name it has in the AMS Console. The AWS CloudFormation Console provides more details about failure causes. Before deleting a stack, you should consider how the stack was created. If you created the stack using an AMS CT and did not add or edit the stack resources, then you can expect to delete it without issue. However, it is a good idea for you remove any manually-added resources from a stack before submitting a delete stack RFC against it. For example, if you create a stack using the full stack CT (HA Two Tier), it includes a security group - SG1. If you then use AMS to create another security group - SG2, and reference the new SG2 in the SG1 created as part of the full stack, and then use the delete stack CT to delete the stack, the SG1 will not delete as it is referenced by SG2. Important Deleting stacks can have unwanted and unanticipated consequences. AMS prefers to not delete stacks or stack resources on behalf of customers for this reason. Note, that AMS will only delete resources on your behalf (through a submitted Mangement \| Other \| Other \| Update change type) that are not possible to delete using the appropriate, automated, change type to delete. Additional considerations: • If the resources are enabled for 'delete protection', AMS can help to unblock this if you submit a Management \| Other \| Other \| Update change type and, after the deletion protection is removed, you can use the automated CT to delete that resource. • If there are multiple resources in a stack, and you want to delete only a subset of the stack resources, use the CloudFormation Update change type (see CloudFormation Ingest Stack: Updating). You can also submit a Management \| Other \| Other \| Update change type and AMS engineers can help you craft the changeset, if needed. Troubleshooting RFC errors Version May 08, 2024 138 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information • If there are issues using the CloudFormation Update CT due to drifts, AMS can help if you submit a Management \| Other \| Other \| Update to resolve the drift (as far as supported by the AWS CloudFormation Service) and provide a ChangeSet that you can then validate and execute using the automated CT, Management/Custom Stack/Stack From CloudFormation Template/Approve Changeset and Update. AMS maintains the above restrictions to help ensure there are no unexpected or unanticipated resource deletions. For more information, see Troubleshooting AWS CloudFormation: delete stack fails. RFC update DNS errors Multiple RFCs to update a DNS hosted zone can fail, some without reason. Creating multiple RFCs at the same time to update DNS hosted zones (private or public) can cause some RFCs to fail because they are trying to update the same stack at the same time. AMS change management rejects or fails RFCs that are not able to update a stack because the stack is already being updated by another RFC. AMS recommends that you create one RFC at a time and wait for the RFC to succeed before raising a new one for the same stack. RFC IAM entities errors AMS provisions a number of default IAM roles and proﬁles into AMS accounts that are designed to meet your needs. However, you may need to request additional IAM resources occasionally. The process for submitting RFCs requesting custom IAM resources follows the standard workﬂow for manual RFCs, but the approval process also includes a security review to ensure appropriate security controls are in place. Therefore, the process typically takes longer than other manual RFCs. To reduce the cycle time on these RFCs, please follow the following guidelines. For information on what we mean by an IAM review and how it maps to our Technical Standards and Risk Acceptance process, see Understand RFC security reviews. Common IAM resources requests: • If you are asking for a policy pertaining to a major cloud-compatible application, such as CloudEndure, see the AMS pre-approved IAM CloudEndure policy: Unpack the WIGs Cloud Endure Landing Zone Example ﬁle and open the customer_cloud_endure_policy.json Troubleshooting RFC errors Version May 08, 2024 139 AMS Advanced Onboarding Guide AMS Advanced
ams-og-045	ams-og.pdf	45	longer than other manual RFCs. To reduce the cycle time on these RFCs, please follow the following guidelines. For information on what we mean by an IAM review and how it maps to our Technical Standards and Risk Acceptance process, see Understand RFC security reviews. Common IAM resources requests: • If you are asking for a policy pertaining to a major cloud-compatible application, such as CloudEndure, see the AMS pre-approved IAM CloudEndure policy: Unpack the WIGs Cloud Endure Landing Zone Example ﬁle and open the customer_cloud_endure_policy.json Troubleshooting RFC errors Version May 08, 2024 139 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Note If you want a more permissive policy, discuss your needs with your CloudArchitect/CSDM and obtain, if needed, an AMS Security Review and Signoﬀ before submitting an RFC implementing the policy. • If you want to modify a resource deployed by AMS in your account by default, we recommend that you ask for a modiﬁed copy of that resource instead of changes to the existing one. • If you are requesting permissions for a human user (instead of attaching the permissions to the user) attach the permissions to a role, and then grant the user permission to assume that role. For details on doing this, see Temporary AMS Advanced console access. • If you require exceptional permissions for a temporary migration or workﬂow, provide an end date for those permissions in your request. • If you’ve already discussed the subject of your request with your security team, provide evidence of their approval to your CSDM with as much detail as possible. If AMS rejects an IAM RFC we provide a clear reason for the rejection. For example, we might reject an IAM policy create request and explain what about the policy is inappropriate. In that case, you can make the identiﬁed changes and resubmit the request. If additional clarity on the status of a request is required, submit a service request, or contact your CSDM. The following list describes the typical risks that AMS tries to mitigate as we review your IAM RFCs. If your IAM RFC has any of these risks, it may result in the rejection of the RFC. In cases where you require an exception, AMS asks for approvals from your security team. To seek such an exception, coordinate with your CSDM. Note AMS may, for any reason, decline any change to IAM resources inside of an account. For concerns regarding any RFC rejection, reach out to AMS Operations via a service request, or contact your CSDM. • Privilege escalation, such as permissions that allow you to modify your own permissions, or to modify the permissions of other resources inside the account. Examples: • The use of iam:PassRole with another, more privileged role. Troubleshooting RFC errors Version May 08, 2024 140 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information • Permission to attach/detach IAM policies from a role or user. • The modiﬁcation of IAM policies in the account. • The ability to make API calls in the context of management infrastructure. • Permissions to modify resources or applications that are required to provide AMS services to you. Examples: • Modiﬁcation of AMS infrastructure like the bastions, management host, or EPS infrastructure. • Deletion of log management AWS Lambda functions, or log streams. • The deletion or modiﬁcation of the default CloudTrail monitoring application. • The modiﬁcation of the Directory Services Active Directory (AD). • Disabling CloudWatch (CW) alarms. • The modiﬁcation of the principals, policies, and namespaces deployed in the account as a part of the landing zone. • Deployment of infrastructure outside of best practices, such as permissions that allow the creation of infrastructure in a state that endangers your information security. Examples: • The creation of public, or unencrypted, S3 buckets or public sharing of EBS volumes. • The provisioning of public IP addresses. • The modiﬁcation of security groups to allow broad access. • Overly broad permissions capable of causing application impact, such as permissions that can result in data loss, integrity loss, inappropriate conﬁguration, or interruptions of service for your infrastructure and the applications inside the account. Examples: • Disabling, or redirecting, network traﬃc through APIs like ModifyNetworkInterfaceAttribute or UpdateRouteTable. • The disabling of managed infrastructure by detaching volumes from managed hosts. • Permissions for services not a part of the AMS service description and not supported by AMS. Services not listed in the AMS Service description cannot be used in AMS accounts. To request support for a feature or service, please reach out to your CSDM. • Permissions that do not meet your stated goal as they are either too generous, or too conservative, or are applied to the wrong resources. Examples: • A request for s3:PutObject permissions to an S3 bucket that has mandatory KMS encryption,
ams-og-046	ams-og.pdf	46	or UpdateRouteTable. • The disabling of managed infrastructure by detaching volumes from managed hosts. • Permissions for services not a part of the AMS service description and not supported by AMS. Services not listed in the AMS Service description cannot be used in AMS accounts. To request support for a feature or service, please reach out to your CSDM. • Permissions that do not meet your stated goal as they are either too generous, or too conservative, or are applied to the wrong resources. Examples: • A request for s3:PutObject permissions to an S3 bucket that has mandatory KMS encryption, without KMS:Encrypt permissions to the relevant key. • Permissions that pertain to resources that don’t exist in the account. Troubleshooting RFC errors Version May 08, 2024 141 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information • IAM RFCs where the description of the RFC does not seem to match the request. "Deployment" RFC errors AMS "Deployment" Category change types (CTs) allow you to request various AMS-supported resources be added to your account. Most AMS CTs that create a resource are based on AWS CloudFormation templates. As a customer you have read-only access to all AWS services including AWS CloudFormation, you can quickly identify the AWS CloudFormation stack that represents your stack based on the stack description using the AWS CloudFormation Console. The failed stack will likely be in a state of DELETE_COMPLETE. Once you have identiﬁed the AWS CloudFormation stack, the events will show you the speciﬁc resource that failed to create, and why. Using CloudFormation documentation to troubleshoot Most AMS provisioning RFCs use a CloudFormation template and that documentation can be helpful for troubleshooting. See documentation for that AWS CloudFormation template: • Create application load balancer failure: AWS::ElasticLoadBalancingV2::LoadBalancer (Application Load Balancer) • Create Auto scaling group: AWS::AutoScaling::AutoScalingGroup (Auto Scaling Group) • Create memcached cache: AWS::ElastiCache::CacheCluster (Cache Cluster) • Create Redis cache: AWS::ElastiCache::CacheCluster (Cache Cluster) • Create DNS Hosted Zone (used with Create DNS private/public): AWS::Route53::HostedZone (R53 Hosted Zone) • Create DNS Record Set (used with Create DNS private/public): AWS::Route53::RecordSet (Resource Record Sets) • Create EC2 stack: AWS::EC2::Instance (Elastic Compute Cloud) • Create Elastic File System (EFS): AWS::EFS::FileSystem (Elastic File System) • Create Load balancer: AWS::ElasticLoadBalancing::LoadBalancer (Elastic Load Balancer) • Create RDS DB: AWS::RDS::DBInstance (Relational Database) • Create Amazon S3: AWS::S3::Bucket (Simple Storage Service) • Create Queue: AWS::SQS::Queue (Simple Queue Service) Troubleshooting RFC errors Version May 08, 2024 142 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information RFC creating AMIs errors An Amazon Machine Image (AMI) is a template that contains a software conﬁguration (for example, an operating system, an application server, and applications). From an AMI, you launch an instance, which is a copy of the AMI running as a virtual server in the cloud. AMIs are very useful, and required to create EC2 instances or Auto Scaling groups; however, you must observe some requirements: • The instance you specify for Ec2InstanceId must be in a stopped state for the RFC to succeed. Do not use Auto Scaling group (ASG) instances for this parameter because the ASG will terminate a stopped instance. • To create an AMS Amazon Machine Image (AMI), you must start with an AMS instance. Before you can use the instance to create the AMI, you must prepare it by ensuring that it is stopped and dis-joined from its domain. For details, see Create a Standard Amazon Machine Image Using Sysprep • The name you specify for the new AMI must be unique within the account or the RFC fails. How to do this is described in AMI \| Create, and for more details, see and AWS AMI Design. Note For additional information for prepping for AMI creation, see AMI \| Create. RFCs creating EC2s or ASGs errors For EC2 or ASG failures with timeouts, AMS recommends that you conﬁrm if the AMI used is customized. If it is, please refer to the AMI creation steps included in this guide (see AMI \| Create) to ensure that the AMI was created correctly. A common mistake when creating a custom AMI is not following the steps in the guide to rename or invoke Sysprep. RFCs creating RDS errors Amazon Relational Database Service (RDS) failures can occur for many diﬀerent reasons because you can use many diﬀerent engines when you create the RDS, and each engine has its own requirements and limitations. Before attempting to create an AMS RDS stack, carefully review AWS RDS parameter values, see CreateDBInstance. To learn more about Amazon RDS in general, including size recommendations, see Amazon Relational Database Service Documentation. Troubleshooting RFC errors Version May 08, 2024 143 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information RFCs creating Amazon S3s errors One common error when creating an S3 storage bucket is not using a unique name for the bucket. If
ams-og-047	ams-og.pdf	47	occur for many diﬀerent reasons because you can use many diﬀerent engines when you create the RDS, and each engine has its own requirements and limitations. Before attempting to create an AMS RDS stack, carefully review AWS RDS parameter values, see CreateDBInstance. To learn more about Amazon RDS in general, including size recommendations, see Amazon Relational Database Service Documentation. Troubleshooting RFC errors Version May 08, 2024 143 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information RFCs creating Amazon S3s errors One common error when creating an S3 storage bucket is not using a unique name for the bucket. If you submitted an S3 bucket Create CT with the same name as one previously submitted, it would fail because an S3 bucket would already exist with that BucketName. This would be detailed in the AWS CloudFormation Console, where you will see that the stack event shows that the bucket name is already in use. RFC validation versus execution errors RFC failures and related messages diﬀer in the output messages on the AMS console RFC details page for a selected RFC: • Validation Failures reasons are available in Status Field only • Execution Failures reasons are available in Execution Output as well as Status Fields. Troubleshooting RFC errors Version May 08, 2024 144 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information RFC error messages When you come across the following error for the listed change types (CTs), you can use these solutions to help you ﬁnd the source of the problems and ﬁx them. {"errorMessage":"An error has occurred during RFC execution. We are investigating the issue.","errorType":"InternalError"} If you require further assistance after referring to the following troubleshooting options, then engage AMS via RFC correspondence or create a service request. See RFC Correspondence and Attachment (Console) and Creating a Service Request in AMS for more details. Troubleshooting RFC errors Version May 08, 2024 145 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Workload ingestion (WIGS) errors Note Validation tools for both Windows and Linux can be downloaded and run directly on your on-premises servers, as well as EC2 instances in AWS. These can be found through the AMS Advanced Application Developer's Guide Migrating workloads: Linux pre-ingestion validation and Migrating workloads: Windows pre-ingestion validation. • Make sure EC2 instance exists in target AMS account. For example, if you have shared your AMI from a non-AMS account to an AMS account, you'll have to create an EC2 instance in your AMS account with the shared AMI before you can submit a Workload Ingest RFC. • Check to see if the security groups attached to the instance have egress traﬃc allowed. The SSM Agent needs to be able to connect to its public endpoint. • Check to see if the instance has the right permissions to connect with the SSM agent. These permissions come with the customer-mc-ec2-instance-profile, you can check for this in the EC2 console: EC2 instance stack stop errors • Check to see if the instance is already in a stopped or terminated state. • If the EC2 instance is online and you see the InternalError error, then submit a service request for AMS to investigate. Troubleshooting RFC errors Version May 08, 2024 146 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information • Note that you can't use the change type Management \| Advanced stack components \| EC2 instance stack \| Stop ct-3mvvt2zkyveqj to stop an Auto Scaling group (ASG) instance. If you need to stop an ASG instance, then submit a service request. EC2 instance stack create errors The InternalError message is from CloudFormation; a CREATION_FAILED status reason. You can ﬁnd details on the stack failure in CloudWatch stack events by following these steps: • In the AWS Management console, you can view a list of stack events while your stack is being created, updated, or deleted. From this list, ﬁnd the failure event and then view the status reason for that event. The status reason might contain an error message from AWS CloudFormation or from a particular service that can help you understand the problem. • For more information about viewing stack events, see Viewing AWS CloudFormation Stack Data and Resources on the AWS Management Console. EC2 instance volume restore errors AMS creates an internal troubleshooting RFC when EC2 instance volume restore fails. This is done because EC2 instance volume restore is an important part of disaster recovery (DR) and AMS creates this internal troubleshooting RFC for you automatically. When the internal troubleshooting RFC is created, a banner is displayed providing you with links to the RFC. This internal troubleshooting RFC provides your with more visibility into RFC failures and, rather than submitting retry RFCs leading to the same errors, or making you manually reach out to AMS for this failure, you can keep track of your changes
ams-og-048	ams-og.pdf	48	volume restore errors AMS creates an internal troubleshooting RFC when EC2 instance volume restore fails. This is done because EC2 instance volume restore is an important part of disaster recovery (DR) and AMS creates this internal troubleshooting RFC for you automatically. When the internal troubleshooting RFC is created, a banner is displayed providing you with links to the RFC. This internal troubleshooting RFC provides your with more visibility into RFC failures and, rather than submitting retry RFCs leading to the same errors, or making you manually reach out to AMS for this failure, you can keep track of your changes and know that the failure is being worked on by AMS. This also reduces the time-to-recovery (TTR) metric for their change as AMS Operators proactively work on the RFC failure instead of waiting for your request. How to get help with an RFC You can reach out to AMS to identify the root cause of your failure. AMS business hours are 24 hours a day, 7 days a week, 365 days a year. AMS provides several avenues for you to ask for help or make service requests. Troubleshooting RFC errors Version May 08, 2024 147 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information • To ask for information or advice, or for access to an AMS-managed IT service, or to request an additional service from AMS, use the AMS console and submit a service request. For details, see Creating a Service Request. For general information about AMS service requests, see Service Request Management. • 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. • For speciﬁc questions about how you or your resources or applications are working with AMS, or to escalate an incident, email one or more of the following: 1. First, if you are unsatisﬁed with the service request or incident report response, email your CSDM: ams-csdm@amazon.com 2. Next, if escalation is required, you can email the AMS Operations Manager (but your CSDM will probably do this): ams-opsmanager@amazon.com 3. Further escalation would be to the AMS Director: ams-director@amazon.com 4. Finally, you are always able to reach the AMS VP: ams-vp@amazon.com Direct Change mode in AMS Topics • Getting Started with Direct Change mode • Security and compliance • Change management in Direct Change mode • Creating stacks using Direct Change mode • Direct Change Mode use cases AWS Managed Services (AMS) Direct Change mode (DCM) extends AMS Advanced change management by providing native AWS access to AMS Advanced Plus and Premium accounts to provision and update AWS resources. With DCM, you have the option to use native AWS API (console or CLI/SDK) or AMS Advanced change management requests for change (RFCs), and in either case the resources and changes to them are fully supported by AMS, including monitoring, patch, backup, incident response management. Resources provisioned through DCM are registered in the AMS service knowledge management system (SKMS), joined to the AMS managed Active Directory domain (when applicable), and run AMS management agents. Use existing tooling Direct Change mode Version May 08, 2024 148 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information (for example, CloudFormation, AWS SDK, and CDK) to develop and deploy AMS-managed CloudFormation stacks. Note Direct Change mode does not remove AMS change management RFCs. You have full access to AMS RFCs with DCM. Watch Akash’s video to learn more (6:30) Getting Started with Direct Change mode Begin by checking prerequisites and then submitting a request for change (RFC) in your eligible AMS Advanced account. 1. Conﬁrm that the account that you want to use with DCM meets the requirements: • The account is AMS Advanced Plus or Premium. • The account doesn't have Service Catalog enabled. We currently don't support onboarding accounts to both DCM and Service Catalog at the same time. If you are already onboarded to Service Catalog but are interested in DCM, discuss your needs with your cloud service delivery manager (CSDM). If you decide to switch from Service Catalog to DCM, oﬀboard Service Catalog, to do that, include the ask in the request for change below. For details about Service Catalog in AMS, see AMS and Service Catalog. 2. Submit a request for change (RFC) using the Management \| Managed account \| Direct Change mode \| Enable change type (ct-3rd4781c2nnhp). For an example walkthrough, see Direct Change mode \| Enable. After the CT is processed, the predeﬁned IAM roles, AWSManagedServicesCloudFormationAdminRole and AWSManagedServicesUpdateRole are provisioned in the speciﬁed account. 3. Assign the appropriate role to the users that require DCM access using your internal federation process. Getting Started with Direct Change mode Version May 08, 2024 149 AMS Advanced Onboarding Guide
ams-og-049	ams-og.pdf	49	in the request for change below. For details about Service Catalog in AMS, see AMS and Service Catalog. 2. Submit a request for change (RFC) using the Management \| Managed account \| Direct Change mode \| Enable change type (ct-3rd4781c2nnhp). For an example walkthrough, see Direct Change mode \| Enable. After the CT is processed, the predeﬁned IAM roles, AWSManagedServicesCloudFormationAdminRole and AWSManagedServicesUpdateRole are provisioned in the speciﬁed account. 3. Assign the appropriate role to the users that require DCM access using your internal federation process. Getting Started with Direct Change mode Version May 08, 2024 149 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Note You can specify any number of SAMLIdentityProviders, AWS Services, and IAM Entities (Roles, Users etc) to assume the roles. You must provide at least one: SAMLIdentityProviderARNs, IAMEntityARNs, or AWSServicePrincipals. For more information, consult with your company's IAM department or with your AMS cloud architect (CA). Direct Change mode IAM roles and policies When Direct Change mode is enabled in an account, these new IAM entities are deployed: AWSManagedServicesCloudFormationAdminRole: This role grants access to the CloudFormation console, create and update CloudFormation stacks, view drift reports, and create and execute CloudFormation ChangeSets. Access to this role is managed through the your SAML provider. Managed policies that are deployed and attached to the role AWSManagedServicesCloudFormationAdminRole are: • AMS Advanced multi-account landing zone (MALZ) Application account • AWSManagedServices_CloudFormationAdminPolicy1 • AWSManagedServices_CloudFormationAdminPolicy2 • This policy represents the permissions granted to the AWSManagedServicesCloudFormationAdminRole. You and partners use this policy to grant access to an existing role in the account and allow that role to launch and update CloudFormation stacks in the account. This might require additional AMS service control policy (SCP) updates to allow other IAM entities to launch CloudFormation stacks. • AMS Advanced single-account landing zone (SALZ) account • AWSManagedServices_CloudFormationAdminPolicy1 • AWSManagedServices_CloudFormationAdminPolicy2 • cdk-legacy-mode-s3-access [in-line policy] • AWS ReadOnlyAccess policy Getting Started with Direct Change mode Version May 08, 2024 150 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information AWSManagedServicesUpdateRole: This role grants restricted access to downstream AWS service APIs. The role is deployed with managed policies that provide mutating and non-mutating API operations, but in general restricts mutating operations (such as Create/Delete/PUT), against certain services such as IAM, KMS,GuardDuty, VPC, AMS infrastructure resources and conﬁguration, and so forth. Access to this role is managed through the your SAML provider. Managed policies that are deployed and attached to the role AWSManagedServicesUpdateRole are: • AMS Advanced multi-account landing zone Application account • AWSManagedServicesUpdateBasePolicy • AWSManagedServicesUpdateDenyPolicy • AWSManagedServicesUpdateDenyProvisioningPolicy • AWSManagedServicesUpdateEC2AndRDSPolicy • AWSManagedServicesUpdateDenyActionsOnAMSInfraPolicy • AMS Advanced single-account landing zone account • AWSManagedServicesUpdateBasePolicy • AWSManagedServicesUpdateDenyProvisioningPolicy • AWSManagedServicesUpdateEC2AndRDSPolicy • AWSManagedServicesUpdateDenyActionsOnAMSInfraPolicy1 • AWSManagedServicesUpdateDenyActionsOnAMSInfraPolicy2 Besides these, the managed policy AWSManagedServicesUpdateRole role also has the AWS managed policy ViewOnlyAccess attached to it. Security and compliance Security and compliance is a shared responsibility between AMS Advanced and you, as our customer. AMS Advanced Direct Change mode does not change this shared responsibility. Security in Direct Change mode AMS Advanced oﬀers additional value with a prescriptive landing zone, a change management system, and access management. When using Direct Change mode, this responsibility model does not change. However, you should be aware of additional risks. Security and compliance Version May 08, 2024 151 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information The Direct Change Mode "Update" role (see Direct Change mode IAM roles and policies) provides elevated permissions allowing the entity with access to it, to make changes to infrastructure resources of AMS-supported services within your account. With elevated permissions, varied risks exist depending on the resource, service, and actions, especially in situations where an incorrect change is made due to oversight, mistake, or lack of adherence to your internal process and control framework. As per AMS Technical Standards, the following risks have been identiﬁed and recommendations are made as follows. Detailed information about AMS Technical Standards is available through AWS Artifact. To access AWS Artifact, contact your CSDM for instructions or go to Getting Started with AWS Artifact. AMS-STD-001: Tagging Standards Does it break Risks Recommendations All the AMS owned resources must have Yes. Breaks for CloudFormation,Clo following key-value udTrail, EFS, pair All the AMS-owned tags other than those listed above must have preﬁxes like AMS* or MC* in upper/lower/mix case. OpenSearch, CloudWatch Logs, SQS, SSM, Tagging api - as these services do not support the aws:TagsKey condition to restrict tagging for the AMS namespace. Standard given in table AMS-STD-0 03, following, states that you can change AppId, Environme nt and AppName, but not for AMS- owned resources. Not Incorrect tagging of AMS resources may adversly impact the reporting, alerting and patching operations of your resources, on the AMS side. Access must be restrticted to make any changes on the AMS default tagging requirements for anyone other than AMS teams. Security and compliance Version May 08, 2024 152
ams-og-050	ams-og.pdf	50	in upper/lower/mix case. OpenSearch, CloudWatch Logs, SQS, SSM, Tagging api - as these services do not support the aws:TagsKey condition to restrict tagging for the AMS namespace. Standard given in table AMS-STD-0 03, following, states that you can change AppId, Environme nt and AppName, but not for AMS- owned resources. Not Incorrect tagging of AMS resources may adversly impact the reporting, alerting and patching operations of your resources, on the AMS side. Access must be restrticted to make any changes on the AMS default tagging requirements for anyone other than AMS teams. Security and compliance Version May 08, 2024 152 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Standards Does it break Risks Recommendations achievable through IAM permissions. Any tag on AMS- owned stacks must Yes. CloudFormation does not support not be deleted based on your change requests. the aws:TagsKey condition to restrict tags for the AMS namespace. You are not permitted to use AMS tag naming conventio Yes. Breaks for CloudFormation, CloudTrail, Amazon n in your infrastru Elastic File System cture as mentioned in table AMS-STD-002, next. (EFS), OpenSearch, CloudWatch Logs, Amazon Simple Queue Service (SQS), Amazon EC2 Systems Manager (SSM), Tagging API; these services do not support the aws:TagsKey condition to restrict tagging for the AMS namespace. AMS-STD-002: Identity and Access Management (IAM) Standards Does it break Risks Recommendations 4.7 Actions, which bypass the change Yes. The purpose of self service actions The secure access model is a core The IAM user should be time-bounded and management allow you to perform technical facet of granted permissio Security and compliance Version May 08, 2024 153 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Standards Does it break Risks Recommendations process (RFC), must actions bypassing the AMS and an IAM ns based on least-pri AMS RFC system. user for console or programmatic access vilege and need-to-k now. circumvents this access control. The IAM users access is not monitored by AMS change management. Access is logged in CloudTrai l only. not be permitted such as starting or stopping of an instance, creation of S3 buckets or RDS instances, and so forth. Developer mode accounts and Self-Service Provision ed mode services (SSPS) are exempted as long as actions are performed within the boundaries of the assigned role. AMS-STD-003: Network Security Standards Does it break Risks Recommendations S2. Elastic IP on EC2 instances must be Yes. Self service actions allow you Adding an elastic IP to an instance Block any unnecessa ry traﬃc to that used only with a to associate and exposes it to the instance through formal risk acceptanc e agreement, or with a valid use case by internal teams. disassociate elastic IP addresses (EIP). Internet. This increases the risk of information disclosur e and unauthorized activity. security groups, and verify that your security groups are attached with the instance to ensure that it allows the traﬃc only as needed for business reasons. S14. VPC Peering and endpoint connectio Yes. Not possible through IAM policy. Traﬃc leaving your AMS account is not We recommend peering only with Security and compliance Version May 08, 2024 154 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Standards Does it break Risks Recommendations ns between accounts that belong to the same customer can be permitted. AMS base AMIs can be shared between AMS-managed and unmanaged accounts as long as we can verify that they are owned by the same AWS organization. AMS-STD-007: Logging monitored once AMS accounts that egressing the account boundary. you own. If your use case requires this, use security groups and route tables to limit what traﬃc ranges, resources, and types can egress through the relevant connection. AMIs may contain sensitive data and it Share AMIs with only the account owned may be exposed to by your organizat unintended accounts. ion or validate the use-case and account information before sharing outside the organization. Standards Does it break Risks Recommendations 19. Any log can be forwarded from one AMS account to another AMS account of the same customer. 20. Any log can be forwarded from AMS to a non-AMS account only if the Yes. Potential insecurity for customer logs as veriﬁcation of the customer accounts being in the same organization can not be achieved through IAM policy. Share logs with only accounts managed by your AWS Org, or validate the use- case and account information before Logs may contain sensitive data and it may be exposed to unintended accounts. sharing outside of your organization. We can verify this via multiple ways, Security and compliance Version May 08, 2024 155 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Standards Does it break Risks Recommendations non-AMS account is owned by the same AMS customer (by conﬁrming that they are under the same AWS Organizat ions account or by matching the email
ams-og-051	ams-og.pdf	51	can not be achieved through IAM policy. Share logs with only accounts managed by your AWS Org, or validate the use- case and account information before Logs may contain sensitive data and it may be exposed to unintended accounts. sharing outside of your organization. We can verify this via multiple ways, Security and compliance Version May 08, 2024 155 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Standards Does it break Risks Recommendations non-AMS account is owned by the same AMS customer (by conﬁrming that they are under the same AWS Organizat ions account or by matching the email domain with the customer's company name and PAYER linked account) using internal tools. check with your cloud service delivery manager (CSDM). Work with your internal authorization and authentication team to control the permissions to the Direct Change mode roles accordingly. Compliance in Direct Change mode Direct Change mode is compatible with both production and non-production workloads. It's your responsibility to ensure adherence to any compliance standards (for example, PHI, HIPAA, PCI), and to ensure that the use of Direct Change mode complies with your internal control frameworks and standards. Change management in Direct Change mode Change management is the process that AMS Advanced uses to implement requests for change. A request for change (RFC) is a request created by either you, or AMS Advanced through the AMS Advanced interface to make a change to your managed environment and includes an AMS Advanced change type (CT) ID for a particular operation. For more information, see Change management. Change management in Direct Change mode Version May 08, 2024 156 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Note Direct Change mode does not remove AMS change management RFCs, you still have full access to AMS RFCs with DCM. AMS Direct Change mode (DCM) extends AMS Advanced change management by providing native AWS access to AMS Advanced Plus and Premium accounts to provision and update AWS resources. Users who have been granted Direct Change mode permission through the IAM roles, can use native AWS API access to provision and make changes to resources in their AMS Advanced accounts. The users can still use AMS Advanced change management RFCs using the same IAM roles. In both cases the resources and changes to them are fully supported by AMS, including monitoring, patch, backup, incident response management. Users who do not have the appropriate role in these accounts must use the AMS Advanced change management RFC process to make changes. Change management use cases For security reasons, some changes in AMS Advanced can only be done through the change management request for change (RFC) process. The AWSManagedServicesCloudFormationAdminRole is restricted to actions taken through CloudFormation (CFN). For more about how to create stacks through DCM, see Creating stacks using Direct Change mode. The AWSManagedServicesUpdateRole is restricted for the following actions. For example walkthroughs for each change type, including the Management \| Managed account \| Direct Change mode \| Enable (ct-3rd4781c2nnhp) change type, see the "Additional Information" section for the relevant change type in the AMS Advanced Change Type Reference Change Types by Classiﬁcation section. Service Action AWS Key Management Service (AWS KMS) Update AWS Certiﬁcate Manager Create AWS Identity and Access Management (IAM) Any AWS VPN Any Change management in Direct Change mode Version May 08, 2024 157 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Service Action AMS Resource Scheduler AWS Backup Create backup plan AMS Workload Ingestion (WIGs) AMS Egress Filtering (Managed Palo Alto) AMS Advanced MALZ account changes Amazon GuardDuty AMS Advanced Stack Access Any Any Amazon Elastic Block Store (EBS) volume Delete Amazon Elastic Block Store (EBS) default encryption Enable default encryption Amazon Elastic Compute Cloud (Amazon EC2) Change hostname Amazon Machine Images (AMI) Delete, share Amazon EC2 Security Group AMS Advanced SSPS AWS Managed Microsoft AD AMS Advanced developer mode Any Amazon Simple Storage Service (Amazon S3) Create S3 bucket policies AWS Systems Manager Create Change management in Direct Change mode Version May 08, 2024 158 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Creating stacks using Direct Change mode There are two requirements when launching stacks in CloudFormation using the AWSManagedServicesCloudFormationAdminRole, in order for the stack to be managed by AMS: • The template must contain an AmsStackTransform. • The stack name must start with the preﬁx stack- followed by a 17 character alphanumeric string. Note To successfully use the AmsStackTransform, you must acknowledge that your stack template contains the CAPABILITY_AUTO_EXPAND capability in order for AWS CloudFormation (CFN) to create or update the stack. You do this by passing the CAPABILITY_AUTO_EXPAND as part of your create-stack request. CFN rejects the request if this capability is not acknowledged when the AmsStackTransform is included in the template. The CFN console ensures that you pass this capability if you have the
ams-og-052	ams-og.pdf	52	managed by AMS: • The template must contain an AmsStackTransform. • The stack name must start with the preﬁx stack- followed by a 17 character alphanumeric string. Note To successfully use the AmsStackTransform, you must acknowledge that your stack template contains the CAPABILITY_AUTO_EXPAND capability in order for AWS CloudFormation (CFN) to create or update the stack. You do this by passing the CAPABILITY_AUTO_EXPAND as part of your create-stack request. CFN rejects the request if this capability is not acknowledged when the AmsStackTransform is included in the template. The CFN console ensures that you pass this capability if you have the transform in your template, but this can be missed when you are interacting with CFN via their APIs. You must pass this capability whenever you use the following CFN API calls: • CreateChangeSet • CreateStack • UpdateStack When creating or updating a stack with DCM, the same validations and augmentations of CFN Ingest and Stack Update CTs are performed on the stack, for more information see AWS CloudFormation Ingest Guidelines, Best Practices, and Limitations. The exception to this is that the AMS default security groups (SGs) will not be attached to any stand-alone EC2 instances or EC2 instances in Auto Scaling groups (ASGs). When you create your CloudFormation template, with stand-alone EC2 instances or ASGs, you can attach the default SGs. Creating stacks using Direct Change mode Version May 08, 2024 159 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Note IAM roles can now be created and managed with the AWSManagedServicesCloudFormationAdminRole. The AMS default SGs have ingress and egress rules that allow the instances to launch successfully and to be accessed later through SSH or RDP by AMS operations and you. If the you ﬁnd that the AMS default security groups are too permissive, you can create your own SGs with more restrictive rules and attach them to your instance, as long as it still allows you and AMS operations to access the instance during incidents. The AMS default security groups are the following: • SentinelDefaultSecurityGroupPrivateOnly: Can be accessed in the CFN template through this SSM parameter /ams/${VpcId}/SentinelDefaultSecurityGroupPrivateOnly • SentinelDefaultSecurityGroupPrivateOnlyEgressAll: Can be accessed in the CFN template through this SSM parameter /ams/${VpcId}/ SentinelDefaultSecurityGroupPrivateOnlyEgressAll AMS Transform Add a Transform statement to your CloudFormation template. This adds a CloudFormation macro that validates and registers the stack with AMS at launch time. JSON Example "Transform": { "Name": "AmsStackTransform", "Parameters": { "StackId": {"Ref" : "AWS::StackId"} } } YAML Example Transform: Name: AmsStackTransform Parameters: Creating stacks using Direct Change mode Version May 08, 2024 160 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information StackId: !Ref 'AWS::StackId' Also add the Transform statement when updating the template of an existing stack. JSON Example { "AWSTemplateFormatVersion": "2010-09-09", "Description" : "Create an SNS Topic", "Transform": { "Name": "AmsStackTransform", "Parameters": { "StackId": {"Ref" : "AWS::StackId"} } }, "Parameters": { "TopicName": { "Type": "String", "Default": "HelloWorldTopic" } }, "Resources": { "SnsTopic": { "Type": "AWS::SNS::Topic", "Properties": { "TopicName": {"Ref": "TopicName"} } } } } YAML Example AWSTemplateFormatVersion: '2010-09-09' Description: Create an SNS Topic Transform: Name: AmsStackTransform Parameters: StackId: !Ref 'AWS::StackId' Parameters: TopicName: Type: String Default: HelloWorldTopic Creating stacks using Direct Change mode Version May 08, 2024 161 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Resources: SnsTopic: Type: AWS::SNS::Topic Properties: TopicName: !Ref TopicName Stack name The stack name must start with the preﬁx stack- followed by a 17 character alphanumeric string. This is to maintain compatibility with other AMS systems that operate on AMS stack IDs. The following are examples of ways to generate compatible stack IDs: Bash: echo "stack-$(env LC_CTYPE=C tr -dc 'a-z0-9' < /dev/urandom \| head -c 17)" Python: import string import random 'stack-' + ''.join(random.choices(string.ascii_lowercase + string.digits, k=17)) Powershell: "stack-" + ( -join ((0x30..0x39) + ( 0x61..0x7A) \| Get-Random -Count 17 \| % {[char]$_}) ) Direct Change Mode use cases The following are uses cases for Direct Change Mode: Resource provision and management through AWS CloudFormation • Integrate existing CloudFormation-based tooling and processes. Ongoing resource management and updates • Small atomic changes with low risk. • Changes that would otherwise run through a manual or automated RFC. Direct Change Mode use cases Version May 08, 2024 162 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information • Tooling that requires native AWS API access. • The DCM role can be utilized if you're in the migration stage. Migration teams leverage the permissions on the DCM to create or modify stacks. • DCM roles can be used in the CI/CD pipeline to build new AMIs, create Amazon ECS tasks, and so on. AMS Advanced Developer mode Topics • Getting started with AMS Advanced Developer mode • Security and compliance in Developer mode • Change management in Developer mode • Provisioning infrastructure in AMS Developer mode • Detective controls in AMS Developer mode • Logging, monitoring, and
ams-og-053	ams-og.pdf	53	Information • Tooling that requires native AWS API access. • The DCM role can be utilized if you're in the migration stage. Migration teams leverage the permissions on the DCM to create or modify stacks. • DCM roles can be used in the CI/CD pipeline to build new AMIs, create Amazon ECS tasks, and so on. AMS Advanced Developer mode Topics • Getting started with AMS Advanced Developer mode • Security and compliance in Developer mode • Change management in Developer mode • Provisioning infrastructure in AMS Developer mode • Detective controls in AMS Developer mode • Logging, monitoring, and event management in AMS Developer mode • Incident management in AMS Developer mode • Patch management in AMS Developer mode • Continuity management in AMS Developer mode • Security and access management in AMS Developer mode AWS Managed Services (AMS) Developer mode uses elevated permissions in AMS Advanced Plus and Premium accounts to provision and update AWS resources outside of the AMS Advanced change management process. AMS Advanced Developer mode does this by leveraging native AWS API calls within the AMS Advanced Virtual Private Cloud (VPC), enabling you to design and implement infrastructure and applications in your managed environment. When using an account that has Developer mode enabled, continuity management, patch management, and change management are provided for resources provisioned through the AMS Advanced change management process or by using an AMS Amazon Machine Image (AMI). However, these AMS management features are not oﬀered for resources provisioned through native AWS APIs. You are responsible for monitoring infrastructure resources that are provisioned outside of the AMS Advanced change management process. Developer mode is compatible with both production Developer mode Version May 08, 2024 163 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information and non-production workloads. With elevated permissions, you have an increased responsibility to ensure adherence to internal controls. Important Resources that you create using Developer mode can be managed by AMS Advanced only if they are created using AMS Advanced change management processes. Developer mode is one of the AMS Advanced modes you can employ. For more information, see Modes overview. Getting started with AMS Advanced Developer mode Learn the various AMS Advanced accounts with AMS Advanced Developer mode and how to successfully implement Developer mode. Topics • Before you begin with AMS Developer mode • Prerequisites for AMS Developer mode • How to implement AMS Advanced Developer mode • AMS Advanced Developer mode permissions Before you begin with AMS Developer mode Before implementing Developer mode, there are a few things you should know. AMS Advanced cannot manage existing stacks or resources in a DevMode account that were created outside of the AMS Advanced change management process through requests for change (RFCs). However, while the account is in DevMode, AMS Advanced continues to manage resources provisioned through the AMS Advanced change management process with RFCs. You cannot start with a DevMode account and later covert it to an AMS Advanced-managed application account. Prerequisites for AMS Developer mode The following are the prerequisites for implementing Developer mode: Getting started with Developer mode Version May 08, 2024 164 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information • You must be an AMS Advanced customer with at least one onboarded AMS Advanced Plus or Premium account. • Any account you use must be an AMS Advanced Plus or Premium account. • Multi-Account Landing Zone (MALZ): You must use the AWSManagedServicesDevelopmentRole predeﬁned AWS Identity and Access Management (IAM) role. You request this role. The next section describes how to acquire Developer mode permissions. • Single-Account Landing Zone (SALZ): You must use the customer_developer_role predeﬁned AWS Identity and Access Management (IAM) role. You request this role. The next section describes how to acquire Developer mode permissions. How to implement AMS Advanced Developer mode You implement Developer mode by requesting that your eligible AMS Advanced account be provisioned with the predeﬁned IAM role: • MALZ: AWSManagedServicesDevelopmentRole • SALZ: customer_developer_role You then assign the role to the relevant users in your federated network. AMS Advanced recommends that you ensure that your use of Developer mode complies with your internal control frameworks and standards as Developer mode creates two vectors of change: AMS Advanced change management for AMS Advanced-managed resources and customer-managed role federation for resources that you, as our customer, manage. While AMS Advanced processes remain compliant with our declarations, customer processes and control frameworks might need to be updated. To implement Developer mode in your AMS Advanced account 1. Conﬁrm the account that you want to use with Developer mode meets the requirements listed in Prerequisites for AMS Developer mode. 2. Submit a request for change (RFC) using the change type (CT) Management \| Managed account \| Developer mode \| Enable (review required). For an example of how to use this CT, see Developer
ams-og-054	ams-og.pdf	54	for AMS Advanced-managed resources and customer-managed role federation for resources that you, as our customer, manage. While AMS Advanced processes remain compliant with our declarations, customer processes and control frameworks might need to be updated. To implement Developer mode in your AMS Advanced account 1. Conﬁrm the account that you want to use with Developer mode meets the requirements listed in Prerequisites for AMS Developer mode. 2. Submit a request for change (RFC) using the change type (CT) Management \| Managed account \| Developer mode \| Enable (review required). For an example of how to use this CT, see Developer Mode \| Enable (Review Required). Getting started with Developer mode Version May 08, 2024 165 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information After the CT is processed, the predeﬁned IAM role, (AWSManagedServicesDevelopmentRole for MALZ, customer_developer_role for SALZ), is provisioned in the requested account. 3. Assign the appropriate role to the users that require Developer mode access using your internal federation process. AMS Advanced recommends that you limit access to prevent unwanted or unapproved provisioning of, or changes to, resources. AMS Advanced Developer mode permissions The predeﬁned role (AWSManagedServicesDevelopmentRole for MALZ, customer_developer_role for SALZ), grants permission to create application infrastructure resources within the AMS Advanced VPC, including IAM roles, while restricting access to shared service components that are operated by AMS Advanced (for example, management hosts, domain controllers, Trend Micro EPS, bastions, and unsupported AWS services). The role also restricts access to the following AWS services: Amazon GuardDuty, AWS Organizations, AWS Directory Service APIs, and AMS Advanced logs. While the role allows you to create additional IAM roles, the same permissions boundaries included in Developer mode access are enforced on any IAM role created by the AWSManagedServicesDevelopmentRole. Security and compliance in Developer mode Security and compliance is a shared responsibility between AMS Advanced and you as our customer. AMS Advanced Developer mode shifts the shared responsibility to you for resources provisioned outside of the change management process or provisioned through change management but updated with Developer mode permissions. For more information about shared responsibility, see AWS Managed Services. Cautions: • DevMode allows you and your authorized team to bypass the deny-by-default principles at the core of AMS security. The advantages, self-service, less time waiting for AMS must be weighed against the disadvantages, anyone can perform unexpected and destructive actions without the knowledge of their security team. Automated change types to enable Dev mode and Direct Security and compliance Version May 08, 2024 166 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Change mode are exposed, and any authorized person in your org can run these CTs and enable these modes. • You are responsible for managing the permissions of CT execution from your user base. • AMS doesn’t manage CT execution permissions Recommendations: • Protect • Customers can prevent access to this CT via permissioning, see Restrict permissions with IAM role policy statements • Prevent access to this CT by implementing a proxy such as an ITSM system • Utilize service control policies (SCPs) that prevent policies and behaviors as needed, see AMS Preventative and Detective Controls Library • Detect • Monitor your RFC’s for these CTs (Enable developer mode ct-1opjmhuddw194 and Direct change mode, Enable ct-3rd4781c2nnhp) being executed and respond accordingly • Review and/or audit your accounts for the presence of the IAM resources to identify those accounts where Developer mode or Direct Change mode have been deployed • Respond • Remove accounts in Developer mode as needed Security in Developer mode AMS Advanced oﬀers additional value with a prescriptive landing zone, a change management system, and access management. When using Developer mode the security value of AMS Advanced is persisted by using the same account conﬁguration of standard AMS Advanced accounts that establishes the baseline AMS Advanced security hardened network. The network is protected by the permissions boundary enforced in the role (AWSManagedServicesDevelopmentRole for MALZ, customer_developer_role for SALZ), which restricts the user from breaking down the parameter protections established when the account is set up. For example, users with the role can access Amazon Route 53 but AMS Advanced internal hosted zone is restricted. The same permissions boundaries are enforced on an IAM role created by the AWSManagedServicesDevelopmentRole, enforcing permissions boundaries on the Security and compliance Version May 08, 2024 167 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information AWSManagedServicesDevelopmentRole that restricts the user from breaking down the parameter protections established when the account is onboarded to AMS Advanced. Compliance in Developer mode Developer mode is compatible with both production and non-production workloads. It's your responsibility to ensure adherence to any compliance standards (for example, PHI, HIPAA, PCI), and to ensure that the use of Developer mode complies with your internal control frameworks and standards. Change management in Developer mode Change management is the process
ams-og-055	ams-og.pdf	55	the AWSManagedServicesDevelopmentRole, enforcing permissions boundaries on the Security and compliance Version May 08, 2024 167 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information AWSManagedServicesDevelopmentRole that restricts the user from breaking down the parameter protections established when the account is onboarded to AMS Advanced. Compliance in Developer mode Developer mode is compatible with both production and non-production workloads. It's your responsibility to ensure adherence to any compliance standards (for example, PHI, HIPAA, PCI), and to ensure that the use of Developer mode complies with your internal control frameworks and standards. Change management in Developer mode Change management is the process the AMS Advanced service uses to implement requests for change. A request for change (RFC) is a request created by either you or AMS Advanced through the AMS Advanced interface to make a change to your managed environment and includes a change type (CT) ID for a particular operation. For more information, see Change management modes. Change management is not enforced in AMS Advanced accounts where Developer mode permissions are granted. Users who have been granted Developer mode permission with the IAM role (AWSManagedServicesDevelopmentRole for MALZ, customer_developer_role for SALZ), can use native AWS API access to provision and make changes to resources in their AMS Advanced accounts. Users who do not have the appropriate role in these accounts must use the AMS Advanced change management process to make changes. Important Resources that you create using Developer mode can be managed by AMS Advanced only if they are created using AMS Advanced change management processes. Requests for changes submitted to AMS Advanced for resources created outside of the AMS Advanced change management process are rejected by AMS Advanced because they must be handled by you. Self-service provisioning services API restrictions All AMS Advanced self-provisioned services are supported with Developer mode. Access to self- provisioned services are subject to the limitations outlined in the respective user guide sections for each. If a self-provisioned service is not available with your Developer mode role, you can request an updated role through the Developer mode change type. Change management Version May 08, 2024 168 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information The following services do not provide full access to service APIs: Self-Provisioned Services Restricted in Developer mode Service Notes Amazon API Gateway All Gateway APIs calls are allowed except Application Auto Scaling SetWebACL . Can only register or deregister scalable targets, and put or delete a scaling policy. AWS CloudFormation Can't access or modify CloudFormation stacks AWS CloudTrail that have a name preﬁxed with mc-. Can't access or modify CloudTrail resources that have a name preﬁxed with ams- and/or mc-. Amazon Cognito (User Pools) Can't associate software tokens. AWS Directory Service Can't create user pools, user import jobs, resource servers, or identity providers. Only the following AWS Directory Service actions are required by Connect and WorkSpaces services. All other Directory Service actions are denied by the Developer mode permission boundary policy: • ds:AuthorizeApplication • ds:CreateAlias • ds:CreateIdentityPoolDirectory • ds:DeleteDirectory • ds:DescribeDirectories • ds:GetAuthorizedApplication Details • ds:ListAuthorizedApplications Change management Version May 08, 2024 169 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Service Notes • ds:UnauthorizeApplication In single-account landing zone accounts, the boundary policy explicitly denies access to the AMS Advanced managed directory used by AMS Advanced for maintaining access to dev- mode enabled accounts. Amazon Elastic Compute Cloud Can't access Amazon EC2 APIs that contain the Amazon EC2 (Reports) string: DhcpOptions , Gateway, Subnet, VPC, and VPN. Can't access or modify Amazon EC2 resources that have a tag preﬁxed with AMS, mc, ManagementHostASG , and/or sentinel. Only view access is granted (cannot modify). Note: Amazon EC2 Reports is moving. The Reports menu item will be removed from the Amazon EC2 console navigation menu. To view your Amazon EC2 usage reports after it has been removed, use the AWS Billing and Cost Management console. Change management Version May 08, 2024 170 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Service Notes AWS Identity and Access Management (IAM) Can't delete existing permission boundaries, or modify IAM user password policies. Can't create or modify IAM resources unless you are using the correct IAM role (AWSManagedServicesDevelopme ntRole for MALZ, customer_developer _role for SALZ)). Can't modify IAM resources that are preﬁxed with: ams, mc, customer_deny_policy , and/or sentinel. When creating a new IAM resource (role, user, or group), the permission boundary (MALZ: AWSManagedServicesDevelopme , SALZ: ntRolePermissionsBoundary ams-app-infra-permissions-b oundary ) must be attached. AWS Key Management Service (AWS KMS) Can't access or modify AMS Advanced- managed KMS keys. AWS Lambda Can't access or modify AWS Lambda functions CloudWatch Logs that are preﬁxed with AMS. Can't access CloudWatch log streams that a name preﬁxed with: mc, aws, lambda, and/or AMS. Amazon Relational Database Service (Amazon RDS) Can't access or modify Amazon Relational Database Service (Amazon RDS) databases
ams-og-056	ams-og.pdf	56	modify IAM resources that are preﬁxed with: ams, mc, customer_deny_policy , and/or sentinel. When creating a new IAM resource (role, user, or group), the permission boundary (MALZ: AWSManagedServicesDevelopme , SALZ: ntRolePermissionsBoundary ams-app-infra-permissions-b oundary ) must be attached. AWS Key Management Service (AWS KMS) Can't access or modify AMS Advanced- managed KMS keys. AWS Lambda Can't access or modify AWS Lambda functions CloudWatch Logs that are preﬁxed with AMS. Can't access CloudWatch log streams that a name preﬁxed with: mc, aws, lambda, and/or AMS. Amazon Relational Database Service (Amazon RDS) Can't access or modify Amazon Relational Database Service (Amazon RDS) databases AWS Resource Groups (DBs) that have a name preﬁxed with: mc-. Can only access Get, List, and Search Resource Group API actions. Change management Version May 08, 2024 171 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Service Amazon Route 53 Amazon S3 Notes Can't access or modify Route53 AMS Advanced-maintained resources. Can't access Amazon S3 buckets that have a name preﬁxed with: ams-*, ams, ms-a, or mc- a. AWS Security Token Service The only security token service API allowed is Amazon SNS DecodeAuthorizationMessage . Can't access SNS topics that have a name preﬁxed with: AMS-, Energon-Topic , or MMS-Topic . AWS Systems Manager Manager (SSM) Can't modify SSM parameters that are AWS Tagging preﬁxed with ams, mc, or svc. Can't use the SSM API SendCommand against Amazon EC2 instances that have a tag preﬁxed with ams or mc. You only have access to AWS Tagging API actions that are preﬁxed with Get. Change management Version May 08, 2024 172 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Service Notes AWS Lake Formation The following AWS Lake Formation API actions are denied: • lakeformation:DescribeResource • lakeformation:GetDataLakeSe ttings • lakeformation:DeregisterRes ource • lakeformation:RegisterResource • lakeformation:UpdateResource • lakeformation:PutDataLakeSe ttings Amazon Elastic Inference You can only call the Elastic Inference API action elastic-inference:Connect This permission is included in the customer_ . sagemaker_admin_policy attached to the customer_sagemaker _admin_role . This action gives you access to the Elastic Inference accelerator. that is No access to any of this services APIs or console. No access to any of this services APIs or console. AWS Shield Amazon Simple Workﬂow Service Provisioning infrastructure in AMS Developer mode Users that don't have the Developer mode IAM role, AWSManagedServicesDevelopmentRole, in accounts where Developer mode is enabled, are required to follow the AMS Advanced change management process that leverages AMS Advanced AMIs. Users with correct role (MALZ: AWSManagedServicesDevelopmentRole, SALZ: customer_developer_role) can use the AMS Advanced change management system and AMS Advanced AMIs but are not required to. Provisioning infrastructure Version May 08, 2024 173 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Note An AWS AMI, that has not been processed through AMS Advanced workload ingestion, or created in an AMS Advanced account, will not include AMS Advanced-required conﬁgurations. Detective controls in AMS Developer mode This section has been redacted because it contains sensitive AMS security-related information. This information is available through the AMS console Documentation. To access AWS Artifact, you can contact your CSDM for instructions or go to Getting Started with AWS Artifact. Logging, monitoring, and event management in AMS Developer mode Logging, monitoring, and event management aren't available for resources provisioned outside of the AMS Advanced change management process, or for resources provisioned through change management and then altered by an account using Developer mode permissions. Incident management in AMS Developer mode No change to incident response times. Incident resolution is a best eﬀort for resources provisioned outside the change management process, or resources provisioned through change management and then altered by an account using Developer mode permissions. Note AMS service level agreement (SLA) does not apply for resources created or updated outside of the AMS change management system (requests for change or RFCs), Developer mode included; therefore, resources updated or created in Developer mode are automatically degraded to a P3 and AMS support is best eﬀort. Patch management in AMS Developer mode Patch management is not available for resources provisioned outside of the AMS Advanced change management process, or for resources provisioned through change management and then altered by an account using Developer mode permissions. Patching times: Detective controls Version May 08, 2024 174 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information • For a critical security update: Within 10 business days of release by the vendor for resources provisioned through change management and then altered by an account using Developer mode permissions. • For an important update: Within 2 months of release by the vendor for resources provisioned through change management and then altered by an account using Developer mode permissions. Continuity management in AMS Developer mode Continuity management is not available for resources provisioned outside of the AMS Advanced change management process, or for resources provisioned through change management and then
ams-og-057	ams-og.pdf	57	AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information • For a critical security update: Within 10 business days of release by the vendor for resources provisioned through change management and then altered by an account using Developer mode permissions. • For an important update: Within 2 months of release by the vendor for resources provisioned through change management and then altered by an account using Developer mode permissions. Continuity management in AMS Developer mode Continuity management is not available for resources provisioned outside of the AMS Advanced change management process, or for resources provisioned through change management and then altered by an account using Developer mode permissions. Environment recovery initiation time can take up to 12 hours for resources provisioned outside of the AMS Advanced change management process, or for resources provisioned through change management and then altered by an account using Developer mode permissions. Security and access management in AMS Developer mode Anti-malware protection is your responsibility for resources provisioned outside of the AMS Advanced change management process, or for resources provisioned through change management and then altered by an account using Developer mode permissions. Access to Amazon Elastic Compute Cloud (Amazon EC2) instances not provisioned through AMS Advanced change management might be controlled by key pairs instead of providing federated access. Self-Service Provisioning mode in AMS AWS Managed Services (AMS) Self-Service Provisioning (SSP) mode provides full access to native AWS service and API capabilities in AMS managed accounts. You access services through standardized, scoped down, AWS Identity and Access Management roles. AMS provides service requests and incident management. Alerting, monitoring, logging, patch, back up, and change management are your responsibility. In many cases, Self-Service Provisioning services (SSPS) are self-managed, or serverless, and don’t require management of certain operational tasks like patching. You beneﬁt from using these services within the environment boundary deﬁned by AMS guardrails and any IAM changes (including service linked roles, service roles, cross-account roles, or policy updates) need to be approved by AMS Operations to maintain the baseline security of Continuity management Version May 08, 2024 175 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information the platform. You can leverage AWS CloudFormation templates to automate deployment of these services, but this isn't supported for all SSP services. Important Use SSP mode in your AWS Managed Services (AMS) accounts to access and employ AWS services, with restrictions as noted. There are some AWS services that you can use without AMS management, in your AMS account. The Self-Service Provisioning mode services, or SSPS for short, how to add them into your AMS account and FAQs for each, are described in the section. Self-service provisioning services are oﬀered as is, and you're responsible for managing them. AMS provides no alerts, monitoring, logging, or patching for the resources associated with those services. AMS provides IAM roles that enable you to use the service in your AMS account safely. AMS SLAs do not apply. 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 and 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. Getting started with SSP mode in AMS Self-service provisioning is one of the AMS modes for multi-account landing zone (MALZ) that you can employ. For more information, see Modes overview. To provide self-service provisioning capabilities, AMS has created elevated IAM roles with permission boundaries to limit unintended changes from direct AWS service access. The roles don't prevent all changes and you must adhere to your internal controls and compliance policies, and validate that all AWS services being used meet the required certiﬁcations. This is the self-service provisioning mode. For details on AWS compliance requirements, see AWS Compliance. To add a self-service provisioning service to your multi-account landing zone Application account, use the Management \| AWS service \| Self-provisioned service \| Add change type (CT), either the review-required CT or automated CT, as instructed for the service. Getting started with SSP mode in AMS Version May 08, 2024 176 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Note To request that AMS provide an additional self-service provisioning service, ﬁle a service request. Use AMS SSP to provision Amazon API Gateway in your AMS account Use AMS Self-Service Provisioning (SSP) mode to access Amazon API Gateway capabilities directly in your AMS managed account. Amazon API Gateway is a fully managed service that makes it easy for developers to create, publish, maintain, monitor, and secure APIs at any scale. Using the AWS Management Console you can create REST and WebSocket APIs that act as a front door for applications to access data, business logic,
ams-og-058	ams-og.pdf	58	AMS Advanced Account Onboarding Information Note To request that AMS provide an additional self-service provisioning service, ﬁle a service request. Use AMS SSP to provision Amazon API Gateway in your AMS account Use AMS Self-Service Provisioning (SSP) mode to access Amazon API Gateway capabilities directly in your AMS managed account. Amazon API Gateway is a fully managed service that makes it easy for developers to create, publish, maintain, monitor, and secure APIs at any scale. Using the AWS Management Console you can create REST and WebSocket APIs that act as a front door for applications to access data, business logic, or functionality from your back-end services, such as workloads running on Amazon Elastic Compute Cloud (Amazon EC2), code running on AWS Lambda, any web application, or real-time communication applications. API Gateway handles all the tasks involved in accepting and processing up-to hundreds of thousands of concurrent API calls, including traﬃc management, authorization and access control, monitoring, and API version management. API Gateway has no minimum fees or startup costs. You pay only for the API calls you receive and the amount of data transferred out and, with the API Gateway tiered pricing model, you can reduce your cost as your API usage scales. To learn more, see Amazon API Gateway. FAQs: API Gateway in AMS Q: How do I request access to Amazon API Gateway in my AMS account? Request access to API Gateway by submitting an RFC with the Management \| AWS service \| Self-provisioned service \| Add (ct-1w8z66n899dct) change type. This RFC provisions the following IAM roles to your account: customer_apigateway_author_role and customer_apigateway_cloudwatch_role. After provisioned in your account, you must onboard the roles in your federation solution. Q: What are the restrictions to using Amazon API Gateway in my AMS account? • API Gateway conﬁguration is limited to resources without AMS- or MC- preﬁxes to prevent any modiﬁcations to AMS infrastructure. • CREATE privileges for VPCLink are disabled in order to prevent unregulated creation of Elastic Load Balancers. If VPCLinks are required, see Application Load Balancer \| Create. Amazon API Gateway Version May 08, 2024 177 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Q: What are the prerequisites or dependencies to using Amazon API Gateway in my AMS account? It depends on the type of API Gateway you want to deploy. It can be a standalone service, but it can also request access to existing services (for instance, network load balancer). Use AMS SSP to provision Alexa for Business in your AMS account Use AMS Self-Service Provisioning (SSP) mode to access Alexa for Business capabilities directly in your AMS managed account. Alexa for Business is a service that enables your organization and employees to use Alexa to get more work done. With Alexa for Business, you can use Alexa as your intelligent assistant to be more productive in meeting rooms, at your desk, and even with the Alexa devices you already use at home or on the go. IT and facilities managers can use Alexa for Business to measure and increase the utilization of the existing meeting rooms in their workplace. To learn more, see Alexa for Business. Alexa for Business in AWS Managed Services FAQs Q: How do I request access to Alexa for Business in my AMS account? Request access by submitting a Management \| AWS service \| Self-provisioned service \| Add (review required) (ct-3qe6io8t6jtny) change type. This RFC provisions the following IAM role to your account: customer_alexa_console_role. A customer_alexa_device_setup_user is also created for the Device Setup Tool provided by Alexa for Business; this Device Setup Tool can then be used to set up your devices. Once provisioned in your account, you must onboard the roles in your federation solution. The Alexa for Business gateway enables you to connect Alexa for Business to your Cisco Webex and Poly Group Series endpoints to control meetings with your voice. The gateway software runs on your on-premises hardware and securely proxies conferencing directives from Alexa for Business to your Cisco endpoint. The gateway needs two pairs of AWS credentials to communicate with Alexa for Business. We provide two limited-access IAM users: customer_alexa_gateway_installer_user and customer_alexa_gateway_execution_user for your Alexa for Business gateways, one for installing the gateway and one for operating the gateway; these can be requested by submitting an RFC with the Management \| Other \| Other change type. Alexa for Business Version May 08, 2024 178 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Note To generate usage reports and send them to Amazon S3, specify the Amazon S3 bucket name in the self-provisioned service RFC. Q: What are the restrictions to using Alexa for Business in my AMS account? There are no restrictions. Full functionality of Alexa for Business is available with the Alexa for Business self-provisioned service role. Q: What are the prerequisites or
ams-og-059	ams-og.pdf	59	for operating the gateway; these can be requested by submitting an RFC with the Management \| Other \| Other change type. Alexa for Business Version May 08, 2024 178 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Note To generate usage reports and send them to Amazon S3, specify the Amazon S3 bucket name in the self-provisioned service RFC. Q: What are the restrictions to using Alexa for Business in my AMS account? There are no restrictions. Full functionality of Alexa for Business is available with the Alexa for Business self-provisioned service role. Q: What are the prerequisites or dependencies to using Alexa for Business in my AMS account? • If you intend to use WPA2 Enterprise Wi-Fi to set up your shared devices, then specify this network security type in the Device Setup Tool, for which an AWS Private Certiﬁcate Authority is required. • AMS only creates secret keys that start with the namespace "A4B". This is restrictive only to this namespace. Q: What Alexa for Business functionality requires separate RFCs? To register an Alexa Voice Service (AVS) device with Alexa for Business, provide access to the Alexa built-in device maker. To do this, an IAM role needs to be created in the Alexa for Business console that can be deployed using the Management \| Other \| Other change type. This allows the AVS device maker to register and manage devices with Alexa for Business on your behalf. Use AMS SSP to provision Amazon AppStream 2.0 in your AMS account Use AMS Self-Service Provisioning (SSP) mode to access Amazon AppStream 2.0 (AppStream 2.0) capabilities directly in your AMS managed account. AppStream 2.0 lets you move your desktop applications to AWS, without rewriting them. You can install your applications on AppStream 2.0, set launch conﬁgurations, and make your applications available to users. AppStream 2.0 oﬀers a wide selection of virtual machine options so that you can select the instance type that best matches your application requirements, and set the auto-scale parameters so that you can easily meet the needs of your end users. AppStream 2.0 enables you to launch applications in your own network, which means your applications can interact with your existing AWS resources. Amazon AppStream 2.0 enables you to quickly and easily install, test, and update your applications using the image builder. Any application that runs on Microsoft Windows Server 2012 R2, Windows Amazon AppStream 2.0 Version May 08, 2024 179 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Server 2016, or Windows Server 2019 is supported, and you don’t need to make any modiﬁcations. When your testing is complete, you can set application launch conﬁgurations, default user settings, and publish your image for users to access. To learn more, see AppStream 2.0. AppStream 2.0 in AWS Managed Services FAQs Q: How do I request access to AppStream 2.0 in my AMS account? Request access to AppStream 2.0 by submitting an RFC with the Management \| AWS service \| Self- provisioned service \| Add (ct-3qe6io8t6jtny) change type. This RFC provisions the following IAM role to your account: customer_appstream_console_role. A customer_appstream_stream_role is also deployed to stream applications that require users to be authenticated using their Active Directory login credentials. Once provisioned in your account, you must onboard the roles in your federation solution. Q: What are the restrictions to using AppStream 2.0 in my AMS account? • The following functionality must be conﬁgured by the AMS Support team, and requires speciﬁc RFCs. Instruction on requesting additional functionality can be found in section 4. • Creating and Streaming from Interface VPC Endpoints. • Support for Amazon S3 endpoints for home folders and application setting persistence on a private network. • Creating and choosing the IAM role that will be available on all ﬂeet streaming instances. • Joining AppStream 2.0 ﬂeets and image builders Microsoft Active Directory domains. • Creating AppStream 2.0 Custom Usage Reports. • Custom branding is currently not supported. Q: What are the prerequisites or dependencies to using AppStream 2.0 in my AMS account? While submitting the RFC to onboard AppStream 2.0, include the Amazon S3 bucket name to be used for the AppStream 2.0 usage report. The bucket name is added to the customer- appstream-usagereports-policy that is created when AppStream 2.0 is onboarded. Q: What AppStream 2.0 functionality requires separate RFCs? Amazon AppStream 2.0 Version May 08, 2024 180 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information • In order to choose an interface VPC endpoint for AppStream 2.0, submit a Management \| Other \| Other \| Update change type RFC to create a VPC endpoint in your account. For steps to create custom endpoints for AppStream 2.0, see Creating and Streaming from Interface VPC Endpoints in the AppStream 2.0 user guide. • Support for Amazon S3 endpoints for home folders and application setting
ams-og-060	ams-og.pdf	60	that is created when AppStream 2.0 is onboarded. Q: What AppStream 2.0 functionality requires separate RFCs? Amazon AppStream 2.0 Version May 08, 2024 180 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information • In order to choose an interface VPC endpoint for AppStream 2.0, submit a Management \| Other \| Other \| Update change type RFC to create a VPC endpoint in your account. For steps to create custom endpoints for AppStream 2.0, see Creating and Streaming from Interface VPC Endpoints in the AppStream 2.0 user guide. • Support for Amazon S3 endpoints for home folders and application setting persistence on a private network can be conﬁgured by requesting Amazon S3 VPC endpoints with a Management \| Other \| Other \| Create change type RFC. The RFC must include the target Amazon S3 bucket hosting the home folder contents, or application settings Amazon S3 buckets, respectively. This RFC will provide AppStream 2.0 the permissions it needs to access Amazon S3 VPC endpoints. For steps to create custom endpoints for streams, see Using Amazon S3 VPC Endpoints for Home Folders and Application Settings Persistence in the AppStream 2.0 user guide. • In order to create and choose an IAM role that will be available on all ﬂeet streaming instances, submit a Management \| Other \| Other \| Create change type RFC requesting the IAM role with the required policy. The IAM role name should always start with preﬁx : "customer_appstream". • Amazon AppStream 2.0 ﬂeets and image builders can be joined to domains in Microsoft Active Directory by submitting a Management \| Other \| Other \| Update change type RFC for the Service Account creation in Active Directory (AD). Minimal permissions required to join Microsoft Active Directory are deﬁned in the AppStream 2.0 documentation at Granting Permissions to Create and Manage Active Directory Computer Objects. • In order to create custom AppStream 2.0 Usage Reports, submit a Management \| Other \| Other \| Create change type RFC requesting following: • "AppStreamUsageReports" CFN stack creation • "customer_appstream_usagereports_role" be provisioned in the account • Also, provide the following details: • Provide CRON expression to schedule Crawler run. By default it is 23:00 UTC everyday. • Amazon S3 bucket ARN to be used for Athena query results. This bucket should have preﬁx: aws-athena-query-results • Amazon S3 bucket ARN for AppStream 2.0 Usage Reports Logs. After the role is provisioned, onboard the role into your federation solution and login, then access AWS GlueAWS Glue and Athena for generating custom reports using the usage report role. For details about using AppStream 2.0 Usage Reports see Create Custom Reports and Analyze AppStream 2.0 Usage Data, in the AppStream 2.0 documentation. Amazon AppStream 2.0 Version May 08, 2024 181 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Use AMS SSP to provision Amazon Athena in your AMS account Use AMS Self-Service Provisioning (SSP) mode to access Amazon Athena (Athena) capabilities directly in your AMS managed account. Athena is an interactive query service that helps you to analyze data in Amazon S3 using standard SQL. Athena is serverless, so there is no infrastructure to manage, and you pay only for the queries that you run. You point to your data in Amazon S3, deﬁne the schema, and start querying using standard SQL. Most results are delivered within seconds. With Athena, there’s no need for complex exact-transform-load (ETL) jobs to prepare your data for analysis. This makes it straight-forward for anyone with SQL skills to quickly analyze large- scale datasets. To learn more, see Amazon Athena. FAQs: Athena in AMS Q: How do I request access to Amazon Athena in my AMS account? Request access to Athena by submitting an RFC with the Management \| AWS service \| Self- provisioned service \| Add (ct-1w8z66n899dct) change type. This RFC provisions the following IAM role to your account: customer_athena_console_role. After it's provisioned in your account, you must onboard the role in your federation solution. Q: What are the restrictions to using Amazon Athena in my AMS account? There are no restrictions. Full functionality of Amazon Athena is available in your AMS account. Q: What are the prerequisites or dependencies to using Amazon Athena in my AMS account? Athena has a major dependency on the AWS Glue service, as it uses the data catalog/metastore created with AWS Glue. Therefore, AWS Glue permissions are included in the successful Athena RFC. The role customer_athena_console_role has a prerequisite for an Amazon S3 bucket. To create a new bucket, use the automated CT ct-1a68ck03fn98r (Deployment \| Advanced stack components \| S3 storage \| Create). When you use this automated CT to create an S3 bucket for Athena, the bucket name must begin with preﬁx athena-query-results-*. Use AMS SSP to provision Amazon Bedrock in your AMS account Use AMS Self-Service Provisioning (SSP) mode to access Amazon
ams-og-061	ams-og.pdf	61	major dependency on the AWS Glue service, as it uses the data catalog/metastore created with AWS Glue. Therefore, AWS Glue permissions are included in the successful Athena RFC. The role customer_athena_console_role has a prerequisite for an Amazon S3 bucket. To create a new bucket, use the automated CT ct-1a68ck03fn98r (Deployment \| Advanced stack components \| S3 storage \| Create). When you use this automated CT to create an S3 bucket for Athena, the bucket name must begin with preﬁx athena-query-results-*. Use AMS SSP to provision Amazon Bedrock in your AMS account Use AMS Self-Service Provisioning (SSP) mode to access Amazon Bedrock capabilities directly in your AMS managed account. Amazon Bedrock is a fully managed service that makes high- Amazon Athena Version May 08, 2024 182 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information performing foundation models (FMs) from leading AI startups and AWS available for your use through a uniﬁed API. You can choose from a wide range of foundation models to ﬁnd the model that is best suited for your use case. Amazon Bedrock also oﬀers a broad set of capabilities to build generative AI applications with security, privacy, and responsible AI. Using Amazon Bedrock, you can easily experiment with and evaluate top foundation models for your use cases, privately customize them with your data using techniques such as ﬁne-tuning and Retrieval Augmented Generation (RAG), and build agents that execute tasks using your enterprise systems and data sources. With Amazon Bedrock's serverless experience, you can get started quickly, privately customize foundation models with your own data, and easily and securely integrate and deploy them into your applications using AWS tools without having to manage any infrastructure. For more information, see Amazon Bedrock. FAQs: Amazon Bedrock in AMS Q: How do I request access to Amazon Bedrock in my AMS account? To request access to Amazon Bedrock submit an RFC with the Management \| AWS service \| Self- provisioned service \| Add (review required) (ct-3qe6io8t6jtny) change type. This RFC provisions the following IAM role to your account: customer_bedrock_console_role. After it's provisioned in your account, you must onboard the role in your federation solution. Q: What are the restrictions to using Amazon Bedrock in my AMS account? • Amazon Bedrock knowledge bases aren't supported by default as part of the SSPS role due to its dependency on Amazon OpenSearch Service Serverless which is not currently supported on AMS. • Bedrock Studio isn't supported due to its dependency on unsupported services such as Amazon DataZone. Q: What are the prerequisites or dependencies to using Amazon Bedrock in my AMS account? • Third-party model subscriptions that require AWS Marketplace permissions must be done by the default role (AWSManagedServicesAdminRole on MALZ and Customer_ReadOnly_Role on SALZ). This is because the default role includes AWS Marketplace permissions. • If data encryption is used, then you must provide the AWS KMS key ARN when you request creation of the console role. Also, the Amazon S3 bucket in use must have “bedrock” in its name. Amazon Bedrock Version May 08, 2024 183 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Use AMS SSP to provision Amazon CloudSearch in your AMS account Use AMS Self-Service Provisioning (SSP) mode to access Amazon CloudSearch capabilities directly in your AMS managed account. Amazon CloudSearch is a managed service in the AWS Cloud that you use to cost-eﬀective to set up, manage, and scale a search solution for your website or application. Amazon CloudSearch supports 34 languages and popular search features such as highlighting, autocomplete, and geospatial search. To learn more, see Amazon CloudSearch. Note AWS has closed new customer access to Amazon CloudSearch, eﬀective July 25, 2024. Amazon CloudSearch existing customers can continue to use the service as normal. AWS continues to invest in security, availability, and performance improvements for Amazon CloudSearch, but we do not plan to introduce new features. To understand the diﬀerences between Amazon CloudSearch and Amazon OpenSearch Service, and how you can transition to OpenSearch Service, reach out to your cloud architect (CA) for guidance. For more information on transitioning to OpenSearch Service, see Transition from Amazon CloudSearch to Amazon OpenSearch Service service. Amazon CloudSearch in AWS Managed Services FAQs Q: How do I request access to Amazon CloudSearch in my AMS account? Request access to Amazon CloudSearch by submitting an RFC with the Management \| AWS service \| Self-provisioned service \| Add (ct-1w8z66n899dct) change type. This RFC provisions the following IAM roles to your account: customer_csearch_admin_role and customer_csearch_dev_role. After it's provisioned in your account, you must onboard the role in your federation solution. Q: What are the restrictions to using Amazon CloudSearch in my AMS account? Full functionality of Amazon CloudSearch is available in your AMS account. All AMS-supported database solutions are currently supported on Amazon CloudSearch. Note that, currently, DynamoDB is the only managed
ams-og-062	ams-og.pdf	62	to Amazon CloudSearch in my AMS account? Request access to Amazon CloudSearch by submitting an RFC with the Management \| AWS service \| Self-provisioned service \| Add (ct-1w8z66n899dct) change type. This RFC provisions the following IAM roles to your account: customer_csearch_admin_role and customer_csearch_dev_role. After it's provisioned in your account, you must onboard the role in your federation solution. Q: What are the restrictions to using Amazon CloudSearch in my AMS account? Full functionality of Amazon CloudSearch is available in your AMS account. All AMS-supported database solutions are currently supported on Amazon CloudSearch. Note that, currently, DynamoDB is the only managed AWS database solution that can’t be indexed. Q: What are the prerequisites or dependencies to using Amazon CloudSearch in my AMS account? Amazon CloudSearch Version May 08, 2024 184 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Amazon CloudSearch depends on Amazon S3 working with Identity Providers to automatically analyze input data and determine the table ﬁelds. Access to Amazon S3 is not provided with this RFC, and must be requested separately in a service request. Use AMS SSP to provision Amazon CloudWatch Synthetics in your AMS account Use AMS Self-Service Provisioning (SSP) mode to access Amazon CloudWatch Synthetics capabilities directly in your AMS managed account. You can use Amazon CloudWatch Synthetics to create 'canaries' to monitor your endpoints and APIs. Canaries are conﬁgurable scripts, written in Node.js or Python, that run on a schedule. They create Lambda functions in your account that use Node.js or Python as a framework. Canaries work over both HTTP and HTTPS protocols. Canaries check the availability and latency of your endpoints and can store load time data and UI screenshots. They monitor your REST APIs, URLs, and website content, and they can check for unauthorized changes from phishing, code injection and cross-site scripting. Canaries follow the same routes and perform the same actions as a customer, making it possible for you to continually verify your customer experience even when you don't have any customer traﬃc on your applications. By using canaries, you can discover issues before your customers do. To learn more, see Amazon CloudWatch: Using synthetic monitoring. Amazon CloudWatch Synthetics in AWS Managed Services FAQs Q: How do I request access to Amazon CloudWatch Synthetics in my AMS account? Request access to Amazon CloudWatch Synthetics by submitting an RFC with the Management \| AWS service \| Self-provisioned service \| Add (ct-1w8z66n899dct) change type. This RFC provisions the following IAM role to your account: 'customer_cw_synthetics_console_role' and 'customer_cw_synthetics_canary_lambda_role'. Once provisioned in your account, you must onboard the 'customer_cw_synthetics_console_role' role in your federation solution. Q: What are the restrictions to using Amazon CloudWatch Synthetics in my AMS account? There are no restrictions for the use of Amazon CloudWatch Synthetics in your AMS account. Creating roles for canaries outside of the AMS-provided service role 'customer_cw_synthetics_canary_lambda_role' is prohibited. Amazon CloudWatch Synthetics Version May 08, 2024 185 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Q: What are the prerequisites or dependencies to using Amazon CloudWatch Synthetics in my AMS account? Canaries create and use a default Amazon CloudWatch Synthetics S3 bucket: "cw-syn- results-${accountnumber}-${default-region}" Use AMS SSP to provision Amazon Cognito user pools in your AMS account Use AMS Self-Service Provisioning (SSP) mode to access Amazon Cognito user pools capabilities directly in your AMS managed account. Amazon Cognito user pools provide a secure user directory that scales to hundreds of millions of users. As a fully managed service, Amazon Cognito user pools can be set up without any worries about standing up server infrastructure. This service enables you to manage a pool of ﬁnal users that you can use to integrate with your internal applications. This service provides you an alternative to a customized database or a directory of ﬁnal users for web or mobile applications. At the same time, Amazon Cognito user pools provides the full set of functionalities of a directory service like passwords policies, multi factor authentication, password recovery and self-sign up into services. It also allows the application to federate the access in other popular public services like OpenID, Facebook, Amazon or Google. Amazon Cognito is divided into two main products. Amazon Cognito user pools and Amazon Cognito Identity Provider. This section focuses on Amazon Cognito user pools, which provide access to other AWS services like Amazon S3 or DynamoDB. The service allows you to use Amazon Cognito user pools, or a third party identity provider, to provide access to AWS services. It also provides access to AWS services using anonymous guest access. Because of the powerful nature of Amazon Cognito user pools, it would be managed manually on a case-by-case basis as an operation manual service, in order to avoid potential security breaks into the account. To learn more, see Amazon Cognito User Pools. Amazon Cognito user pools in AWS Managed Services
ams-og-063	ams-og.pdf	63	on Amazon Cognito user pools, which provide access to other AWS services like Amazon S3 or DynamoDB. The service allows you to use Amazon Cognito user pools, or a third party identity provider, to provide access to AWS services. It also provides access to AWS services using anonymous guest access. Because of the powerful nature of Amazon Cognito user pools, it would be managed manually on a case-by-case basis as an operation manual service, in order to avoid potential security breaks into the account. To learn more, see Amazon Cognito User Pools. Amazon Cognito user pools in AWS Managed Services FAQs Common questions and answers: Q: How do I request access to Amazon Cognito user pools in my AMS account? Implementation of Amazon Cognito user pools in AMS is a 2 step process: 1. Submit a Management \| Other \| Other \| Create (ct-1e1xtak34nx76) change type and request the creation of the Amazon Cognito user pools in your AMS Account. Include the following information: Amazon Cognito Version May 08, 2024 186 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information • AWS Region. • Name for the Cognito User Pool. • If the you want to use the Amazon Simple Email Service (Amazon SES) to send messages and notiﬁcations instead of the default internal Cognito mail service, then the customer should provide an already validated email address for the Amazon SES Service in the account. This address will be used for the "From" and "REPLY-TO" ﬁelds of the message. They must also indicate the Region where Amazon SES was activated (us-east-1, eu-west-1 or us-west-2). • If the you want to use SMS messages for one-time passwords and veriﬁcation, then the customer should indicate so. 2. Request user access by submitting a Management \| AWS service \| Self-provisioned service \| Add change type (ct-1w8z66n899dct). This RFC provisions the following IAM roles to your account: customer_cognito_admin_role and customer_cognito_importjob_role. After it's provisioned in your account, you must onboard the role in your federation solution. These roles allow you to manage the Amazon Cognito user pools, manage your users and groups in the pool, create importjobs for users, modify the notiﬁcation and subscription messages, associate applications to the user pool, self-manage adding federation services to the pool, and delete already created pools. Q: What are the restrictions to using Amazon Cognito user pools in my AMS account? You won't be able to create the Amazon Cognito user pools. That action requires the creation of IAM roles to leverage services used by Amazon Cognito, like Amazon SES and Amazon Simple Notiﬁcation Service (Amazon SNS). Q: What are the prerequisites or dependencies to using Amazon Cognito user pools in my AMS account? If you want to use Amazon SES to send messages and notiﬁcations by email to your user pools, they should already activate the Amazon SES service in the account, and already validate the email address that should be used in the "FROM" and "REPLY-TO" ﬁelds of the sent emails. For more information about validating email address using Amazon SES, see Verifying Email Addresses in Amazon SES. Use AMS SSP to provision Amazon Comprehend in your AMS account Use AMS Self-Service Provisioning (SSP) mode to access Amazon Comprehend capabilities directly in your AMS managed account. Amazon Comprehend is a natural language processing (NLP) Amazon Comprehend Version May 08, 2024 187 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information service that uses machine learning to ﬁnd insights and relationships in text, no machine learning experience is required. Amazon Comprehend uses machine learning to help you uncover the insights and relationships in your unstructured data. The service identiﬁes the language of the text; extracts key phrases, places, people, brands, or events; understands how positive or negative the text is; analyzes text using tokenization and parts of speech; and automatically organizes a collection of text ﬁles by topic. You can also use AutoML capabilities in Amazon Comprehend to build a custom set of entities or text classiﬁcation models that are tailored uniquely to your organization’s needs. To learn more, see Amazon Comprehend. Amazon Comprehend in AWS Managed Services FAQs Q: How do I request access to Amazon Comprehend in my AMS account? Amazon Comprehend console and data access roles can be requested through the submission of two AMS Service RFCs: Request access by submitting a Management \| AWS service \| Self-provisioned service \| Add (review required) (ct-3qe6io8t6jtny) change type. This RFC provisions the following IAM role to your account: customer_comprehend_console_role. After it's provisioned in your account, you must onboard the role in your federation solution. Q: What are the restrictions to using Amazon Comprehend in my AMS account? Create New IAM Role functionality through the Amazon Comprehend console is restricted. Otherwise, full functionality of Amazon Comprehend is available in your AMS account. Q: What are the prerequisites
ams-og-064	ams-og.pdf	64	access roles can be requested through the submission of two AMS Service RFCs: Request access by submitting a Management \| AWS service \| Self-provisioned service \| Add (review required) (ct-3qe6io8t6jtny) change type. This RFC provisions the following IAM role to your account: customer_comprehend_console_role. After it's provisioned in your account, you must onboard the role in your federation solution. Q: What are the restrictions to using Amazon Comprehend in my AMS account? Create New IAM Role functionality through the Amazon Comprehend console is restricted. Otherwise, full functionality of Amazon Comprehend is available in your AMS account. Q: What are the prerequisites or dependencies to using Amazon Comprehend in my AMS account? Amazon S3 and AWS Key Management Service (AWS KMS) are required in order to use Amazon Comprehend, if Amazon S3 buckets are encrypted with AWS KMS keys. Use AMS SSP to provision Amazon Connect in your AMS account Use AMS Self-Service Provisioning (SSP) mode to access Amazon Connect capabilities directly in your AMS managed account. Amazon Connect is an omnichannel cloud contact center that helps companies provide superior customer service at a lower cost. Amazon Connect provides a seamless experience across voice and chat for customers and agents. This includes one set of tools for skills- based routing, powerful real-time and historical analytics, and easy-to-use intuitive management tools – all with pay-as-you-go pricing. Amazon Connect Version May 08, 2024 188 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information You can create one or more instances of the virtual contact center instances in either AMS multi- account landing zone or single-account landing zone accounts. You can use existing SAML 2.0 identity providers for agent access or use Amazon Connect native support for user life cycle management. Additionally, you can claim toll free/direct dial phone numbers for each Amazon Connect instance from the Amazon Connect console. You can create rich contact ﬂows to achieve the desired customer experience and routing using an easy-to-use graphical user interface. The contact ﬂows can leverage AWS Lambda functions to integrate with on-premises data stores and API’s. You can also enable data streaming using Kinesis Streams and Firehose. The call recordings, chat transcripts, and reports, are stored in an Amazon S3 bucket encrypted using an AWS KMS key. The contact ﬂow logs can be saved to CloudWatch log groups. To learn more, see Amazon Connect. Amazon Connect in AWS Managed Services FAQs Q: How do I request access to Amazon Connect in my AMS account? Request access by submitting a Management \| AWS service \| Self-provisioned service \| Add (review required) (ct-3qe6io8t6jtny) change type. This RFC provisions the following IAM roles to your account: customer_connect_console_role and customer_connect_user_role. After it's provisioned in your account, you must onboard the role in your federation solution. Q: What are the restrictions to using Amazon Connect in my AMS account? There are no restrictions. Full functionality of Amazon Connect is available in your AMS account. Q: What are the prerequisites or dependencies to using Amazon Connect in my AMS account? • You must create an AWS KMS Key and an Amazon S3 bucket using standard AMS RFCs; the Amazon S3 bucket is required for storing call recordings and chat transcripts. • If you want to integrate with Active Directory (AD), an AD Connector is required for integration between AMS-hosted Amazon Connect instances and your on-premises directory services. AD Connector can be conﬁgured in your account by requesting a 'Management \| Other \| Other' RFC. • You can enable the following optional self-provisioned services based on your contact ﬂow requirements. Amazon Connect Version May 08, 2024 189 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information • AWS Lambda: You can use Lambda functions to extend the contact ﬂows to leverage existing on-premises data stores or APIs. You can use the Lambda self-provisioned service to create the Lambda functions. • Amazon Kinesis Data Streams: You can create data streams to enable Data streaming to external applications. You can stream contact trace records or Agent Events. • Amazon Kinesis Data Firehose: You can create Data Firehose to stream high volume contact trace records to external applications. • Amazon Lex: You can leverage Amazon Lex Chatbots to create smart contact ﬂows leveraging Amazon Alexa services for rich customer experience and automation. • Q: How do I request to add list of countries for outbound or inbound calls? To add a list of countries for outbound or inbound calls, submit a service request to AMS. Use AMS SSP to provision Amazon Data Firehose in your AMS account Use AMS Self-Service Provisioning (SSP) mode to access Amazon Data Firehose capabilities directly in your AMS managed account. Firehose is the easiest way to reliably load streaming data into data lakes, data stores, and analytics tools. It can capture, transform, and load streaming data into Amazon S3, Amazon
ams-og-065	ams-og.pdf	65	services for rich customer experience and automation. • Q: How do I request to add list of countries for outbound or inbound calls? To add a list of countries for outbound or inbound calls, submit a service request to AMS. Use AMS SSP to provision Amazon Data Firehose in your AMS account Use AMS Self-Service Provisioning (SSP) mode to access Amazon Data Firehose capabilities directly in your AMS managed account. Firehose is the easiest way to reliably load streaming data into data lakes, data stores, and analytics tools. It can capture, transform, and load streaming data into Amazon S3, Amazon Redshift, Amazon OpenSearch Service, and Splunk, enabling near real-time analytics with existing business intelligence tools and dashboards you’re already using today. It is a fully managed service that automatically scales to match the throughput of your data and requires no ongoing administration. It can also batch, compress, transform, and encrypt the data before loading it, minimizing the amount of storage used at the destination and increasing security. To learn more, see What Is Amazon Data Firehose? Firehose in AWS Managed Services FAQs Common questions and answers: Q: How do I request access to Amazon Data Firehose in my AMS account? Request access by submitting a Management \| AWS service \| Self-provisioned service \| Add (review required) (ct-3qe6io8t6jtny) change type. This RFC provisions the following IAM role to your account: customer_kinesis_firehose_user_role. After it's provisioned in your account, you must onboard the role in your federation solution. Q: What are the restrictions to using Firehose in my AMS account? Amazon Data Firehose Version May 08, 2024 190 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information There are no restrictions. Full functionality of Amazon Data Firehose is available in your AMS account. Q: What are the prerequisites or dependencies to using Firehose in my AMS account? New service-linked IAM roles must be requested for each delivery stream. You can also re-use a single service-linked role for all streams by updating the role policy with the required resource permissions (including S3 buckets/ KMS Keys / Lambda Functions / Kinesis streams). After you have submitted the RFC to add Firehose, an AMS Operations engineer will reach out to you through a Service Request for the ARNs of resources that you would like to connect with Data Firehose (for example, AWS KMS, S3, Lambda, and Kinesis Streams). Use AMS SSP to provision Amazon DevOps Guru in your AMS account Use AMS Self-Service Provisioning (SSP) mode to access Amazon DevOps Guru capabilities directly in your AMS managed account. Amazon DevOps Guru is a fully managed operations service that makes it easy for developers and operators to improve the performance and availability of their applications. DevOps Guru lets you oﬄoad the administrative tasks associated with identifying operational issues so that you can quickly implement recommendations to improve your application. DevOps Guru creates reactive insights you can use to improve your application now. It also creates proactive insights to help you avoid operational issues that might aﬀect your application in the future. DevOps Guru applies machine learning to analyze your operational data and application metrics and events to identify behaviors that deviate from normal operating patterns. You are notiﬁed when DevOps Guru detects an operational issue or risk. For each issue, DevOps Guru presents intelligent recommendations to address current and predicted future operational issues. To learn more, see What is Amazon DevOps Guru. Amazon DevOps Guru in AWS Managed Services FAQs Q: How do I request access to Amazon DevOps Guru in my AMS account? To request access, submit a Management \| AWS service \| Self-provisioned service \| Add (review required) (ct-3qe6io8t6jtny) change type. This RFC provisions the following IAM role to your account: customer_devopsguru_role. After it's provisioned in your account, you must onboard the role in your federation solution. Q: What are the restrictions to using Amazon DevOps Guru in my AMS account? Amazon DevOps Guru Version May 08, 2024 191 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information There are no restrictions. Full functionality of Amazon DevOps Guru is available in your AMS account. Q: What are the prerequisites or dependencies to using Amazon DevOps Guru in my AMS account? There are no prerequisites. DevOps Guru leverages the following AWS services: Amazon CloudWatch Logs, RDS Insights, AWS X-Ray, AWS Lambda, and AWS CloudTrail. Use AMS SSP to provision Amazon DocumentDB (with MongoDB compatibility) in your AMS account Use AMS Self-Service Provisioning (SSP) mode to access Amazon DocumentDB (with MongoDB compatibility) capabilities directly in your AMS managed account. Amazon DocumentDB (with MongoDB compatibility) is a fast, scalable, highly available, and fully managed document database service that supports MongoDB workloads. Amazon DocumentDB gives you the performance, scalability, and availability you need when operating mission-critical MongoDB workloads at scale. Amazon DocumentDB implements the Apache 2.0 open source MongoDB
ams-og-066	ams-og.pdf	66	Guru leverages the following AWS services: Amazon CloudWatch Logs, RDS Insights, AWS X-Ray, AWS Lambda, and AWS CloudTrail. Use AMS SSP to provision Amazon DocumentDB (with MongoDB compatibility) in your AMS account Use AMS Self-Service Provisioning (SSP) mode to access Amazon DocumentDB (with MongoDB compatibility) capabilities directly in your AMS managed account. Amazon DocumentDB (with MongoDB compatibility) is a fast, scalable, highly available, and fully managed document database service that supports MongoDB workloads. Amazon DocumentDB gives you the performance, scalability, and availability you need when operating mission-critical MongoDB workloads at scale. Amazon DocumentDB implements the Apache 2.0 open source MongoDB 3.6 API by emulating the responses that a MongoDB client expects from a MongoDB server, allowing you to use your existing MongoDB drivers and tools with Amazon DocumentDB. In Amazon DocumentDB, the storage and compute are decoupled, allowing each to scale independently, and you can increase the read capacity to millions of requests per second by adding up to 15 low latency read replicas, regardless of the size of your data. Amazon DocumentDB is designed for 99.99% availability and replicates six copies of your data across three AWS Availability Zones (AZs). You can use AWS Database Migration Service (DMS) for free (for six months) to migrate your on-premises or Amazon Elastic Compute Cloud (Amazon EC2) MongoDB databases to Amazon DocumentDB with virtually no downtime. To learn more, see Amazon DocumentDB (with MongoDB compatibility). Amazon DocumentDB in AWS Managed Services FAQs Q: How do I request access to Amazon DocumentDB in my AMS account? Amazon DocumentDB console and data access roles can be requested through the submission of two AMS RFCs, console access and data access: Request access to Amazon DocumentDB by submitting an RFC with the Management \| AWS service \| Self-provisioned service \| Add (ct-1w8z66n899dct) change type. This RFC provisions the following IAM role to your account: customer_documentdb_role. After it's provisioned in your account, you must onboard the role in your federation solution. Amazon DocumentDB (with MongoDB compatibility) Version May 08, 2024 192 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Q: What are the restrictions to using Amazon DocumentDB in my AMS account? Amazon DocumentDB requires Amazon RDS-speciﬁc permissions. Because AMS fully manages Amazon RDS, the IAM role for Amazon DocumentDB includes some restrictions to actions on Amazon RDS. The following restrictions apply: • Access to the DeleteDBInstance and DeleteDBCluster APIs have been restricted. To use those deletion APIs, submit an RFC with the Management \| Other \| Other \| Create (ct-1e1xtak34nx76) change type. • You can't add or remove tags from Amazon RDS instances. • You can't make your Amazon DocumentDB instance public. Q: What are the prerequisites or dependencies to using Amazon DocumentDB in my AMS account? Amazon S3 and AWS KMS are required in order to use Amazon DocumentDB, if Amazon S3 buckets are encrypted with AWS KMS keys. Use AMS SSP to provision Amazon DynamoDB in your AMS account Use AMS Self-Service Provisioning (SSP) mode to access Amazon DynamoDB (DynamoDB) capabilities directly in your AMS managed account. Amazon DynamoDB is a key value and document database that delivers single-digit millisecond performance at any scale. It's a fully managed, multi-region, multi-active database with built-in security, backup and restore, and in- memory caching for internet scale applications. To learn more, see Amazon DynamoDB. Amazon DynamoDB Accelerator (DAX) is a write-through caching service that is designed to simplify the process of adding a cache to DynamoDB tables. DAX is intended for applications that require high-performance reads. DynamoDB in AWS Managed Services FAQs Q: How do I request access to DynamoDB and DAX in my AMS account? Request access to DynamoDB and DAX by submitting an RFC with the Management \| AWS service \| Self-provisioned service \| Add (ct-1w8z66n899dct) change type. This RFC provisions the following IAM roles and policies to your account: • DynamoDB role name: customer_dynamodb_role Amazon DynamoDB Version May 08, 2024 193 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information DAX service role name: customer_dax_service_role • DynamoDB policy name: customer_dynamodb_policy DAX service policy: customer_dax_service_policy Once provisioned in your account, you must onboard the customer_dynamodb_role in your federation solution. Q: What are the restrictions to using DynamoDB in my AMS account? All DynamoDB functionality are supported including DynamoDB Accelerator (DAX). When creating alarms for any given table, the alarm name must be preﬁxed with "customer*"; for example, customer-employee-table-high-put-latency. When creating an Amazon SNS topic for DynamoDB, it must be named: dynamodb. To delete the Amazon SNS topic created by DynamoDB, submit a Management \| Other \| Other \| Update change type RFC. Q: What are the prerequisites or dependencies to using DynamoDB in my AMS account? There are no prerequisites or dependencies to use DynamoDB in your AMS account. Use AMS SSP to provision Amazon Elastic Container Registry in your AMS account Use AMS
ams-og-067	ams-og.pdf	67	are supported including DynamoDB Accelerator (DAX). When creating alarms for any given table, the alarm name must be preﬁxed with "customer*"; for example, customer-employee-table-high-put-latency. When creating an Amazon SNS topic for DynamoDB, it must be named: dynamodb. To delete the Amazon SNS topic created by DynamoDB, submit a Management \| Other \| Other \| Update change type RFC. Q: What are the prerequisites or dependencies to using DynamoDB in my AMS account? There are no prerequisites or dependencies to use DynamoDB in your AMS account. Use AMS SSP to provision Amazon Elastic Container Registry in your AMS account Use AMS Self-Service Provisioning (SSP) mode to access Amazon Elastic Container Registry (Amazon ECR) capabilities directly in your AMS managed account. Amazon Elastic Container Registry is a fully-managed Docker container registry that makes it easy for developers to store, manage, and deploy Docker container images. Amazon ECR is integrated with Amazon Elastic Container Service (Amazon ECS), simplifying your development to production workﬂow. Amazon ECR eliminates the need to operate your own container repositories or worry about scaling the underlying infrastructure. Amazon ECS hosts your images in a highly available and scalable architecture, allowing you to reliably deploy containers for your applications. Integration with AWS Identity and Access Management (IAM) provides resource-level control of each repository. With Amazon ECR, there are no upfront fees or commitments. You pay only for the amount of data you store in your repositories and data transferred to the Internet. Amazon Elastic Container Registry Version May 08, 2024 194 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information To learn more, see Amazon Elastic Container Registry. Amazon Elastic Container Registry in AWS Managed Services FAQs Q: How do I request access to Amazon ECR in my AMS account? Request access to Amazon ECR by submitting an RFC with the Management \| AWS service \| Self- provisioned service \| Add (ct-1w8z66n899dct) change type. This RFC provisions the following IAM role to your account: customer_ecr_console_role. Once provisioned in your account, you must onboard the role in your federation solution. Q: What are the restrictions to using Amazon ECR in my AMS account? There are restrictions around AMS namespaces for the use of Amazon ECR in your AMS account. Container images may not be preﬁxed with "AMS-" or "Sentinel-". Q: What are the prerequisites or dependencies to using Amazon ECR in my AMS account? There are no prerequisites or dependencies to use Amazon ECR in your AMS account. Q: Is it possible to have an instance proﬁle with Amazon ECR power user permissions? Yes, use change type Management \| Applications \| IAM instance proﬁle \| Create (ct-0ixp4ch2tiu04). Use AMS SSP to provision EC2 Image Builder in your AMS account Use AMS Self-Service Provisioning (SSP) mode to access EC2 Image Builder capabilities directly in your AMS managed account. EC2 Image Builder is a fully managed AWS service that makes it easier to automate the creation, management, and deployment of customized, secure, and up-to-date "golden" server images that are pre-installed and pre-conﬁgured with software and settings to meet speciﬁc IT standards. You can use the AWS Management Console, AWS CLI, or APIs to create custom images in your AWS account. When you use the AWS Management Console, the Amazon EC2 Image Builder wizard guides you through steps to: • Provide starting artifacts • Add and remove software • Customize settings and scripts • Run selected tests • Distribute images to AWS Regions EC2 Image Builder Version May 08, 2024 195 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information The images you build are created in your account and can be conﬁgured for operating system patches on an ongoing basis. To learn more, see EC2 Image Builder. EC2 Image Builder in AWS Managed Services FAQs Common questions and answers: Q: How do I request access to EC2 Image Builder in my AMS account? Request access by submitting a Management \| AWS service \| Self-provisioned service \| Add (review required) (ct-3qe6io8t6jtny) change type. Through this RFC, the following IAM role will be provisioned in your account: customer_ec2_imagebuilder_role. Once provisioned in your account, you must onboard the role in your federation solution. Q: What are the restrictions for EC2 Image Builder? AMS does not support the use of Service Defaults for infrastructure conﬁguration. You can create a new infrastructure conﬁguration or use an existing one. AMS does not currently support the creation of container recipes. Q: What are the prerequisites or dependencies to enable EC2 Image Builder? • EC2 Image Builder service-linked role: You don't need to manually create a service-linked role. When you create your ﬁrst Image Builder resource in the AWS Management Console, the AWS CLI, or the AWS API, Image Builder creates the service-linked role for you. • Instances used to build images and run tests using Image Builder must have access
ams-og-068	ams-og.pdf	68	the use of Service Defaults for infrastructure conﬁguration. You can create a new infrastructure conﬁguration or use an existing one. AMS does not currently support the creation of container recipes. Q: What are the prerequisites or dependencies to enable EC2 Image Builder? • EC2 Image Builder service-linked role: You don't need to manually create a service-linked role. When you create your ﬁrst Image Builder resource in the AWS Management Console, the AWS CLI, or the AWS API, Image Builder creates the service-linked role for you. • Instances used to build images and run tests using Image Builder must have access to the Systems Manager service. The SSM Agent will be installed on the source image if it is not already present, and it will be removed before the image is created. • AWS IAM: The IAM role that you associate with your instance proﬁle must have permissions to run the build and test components included in your image. The following IAM role policies must be attached to the IAM role that is associated with the instance proﬁles: EC2InstanceProfileForImageBuilder and AmazonSSMManagedInstanceCore. The IAM role name should contain the imagebuilder keyword. • If you conﬁgure logging, the instance proﬁle speciﬁed in your infrastructure conﬁguration must have s3:PutObject permissions for the target bucket (arn:aws:s3:::{bucket-name}/). For example: { "Version": "2012-10-17", EC2 Image Builder Version May 08, 2024 196 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information "Statement": [ { "Effect": "Allow", "Action": [ "s3:PutObject" ], "Resource": "arn:aws:s3:::{bucket-name}/" } ] } • Create an SNS topic with name 'imagebuilder' to receive any alerts and notiﬁcation from EC2 Image Builder. Use AMS SSP to provision Amazon ECS on AWS Fargate in your AMS account Use AMS Self-Service Provisioning (SSP) mode to access Amazon ECS on AWS Fargate capabilities directly in your AMS managed account. AWS Fargate is a technology that you can use with Amazon ECS to run containers (see Containers on AWS) without having to manage servers or clusters of Amazon EC2 instances. With AWS Fargate, you no longer have to provision, conﬁgure, or scale, clusters of virtual machines to run containers. This removes the need to choose server types, decide when to scale your clusters, or optimize cluster packing. To learn more, see Amazon ECS on AWS Fargate. Amazon ECS on Fargate in AWS Managed Services FAQs Q: How do I request access to Amazon ECS on Fargate in my AMS account? Request access to Amazon ECS on Fargate by submitting an RFC with the Management \| AWS service \| Self-provisioned service \| Add (ct-1w8z66n899dct) change type. This RFC provisions the following IAM roles to your account: customer_ecs_fargate_console_role (if no existing IAM role is provided to associate the ECS policy to), customer_ecs_fargate_events_service_role, customer_ecs_task_execution_service_role, customer_ecs_codedeploy_service_role, and AWSServiceRoleForApplicationAutoScaling_ECSService. Once provisioned in your account, you must onboard the roles in your federation solution. Amazon ECS on AWS Fargate Version May 08, 2024 197 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Q: What are the restrictions to using Amazon ECS on Fargate in my AMS account? • Amazon ECS task monitoring and logging are considered your responsibility since container level activities occur above the hypervisor, and logging capabilities are limited by Amazon ECS on Fargate. As a user of Amazon ECS on Fargate, we recommend that you take the necessary steps to enable logging on your Amazon ECS tasks. For more information, see Enabling the awslogs Log Driver for Your Containers. • Security and malware protection at the container level are also considered to be your responsibility. Amazon ECS on Fargate doesn't include Trend Micro or preconﬁgured network security components. • This service is available for both multi-account landing zone and single-account landing zone AMS accounts. • Amazon ECS Service Discovery is restricted by default in the self-provisioned role since elevated permissions are required to create Route 53 private hosted zones. To enable Service Discovery on a service, submit a Management \| Other \| Other \| Update change type. To provide the information required to enable Service Discovery for your Amazon ECS Service, see the Service Discovery manual. • AMS does not currently manage or restrict images used to deploy to containers onto Amazon ECS Fargate. You will be able to deploy images from Amazon ECR, Docker Hub, or any other private image repository. Therefore, we advised that public or any unsecured images not be deployed, since they may result in malicious activity on the account. Q: What are the prerequisites or dependencies to using Amazon ECS on Fargate in my AMS account? • The following are dependencies of Amazon ECS on Fargate; however, no additional action is required to enable these services with your self-provisioned role: • CloudWatch logs • CloudWatch events • CloudWatch alarms • CodeDeploy • App Mesh • Cloud Map • Route 53 Amazon ECS on AWS Fargate Version May 08,
ams-og-069	ams-og.pdf	69	ECR, Docker Hub, or any other private image repository. Therefore, we advised that public or any unsecured images not be deployed, since they may result in malicious activity on the account. Q: What are the prerequisites or dependencies to using Amazon ECS on Fargate in my AMS account? • The following are dependencies of Amazon ECS on Fargate; however, no additional action is required to enable these services with your self-provisioned role: • CloudWatch logs • CloudWatch events • CloudWatch alarms • CodeDeploy • App Mesh • Cloud Map • Route 53 Amazon ECS on AWS Fargate Version May 08, 2024 198 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information • Depending on your use case, the following are resources that Amazon ECS relies on, and may require prior to using Amazon ECS on Fargate in your account: • Security group to be used with the Amazon ECS service. You can use the Deployment \| Advanced stack components \| Security Group \| Create (auto) (ct-3pc215bnwb6p7), or, if your security group requires special rules, use Deployment \| Advanced stack components \| Security Group \| Create (review required) (ct-1oxx2g2d7hc90). Note: The security group your select with Amazon ECS has to be created speciﬁcally for Amazon ECS where the Amazon ECS service or cluster reside. You can learn more in the Security Group section at Setting Up with Amazon ECS and Security in Amazon Elastic Container Service. • Application load balancer (ALB), network load balancer (NLB), classic load balancer (ELB) for load balancing between tasks. • Target Groups for ALBs. • App mesh resources (for instance, Virtual Routers, Virtual Services, Virtual Nodes) to integrate with your Amazon ECS Cluster. • Currently, there is no way for AMS to automatically mitigate risk associated with supporting security groups' permissions when created outside of the standard AMS change types. We recommend that you request a speciﬁc security group for use with your Fargate cluster to limit the possibility of using a security group not designated for the use with Amazon ECS. Use AMS SSP to provision Amazon EKS on AWS Fargate in your AMS account Use AMS Self-Service Provisioning (SSP) mode to access Amazon EKS on AWS Fargate capabilities directly in your AMS managed account. AWS Fargate is a technology that provides on-demand, right-sized compute capacity for containers (to understand containers, see What are Containers?). With AWS Fargate, you no longer have to provision, conﬁgure, or scale groups of virtual machines to run containers. This removes the need to choose server types, decide when to scale your node groups, or optimize cluster packing. Amazon Elastic Kubernetes Service (Amazon EKS) integrates Kubernetes with AWS Fargate by using controllers that are built by AWS using the upstream, extensible model provided by Kubernetes. These controllers run as part of the Amazon EKS-managed Kubernetes control plane and are responsible for scheduling native Kubernetes pods onto Fargate. The Fargate controllers include a new scheduler that runs alongside the default Kubernetes scheduler in addition to several mutating and validating admission controllers. When you start a pod that meets the criteria for Amazon EKS on AWS Fargate Version May 08, 2024 199 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information running on Fargate, the Fargate controllers running in the cluster recognize, update, and schedule the pod onto Fargate. To learn more, see Amazon EKS on AWS Fargate Now Generally Available and Amazon EKS Best Practices Guide for Security (includes "Recommendations" such as "Review and revoke unnecessary anonymous access" and more). Tip AMS has a change type, Deployment \| Advanced stack components \| Identity and Access Managment (IAM) \| Create OpenID Connect provider (ct-30ecvﬁ3tq4k3), that you can use with Amazon EKS. For an example, see Identity and Access Management (IAM) \| Create OpenID Connect Provider. Amazon EKS on AWS Fargate in AWS Managed Services FAQs Q: How do I request access to Amazon EKS on Fargate in my AMS account? Request access by submitting a Management \| AWS service \| Self-provisioned service \| Add (review required) (ct-3qe6io8t6jtny) change type. This RFC provisions the following IAM role to your account. • customer_eks_fargate_console_role. After it's provisioned in your account, you must onboard the role in your federation solution. • These service roles give Amazon EKS on Fargate permission to call other AWS services on your behalf: • customer_eks_pod_execution_role • customer_eks_cluster_service_role Q: What are the restrictions to using Amazon EKS on Fargate in my AMS account? • Creating managed or self-managed EC2 nodegroups is not supported in AMS. If you have a requirement for using EC2 worker nodes, reach out to your AMS Cloud Service Delivery Manager(CSDM) or Cloud Architect(CA). Amazon EKS on AWS Fargate Version May 08, 2024 200 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information • AMS does not include Trend Micro or preconﬁgured network security components for container images. You
ams-og-070	ams-og.pdf	70	EKS on Fargate permission to call other AWS services on your behalf: • customer_eks_pod_execution_role • customer_eks_cluster_service_role Q: What are the restrictions to using Amazon EKS on Fargate in my AMS account? • Creating managed or self-managed EC2 nodegroups is not supported in AMS. If you have a requirement for using EC2 worker nodes, reach out to your AMS Cloud Service Delivery Manager(CSDM) or Cloud Architect(CA). Amazon EKS on AWS Fargate Version May 08, 2024 200 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information • AMS does not include Trend Micro or preconﬁgured network security components for container images. You are expected to manage your own image scanning services to detect malicious container images prior to deployment. • EKSCTL is not supported due to CloudFormation interdependencies. • During cluster creation, you have permissions to disable cluster control plane logging. For more information, see Amazon EKS control plane logging. We advise that you enable all important API, Authentication, and Audit logging on cluster creation. • During cluster creation, cluster endpoint access for Amazon EKS clusters are defaulted to public; for more information, see Amazon EKS cluster endpoint access control. We recommend that Amazon EKS endpoints be set to private. If endpoints are required for public access, then it's a best practice to set them to public only for speciﬁc CIDR ranges. • AMS doesn't have a method to force and restrict images used to deploy to containers on Amazon EKS Fargate. You can deploy images from Amazon ECR, Docker Hub, or any other private image repository. Therefore, there is a risk of deploying a public image that might perform malicious activity on the account. • Deploying EKS clusters through the cloud development kit (CDK) or CloudFormation Ingest isn't supported in AMS. • You must create the required security group using ct-3pc215bnwb6p7 Deployment \| Advanced stack components \| Security group \| Create and reference in the manifest ﬁle for ingress creation. This is because the role customer-eks-alb-ingress-controller-role isn't authorized to create security groups. Q: What are the prerequisites or dependencies to using Amazon EKS on Fargate in my AMS account? In order to use the service, the following dependencies must be conﬁgured: • For authenticating against the service, both KUBECTL and aws-iam-authenticator must be installed; for more information, see Managing cluster authentication. • Kubernetes rely on a concept called "service accounts." In order to utilize the service accounts functionality inside of a kubernetes cluster on EKS, a Management \| Other \| Other \| Update RFC is required with the following inputs: • [Required] Amazon EKS Cluster name • [Required] Amazon EKS Cluster namespace where service account (SA) will be deployed. • [Required] Amazon EKS Cluster SA name. Amazon EKS on AWS Fargate Version May 08, 2024 201 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information • [Required] IAM Policy name and permissions/document to be associated. • [Required] IAM Role name being requested. • [Optional] OpenID Connect provider URL. For more information, see • Enabling IAM roles for service accounts on your cluster • Introducing ﬁne-grained IAM roles for service accounts • We recommend that Conﬁg rules be conﬁgured and monitored for • Public cluster endpoints • Disabled API logging It is your responsibility to monitor and remediate these Conﬁg rules. If you want to deploy an ALB Ingress controller, submit a Management \| Other \| Other Update RFC to provision the necessary IAM role to be used with the ALB Ingress Controller pod. The following inputs are required for creating IAM resources to be associated with ALB Ingress Controller (include these with your RFC): • [Required] Amazon EKS Cluster name • [Optional] OpenID Connect provider URL • [Optional] Amazon EKS Cluster namespace where the application load balancer (ALB) ingress controller service will be deployed. [default: kube-system] • [Optional] Amazon EKS Cluster service account (SA) name. [default: aws-load-balancer- controller] If you want to enable envelope secrets encryption in your cluster (which we recommend), provide the KMS key IDs you intend to use, in the description ﬁeld of the RFC to add the service (Management \| AWS service \| Self-provisioned service \| Add (ct-1w8z66n899dct). To learn more about envelope encryption, see Amazon EKS adds envelope encryption for secrets with AWS KMS. Use AMS SSP to provision Amazon EMR in your AMS account Use AMS Self-Service Provisioning (SSP) mode to access Amazon EMR capabilities directly in your AMS managed account. Amazon EMR is the industry-leading cloud big data platform for processing vast amounts of data using open source tools such as Apache Spark, Apache Hive, Apache HBase, Apache Flink, Apache Hudi, and Presto. With Amazon EMR you can run Petabyte-scale analysis at less than half of the cost of traditional on-premises solutions and over 3x faster than standard Amazon EMR Version May 08, 2024 202 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information
ams-og-071	ams-og.pdf	71	SSP to provision Amazon EMR in your AMS account Use AMS Self-Service Provisioning (SSP) mode to access Amazon EMR capabilities directly in your AMS managed account. Amazon EMR is the industry-leading cloud big data platform for processing vast amounts of data using open source tools such as Apache Spark, Apache Hive, Apache HBase, Apache Flink, Apache Hudi, and Presto. With Amazon EMR you can run Petabyte-scale analysis at less than half of the cost of traditional on-premises solutions and over 3x faster than standard Amazon EMR Version May 08, 2024 202 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Apache Spark. For short-running jobs, you can spin up and spin down clusters and pay per second for the instances used. For long-running workloads, you can create highly available clusters that automatically scale to meet demand. You can create one or more instances of the Amazon EMR clusters in either AMS multi-account landing zone or single-account landing zone accounts to support both transient and persistent Amazon EMR clusters. You can also enable Kerberos authentication to enable authenticate users from on-premises Active Directory domain. You can leverage multiple data stores with the Amazon EMR clusters to support use-case speciﬁc Hadoop tools and libraries. The Amazon EMR clusters can be created using OnDemand or Spot instances and conﬁgure autoscaling to manage capacity and reduce the cost. The cluster log ﬁles can be archived to an Amazon S3 bucket for logging and debugging. You can also access the web interfaces hosted in the Amazon EMR cluster to support hadoop administration requirements or note book experiences for customers. To learn more, see Amazon EMR. Amazon EMR in AWS Managed Services FAQs Q: How do I request access to Amazon EMR in my AMS account? Request access by submitting a Management \| AWS service \| Self-provisioned service \| Add (review required) (ct-3qe6io8t6jtny) change type. This RFC provisions the following IAM roles to your account: • customer_emr_cluster_instance_profile • customer_emr_cluster_autoscaling_role • customer_emr_console_role • customer_emr_cluster_service_role After it's provisioned in your account, you must onboard the customer_emr_console_role in your federation solution. Q: What are the restrictions to using Amazon EMR in my AMS account? While creating Amazon EMR on an EC2 cluster from the AWS console, we advise you to use the Create Cluster – Advanced option. Amazon EMR clusters must be created by adding the tag with Amazon EMR Version May 08, 2024 203 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information the Key "for-use-with-amazon-emr-managed-policies" with Value "true". Select the following conﬁgurations in the Security options: • Select custom roles for your cluster: • EMR Role : customer_emr_cluster_service_role • EC2 Instance Proﬁle : customer_emr_cluster_instance_proﬁle • Auto Scaling Role : customer_emr_cluster_autoscaling_role • EC2 Security groups: • Master : ams-emr-master-security-group • Core & Task : ams-emr-worker-security-group • Service Access : ams-emr-serviceaccess-security-group Q: What are the prerequisites or dependencies to using Amazon EMR in my AMS account? AMS creates default security groups for the Amazon EMR master, worker, and services nodes. The launch templates and security groups to be used with Amazon EMR clusters must have the tag key "for-use-with-amazon-emr-managed-policies" with value "true". The default Amazon EMR cluster instance proﬁle enables access to the resources such as s3 buckets and dynamodb tables with their names containing "emr". You can request additional IAM policies to use any additional resources to be used with Amazon EMR. The following resource ARN's can be used with Amazon EMR jobs using the customer_emr_cluster_instance_proﬁle: • arn:aws:dynamodb:::table/emr • arn:aws:kinesis:::stream/emr • arn:aws:sns:::emrarn:aws:sqs:::emr • arn:aws:sqs:::emr • arn:aws:sqs:::AWS-ElasticMapReduce-* • arn:aws:sdb:::domain:emr • arn:aws:s3:::emr If kerberos authentication is required for the Amazon EMR cluster: • Provide the realm name to be used for each kerberized Amazon EMR cluster and the on-premise Active Directory IP addresses. Amazon EMR Version May 08, 2024 204 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information • Infrastructure requirements: Multi-Account Landing Zone (MALZ): Submit an RFC to create a new Managed application account or a new VPC in an existing application account. Single-Account Landing Zone (SALZ): Submit an RFC to create a new subnet in your VPC. • Conﬁgure the incoming trust for the cluster’s realm on the on-premise Active Directory. • Submit an RFC to conﬁgure DNS zones for the realm in the Managed AD. • Realm conﬁguration: MALZ: Submit a Management \| Other \| Other \| Update (ct-0xdawir96cy7k) RFC to update the VPC DHCP option set to use the realm name for domain name suﬃx. SALZ: Submit a Management \| Other \| Other \| Update (ct-0xdawir96cy7k) RFC to generate a new Amazon EMR AMI to use the speciﬁc realm for domain name suﬃx. To deploy Amazon EMR studio, the role customer_emr_cluster_service_role has a prerequisite for an Amazon Simple Storage Service bucket. To create the bucket, use the automated CT ct-1a68ck03fn98r (Deployment \| Advanced stack components \| S3 storage \| Create). When you use this automated
ams-og-072	ams-og.pdf	72	Realm conﬁguration: MALZ: Submit a Management \| Other \| Other \| Update (ct-0xdawir96cy7k) RFC to update the VPC DHCP option set to use the realm name for domain name suﬃx. SALZ: Submit a Management \| Other \| Other \| Update (ct-0xdawir96cy7k) RFC to generate a new Amazon EMR AMI to use the speciﬁc realm for domain name suﬃx. To deploy Amazon EMR studio, the role customer_emr_cluster_service_role has a prerequisite for an Amazon Simple Storage Service bucket. To create the bucket, use the automated CT ct-1a68ck03fn98r (Deployment \| Advanced stack components \| S3 storage \| Create). When you use this automated CT to create an Amazon S3 bucket for Amazon EMR, the bucket name must begin with the preﬁx customer-emr-*. And, you must create the bucket in the same AWS Region as the Amazon EMR cluster. Use AMS SSP to provision Amazon EventBridge in your AMS account Use AMS Self-Service Provisioning (SSP) mode to access Amazon EventBridge capabilities directly in your AMS managed account. Amazon EventBridge is a serverless event bus service that makes it easy to connect your applications with data from a variety of sources. EventBridge delivers a stream of real-time data from your own applications, Software-as-a-Service (SaaS) applications, and AWS services and routes that data to targets such as AWS Lambda. You can set up routing rules to determine where to send your data to build application architectures that react in real time to all of your data sources. EventBridge allows you to build event driven architectures, which are loosely coupled and distributed. To learn more, see Amazon EventBridge. EventBridge in AWS Managed Services FAQs Q: How do I request access to EventBridge in my AMS account? Amazon EventBridge Version May 08, 2024 205 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Request access to EventBridge by submitting an RFC with the Management \| AWS service \| Self-provisioned service \| Add (ct-1w8z66n899dct) change type. This RFC provisions the following IAM roles to your account: customer_eventbridge_role and customer_eventbridge_scheduler_execution_role. After it's provisioned in your account, you must onboard the role in your federation solution. The execution role, customer_eventbridge_scheduler_execution_role is an IAM role that EventBridge Scheduler assumes to interact with other AWS services on your behalf. The permission policies attached to this role grant EventBridge Scheduler access to invoke targets. Note By default, EventBridge Scheduler uses AWS owned keys for EventBridge to encrypt the data. To use a customer managed key for EventBridge to encrypt the data, submit the RFC using the Management \| AWS service \| Self-provisioned service \| Add (review required) change type (ct-3qe6io8t6jtny) for service provisioning. Q: What are the restrictions to using EventBridge in my AMS account? You must submit AMS RFCs and create the following resources: Service roles to trigger the batch job, SQS queue, CodeBuild, CodePipeline, and SSM commands. Q: What are the prerequisites or dependencies to using EventBridge in my AMS account? You must request an EventBridge service role with an RFC using the Management \| Other \| Other \| Create change type prior to using EventBridge to trigger other AWS resources, such as AWS Batch, Lambda, Amazon SNS, Amazon SQS, or Amazon CloudWatch Logs resources. Specify the services to invoke when requesting your service role. To learn about permissions required to invoke targets, see Using Resource-Based Policies for EventBridge. EventBridge is integrated with AWS CloudTrail, a service that provides a record of actions taken by a user, role, or an AWS service in EventBridge. CloudTrail must be enabled and allowed to store the log ﬁles to S3 buckets. Note: All AMS accounts have CloudTrail enabled, so no action is needed. Q: The role customer_eventbridge_scheduler_execution_role has a prerequisite for an AWS Key Management Service Key (optional, if used for encryption). How do I adopt AWS KMS CMKs in data encryption at rest/transit? Amazon EventBridge Version May 08, 2024 206 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information By default, EventBridge Scheduler encrypts event metadata and message data that it stores under an AWS owned key (encryption at rest). EventBridge Scheduler also encrypts data that passes between EventBridge Scheduler and other services using Transport Layer Security (TLS) (encryption in transit). If your speciﬁc use case requires that you control and audit the encryption keys that protect your data on EventBridge Scheduler, you can use a customer managed key. You must request an RFC using the Management \| AWS service \| Self-provisioned service \| Add (review required) change type prior to using Amazon EventBridge to onboard the AWS KMS permission. Use AMS SSP to provision Amazon Forecast in your AMS account Use AMS Self-Service Provisioning (SSP) mode to access Amazon Forecast (Forecast) capabilities directly in your AMS managed account. Amazon Forecast is a fully managed service that uses machine learning to deliver highly accurate forecasts. Note AWS has closed new customer access to Amazon
ams-og-073	ams-og.pdf	73	keys that protect your data on EventBridge Scheduler, you can use a customer managed key. You must request an RFC using the Management \| AWS service \| Self-provisioned service \| Add (review required) change type prior to using Amazon EventBridge to onboard the AWS KMS permission. Use AMS SSP to provision Amazon Forecast in your AMS account Use AMS Self-Service Provisioning (SSP) mode to access Amazon Forecast (Forecast) capabilities directly in your AMS managed account. Amazon Forecast is a fully managed service that uses machine learning to deliver highly accurate forecasts. Note AWS has closed new customer access to Amazon Forecast, eﬀective July 29, 2024. Amazon Forecast existing customers can continue to use the service as normal. AWS continues to invest in security, availability, and performance improvements for Amazon Forecast, but AWS does not plan to introduce new features. If you want to use Amazon Forecast, reach out to your CSDM so that they can guide you further regarding how to Transition your Amazon Forecast usage to Amazon SageMaker Canvas. Based on the same technology used at Amazon.com, Forecast uses machine learning to combine time series data with additional variables to build forecasts. Forecast requires no machine learning experience to get started. You only need to provide historical data, plus any additional data that you believe may impact your forecasts. For example, the demand for a particular color of a shirt may change with the seasons and store location. This complex relationship is hard to determine on its own, but machine learning is ideally suited to recognize it. Once you provide your data, Amazon Forecast Version May 08, 2024 207 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Forecast will automatically examine it, identify what is meaningful, and produce a forecasting model capable of making predictions that are up to 50% more accurate than looking at time series data alone. To learn more, see Amazon Forecast. Amazon Forecast in AWS Managed Services FAQs Q: How do I request access to Forecast in my AMS account? Request access to AWS Firewall Manager by submitting an RFC with the Management \| AWS service \| Self-provisioned service \| Add (ct-1w8z66n899dct) change type. This RFC provisions the following IAM role to your account: customer_forecast_admin_role. Once provisioned in your account, you must onboard the role in your federation solution. Q: What are the restrictions to using Forecast in my AMS account? The default S3 bucket access only allows you to access buckets with the naming pattern 'customer- forecast-'. If you have your own naming convention for data buckets, discuss bucket naming and related access setup with your Cloud Architect (CA). For example: • You could deﬁne your speciﬁc Amazon Forecast service role with naming like 'AmazonForecast- ExecutionRole-' and associated proper S3 bucket access. See the Service role - AmazonForecast- ExecutionRole-Admin and IAM policy - customer_forecast_default_s3_access_policy, in the IAM console. • You may need to associate related S3 buckets access to IAM federation role. See the IAM policy - customer_forecast_default_s3_access_policy, in the IAM console. Q: What are the prerequisites or dependencies to using Forecast in my AMS account? • Proper Amazon S3 bucket(s) must be created before using Forecast. Especially, the default S3 buckets access is with naming pattern ‘customer-forecast-’ • If you want to use naming patterns on S3 buckets other than 'customer-forecast-', you must create a new service role with S3 access permissions on the buckets: 1. A new service role to be created with naming 'AmazonForecast-ExecutionRole-{suﬃx}'. 2. A new IAM policy to be created which is similar to customer_forecast_default_s3_access_policy and to be associated with the new service role and related federation admin role (e.g. 'customer_forecast_admin_role') Amazon Forecast Version May 08, 2024 208 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Q: How can I enhance data security while using Amazon Forecast? • For data encryption at rest, you can use AWS KMS to provision a customer-managed CMK to protect data storage on Amazon S3 service: • Enable default encryption on the bucket with the provision key and set up bucket policy to accept AWS KMS data encryption while putting data. • Enable the Amazon Forecast service role 'AmazonForecast-ExecutionRole-' and federation admin role (e.g. 'customer_forecast_admin_role') as the AWS KMS key user. • For data encryption in transit, you can set up the HTTPS protocol, which is required while transferring objects on Amazon S3 bucket policy. • Further restrictions on access control, enable a bucket policy for approved access for the Amazon Forecast service role 'AmazonForecast-ExecutionRole-' and admin role (e.g. 'customer_forecast_admin_role'). Q: What are the best practices while using Amazon Forecast? • You should have a good understanding of your data classiﬁcation practices and map out the related data security needs while using S3 buckets with Amazon Forecast. • For Amazon S3 bucket conﬁguration, we strongly advise you to enable HTTPS enforcement in
ams-og-074	ams-og.pdf	74	For data encryption in transit, you can set up the HTTPS protocol, which is required while transferring objects on Amazon S3 bucket policy. • Further restrictions on access control, enable a bucket policy for approved access for the Amazon Forecast service role 'AmazonForecast-ExecutionRole-' and admin role (e.g. 'customer_forecast_admin_role'). Q: What are the best practices while using Amazon Forecast? • You should have a good understanding of your data classiﬁcation practices and map out the related data security needs while using S3 buckets with Amazon Forecast. • For Amazon S3 bucket conﬁguration, we strongly advise you to enable HTTPS enforcement in your S3 bucket policy. • You must be aware of the admin role 'customer_forecast_admin_role' support permissive access (Get/Delete/Put S3 objects) on Amazon S3 buckets with naming of 'customer-forecast-'. NOTE: If you require ﬁne-grained access control for multiple teams, follow these practices: • Deﬁne your team-based access IAM identity (role/user) with least-privilege access to related Amazon S3 buckets. • Create team/project based AWS KMS CMKs grant proper access to corresponding IAM identities. (user access and 'AmazonForecast-ExecutionRole-{team/project}'. • Setup S3 bucket default encryption with the created AWS KMS CMKs. • Enforce S3 API traﬃcs with HTTPS protocol on S3 bucket policy. • Enforce S3 bucket conﬁguration for approved access for related IAM identities (user access and 'AmazonForecast-ExecutionRole-{team/project}' to the buckets. • If you want to use the 'customer_forecast_admin_role' for general purpose, consider points listed previously to protect S3 buckets. Amazon Forecast Version May 08, 2024 209 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Q: Where is compliance information about Amazon Forecast? See the AWS services Compliance Program. Use AMS SSP to provision Amazon FSx in your AMS account Use AMS Self-Service Provisioning (SSP) mode to access Amazon FSx capabilities directly in your AMS managed account. Amazon FSx provides fully managed third-party ﬁle systems. Amazon FSx provides you with the native compatibility of third-party ﬁle systems with feature sets for workloads such as Windows-based storage, high-performance computing (HPC), machine learning, and electronic design automation (EDA). Amazon FSx automates the time-consuming administration tasks such as hardware provisioning, software conﬁguration, patching, and backups. Amazon FSx integrates the ﬁle systems with cloud-native AWS services, making them even more useful for a broader set of workloads. Amazon FSx provides you with two ﬁle systems to choose from: Amazon FSx for Windows File Server for Windows-based applications and Amazon FSx for Lustre for compute-intensive workloads. To learn more, see Amazon FSx. Amazon FSx in AWS Managed Services FAQs Q: How do I request access to Amazon FSx in my AMS account? Request access to Amazon FSx by submitting an RFC with the Management \| AWS service \| Self- provisioned service \| Add (ct-1w8z66n899dct) change type. This RFC provisions the following IAM role to your account: customer_fsx_admin_role. After it's provisioned in your account, you must onboard the role in your federation solution. Q: What are the restrictions to using Amazon FSx in my AMS account? There are no restrictions. Full functionality of the service is available. Q: What are the prerequisites or dependencies to using Amazon FSx in my AMS account? There are no prerequisites. However, for advance conﬁgurations like Multi-AZ, you must install and manage the DFS Replication and DFS Namespaces services. For more information, see Deploying Multi-AZ File Systems. Q: How do I integrate my Amazon FSx ﬁle system with my multi-account landing zone Managed AD? Amazon FSx Version May 08, 2024 210 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information When creating an Amazon FSx ﬁle system, you can specify your MALZ Managed AD as the 'AWS Managed Microsoft Active Directory' for Windows Authentication. For more information see, Using Amazon FSx with AWS Directory Service for Microsoft Active Directory You must also share the Managed AD to the application account ﬁrst. Do this by submitting an RFC with the Management \| Other \| Other \| Create (ct-1e1xtak34nx76) change type. Q: Which users belong in the AWS Delegated FSx Administrators group? Only IT ﬁle server administrators. This group has Full Access privileges across all ﬁle shares. Q: Should I use the default ﬁle share, share, which is created when the FSx system is provisioned? No, we don't recommend using the the default ﬁle share, share, as provisioned. It grants Full Access to Everyone, which which violates the principle of least privilege. Instead, create smaller, custom ﬁle shares that match your business needs. Q: How can I create custom ﬁle shares for speciﬁc organizations in my business? See File Shares for instructions on creating custom ﬁle shares. Restrict access on each ﬁle share using the principle of least privilege. Use AMS SSP to provision Amazon FSx for OpenZFS in your AMS account Use AMS Self-Service Provisioning (SSP) mode to access Amazon FSx for OpenZFS capabilities directly in your AMS managed account. FSx for OpenZFS is
ams-og-075	ams-og.pdf	75	share, as provisioned. It grants Full Access to Everyone, which which violates the principle of least privilege. Instead, create smaller, custom ﬁle shares that match your business needs. Q: How can I create custom ﬁle shares for speciﬁc organizations in my business? See File Shares for instructions on creating custom ﬁle shares. Restrict access on each ﬁle share using the principle of least privilege. Use AMS SSP to provision Amazon FSx for OpenZFS in your AMS account Use AMS Self-Service Provisioning (SSP) mode to access Amazon FSx for OpenZFS capabilities directly in your AMS managed account. FSx for OpenZFS is a fully managed ﬁle storage service that makes it easy to move data residing in on-premises ZFS or other Linux-based ﬁle servers to AWS without changing your application code or how you manage data. It oﬀers highly reliable, scalable, performant, and feature-rich ﬁle storage built on the open-source OpenZFS ﬁle system, providing the familiar features and capabilities of OpenZFS ﬁle systems with the agility, scalability, and simplicity of a fully managed AWS service. For developers building cloud-native applications, it oﬀers simple, high-performance storage with rich capabilities for working with data. FSx for OpenZFS ﬁle systems are broadly accessible from Linux, Windows, and macOS compute instances and containers using the industry-standard NFS protocol (v3, v4.0, v4.1, v4.2). Powered by AWS Graviton processors and the latest AWS disk and networking technologies (including AWS Scalable Reliable Datagram networking and the AWS Nitro system), FSx for OpenZFS delivers up Amazon FSx for OpenZFS Version May 08, 2024 211 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information to 1 million IOPS with latencies of hundreds of microseconds. With complete support for OpenZFS features like instant point-in-time snapshots and data cloning, FSx for OpenZFS makes it easy for you to replace your on-premises ﬁle servers with AWS storage that provides familiar ﬁle system capabilities and eliminates the need to perform lengthy qualiﬁcations and change or re-architect existing applications or tools. And, by combining the power of OpenZFS data management capabilities with the high performance and cost eﬃciency of the latest AWS technologies, FSx for OpenZFS enables you to build and run high-performance, data-intensive applications. As a fully managed service, FSx for OpenZFS makes it easy to launch, run, and scale fully managed ﬁle systems on AWS that replace the ﬁle servers you run on premises while helping to provide better agility and lower costs. With FSx for OpenZFS, you no longer have to worry about setting up and provisioning ﬁle servers and storage volumes, replicating data, installing and patching ﬁle server software, detecting and addressing hardware failures, and manually performing backups. It also provides rich integration with other AWS services, such as AWS Identity and Access Management (IAM), AWS Key Management Service (AWS KMS), Amazon CloudWatch, and AWS CloudTrail. Amazon FSx provides you with two ﬁle systems to choose from: Amazon FSx for Windows File Server for Windows-based applications and Amazon FSx for Lustre for compute-intensive workloads. To learn more, see Amazon FSx. Amazon FSx for OpenZFS in AWS Managed Services FAQs Q: How do I request access to use FSx for OpenZFS in my AMS account? Request access to Amazon FSx OpenZFS by submitting an RFC with the Management \| AWS service \| Self-provisioned service \| Add (ct-1w8z66n899dct) change type. This RFC provisions the following IAM role to your account: customer_fsx_ontap_admin_role. After it's provisioned in your account, you must onboard the role in your federation solution. Q: What are the restrictions to using FSx for OpenZFS in my AMS account? Replacing the security group on the Amazon FSx elastic network interfaces (ENIs) requires you to submit Management \| Other \| Other \| Update RFCs since security groups are a critical perimeter for the AMS environment. That is the only restriction. Q: What are the prerequisites or dependencies to using FSx for OpenZFS in my AMS account? There are no prerequisites. However, you must have Use AMS SSP to provision Amazon FSx in your AMS account installed. Amazon FSx for OpenZFS Version May 08, 2024 212 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Use AMS SSP to provision Amazon FSx for NetApp ONTAP in your AMS account Use AMS Self-Service Provisioning (SSP) mode to access Amazon FSx for NetApp ONTAP capabilities directly in your AMS managed account. Amazon FSx for NetApp ONTAP is a fully managed service that provides highly reliable, scalable, performant, and feature-rich ﬁle storage built on NetApp's popular ONTAP ﬁle system. It provides the familiar features, performance, capabilities, and APIs of NetApp ﬁle systems with the agility, scalability, and simplicity of a fully managed AWS service. Amazon FSx for NetApp ONTAP provides feature-rich, fast, and ﬂexible shared ﬁle storage that’s broadly accessible from Linux, Windows, and macOS compute instances running in AWS or on premises. FSx for ONTAP oﬀers high-performance
ams-og-076	ams-og.pdf	76	to access Amazon FSx for NetApp ONTAP capabilities directly in your AMS managed account. Amazon FSx for NetApp ONTAP is a fully managed service that provides highly reliable, scalable, performant, and feature-rich ﬁle storage built on NetApp's popular ONTAP ﬁle system. It provides the familiar features, performance, capabilities, and APIs of NetApp ﬁle systems with the agility, scalability, and simplicity of a fully managed AWS service. Amazon FSx for NetApp ONTAP provides feature-rich, fast, and ﬂexible shared ﬁle storage that’s broadly accessible from Linux, Windows, and macOS compute instances running in AWS or on premises. FSx for ONTAP oﬀers high-performance SSD storage with sub-millisecond latencies, and makes it quick and easy to manage your data by enabling you to snapshot, clone, and replicate your ﬁles with the click of a button. It also automatically tiers your data to lower-cost, elastic storage, eliminating the need to provision or manage capacity and allowing you to achieve SSD levels of performance for your workload while only paying for SSD storage for a small fraction of your data. It provides highly available and durable storage with fully managed backups and support for cross-region disaster recovery, and supports popular data security and anti-virus applications that make it even easier to protect and secure your data. For customers who use NetApp ONTAP on-premises, FSx for ONTAP is an ideal solution to migrate, back up, or burst your ﬁle-based applications from on-premises to AWS without the need to change your application code or how you manage your data. As a fully managed service, Amazon FSx for NetApp ONTAP makes it simple to launch and scale reliable, performant, and secure shared ﬁle storage in the cloud. With Amazon FSx for NetApp ONTAP, you no longer have to worry about setting up and provisioning ﬁle servers and storage volumes, replicating data, installing and patching ﬁle server software, detecting and addressing hardware failures, managing failover and failback, and manually performing backups. It also provides rich integration with other AWS services, such as AWS Identity and Access Management, Amazon WorkSpaces, AWS Key Management Service, and AWS CloudTrail. Amazon FSx provides you with two ﬁle systems to choose from: Amazon FSx for Windows File Server for Windows-based applications and Amazon FSx for Lustre for compute-intensive workloads. To learn more, see Amazon FSx. Amazon FSx for NetApp ONTAP Version May 08, 2024 213 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Amazon FSx for NetApp ONTAP in AWS Managed Services FAQs Q: How do I request access to Amazon FSx for NetApp ONTAP in my AMS account? Request access to Amazon FSx for NetApp ONTAP by submitting an RFC with the Management \| AWS service \| Self-provisioned service \| Add (ct-1w8z66n899dct) change type. This RFC provisions the following IAM role to your account: customer_fsx_ontap_admin_role. After it's provisioned in your account, you must onboard the role in your federation solution. Q: What are the restrictions to using Amazon FSx for NetApp ONTAP in my AMS account? Replacing the security group on the Amazon FSx for NetApp ONTAP elastic network interfaces (ENIs) requires you to submit Management \| Other \| Other \| Update RFCs since security groups are a critical perimeter for the AMS environment. That is the only restriction. Q: What are the prerequisites or dependencies to using Amazon FSx for NetApp ONTAP in my AMS account? There are no prerequisites. However, you must have Use AMS SSP to provision Amazon FSx in your AMS account installed. Use AMS SSP to provision Amazon Inspector Classic in your AMS account Use AMS Self-Service Provisioning (SSP) mode to access Amazon Inspector Classic capabilities directly in your AMS managed account. Amazon Inspector Classic is an automated security assessment service that helps improve the security and compliance of applications deployed on AWS. Amazon Inspector Classic automatically assesses applications for exposure, vulnerabilities, and deviations from best practices. After performing an assessment, Amazon Inspector Classic produces a detailed list of security ﬁndings prioritized by level of severity. These ﬁndings can be reviewed directly or as part of detailed assessment reports, which are available via the Amazon Inspector Classic console or API. To learn more, see Amazon Inspector Classic. Amazon Inspector in AWS Managed Services FAQs Q: How do I request access to Amazon Inspector Classic in my AMS account? Request access to Amazon Inspector Classic by submitting an RFC with the Management \| AWS service \| Self-provisioned service \| Add (ct-1w8z66n899dct) change type. This RFC provisions the customer_inspector_admin_role IAM role to your account. The role includes the AWS- Amazon Inspector Classic Version May 08, 2024 214 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information managed AmazonInspectorFullAccess policy. Once provisioned in your account, you must onboard the role in your federation solution. Q: What are the restrictions to using Amazon Inspector Classic in my AMS account? There are no
ams-og-077	ams-og.pdf	77	request access to Amazon Inspector Classic in my AMS account? Request access to Amazon Inspector Classic by submitting an RFC with the Management \| AWS service \| Self-provisioned service \| Add (ct-1w8z66n899dct) change type. This RFC provisions the customer_inspector_admin_role IAM role to your account. The role includes the AWS- Amazon Inspector Classic Version May 08, 2024 214 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information managed AmazonInspectorFullAccess policy. Once provisioned in your account, you must onboard the role in your federation solution. Q: What are the restrictions to using Amazon Inspector Classic in my AMS account? There are no restrictions. Full functionality of Amazon Inspector Classic is available in your AMS account. Q: What are the prerequisites or dependencies to using Amazon Inspector Classic in my AMS account? There are no prerequisites or dependencies to use Amazon Inspector Classic in your AMS account. Use the new Amazon Inspector in AMS You can now use the new Amazon Inspector in your AMS account. For Amazon Inspector Classic, the customer-inspector-admin-role-ssm-inspector- agent-policy and AmazonInspectorFullAccess were required. However, there has been an update to the SSPS role customer-inspector-admin-role, which now includes an additional policyAmazonInspector2FullAccess. This new policy allows API permissions for the new version of Amazon Inspector. Use AMS SSP to provision Amazon Kendra in your AMS account Use AMS Self-Service Provisioning (SSP) mode to access Amazon Kendra capabilities directly in your AMS managed account. Amazon Kendra is an intelligent search service that uses natural language processing and advanced machine learning algorithms to return speciﬁc answers to search questions from your data. Unlike traditional keyword-based search, Amazon Kendra uses its semantic and contextual understanding capabilities to determine if a document is relevant to a search query. Amazon Kendra returns speciﬁc answers to questions, so your experience is close to interacting with a human expert. Amazon Kendra is highly scalable, capable of meeting performance demands, is tightly integrated with other AWS services such as Amazon S3 and Amazon Lex, and oﬀers enterprise-grade security. To learn more, see Amazon Kendra;. Amazon Kendra in AWS Managed Services FAQs Q: How do I request access to Amazon Kendra in my AMS account? To request access to Amazon Inspector Classic, submit an RFC with the Management \| AWS service \| Self-provisioned service \| Add (ct-3qe6io8t6jtny) change type. This RFC provisions the Amazon Kendra Version May 08, 2024 215 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information customer_kendra_console_role IAM role to your account. After provisioned in your account, you must onboard the role in your federation solution. Q: What are the restrictions to using Amazon Kendra in my AMS account? There are no restrictions. Full functionality of Amazon Kendra is available in your AMS account. Q: What are the prerequisites or dependencies to using Amazon Kendra in my AMS account? There are no prerequisites or dependencies to get started with Amazon Kendra. However, depending on your speciﬁc use case, you might require access to other AWS services. Use AMS SSP to provision Amazon Kinesis Data Streams in your AMS account Use AMS Self-Service Provisioning (SSP) mode to access Amazon Kinesis Data Streams (KDS) capabilities directly in your AMS managed account. Amazon Kinesis Data Streams is a highly scalable, and durable, real-time data streaming service. KDS can continuously capture gigabytes of data per second from hundreds of thousands of sources such as website clickstreams, database event streams, ﬁnancial transactions, social media feeds, IT logs, and location-tracking events. The data collected is available in milliseconds to enable real-time analytics use cases such as real-time dashboards, real-time anomaly detection, dynamic pricing, and more. To learn more, see Amazon Kinesis Data Streams. Kinesis Data Streams in AWS Managed Services FAQs Common questions and answers: Q: How do I request access to Amazon Kinesis Data Streams in my AMS account? Request access to Amazon Kinesis Data Streams by submitting an RFC with the Management \| AWS service \| Self-provisioned service \| Add change type (ct-1w8z66n899dct). This RFC provisions the following IAM role to your account: customer_kinesis_data_streaming_user_role. After it's provisioned in your account, you must onboard the role in your federation solution. Q: What are the restrictions to using Amazon Kinesis Data Streams in my AMS account? There are no restrictions. Full functionality of Amazon Kinesis Data Streams is available in your AMS account. Q: What are the prerequisites or dependencies to using Amazon Kinesis Data Streams in my AMS account? Amazon Kinesis Data Streams Version May 08, 2024 216 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information There are no prerequisites or dependencies to use Amazon Kinesis Data Streams in your AMS account. Use AMS SSP to provision Amazon Kinesis Video Streams in your AMS account Use AMS Self-Service Provisioning (SSP) mode to access Amazon Kinesis Video Streams (KVS) capabilities directly in your AMS managed account. Amazon Kinesis Video Streams helps you
ams-og-078	ams-og.pdf	78	Amazon Kinesis Data Streams is available in your AMS account. Q: What are the prerequisites or dependencies to using Amazon Kinesis Data Streams in my AMS account? Amazon Kinesis Data Streams Version May 08, 2024 216 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information There are no prerequisites or dependencies to use Amazon Kinesis Data Streams in your AMS account. Use AMS SSP to provision Amazon Kinesis Video Streams in your AMS account Use AMS Self-Service Provisioning (SSP) mode to access Amazon Kinesis Video Streams (KVS) capabilities directly in your AMS managed account. Amazon Kinesis Video Streams helps you to securely stream video from connected devices to AWS for analytics, machine learning (ML), playback, and other processing. Kinesis Video Streams automatically provisions, and elastically scales, all the infrastructure needed to ingest streaming video data from millions of devices. It also durably stores, encrypts, and indexes video data in your streams, and allows you to access your data through easy-to-use APIs. Kinesis Video Streams enables you to playback video for live and on-demand viewing, and quickly build applications that take advantage of computer vision and video analytics through integration with Amazon Rekognition Video, and libraries for ML frameworks such as Apache MxNet, TensorFlow, and OpenCV. To learn more, see Amazon Kinesis Video Streams. Amazon Kinesis Video Streams in AWS Managed Services FAQs Common questions and answers: Q: How do I request access to Amazon Kinesis Video Streams in my AMS account? Request access to Amazon Kinesis Video Streams by submitting an RFC with the Management \| AWS service \| Self-provisioned service \| Add change type (ct-1w8z66n899dct). This RFC provisions the following IAM role to your account: customer_kinesis_video_streaming_user_role. After it's provisioned in your account, you must onboard the role in your federation solution. Q: What are the restrictions to using Amazon Kinesis Video Streams in my AMS account? There are no restrictions. Full functionality of Amazon Kinesis Video Streams is available in your AMS account. Q: What are the prerequisites or dependencies to using Amazon Kinesis Video Streams in my AMS account? There are no prerequisites or dependencies to use Amazon Kinesis Video Streams in your AMS account. Amazon Kinesis Video Streams Version May 08, 2024 217 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Use AMS SSP to provision Amazon Lex in your AMS account Use AMS Self-Service Provisioning (SSP) mode to access Amazon Lex capabilities directly in your AMS managed account. Amazon Lex is a service for building conversational interfaces into any application using voice and text. Amazon Lex provides the advanced deep learning functionalities of automatic speech recognition (ASR) for converting speech to text, and natural language understanding (NLU) to recognize the intent of the text, to enable you to build applications with highly engaging user experiences and lifelike conversational interactions. With Amazon Lex, the same deep learning technologies that power Amazon Alexa are now available to any developer, enabling you to quickly and easily build sophisticated, natural language, conversational bots or chatbots. To learn more, see Amazon Lex. Amazon Lex in AWS Managed Services FAQs Common questions and answers: Q: How do I request access to Amazon Lex in my AMS account? Request access by submitting a Management \| AWS service \| Self-provisioned service \| Add change type (ct-1w8z66n899dct). This RFC provisions the following IAM role to your account: customer_lex_author_role. Once provisioned in your account, you must onboard the role in your federation solution. Q: What are the restrictions to using Amazon Lex in my AMS account? Amazon Lex integration with Lambda is limited to Lambda functions without an "AMS-" preﬁx, in order to prevent any modiﬁcations to AMS infrastructure. Q: What are the prerequisites or dependencies to using Amazon Lex in my AMS account? There are no prerequisites or dependencies to use Amazon Lex in your AMS account. Use AMS SSP to provision Amazon MQ in your AMS account Use AMS Self-Service Provisioning (SSP) mode to access Amazon MQ capabilities directly in your AMS managed account. Amazon MQ is a managed message broker service for Apache ActiveMQ that helps you to set up and operate message brokers in the cloud. Message brokers allow diﬀerent software systems, often using diﬀerent programming languages and on diﬀerent platforms, to communicate and exchange information. Amazon MQ reduces your operational load by managing the provisioning, setup, and maintenance of ActiveMQ, a popular open-source message broker. Amazon Lex Version May 08, 2024 218 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Connecting your current applications to Amazon MQ uses industry standard APIs and protocols for messaging, including JMS, NMS, AMQP, STOMP, MQTT, and WebSocket. Using standards means that, in most cases, there’s no need to rewrite any messaging code when you migrate to AWS. To learn more, see What Is Amazon MQ? Amazon MQ in AWS Managed Services FAQs Common
ams-og-079	ams-og.pdf	79	to communicate and exchange information. Amazon MQ reduces your operational load by managing the provisioning, setup, and maintenance of ActiveMQ, a popular open-source message broker. Amazon Lex Version May 08, 2024 218 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Connecting your current applications to Amazon MQ uses industry standard APIs and protocols for messaging, including JMS, NMS, AMQP, STOMP, MQTT, and WebSocket. Using standards means that, in most cases, there’s no need to rewrite any messaging code when you migrate to AWS. To learn more, see What Is Amazon MQ? Amazon MQ in AWS Managed Services FAQs Common questions and answers: Q: How do I request access to Amazon MQ in my AMS account? Utilization of Amazon MQ in your AMS account is a two-step process: 1. Provision the Amazon MQ Broker. To do this, submit a CFN Template, with the Amazon MQ Broker included, through an RFC with the Deployment \| Ingestion \| Stack from CloudFormation Template \| Create change type (ct-36cn2avfrrj9v), or submit an RFC with the Management \| Other \| Other \| Create change type (ct-1e1xtak34nx76) change type requesting that Amazon MQ Broker be provisioned in your account. 2. Access the Amazon MQ console. After the Amazon MQ Broker is provisioned, obtain access to the Amazon MQ console by submitting an RFC with the Management \| AWS service \| Self- provisioned service \| Add change type (ct-1w8z66n899dct). This RFC provisions the following IAM role to your account: customer_mq_console_role. After the role is provisioned in your account, you must onboard it in your federation solution. Q: What are the restrictions to using Amazon MQ in my AMS account? Full functionality of Amazon MQ is available in your AMS account; however, provisioning Amazon MQ Broker is not available through the policy due to the elevated permission required. See above for details on how to provision Amazon MQ broker in your accounts. Q: What are the prerequisites or dependencies to using Amazon MQ in my AMS account? There are no prerequisites or dependencies to use Amazon MQ in your AMS account. Use AMS SSP to provision Amazon Managed Service for Apache Flink in your AMS account Use AMS Self-Service Provisioning (SSP) mode to access Amazon Managed Service for Apache Flink capabilities directly in your AMS managed account. Managed Service for Apache Flink is the Amazon Managed Service for Apache Flink Version May 08, 2024 219 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information easiest way to analyze streaming data, gain actionable insights, and respond to your business and customer needs in real time. Amazon Managed Service for Apache Flink reduces the complexity of building, managing, and integrating streaming applications with other AWS services. SQL users can easily query streaming data or build entire streaming applications using templates and an interactive SQL editor. Java developers can quickly build sophisticated streaming applications using open source Java libraries and AWS integrations to transform and analyze data in real time. Amazon Managed Service for Apache Flink takes care of everything required to run your real-time applications continuously and scales automatically to match the volume and throughput of your incoming data. With Amazon Managed Service for Apache Flink, you only pay for the resources your streaming applications consume. There is no minimum fee or setup cost. To learn more, see Amazon Managed Service for Apache Flink. Managed Service for Apache Flink in AWS Managed Services FAQs Common questions and answers: Q: How do I request access to Amazon Managed Service for Apache Flink in my AMS account? Request access by submitting a Management \| AWS service \| Self-provisioned service \| Add (review required) (ct-3qe6io8t6jtny) change type. This RFC provisions the following IAM role to your account: customer_kinesis_analytics_application_role. After it's provisioned in your account, you must onboard the role in your federation solution. Q: What are the restrictions to using Amazon Managed Service for Apache Flink in my AMS account? • Conﬁgurations are limited to resources without ‘AMS-‘ or ’MC-’ preﬁxes to prevent any modiﬁcations to AMS infrastructure. • Permission to delete or create new Kinesis Data Streams or Firehose has been removed from the policy. We have another policy that allows that. Q: What are the prerequisites or dependencies to using Amazon Kinesis Data Streams in my AMS account? There are a few dependencies: • Amazon Managed Service for Apache Flink requires that Kinesis Data Streams or Firehose must be created prior to conﬁguring an application with Managed Service for Apache Flink. Amazon Managed Service for Apache Flink Version May 08, 2024 220 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information • The resource-based policy permissions should indicate a particular input data source. Use AMS SSP to provision Amazon Managed Streaming for Apache Kafka in your AMS account Use AMS Self-Service Provisioning (SSP) mode to access Amazon Managed Streaming for Apache
ams-og-080	ams-og.pdf	80	Kinesis Data Streams in my AMS account? There are a few dependencies: • Amazon Managed Service for Apache Flink requires that Kinesis Data Streams or Firehose must be created prior to conﬁguring an application with Managed Service for Apache Flink. Amazon Managed Service for Apache Flink Version May 08, 2024 220 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information • The resource-based policy permissions should indicate a particular input data source. Use AMS SSP to provision Amazon Managed Streaming for Apache Kafka in your AMS account Use AMS Self-Service Provisioning (SSP) mode to access Amazon Managed Streaming for Apache Kafka (Amazon MSK) capabilities directly in your AMS managed account. Amazon Managed Streaming for Apache Kafka is a fully managed AWS streaming data service makes it easy for you to build and run applications that use Apache Kafka to process streaming data without needing to become an expert in operating Apache Kafka clusters. Amazon MSK manages the provisioning, conﬁguration, and maintenance of Apache Kafka clusters and Apache ZooKeeper nodes for you. Amazon MSK also shows key Apache Kafka performance metrics in the AWS Console. Amazon MSK provides multiple levels of security for your Apache Kafka clusters, including VPC network isolation, AWS IAM for control-plane API authorization, encryption at rest, TLS encryption in-transit, TLS based certiﬁcate authentication, SASL/SCRAM authentication secured by AWS Secrets Manager. To learn more, see Amazon MSK. Amazon MSK in AWS Managed Services FAQs Common questions and answers: Q: How do I request access to Amazon MSK in my AMS account? Request access by submitting a Management \| AWS service \| Self-provisioned service \| Add (review required) (ct-3qe6io8t6jtny) change type. This RFC provisions the following IAM policies and role to your account: • customer-msk-admin-policy.json • AmazonMSKFullAccess • customer-msk-admin-role.json Once provisioned in your account you must onboard the role in your federation solution. Q: What are the restrictions to using Amazon MSK? For Amazon MSK to deliver broker logs to the destinations that you conﬁgure, ensure that the AmazonMSKFullAccess policy is attached to your IAM role. So full access permissions are already in place. Amazon Managed Streaming for Apache Kafka Version May 08, 2024 221 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Q: What are the prerequisites or dependencies to using Amazon MSK? Before creating your MSK cluster, you must have a VPC and subnets within that VPC. By default, AMS has this covered as part of default AMS VPC creation. To learn about the limitation of Amazon MSK, refer to Amazon MSK Limits. Use AMS SSP to provision Amazon Managed Service for Prometheus in your AMS account Use AMS Self-Service Provisioning (SSP) mode to access Amazon Managed Service for Prometheus (AMP) capabilities directly in your AMS managed account. Amazon Managed Service for Prometheus is a serverless, Prometheus-compatible monitoring service for container metrics that makes it easier to securely monitor container environments at scale. With Amazon Managed Service for Prometheus, you can use the same open-source Prometheus data model and query language that you use today to monitor the performance of your containerized workloads, and also enjoy improved scalability, availability, and security without having to manage the underlying infrastructure. Amazon Managed Service for Prometheusautomatically scales the ingestion, storage, and querying of operational metrics as workloads scale up and down. It integrates with AWS security services to enable fast and secure access to data. For more information, see What is Amazon Managed Service for Prometheus? Amazon Managed Service for Prometheus in AWS Managed Services FAQs Common questions and answers: Q: How do I request access to Amazon Managed Service for Prometheus in my AMS account? Request access by submitting a Management \| AWS service \| Self-provisioned service \| Add (review required) (ct-3qe6io8t6jtny) change type. This RFC provisions the following IAM role to your account: customer-prometheus-console-role. After it's provisioned in your account, you must onboard the customer-prometheus-console-role role in your federation solution. Q: What are the restrictions to using Amazon Managed Service for Prometheus in my AMS account? All features are supported. Amazon Managed Service for Prometheus Version May 08, 2024 222 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Q: What are the prerequisites or dependencies to using Amazon Managed Service for Prometheus in my AMS account? There are no prerequisites or dependencies to get started with Amazon Managed Service for Prometheus. However, depending on your speciﬁc use case, you might require access to other AWS services. Use AMS SSP to provision Amazon Personalize in your AMS account Use AMS Self-Service Provisioning (SSP) mode to access Amazon Personalize capabilities directly in your AMS managed account. Amazon Personalize is a machine learning service that makes it easy for developers to create individualized recommendations for customers using their applications. Machine learning is being increasingly used to improve customer engagement by powering personalized product and content recommendations, tailored search results,
ams-og-081	ams-og.pdf	81	There are no prerequisites or dependencies to get started with Amazon Managed Service for Prometheus. However, depending on your speciﬁc use case, you might require access to other AWS services. Use AMS SSP to provision Amazon Personalize in your AMS account Use AMS Self-Service Provisioning (SSP) mode to access Amazon Personalize capabilities directly in your AMS managed account. Amazon Personalize is a machine learning service that makes it easy for developers to create individualized recommendations for customers using their applications. Machine learning is being increasingly used to improve customer engagement by powering personalized product and content recommendations, tailored search results, and targeted marketing promotions. However, developing the machine-learning capabilities necessary to produce these sophisticated recommendation systems has been beyond the reach of most organizations today due to the complexity. Amazon Personalize allows developers with no prior machine learning experience to easily build sophisticated personalization capabilities into their applications, using machine learning technology perfected from years of use on Amazon.com. With Amazon Personalize, you provide an activity stream from your application – clicks, page views, signups, purchases, and so forth – as well as an inventory of the items you want to recommend, such as articles, products, videos, or music. You can also choose to provide Amazon Personalize with additional demographic information from your users such as age, or geographic location. Amazon Personalize will process and examine the data, identify what is meaningful, select the right algorithms, and train and optimize a personalization model that is customized for your data. All data analyzed by Amazon Personalize is kept private and secure, and only used for your customized recommendations. You can start serving personalized recommendations via a simple API call. You pay only for what you use, and there are no minimum fees and no upfront commitments. To learn more, see Amazon Personalize. Amazon Personalize in AWS Managed Services FAQs Q: How do I request access to Amazon Personalize in my AMS account? Request access by submitting a Management \| AWS service \| Self-provisioned service \| Add (review required) (ct-3qe6io8t6jtny) change type, and you need to specify which S3 bucket contains the data to be used by AWS personalize to generate the recommendations. This RFC Amazon Personalize Version May 08, 2024 223 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information provisions the following IAM roles to your account: customer_personalize_console_role and customer_personalize_service_role. • Once the customer_personalize_console_role is provisioned in your account, you must onboard the role in your federation solution. You can also attach the customer_personalize_console_policy to another existing role other than Customer_ReadOnly_Role. • After the customer_personalize_service_role is provided to your account, then you can refer its ARN when creating a new dataset group. At this time, AMS Operations will also deploy this service role in your account: aws_code_pipeline_service_role_policy. Q: What are the restrictions to using Amazon Personalize in my AMS account? Amazon Personalize conﬁguration is limited to resources without 'ams-' or 'mc-' preﬁxes, to prevent any modiﬁcations to AMS infrastructure. Q: What are the prerequisites or dependencies to using Amazon Personalize in my AMS account? • If the S3 bucket where data is stored is encrypted, the KMS key ID must be provided, so we can allow the role used by Amazon Personalize to decrypt the bucket. Amazon Personalize does not support the default KMS S3 key. If required to use KMS, create a custom key and add the following policy to it by opening an RFC with change type KMS Key \| Create (Review Required): { "Version": "2012-10-17", "Id": "key-consolepolicy-3", "Statement": [ { "Sid": "Enable IAM User Permissions", "Effect": "Allow", "Principal": { "Service": "personalize.amazonaws.com" }, "Action": "kms:", "Resource": "" Amazon Personalize Version May 08, 2024 224 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information } ] } • An S3 bucket must be created with the following bucket policy. Do this by submitting an RFC with change type S3 Storage \| Create Policy. This policy allows Amazon Personalize to access data; that bucket will contain the data to be used by Amazon Personalize. { "Version": "2012-10-17", "Id": "PersonalizeS3BucketAccessPolicy", "Statement": [ { "Sid": "PersonalizeS3BucketAccessPolicy", "Effect": "Allow", "Principal": { "Service": "personalize.amazonaws.com" }, "Action": [ "s3:GetObject", "s3:ListBucket" ], "Resource": [ "arn:aws:s3:::bucket-name", "arn:aws:s3:::bucket-name/*" ] } ] } Use AMS SSP to provision Amazon QuickSight in your AMS account Use AMS Self-Service Provisioning (SSP) mode to access QuickSight capabilities directly in your AMS managed account. QuickSight is a fast, cloud-powered business intelligence service that delivers insights to everyone in your organization. As a fully managed service, QuickSight lets you easily create and publish interactive dashboards that include machine learning (ML) insights. To learn more, see Amazon QuickSight. QuickSight in AWS Managed Services FAQs Common questions and answers: Amazon QuickSight Version May 08, 2024 225 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Q: How do I request access to QuickSight in my AMS
ams-og-082	ams-og.pdf	82	QuickSight in your AMS account Use AMS Self-Service Provisioning (SSP) mode to access QuickSight capabilities directly in your AMS managed account. QuickSight is a fast, cloud-powered business intelligence service that delivers insights to everyone in your organization. As a fully managed service, QuickSight lets you easily create and publish interactive dashboards that include machine learning (ML) insights. To learn more, see Amazon QuickSight. QuickSight in AWS Managed Services FAQs Common questions and answers: Amazon QuickSight Version May 08, 2024 225 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Q: How do I request access to QuickSight in my AMS account? Request access by submitting a Management \| AWS service \| Self-provisioned service \| Add change type (ct-1w8z66n899dct). This RFC provisions the following IAM role to your account: customer_quicksight_console_admin_role. After it's provisioned in your account, you must onboard the role in your federation solution. Q: What are the restrictions to using QuickSight in my AMS account? • AWS resource settings on QuickSight won’t be accessible to you because of the IAM policy dependency. However, the AMS team enables each resource for you in response to your request to enable the service. • Resource access for individual users and groups are not supported in this model because this feature enables users to alter IAM permissions that could compromise AMS infrastructure. • The ability to invite IAM identities from within QuickSight is not supported due to the risk involved altering IAM objects. • QuickSight service oﬀers two editions: Enterprise and Standard. Both provide a single sign- on (SSO) option that is supported on AMS. However, the Enterprise Edition has an option to integrate QuickSight with Active Directory (AD). QuickSight on AMS does not support integration with AD due to incompatibilities between AMS account structure and the QuickSight trust requirements. Q: What are the prerequisites or dependencies to using QuickSight in my AMS account? • When AMS receives this RFC to add QuickSight, you are sent a service request for additional information; provide them the following: • QuickSight account name (for example, CustomerName-quicksight • QuickSight Edition (Standard versus Enterprise) • The AWS Region in which to enable the QuickSight service (defaults to your AMS AWS Region). • A notiﬁcation email address for QuickSight account. • (Optional) The S3 bucket where data ﬁles to be analyzed are located. • The VPC and subnet IDs that connect to QuickSight support a feature to add a VPC connection, which enables private connectivity between QuickSight and resources inside the account. An AMS operator performs the sign up process on your behalf and conﬁgures two QuickSight functionalities: Amazon QuickSight Version May 08, 2024 226 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information • Auto discovery to data sources. • VPC connections. Note These actions need to be performed by an AMS operator because elevated IAM and VPC permissions are required during the sign-in process. Use AMS SSP to provision Amazon Rekognition in your AMS account Use AMS Self-Service Provisioning (SSP) mode to access Amazon Rekognition capabilities directly in your AMS managed account. Amazon Rekognition makes it easy to add image and video analysis to your applications using proven, highly scalable, deep learning technology that requires no machine learning expertise to use. With Amazon Rekognition, you can identify objects, people, text, scenes, and activities in images and videos, as well as detect any inappropriate content. Amazon Rekognition also provides highly accurate facial analysis and facial search capabilities that you can use to detect, analyze, and compare faces for a wide variety of user veriﬁcation, people counting, and public safety use cases. With Amazon Rekognition Custom Labels, you can identify objects and scenes in images that are speciﬁc to your business needs. For example, you can build a model to classify speciﬁc machine parts on your assembly line or to detect unhealthy plants. Amazon Rekognition Custom Labels takes care of the model development heavy lifting for you, so no machine learning experience is required. You simply need to supply images of objects or scenes you want to identify, and the service handles the rest. To learn more, see Amazon Rekognition. Amazon Rekognition in AWS Managed Services FAQs Common questions and answers: Q: How do I request access to Amazon Rekognition in my AMS account? Request access by submitting a Management \| AWS service \| Self-provisioned service \| Add (review required) (ct-3qe6io8t6jtny) change type. This RFC provisions the following IAM role to your account: customer_rekognition_console_role & Amazon Rekognition Version May 08, 2024 227 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information customer_rekognition_service_role. Once provisioned in your account, you must onboard the role in your federation solution. Q: What are the restrictions to using Amazon Rekognition in my AMS account? Full functionality of Amazon Rekognition is available with the Amazon Rekognition self- provisioned service role. Q: What are the prerequisites
ams-og-083	ams-og.pdf	83	Rekognition in my AMS account? Request access by submitting a Management \| AWS service \| Self-provisioned service \| Add (review required) (ct-3qe6io8t6jtny) change type. This RFC provisions the following IAM role to your account: customer_rekognition_console_role & Amazon Rekognition Version May 08, 2024 227 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information customer_rekognition_service_role. Once provisioned in your account, you must onboard the role in your federation solution. Q: What are the restrictions to using Amazon Rekognition in my AMS account? Full functionality of Amazon Rekognition is available with the Amazon Rekognition self- provisioned service role. Q: What are the prerequisites or dependencies to using Amazon Rekognition in my AMS account? If you use Kinesis Video Streams that provide the source streaming video for an Amazon Rekognition Video stream processor or a data stream as a destination to write data to Kinesis Data Streams, kindly provide AMS with a kinesisStreamName when creating the RFC. Use AMS SSP to provision Amazon SageMaker AI in your AMS account Use AMS Self-Service Provisioning (SSP) mode to access Amazon SageMaker AI capabilities directly in your AMS managed account. SageMaker AI provides every developer and data scientist with the ability to build, train, and deploy machine learning models quickly. Amazon SageMaker AI is a fully- managed service that covers the entire machine learning workﬂow to label and prepare your data, choose an algorithm, train the model, tune and optimize it for deployment, make predictions, and take action. Your models get to production faster with much less eﬀort and lower cost. To learn more, see Amazon SageMaker AI. SageMaker AI in AWS Managed Services FAQs Common questions and answers: Q: How do I request access to SageMaker AI in my AMS account? Request access by submitting a Management \| AWS service \| Self-provisioned service \| Add (ct-1w8z66n899dct) change type. This RFC provisions the following IAM roles to your account: customer_sagemaker_admin_role and service role AmazonSageMaker- ExecutionRole-Admin. After SageMaker AI is provisioned in your account, you must onboard the customer_sagemaker_admin_role role in your federation solution. The service role cannot be accessed by you directly; the SageMaker AI service uses it while doing various actions as described here: Passing Roles. Q: What are the restrictions to using SageMaker AI in my AMS account? Amazon SageMaker AI Version May 08, 2024 228 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information • The following use cases are not supported by the AMS Amazon SageMaker AI IAM role: • SageMaker AI Studio is not supported at this time. • SageMaker AI Ground Truth to manage private workforces is not supported since this feature requires overly permissive access to Amazon Cognito resources. If managing a private workforce is required, you can request a custom IAM role with combined SageMaker AI and Amazon Cognito permissions. Otherwise, we recommend using public workforce (backed by Amazon Mechanical Turk), or AWS Marketplace service providers, for data labeling. • Creating VPC Endpoints to support API calls to SageMaker AI services (aws.sagemaker. {region}.notebook, com.amazonaws.{region}.sagemaker.api & com.amazonaws. {region}.sagemaker.runtime) is not supported as permissions can’t be scoped down to SageMaker AI related services only. To support this use case, submit a Management \| Other \| Other RFC to create related VPC endpoints. • SageMaker AI endpoint auto scaling is not supported as SageMaker AI requires DeleteAlarm permissions on any ("") resource. To support endpoint auto scaling, submit a Management \| Other \| Other RFC to setup auto scaling for a SageMaker AI endpoint. Q: What are the prerequisites or dependencies to using SageMaker AI in my AMS account? • The following use cases require special conﬁguration prior to use: • If an S3 bucket will be used to store model artifacts and data, then you must request an S3 bucket named with the required keywords ("SageMaker", "Sagemaker", "sagemaker" or "aws- glue") with a Deployment \| Advanced stack components \| S3 storage \| Create RFC. • If Elastic File Store (EFS) will be used, then EFS storage must be conﬁgured in the same subnet, and allowed by security groups. • If other resources require direct access to SageMaker AI services (notebooks, API, runtime, and so on), then conﬁguration must be requested by: • Submitting an RFC to create a security group for the endpoint (Deployment \| Advanced stack components \| Security group \| Create (auto)). • Submitting a Management \| Other \| Other \| Create RFC to set up related VPC endpoints. Q: What are the supported naming conventions for resources that the customer_sagemaker_admin_role can access directly? (The following are for update and delete permissions; if you require additional supported naming conventions for your resources, reach out to an AMS Cloud Architect for consultation.) Amazon SageMaker AI Version May 08, 2024 229 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information • Resource: Passing AmazonSageMaker-ExecutionRole- role • Permissions: The SageMaker AI self-provisioned
ams-og-084	ams-og.pdf	84	the endpoint (Deployment \| Advanced stack components \| Security group \| Create (auto)). • Submitting a Management \| Other \| Other \| Create RFC to set up related VPC endpoints. Q: What are the supported naming conventions for resources that the customer_sagemaker_admin_role can access directly? (The following are for update and delete permissions; if you require additional supported naming conventions for your resources, reach out to an AMS Cloud Architect for consultation.) Amazon SageMaker AI Version May 08, 2024 229 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information • Resource: Passing AmazonSageMaker-ExecutionRole-* role • Permissions: The SageMaker AI self-provisioned service role supports your use of the SageMaker AI service role (AmazonSageMaker-ExecutionRole-) with AWS Glue, AWS RoboMaker, and AWS Step Functions. • Resource: Secrets on AWS Secrets Manager • Permissions: Describe, Create, Get, Update secrets with a AmazonSageMaker- preﬁx. • Permissions: Describe, Get secrets when the SageMaker resource tag is set to true. • Resource: Repositories on AWS CodeCommit • Permissions: Create/ delete repositories with a AmazonSageMaker-* preﬁx. • Permissions: Git Pull/Push on repositories with following preﬁxes, sagemaker, SageMaker, and Sagemaker. • Resource: Amazon ECR (Amazon Elastic Container Registry) Repositories • Permissions: Permissions: Set, delete repository policies, and upload container images, when the following resource naming convention is used, sagemaker. • Resource: Amazon S3 buckets • Permissions: Get, Put, Delete object, abort multipart upload S3 objects when resources have the following preﬁxes: SageMaker, Sagemaker, sagemaker and aws-glue. • Permissions: Get S3 objects when the SageMaker tag is set to true. • Resource: Amazon CloudWatch Log Group • Permissions: Create Log Group or Stream, Put Log Event, List, Update, Create , Delete log delivery with following preﬁx: /aws/sagemaker/. • Resource: Amazon CloudWatch Metric • Permissions: Put metric data when the following preﬁxes are used: AWS/SageMaker, AWS/ SageMaker/, aws/SageMaker, aws/SageMaker/, aws/sagemaker, aws/sagemaker/, and /aws/sagemaker/.. • Resource: Amazon CloudWatch Dashboard • Permissions: Create/Delete dashboards when the following preﬁxes are used: customer_. • Resource: Amazon SNS (Simple Notiﬁcation Service) topic • Permissions: Subscribe/Create topic when following preﬁxes are used: sagemaker, SageMaker, and Sagemaker. Amazon SageMaker AI Version May 08, 2024 230 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Q: What’s the diﬀerence between AmazonSageMakerFullAccess and customer_sagemaker_admin_role? The customer_sagemaker_admin_role with the customer_sagemaker_admin_policy provides almost the same permissions as AmazonSageMakerFullAccess except: • Permission to connect with AWS RoboMaker, Amazon Cognito, and AWS Glue resources. • SageMaker AI endpoint autoscaling. You must submit a Management \| Other \| Other \| Update RFC to elevate to autoscaling permissions temporarily, or permanently, as autoscaling requires permissive access on CloudWatch service. Q: How do I adopt AWS KMS customer managed key in data encryption at rest? You must ensure that the key policy has been set up properly on the customer managed keys so that related IAM users or roles can use the keys. For more information, see the AWS KMS Key Policy document. Use AMS SSP to provision Amazon Simple Email Service in your AMS account Use AMS Self-Service Provisioning (SSP) mode to access Amazon Simple Email Service (Amazon SES) capabilities directly in your AMS managed account. Amazon Simple Email Service is a cloud- based email sending service designed to help digital marketers and application developers, send marketing, notiﬁcation, and transactional emails. You can use the SMTP interface or one of the AWS SDKs to integrate Amazon SES directly into your existing applications. You can also integrate the email sending capabilities of Amazon SES into the software you already use, such as ticketing systems and email clients. To learn more, see Amazon Simple Email Service. Amazon SES in AWS Managed Services FAQs Q: How do I request access to Amazon SES in my AMS account? Request access to Amazon SES by submitting an RFC with the Management \| AWS service \| Self- provisioned service \| Add (ct-1w8z66n899dct) change type. This RFC provisions the following IAM role to your account: customer_ses_admin_role. After it's provisioned in your account, you must onboard the role in your federation solution. Amazon Simple Email Service Version May 08, 2024 231 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Q: What are the prerequisites or dependencies to using Amazon SES in my AMS account? • You must conﬁgure an S3 bucket policy to allow Amazon SES to publish events to the bucket. • You must use a default (AWS SES), or conﬁgure, a CMK key to allow Amazon SES to encrypt emails and push events to other service resources such as Amazon S3, Amazon SNS, Lambda, and Firehose, belonging to the account. Q: What are the restrictions to using Amazon SES in my AMS account? You must raise RFCs to create the following resources: • An SMTP user and IAM service role with PutEvents permission, to a Kinesis Firehose stream. • You must create new AWS resources such as S3 bucket, Firehose stream,
ams-og-085	ams-og.pdf	85	allow Amazon SES to publish events to the bucket. • You must use a default (AWS SES), or conﬁgure, a CMK key to allow Amazon SES to encrypt emails and push events to other service resources such as Amazon S3, Amazon SNS, Lambda, and Firehose, belonging to the account. Q: What are the restrictions to using Amazon SES in my AMS account? You must raise RFCs to create the following resources: • An SMTP user and IAM service role with PutEvents permission, to a Kinesis Firehose stream. • You must create new AWS resources such as S3 bucket, Firehose stream, SNS topic by using AMS change types in order for your Amazon SES rules and conﬁguration sets' destinations to work with those resources. • SMTP credentials. To request new SMTP credentials, use the Change Type (Management \| Other \| Other \| Create). AMS creates the credentials and adds them to Secrets Manager for you. Use AMS SSP to provision Amazon Simple Workﬂow Service in your AMS account Use AMS Self-Service Provisioning (SSP) mode to access Amazon Simple Workﬂow Service (Amazon SWF) capabilities directly in your AMS managed account. Amazon Simple Workﬂow Service helps developers build, run, and scale background jobs that have parallel or sequential steps. You can think of Amazon SWF as a fully-managed state tracker and task coordinator in the Cloud. If your application's steps take more than 500 milliseconds to complete, you need to track the state of processing, or you need to recover or retry if a task fails, Amazon SWF can help you. To learn more, see Amazon Simple Workﬂow Service. Amazon SWF in AWS Managed Services FAQs Common questions and answers: Q: How do I request access to Amazon SWF in my AMS account? Request access by submitting a Management \| AWS service \| Self-provisioned service \| Add change type (ct-1w8z66n899dct). This RFC provisions the following IAM role to your account: Amazon Simple Workﬂow Service Version May 08, 2024 232 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information customer_swf_role. Once provisioned in your account, you must onboard the role in your federation solution. Q: What are the restrictions to using Amazon SWF in my AMS account? The Lambda InvokeFunction permissions have been included in this service however, the AMS customer_deny_policy that is added to all AMS customer roles explicitly denies access to AMS Lambda functions and AMS-owned resources. In order to tag or untag resources within Amazon SWF, submit a Management \| Other \| Other Change Type. Q: What are the prerequisites or dependencies to using Amazon SWF in my AMS account? Amazon SWF is dependent on the AWS Lambda service, therefore, permissions to invoke Lambda have been provided as a part of this role and no additional permissions are required to invoke Lambda from Amazon SWF. Otherwise, there are no prerequisites to using Amazon SWF. Use AMS SSP to provision Amazon Textract in your AMS account Use AMS Self-Service Provisioning (SSP) mode to access Amazon Textract capabilities directly in your AMS managed account. Amazon Textract is a fully managed machine learning service that automatically extracts printed text, handwriting, and other data from scanned documents that goes beyond simple optical character recognition (OCR) to identify, understand, and extract data from forms and tables. To learn more, see Amazon Textract. Amazon Textract in AWS Managed Services FAQs Common questions and answers: Q: How do I request Amazon Textract to be set up in my AMS account? Request access by submitting a Management \| AWS service \| Self-provisioned service \| Add (review required) (ct-3qe6io8t6jtny) change type. This RFC provisions the following IAM roles to your account: customer_textract_console_role, customer_textract_human_review_execution_role, and customer_ec2_textract_instance_profile. Once provisioned in your account, you must onboard the role customer_textract_console_role in your federation solution. Q: What are the restrictions to using Amazon Textract in my AMS account? There are no restrictions for the use of Amazon Textract in your AMS account. Q: What are the prerequisites or dependencies to using Amazon Textract in my AMS account? Amazon Textract Version May 08, 2024 233 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information You must request the creation of an S3 bucket by submitting an RFC Deployment \| Advanced stack components \|S3 storage \| Create (ct-1a68ck03fn98r). Use AMS SSP to provision Amazon Transcribe in your AMS account Use AMS Self-Service Provisioning (SSP) mode to access Amazon Transcribe capabilities directly in your AMS managed account. Amazon Transcribe is a fully managed and continuously trained automatic speech recognition service that automatically generates time-stamped text transcripts from audio ﬁles. Amazon Transcribe makes it easy for developers to add speech-to-text capabilities to their applications. Audio data is virtually impossible for computers to search and analyze. Therefore, recorded speech needs to be converted to text before it can be used in applications. Historically, customers had to work with transcription providers
ams-og-086	ams-og.pdf	86	(ct-1a68ck03fn98r). Use AMS SSP to provision Amazon Transcribe in your AMS account Use AMS Self-Service Provisioning (SSP) mode to access Amazon Transcribe capabilities directly in your AMS managed account. Amazon Transcribe is a fully managed and continuously trained automatic speech recognition service that automatically generates time-stamped text transcripts from audio ﬁles. Amazon Transcribe makes it easy for developers to add speech-to-text capabilities to their applications. Audio data is virtually impossible for computers to search and analyze. Therefore, recorded speech needs to be converted to text before it can be used in applications. Historically, customers had to work with transcription providers that required them to sign expensive contracts and were hard to integrate into their technology stacks to accomplish this task. Many of these providers use outdated technology that does not adapt well to diﬀerent scenarios, like low-ﬁdelity phone audio common in contact centers, which results in poor accuracy. Amazon Transcribe uses a deep learning process called automatic speech recognition (ASR) to convert speech into text, quickly and accurately. Amazon Transcribe can be used to transcribe customer service calls, automate closed captioning and subtitling, and generate metadata for media assets to create a fully searchable archive. You can use Amazon Transcribe Medical to add medical speech-to-text capabilities to clinical documentation applications. To learn more, see Amazon Transcribe. Amazon Transcribe in AWS Managed Services FAQs Common questions and answers: Q: How do I request Amazon Transcribe to be set up in my AMS account? Request access by submitting a Management \| AWS service \| Self-provisioned service \| Add (review required) (ct-3qe6io8t6jtny) change type. This RFC provisions the following IAM role to your account: customer_transcribe_role. Once provisioned in your account, you must onboard the role in your federation solution. Q: What are the restrictions to using Amazon Transcribe in my AMS account? You must use 'customer-transcribe' as the preﬁx for your buckets when working with transcribe, unless RA and speciﬁed otherwise. You are not able to create an IAM role within Amazon transcribe. Amazon Transcribe Version May 08, 2024 234 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information You cannot use a service-managed S3 bucket for output data in default SSPS (if this is needed, please reach out to your account CA). You must submit Risk Acceptance if you want to use customer-managed KMS Keys that do not fall under the AMS namespace. Q: What are the prerequisites or dependencies to using Amazon Transcribe in my AMS account? S3 must have access to the buckets with the name 'customer-transcribe'. KMS is required in order to use Amazon Transcribe if your S3 buckets are encrypted with KMS keys. If a bucket doesn’t need to be encrypted "KMStranscribeAllow" can be removed. Use AMS SSP to provision Amazon WorkDocs in your AMS account Use AMS Self-Service Provisioning (SSP) mode to access Amazon WorkDocs capabilities directly in your AMS managed account. Amazon WorkDocs is a fully-managed, secure content creation, storage, and collaboration service. With Amazon WorkDocs, you can easily create, edit, and share content, and because it’s stored centrally on AWS, access it from anywhere on any device. Amazon WorkDocs helps you to collaborate with others, and lets you easily share content, provide rich feedback, and collaboratively edit documents. You can use Amazon WorkDocs to retire your legacy ﬁle share infrastructure by moving ﬁle shares to the cloud. Amazon WorkDocs lets you integrate with your existing systems, and oﬀers a rich API so that you can develop your own content-rich applications. Amazon WorkDocs is built on AWS, where your content is secured on the world's largest cloud infrastructure. To learn more, see Amazon WorkDocs. Amazon WorkDocs in AWS Managed Services FAQs Common questions and answers: Q: How do I request access to Amazon WorkDocs in my AMS account? Request access by submitting a Management \| AWS service \| Self-provisioned service \| Add change type (ct-1w8z66n899dct). This RFC provisions the following IAM role to your account: customer_workdocs_console_role. After it's provisioned in your account, you must onboard the role in your federation solution. Q: What are the restrictions to using Amazon WorkDocs in my AMS account? Full functionality of Amazon WorkDocs is available in your AMS account. However, you can't delete an Amazon WorkDocs site. The permissions required to de-register an Amazon WorkDocs site Amazon WorkDocs Version May 08, 2024 235 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information require modiﬁcation to the AWS Managed Microsoft AD directory. To do this, submit an AMS service request for the deletion of an Amazon WorkDocs site. Q: What are the prerequisites or dependencies to using Amazon WorkDocs in my AMS account? Amazon WorkDocs has a dependency on AWS Directory Service for Microsoft Active Directory (MAD). AMS has MAD already implemented in AMS accounts; however, it is limited to a one-way trust. You must submit a service request to AMS
ams-og-087	ams-og.pdf	87	to de-register an Amazon WorkDocs site Amazon WorkDocs Version May 08, 2024 235 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information require modiﬁcation to the AWS Managed Microsoft AD directory. To do this, submit an AMS service request for the deletion of an Amazon WorkDocs site. Q: What are the prerequisites or dependencies to using Amazon WorkDocs in my AMS account? Amazon WorkDocs has a dependency on AWS Directory Service for Microsoft Active Directory (MAD). AMS has MAD already implemented in AMS accounts; however, it is limited to a one-way trust. You must submit a service request to AMS to have an AD Connector set up to proxy your on- premises domain. Use AMS SSP to provision Amazon WorkSpaces in your AMS account Use AMS Self-Service Provisioning (SSP) mode to access WorkSpaces capabilities directly in your AMS managed account. WorkSpaces enables you to provision virtual, cloud-based Microsoft Windows or Amazon Linux desktops for your users, known as WorkSpaces. WorkSpaces eliminates the need to procure and deploy hardware or install complex software. You can quickly add or remove users as your needs change. Users access their WorkSpaces by using a client application from a supported device or, for Windows WorkSpaces, a web browser, and they log in by using their existing on-premises Active Directory (AD) credentials. To learn more, see Amazon WorkSpaces. WorkSpaces in AWS Managed Services FAQs Common questions and answers: Q: How do I request access to WorkSpaces in my AMS account? Request access by submitting a Management \| AWS service \| Self-provisioned service \| Add (review required) (ct-3qe6io8t6jtny) change type. This RFC provisions the following IAM role to your account: customer_workspaces_console_role. Once provisioned in your account, you must onboard the role in your federation solution. Q: What are the restrictions to using WorkSpaces in my AMS account? Full functionality of Workspaces is available with the Amazon WorkSpaces self-provisioned service role. Q: What are the prerequisites or dependencies to using WorkSpaces in my AMS account? • WorkSpaces are limited by AWS Region; therefore, the AD Connector must be conﬁgured in the same AWS Region where the WorkSpaces instances are hosted. Amazon WorkSpaces Version May 08, 2024 236 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Customers can connect WorkSpaces to customer AD using one of the following two methods: 1. Using AD connector to proxy authentication to on-premises Active Directory service (preferred): Conﬁgure Active Directory (AD) Connector in your AMS account prior to integrating your WorkSpaces instance with your on-premises directory service. The AD Connector acts as a proxy for your existing AD users (from your domain) to connect to WorkSpaces using existing on-premises AD credentials. This is preferred because WorkSpaces are directly joined to the customer's on-prem domain, which acts as both Resource and User forest, leading to more control on the customer side. For more information, see Best Practices for Deploying Amazon WorkSpaces (Scenario 1). 2. Using AD Connector with AWS Microsoft AD, Shared Services VPC, and a one-way trust to on- premises: You can also authenticate users with your on-premises directory by ﬁrst establishing a one- way outgoing trust from AMS-managed AD to your on-premises AD. WorkSpaces will join AMS-managed AD using an AD Connector. WorkSpaces access permissions will then be delegated to the WorkSpaces instances through the AMS-managed AD, without the need to establish a two-way trust with your on-premises environment. In this scenario, the User forest will be in the customer AD and the Resource forest will be in the AMS-managed AD (changes to AMS-managed AD can be requested via RFC). Note that the connectivity between WorkSpaces VPC and the MALZ Shared Services VPC running AMS-managed AD is established via Transit Gateway. For more information, see Best Practices for Deploying Amazon WorkSpaces (Scenario 6). Note The AD Connector can be conﬁgured by submitting a Management \| Other \| Other \| Create change type RFC with the prerequisite AD conﬁguration details; for more information, see Create an AD Connector. If method 2 is used to create a Resource forest in AMS-managed AD, submit another Management \| Other \| Other \| Create change type RFC in AMS shared-services account by running the AMS-managed AD. Amazon WorkSpaces Version May 08, 2024 237 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Use AMS SSP to provision AMS Code services in your AMS account Use AMS Self-Service Provisioning (SSP) mode to access AMS Code services capabilities directly in your AMS managed account. AMS Code services is a proprietary bundling of AWS code management services as detailed next. You can choose to deploy all of the services in AMS with AMS Code services, or you can deploy them in AMS individually. AMS Code services includes the following services: • AWS CodeCommit: A fully managed source control service that hosts secure Git-based repositories. It makes it so teams
ams-og-088	ams-og.pdf	88	Guide AMS Advanced Account Onboarding Information Use AMS SSP to provision AMS Code services in your AMS account Use AMS Self-Service Provisioning (SSP) mode to access AMS Code services capabilities directly in your AMS managed account. AMS Code services is a proprietary bundling of AWS code management services as detailed next. You can choose to deploy all of the services in AMS with AMS Code services, or you can deploy them in AMS individually. AMS Code services includes the following services: • AWS CodeCommit: A fully managed source control service that hosts secure Git-based repositories. It makes it so teams can collaborate on code in a secure and highly scalable ecosystem. CodeCommit eliminates the need to operate your own source control system or worry about scaling its infrastructure. You can use CodeCommit to securely store anything from source code to binaries, and it works seamlessly with your existing Git tools. To learn more, see AWS CodeCommit To deploy this in your AMS account independently of AMS Code services, see Use AMS SSP to provision AWS CodeCommit in your AMS account. • AWS CodeBuild: A fully managed continuous integration service that compiles source code, runs tests, and produces software packages that are ready to deploy. With CodeBuild, you don’t need to provision, manage, and scale your own build servers. CodeBuild scales continuously and processes multiple builds concurrently, so your builds are not left waiting in a queue. You can get started quickly by using prepackaged build environments, or you can create custom build environments that use your own build tools. With CodeBuild, you are charged by the minute for the compute resources you use. To learn more, see AWS CodeBuild To deploy this in your AMS account independently of AMS Code services, see Use AMS SSP to provision AWS CodeBuild in your AMS account. • AWS CodeDeploy: A fully managed deployment service that automates software deployments to a variety of compute services such as Amazon EC2 and your on-premises servers. AWS CodeDeploy helps you to rapidly release new features, helps you avoid downtime during application deployment, and handles the complexity of updating your applications. You can use AWS CodeDeploy to automate software deployments, eliminating the need for error-prone manual operations. The service scales to match your deployment needs. To learn more, see AWS CodeDeploy To deploy this in your AMS account independently of AMS Code services, see Use AMS SSP to provision AWS CodeDeploy in your AMS account. AMS Code services Version May 08, 2024 238 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information • AWS CodePipeline: A fully managed continuous delivery service that helps you automate your release pipelines for fast and reliable application and infrastructure updates. CodePipeline automates the build, test, and deploy phases of your release process every time there is a code change, based on the release model you deﬁne. This enables you to rapidly and reliably deliver features and updates. You can easily integrate AWS CodePipeline with third-party services such as GitHub or with your own custom plugin. With AWS CodePipeline, you only pay for what you use. There are no upfront fees or long-term commitments. To learn more, see AWS CodePipeline To deploy this in your AMS account independently of AMS Code services, see Use AMS SSP to provision AWS CodePipeline in your AMS account. AMS Code services in AWS Managed Services FAQs Q: How do I request access to AMS Code services in my AMS account? Request access by submitting a Management \| AWS service \| Self-provisioned service \| Add (review required) (ct-3qe6io8t6jtny) change type. This RFC provisions the following IAM role to your account: customer_code_suite_console_role. After provisioned in your account, you must onboard the role in your federation solution. At this time AMS Operations will also deploy the customer_codebuild_service_role, customer_codedeploy_service_role, aws_code_pipeline_service_role service roles in your account for CodeBuild, CodeDeploy and CodePipeline services. If additional IAM permissions for the are required for the customer_codebuild_service_role are needed, submit an AMS service request. Note You can also add these services separately; for information, see Use AMS SSP to provision AWS CodeBuild in your AMS account, Use AMS SSP to provision AWS CodeDeploy in your AMS account, and Use AMS SSP to provision AWS CodePipeline in your AMS account, respectively. Q: What are the restrictions to using AMS Code services in my AMS account? • AWS CodeCommit: The triggers feature on CodeCommit is disabled given the associated rights to create SNS topics. Directly authenticating against CodeCommit is restricted; users should authenticate with Credential Helper. Some KMS commands are also restricted: kms:Encrypt, AMS Code services Version May 08, 2024 239 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information kms:Decrypt, kms:ReEncrypt, kms:GenereteDataKey, kms:GenerateDataKeyWithoutPlaintext, and kms:DescribeKey. • CodeBuild: For AWS CodeBuild console admin access, permissions are limited at the resource level; for example, CloudWatch actions are limited on
ams-og-089	ams-og.pdf	89	your AMS account, respectively. Q: What are the restrictions to using AMS Code services in my AMS account? • AWS CodeCommit: The triggers feature on CodeCommit is disabled given the associated rights to create SNS topics. Directly authenticating against CodeCommit is restricted; users should authenticate with Credential Helper. Some KMS commands are also restricted: kms:Encrypt, AMS Code services Version May 08, 2024 239 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information kms:Decrypt, kms:ReEncrypt, kms:GenereteDataKey, kms:GenerateDataKeyWithoutPlaintext, and kms:DescribeKey. • CodeBuild: For AWS CodeBuild console admin access, permissions are limited at the resource level; for example, CloudWatch actions are limited on speciﬁc resources and the iam:PassRole permission is controlled. • CodeDeploy: Currently CodeDeploy supports deployments on Amazon EC2/On-premises only. Deployments on ECS and Lambda through CodeDeploy is not supported. • CodePipeline: CodePipeline features, stages, and providers are limited to the following: • Deploy Stage: Amazon S3 and AWS CodeDeploy • Source Stage: Amazon S3, AWS CodeCommit, Bit Bucket, and GitHub • Build Stage: AWS CodeBuild and Jenkins • Approval Stage: Amazon SNS • Test Stage: AWS CodeBuild, Jenkins, BlazeMeter, Ghost Inspector UI Testing, Micro Focus StormRunner Load, Runscope API Monitoring • Invoke Stage: Step Functions and Lambda Note AMS Operations deploys the customer_code_pipeline_lambda_policy in your account; it must be attached with the Lambda execution role for Lambda invoke stage. Provide the Lambda service/execution role name that you want this policy added with. If there is no custom Lambda service/execution role, then AMS creates a new role named customer_code_pipeline_lambda_execution_role, that is a copy of customer_lambda_basic_execution_role along with customer_code_pipeline_lambda_policy. Q: What are the prerequisites or dependencies to using AMS Code services in my AMS account? • CodeCommit: If S3 buckets are encrypted with AWS KMS keys, S3 and AWS KMS are required to use AWS CodeCommit. • CodeBuild: If additional IAM permissions are required for the deﬁned AWS CodeBuild service role, request them through an AMS service request. • CodeDeploy: None. AMS Code services Version May 08, 2024 240 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information • CodePipeline: None. AWS supported services—AWS CodeCommit, AWS CodeBuild, AWS CodeDeploy—must be launched prior to, or along with, the launch of CodePipeline. However this is done by an AMS engineer. Use AMS SSP to provision AWS Amplify in your AMS account Use AMS Self-Service Provisioning (SSP) mode to access AWS Amplify capabilities directly in your AMS managed account. The AWS Amplify is a complete solution that allows frontend web and mobile developers to easily build, connect, and host fullstack applications. Amplify provides ﬂexibility to leverage the breadth of AWS services as your use cases evolve. Amplify provides products to build fullstack iOS, Android, Flutter, Web, and React Native apps. To learn more, see AWS Amplify. AWS Amplify in AWS Managed Services FAQs Common questions and answers: Q: How do I request AWS Amplify to be set up in my AMS account? Request access by submitting a Management \| AWS service \| Self-provisioned service \| Add (review required) (ct-3qe6io8t6jtny) change type. This RFC provisions the following IAM role to your account: customer_amplify_console_role. After provisioned to your account, you must onboard the role in your federation solution. Additionally, you must provide a Risk Acceptance because AWS Amplify has infrastructure- mutating permissions. To do this, work with your Cloud Service Delivery Manager (CSDM). Q: What are the restrictions to using AWS Amplify in my AMS account? You must use 'amplify*' as the preﬁx for your buckets when working with Amplify, unless RA and speciﬁed otherwise. Q: What are the prerequisites or dependencies to using AWS Amplify in my AMS account? There are no prerequisites for the use of AWS Amplify in your AMS account. Malz environments only: The default onboarded role for Amplify is "customer_amplify_console_role". To use a custom role, ﬁrst deploy the IAM entities. Then, create an additional RFC to add your custom role to the Service Control Policy for Application Accounts allow list. AWS Amplify Version May 08, 2024 241 AMS Advanced Onboarding Guide AMS Advanced Account Onboarding Information Use AMS SSP to provision AWS AppSync Use AMS Self-Service Provisioning (SSP) mode to access AWS AppSync capabilities directly in your AMS managed account. AWS AppSync simpliﬁes application development by letting you create a ﬂexible API to securely access, manipulate, and combine data from one or more data sources. AWS AppSync is a managed service that uses GraphQL to make it easy for applications to get exactly the data they need. With AWS AppSync, you can build scalable applications, including those requiring real-time updates, on a range of data sources such as NoSQL data stores, relational databases, HTTP APIs, and your custom data sources with AWS Lambda. For mobile and web apps, AWS AppSync additionally provides local data access when devices go oﬄine, and data synchronization with customizable conﬂict resolution, when they are back online. To learn

Subsets and Splits

No community queries yet

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