Step 2 (Optional): Launch the remote stack in secondary accounts - Instance Scheduler on AWS

Step 2 (Optional): Launch the remote stack in secondary accounts

Important

The remote stack must be deployed in the same Region as the hub stack.

This automated AWS CloudFormation template configures secondary account permissions that will allow the hub stack to schedule instances in other accounts. Install the remote template only after the primary/hub stack has been successfully installed in the Hub account.

Launch solution button

  1. Sign in to the AWS Management Console of the applicable secondary account and select the button to launch the instance-scheduler-on-aws-remote AWS CloudFormation template.

  2. The template launches in the US East (N. Virginia) Region by default. To launch the solution in a different AWS Region, use the Region selector in the console navigation bar. If the hub stack is configured to use AWS Organizations, then deploy the remote template in the same region as the hub stack.

  3. On the Create stack page, verify that the correct template URL is in the Amazon S3 URL text box and choose Next.

  4. On the Specify Details page, assign a name to your remote stack.

  5. Under Parameters, review the parameter for the template, and modify it.

  6. If the AWS Organizations option is enabled and the hub stack is similarly configured, there are no further changes required in the main stack to start the scheduling.

  7. If the AWS Organization option is set to No, then the hub stack should be updated with the new Account ID.

Parameter Default Description
Hub Account ID <Requires Input> Account ID of the Instance Scheduler on AWS hub stack that will schedule resources in this account.
Use AWS Organizations No Use AWS Organizations to automate spoke account registration. Must be set to the same value as the hub stack.
Namespace default Unique identifier used to differentiate between multiple solution deployments. Must be set to the same value as the hub stack.
Kms Key ARNs for EC2 <Optional Input> Comma-separated list of KMS ARNs to grant the solution kms:CreateGrant permissions to provide the EC2 service with decrypt permissions for encrypted EBS volumes. This allows the scheduler to start EC2 instances with attached encrypted EBS volumes. Provide (*) to give limited access to all KMS keys; leave blank to disable. For details on the exact policy created, refer to Encrypted EC2 EBS Volumes

  1. Choose Next.

  2. On the Options page, choose Next.

  3. On the Review and create page, review and confirm the settings. Be sure to check the box acknowledging that the template will create IAM resources.

  4. Choose Submit to deploy the stack.

You can view the status of the stack in the AWS CloudFormation Console in the Status column. You should see a status of CREATE_COMPLETE in approximately five minutes.