These are the input parameters for this template. All of these parameters must be supplied for this template to be deployed.
CloudFormation cannot create IAM Identity Providers, so it must be created before this teplate is run. Pass in the ARN of the created Shibboleth IDP here.
CF didn't used to support RoleName properties. So for older accounts, the CFDeployerRole is something like "fdn-iam-CloudFormationAdminDeployerRole-12AJKX5827CDR". Once that role is in use in an account however, we can't change it, so we have to just deal with the legacy version of this role forever.
For new accounts, we can specify a RoleName of "fdn-CloudFormationAdminDeployer". The following condition is set up to detect what sort of account we're deploying into, and then specify a RoleName or not.
The Sysadmin role/policy allows those users in the group access to almost everything in the account.
Allow ALL actions on any resource, with the exceptions of the IAM actions.
Allow some IAM abilities
Explicitly DENY access to the billing information
Explicitly DENY access to certain CloudTrail actions
Explicitly ALLOW access to kms:CreateGrant.
Explicitly DENY access to disable the KMS service, except for kms:Create*.
Allow ALL actions on any resource, with the exceptions of the IAM actions.
Allow some IAM abilities
Explicitly DENY access to certain CloudTrail actions
This policy is only attached to the User Group, so will only apply to IAM users who have been added to the group, and not to SAML users logging in via the Role and Shibboleth.
Allow ALL IAM actions on any resource, with the exceptions of the IAM actions. Also enforces that the user MUST have MultiFactor authentication set up.
The IAM Admin role/policy allows full access to all IAM actions.
Allow ALL IAM actions
This policy is only attached to the User Group, so will only apply to IAM users who have been added to the group, and not to SAML users logging in via the Role and Shibboleth.
Allow ALL IAM actions, an enforces MultiFactor authentication is set up.
The Opertions role/policy allows broad access to many AWS systems.
Allow ALL EC2 Actions
Allow ALL ELB Actions
Allow ALL CloudWatch actions
Allow ALL Autoscalling actions
DENY the following EC2 Actions
Deny Billing information
Deny access to the KMS system.
The Read-Only Admin role/policy allows broad read access to most services.
The Read-Only Billing role/policy allows full read access to Billing info.
Allow access to all aws-portal::view* actions
DENY access to aws-portal:*Account actions such as :ViewAccount and :ModifyAccount
Billing & Purchasing role/policy allows full read access to Billing info along with the ability to purchase reserved instances and submit support tickets.
Allow access to EC2 actions
Allow access to RDS actions
Allow access to Redshift actions
DENY access to aws-portal:*Account actions such as :ViewAccount and :ModifyAccount
This is the role allows full admin permissions when deploying a CloudFormation template. This role should only be allowed to be used by trusted users, default this is only the SysAdmin role.
This is the role that is given to the OpsWorks service, which allows OpsWorks to manage AWS resources. This is a standard policy provided by AWS. See the AWS Documentation for OpsWorks Service Role
This is a role that grants roles in other accounts the permission to assume the role and perform CloudFormation creates and updates.
This is a role allows central deployment of CloudFormation Stack Sets https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-prereqs.html
The role name must be AWSCloudFormationStackSetExecutionRole
Additional access for Cloudability to retrieve specific service information.
User Roles CloudFormation Deployment
This CloudFormation template will deploy IAM roles for use by Users of this account.