<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Daniel Rankov</title>
    <description>The latest articles on DEV Community by Daniel Rankov (@danielrankov).</description>
    <link>https://dev.to/danielrankov</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F1115124%2F27172b3b-0855-4612-8aa7-2159a01ee681.jpeg</url>
      <title>DEV Community: Daniel Rankov</title>
      <link>https://dev.to/danielrankov</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/danielrankov"/>
    <language>en</language>
    <item>
      <title>AWS Control Tower Landing Zone upgrade to 3.2 - fix account Enrollment</title>
      <dc:creator>Daniel Rankov</dc:creator>
      <pubDate>Wed, 19 Jul 2023 09:15:46 +0000</pubDate>
      <link>https://dev.to/danielrankov/aws-control-tower-landing-zone-upgrade-to-32-fix-account-enrollment-28ip</link>
      <guid>https://dev.to/danielrankov/aws-control-tower-landing-zone-upgrade-to-32-fix-account-enrollment-28ip</guid>
      <description>&lt;p&gt;AWS Control Tower allows us to set up and govern a secure, multi-account AWS environment. AWS Control Tower simplifies AWS experiences by orchestrating multiple AWS services on your behalf while maintaining your organization's security and compliance needs.&lt;br&gt;
&lt;a href="https://aws.amazon.com/controltower/"&gt;https://aws.amazon.com/controltower/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;AWS Control Tower also establishes a Landing Zone based on best-practices blueprints. &lt;/p&gt;

&lt;p&gt;AWS Control Tower evolves and provides new releases of the Landing Zone and internal, incorporated into the service updates. Release notes: &lt;a href="https://docs.aws.amazon.com/controltower/latest/userguide/release-notes.html"&gt;https://docs.aws.amazon.com/controltower/latest/userguide/release-notes.html&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;AWS Control Tower landing zone version 3.2 was released on June 16, 2023. With this update, there are multiple improvements - &lt;a href="https://docs.aws.amazon.com/controltower/latest/userguide/2023-all.html#lz-3-2"&gt;https://docs.aws.amazon.com/controltower/latest/userguide/2023-all.html#lz-3-2&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Here is the process to update &lt;a href="https://docs.aws.amazon.com/controltower/latest/userguide/update-controltower.html:"&gt;https://docs.aws.amazon.com/controltower/latest/userguide/update-controltower.html:&lt;/a&gt;&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Navigate to AWS Control Tower in the web console -&amp;gt; Landing zone settings&lt;/li&gt;
&lt;li&gt;Select the version number and choose Update&lt;/li&gt;
&lt;li&gt;The update process takes about 30 minutes&lt;/li&gt;
&lt;li&gt;The update changes the AWS Control Tower core accounts only - the Organization itself, Audit, and Log Archive accounts.&lt;/li&gt;
&lt;li&gt;To upgrade the accounts in the rest of the Organization, choose OU (OUs with fewer than 300 AWS accounts) and then Actions -&amp;gt; Re-register organization unit. This will update all the accounts in the current OU.&lt;/li&gt;
&lt;li&gt;Repeat for all the OUs&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;If you update a single account and then try to Re-register the OU which holds the account, an error might arise "Enrollment failed"&lt;br&gt;
The error is related to AWS resources that are already existing - like IAM Roles.&lt;/p&gt;

&lt;p&gt;To clean the account and have a clean Enrollment, these resources need to be deleted:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;AWS IAM Roles aws-controltower-*&lt;/li&gt;
&lt;li&gt;SNS topic aws-controltower-SecurityNotifications&lt;/li&gt;
&lt;li&gt;Lambda Function aws-controltower-NotificationForwarder&lt;/li&gt;
&lt;li&gt;CloudWatch Loggroup /aws/lambda/aws-controltower-NotificationForwarder&lt;/li&gt;
&lt;li&gt;EventBridge Rule aws-controltower-ConfigComplianceChangeEventRule&lt;/li&gt;
&lt;li&gt;Config configuration-recorder aws-controltower-BaselineConfigRecorder
&lt;code&gt;aws configservice delete-configuration-recorder --configuration-recorder-name aws-controltower-BaselineConfigRecorder&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;Config delivery-channel aws-controltower-BaselineConfigDeliveryChannel
&lt;code&gt;aws configservice delete-delivery-channel --delivery-channel-name aws-controltower-BaselineConfigDeliveryChannel&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;Config aggregation-authorization for the region - details can be obtained with this CLI
&lt;code&gt;aws configservice describe-aggregation-authorizations&lt;/code&gt;
&lt;code&gt;aws configservice delete-aggregation-authorization --authorized-account-id ACCOUNT_ID --authorized-aws-region REGION&lt;/code&gt;
&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;All of these resources are protected by SCP, and you would need to "jump" to the particular AWS account from your Organizational using the AWSControlTowerExecution Role.&lt;/p&gt;

&lt;p&gt;Have fun.&lt;br&gt;
Thank you!&lt;/p&gt;

</description>
    </item>
  </channel>
</rss>
