💾 Archived View for cfdocs.wetterberg.nu › stacksets-orgs-manage-auto-deployment.gemini captured on 2024-12-17 at 15:47:16. Gemini links have been rewritten to link to archived content

-=-=-=-=-=-=-

Manage automatic deployments for a stack set with service\-managed permissions

With automatic deployment enabled, StackSets automatically deploys to accounts that are added to the target organization or organizational units (OUs) in the future. With retain stacks enabled, when an account is removed from a target OU, stack resources in the account are retained. You can adjust the automatic deployment settings you specified when you created your stack set at any time.

Topics*

Manage automatic deployments using the AWS CloudFormation console
Manage automatic deployments using the AWS CLI
Auto deployment example

Manage automatic deployments using the AWS CloudFormation console

Open the AWS CloudFormation console at https://console.aws.amazon.com/cloudformation.
From the navigation pane, choose StackSets.
On the StackSets page, select the stack set that you created in Creating a stack set with service-managed permissions.
With the stack set selected, choose Edit automatic deployment from the Actions menu. Automatic deployment is set at the stack set level. You cannot adjust automatic deployments selectively for OUs, accounts, or Regions.[Select stack set and choose Edit automatic deployment from the Actions menu.]
In the Edit automatic deployment modal, manage Automatic deployment and Account removal behavior settings.[Edit automatic deployments modal.]NoteWith Retain stacks selected, stack instances are removed from your stack set, but the stacks and their associated resources are retained. The resources stay in their current state, but are no longer part of the stack set. The stacks cannot be reassociated with an existing or new stack set.
Choose Save.

https://console.aws.amazon.com/cloudformation.

Creating a stack set with service-managed permissions

Manage automatic deployments using the AWS CLI

Open the AWS CLI.
Run the update-stack-set command, specifying the stack set that you created in Creating a stack set with service-managed permissions. Automatic deployment is set at the stack set level. If you specify --auto-deployment in your stack set update, you cannot specify --deployment-targets or --regions.
Using the operation-id that was returned as part of the update-stack-set output in step 2, run describe-stack-set-operation to verify that your stack set was updated successfully.

Creating a stack set with service-managed permissions

Auto deployment example

When you enable automatic deployments, they are triggered when accounts are added to a target organization or OU, removed from a target organization or OU, or moved between target OUs.

For example, a stack set, `StackSet1`, targets an OU, `OU1`, in the `us-east-1` Region. A stack set, `StackSet2`, targets an OU, `OU2`, in the `us-east-1` Region. `OU1` contains an account, `AccountA`.

If we move `AccountA` from `OU1` to `OU2` with automatic deployments enabled, StackSets automatically runs a delete operation to remove the `StackSet1` instance from `AccountA` and queues a create operation that adds the `StackSet2` instance to `AccountA`. After the `StackSet1` instance is deleted, the `StackSet2` instance is created.