Select your cookie preferences

We use essential cookies and similar tools that are necessary to provide our site and services. We use performance cookies to collect anonymous statistics, so we can understand how customers use our site and make improvements. Essential cookies cannot be deactivated, but you can choose “Customize” or “Decline” to decline performance cookies.

If you agree, AWS and approved third parties will also use cookies to provide useful site features, remember your preferences, and display relevant content, including relevant advertising. To accept or decline all non-essential cookies, choose “Accept” or “Decline.” To make more detailed choices, choose “Customize.”

Problem: Couldn’t find or create service linked role - Landing Zone Accelerator on AWS

Problem: Couldn’t find or create service linked role

We updated this solution to make service linked role creation idempotent. When you create a new resource, the solution checks for existing service linked role. If no service linked role exists, the solution creates one. During cleanup, the AWS::IAM::ServiceLinkedRole resource might have been removed successfully, which can cause issues.

Example event from CodeBuild:

AWSAccelerator-OrganizationsStack-<account>-<region> | …​ | DELETE_IN_PROGRESS | AWS::IAM::ServiceLinkedRole | FirewallManagerServiceLinkedRole

AWSAccelerator-OrganizationsStack-<account>-<region> | …​ | DELETE_COMPLETE | AWS::IAM::ServiceLinkedRole | FirewallManagerServiceLinkedRole

Resolution

Manually release the pipeline again. The service linked role will run on every pipeline. If no service linked role exists, the solution creates a new one in the account.

PrivacySite termsCookie preferences
© 2025, Amazon Web Services, Inc. or its affiliates. All rights reserved.