Fix Cloud9 Bootstrap issues (#287)

* Changes for EKS 1.27

* Reboot c9 instance after attaching instance profile

* Add reboot permissions to lambda role

---------

Co-authored-by: Sudheer Sangunni <sangunni@amazon.com>
Co-authored-by: Imaya Kumar Jagannathan <ijaganna@amazon.com>
Co-authored-by: gjohnson <garrjh@amazon.com>
Co-authored-by: Rafael Pereyra <rapg@amazon.com>

Author: 5 people

cloud9-cfn.yaml

@@ -465,6 +465,7 @@ Resources:
             - ec2:AssociateIamInstanceProfile
             - ec2:ModifyInstanceAttribute
             - ec2:ReplaceIamInstanceProfileAssociation
+            - ec2:RebootInstances
             Resource: !Sub "arn:${AWS::Partition}:ec2:${AWS::Region}:${AWS::AccountId}:instance/*"
           - Effect: Allow
             Action:
@@ -595,7 +596,7 @@ Resources:
                       # attach instance profile
                       response = ec2.associate_iam_instance_profile(IamInstanceProfile=iam_instance_profile, InstanceId=instance['InstanceId'])
                       logger.info('response - associate_iam_instance_profile: {}'.format(response))
-                      #r_ec2 = boto3.resource('ec2')
+                      ec2.reboot_instances(InstanceIds=[instance['InstanceId']], DryRun=False)
 
                       responseData = {'Success': 'Started bootstrapping for instance: '+instance['InstanceId']}
                       cfnresponse.send(event, context, cfnresponse.SUCCESS, responseData, 'CustomResourcePhysicalID')