When creating a new IAM role resource using Cloudformation, AWS::IAM::Role
.
There is an optional RoleName
parameter, and I am not sure when if it is better practice to include the RoleName
parameter or exclude it.
The following are the differences that are specified in the documentation
- If you don't specify a name, AWS CloudFormation generates a unique physical ID and uses that ID for the role name.
- If you specify a name, you must specify the CAPABILITY_NAMED_IAM value to acknowledge your template's capabilities.
- Naming an IAM resource can cause an unrecoverable error if you reuse the same template in multiple Regions.
Are there any other functional differences betweeen using or excluding the RoleName
parameter?