In this section your Security and Cloud Administrators will provision resources to act as overall guardrails for controlling access within your team development AWS accounts.
Service control policies (SCPs) are used to constrain the ability to modify cloud networking resources in your team development environments. An IAM permissions boundary is distributed as a means to constrain your builders from modifying foundation resources in your team development environment.
This step should take about 20 minutes to complete.
Learn more about guardrails: See Environment Guardrails for an introduction to the use of guardrails that you can apply to your AWS environments. Guardrails are governance rules for security, operations, and compliance that customers can select and apply enterprise-wide or to specific groups of accounts. You might start with a basic set of guardrails and expand them as you gain experience and your needs evolve.
Automated provisioning of resources: Ideally, you would use automation to deploy policies and other configurations to your AWS accounts. Customizations for AWS Control Tower is an AWS solution that uses AWS services including AWS CodePipeline and AWS Control Tower Lifecycle Events to help you more efficiently manage these types of resources as code and via pipelines. Both the SCPs and IAM permissions boundary policy resources addressed below are candidates for using this automation solution.
Using AWS Organizations, create several Service Control Policies (SCPs) that will initially be applied to the
workloads_dev OU. Combined, these SCPs will disallow any user from creating and modifying foundation VPC networking resources in standard team development AWS accounts.
Since you’ll likely want your Cloud Foundation team members to be able to develop and test changes to foundation VPC resources in their team development AWS accounts, it’s recommended that you don’t want to apply the SCPs to the
Service Control Policies (SCPs): If you’d like to learn more about SCPs, see Managing AWS Organizations policies.
Review the sample team development access controls: See Controlling Builder Team Access for a detailed explanation of the requirements and sample implementation of how you can provide freedom to your builder teams in their team development AWS accounts, but inhibit them from adversely impacting the security of your overall AWS environment.
Either open in a separate browser tab or download to your desktop the following sample SCPs:
Management consoleassociated with the
Service control policies
Service control policies.
Attachlink next to the SCPs
In this step you’ll use AWS CloudFormation StackSets to distribute an IAM permissions boundary policy to the development OUs. This boundary policy will help ensure that builder teams using team development AWS accounts can’t modify your foundation cloud resources.
In a later section, when you create several team development AWS accounts, you will associate the AWS accounts with the development OUs. Any AWS account that is added to the development OUs will automatically be configured with the IAM permissions boundary policy resource. Similarly, when an AWS account is removed from the OUs, the IAM permissions boundary policy resource will be automatically removed from the AWS account.
First, enable the AWS CloudFormation service to automatically configure permissions required to use the CloudFormation StackSets feature to deploy stacks to AWS accounts in your AWS organization.
Enable trusted access.
This is a one time operation: If you’d like more background, see Enabling Trusted Access with AWS Organizations.
Next, download the sample AWS CloudFormation template
example-infra-team-dev-boundary.yml to your desktop.
Create a StackSet to deploy the permissions boundary policy to all AWS accounts associated with the development OUs.
Upload a template file.
Choose fileto select the downloaded template file from your desktop.
StackSet name. For example,
It’s useful to prefix your custom cloud resources that live in a larger name space with your organization identifier and a qualifier such as
infra to represent foundation resources. The important consideration is to be consistent with naming of foundation cloud resources so that you can apply IAM policies that will inhibit unauthorized modification of those resources.
Leave the other parameters at their default settings.
Service managed permissions.
Deployment targets, select
Deploy to organizational units (OUs).
If you didn’t make a copy of the development OU IDs, open a new browser tab and access
AWS Control Tower. Select
Organizational units, and select each of the following development OUs to obtain its OU ID:
Specify regions, select your home AWS region.
Since you have not yet created the team development AWS accounts, this CloudFormation StackSet won’t create CloudFormation stacks in the team development AWS accounts until those AWS accounts are created in a subsequent section.