In this step your Security and Cloud Administrators will provision resources to control the access to team development AWS accounts.
This step should take about 20 minutes to complete.
Automated provisioning of resources: In the next several steps you’ll use a mix of manual steps and automation to provision a set of policies to set up access controls for builder teams’ use of team development environments. Although these approaches may be suitable for your initial iteration of your AWS environment, a more advanced and effective means of provisioning these resources would be to manage the polcies in a source repository and use a continuous delivery (CD) pipeline to automatically detect changes to the policy source, validate the changes, and provision the changes to your environment. 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.
development
OUUsing AWS Organizations, create several Service Control Policies (SCPs) that will initially be applied to the development
OU. When applied to the development
OU, these SCPs will disallow any user including builder team members and foundation team members from creating and modifying foundation VPC networking resources in team development AWS accounts.
Service Control Policies (SCPs): If you’d like to learn more about SCPs, see Managing AWS Organizations policies.
Ability for foundation team builders to create and modify VPC resources: Typically, builders in your foundation team will need to have write acess to VPC resources in their team development accounts so that they can experiment, develop, and perform early forms of testing of VPC related foundational changes. You have several options for enabling foundation team builders to have such access: 1) You could create a new “development-foundation” or similar OU that does not have the SCP described here and create foundation team development AWS accounts under that OU or 2) you could continue to use the common SCP, establish a distinct persmission set for your foundation team development access that has the same policy as other teams, and enhance the SCP to include a condition to exclude the foundation team’s team development IAM role associated with the permission set. In either case, see Controlling Builder Team Access for a more detailed explanation of these options.
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:
master
account.Management console
associated with the AWSAdministratorAccess
role.AWS Organizations
.Policies
.Service control policies
Create policy
.example-base-scp-vpc-core
example-base-scp-vpc-boundaries
development
OUOrganize accounts
.development
OU.Service control policies
.Attach
link next to the SCPs
example-base-scp-vpc-core
example-base-scp-vpc-boundaries
In this step you’ll use AWS CloudFormation StackSets to distribute an IAM permissions boundary policy to the “development” OU that you just created. 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” OU. Any AWS account that is added to that OU will automatically be configured with the IAM permissions boundary policy resource. Similarly, when an AWS account is removed from the OU, 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.
AWS CloudFormation
.StackSets
.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-base-team-dev-boundary.yml
to your desktop.
Create a StackSet to deploy the permissions boundary policy to all AWS accounts associated with the “development” OU.
Create StackSet
.Upload a template file
.Choose file
to select the downloaded template file from your desktop.Next
.StackSet name
. For example, example-base-team-dev-boundary
.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 base
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.
Parameters
:Parameter | Guidance |
---|---|
pOrg |
Replace example with your organization identifier or stock ticker if that applies. This value is used as a prefix in the name of IAM managed policy that is created by the template. |
Leave the other parameters at their default settings.
Next
.Permissions
set to Service managed permissions
.Next
.Deployment targets
, select Deploy to organizational units (OUs)
.Specify regions
, select your home AWS region.Next
.Submit
.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.
Proceed to the next step.
Next, you’ll create a custom permission set in AWS SSO to represent the initial iteration of an AWS IAM policy under which builder team members will work in their team development AWS accounts.
example-base-team-dev-saml.json
to your desktop.example
with a reference to your own organization’s identifier.AWS accounts
in AWS SSO.Permission sets
.Create permission set
.Create a custom permission set
.Name
. For example example-base-team-dev
.Description
. For example, Day-to-day permission used by builders in their team development AWS accounts.
.Session duration
to the desired value.Create a custom permissions policy
.Create
.Later, when you onboard the builder teams to their team development AWS accounts, you’ll reference this permission set.