The 'You are not authorized to perform this operation' error should be accompanied with its related 'Encoded authorization failure message'. You can then decode the message using decodeAuthorizationMessage  to see what went wrong specifically.
Hope that this information helps to solve your issue.
Thanks for your reply. Now, I have decoded the message, using your link, and can see that an IAM permission was further needed to launch the new instances. Thanks.
Dynamically assign an IAM Role between an IAM user and and EC2 instanceasked 7 months ago
Bucket Policy to Restrict Access to an Instance Profileasked 2 years ago
How can you restrict EC2 instances to assuming an IAM role based on the instance's tags?asked 9 months ago
IAM Policy that allows only access to "Switch Role"asked 5 months ago
Limit which IAM roles can be attached to an EC2 instance by different IAM usersasked 10 months ago
IAM Policy SFTPasked 4 years ago
is there a service role that needs to be attached to AWSCodeCommitPowerUser policy for codecommit , we are integrating with Jenkins and with only policy the code /repo is not getting checked outasked 3 months ago
details of IAM role which is attached to ec2 instances with cloudshellAccepted Answerasked 6 months ago
Specify Individual Instance In Trust Policy Of IAM RoleAccepted Answerasked 5 months ago
Not authorized to start new instancesAccepted Answerasked 4 years ago