![]() We will use our web browser to view the web page that was deployed to the Amazon EC2 instance running RHEL instance. We will use the AWS CodeDeploy console to verify the success of the deployment. We've now created an IAM instance profile to attach to Amazon EC2 instances. On the Attach Policy page, select the box next to CodeDeployDemo-EC2-Permissions: On the Select Role Type page, next to Amazon EC2, choose Select. In the Role Name box, give the IAM instance profile a name like CodeDeployDemo-EC2, and then choose Next Step. In the navigation pane, choose Roles, and then choose Create New Role. In the Policy Document box, paste the following: ![]() In the Policy Name box, type CodeDeployDemo-EC2-Permissions. Next to Create Your Own Policy, choose Select: In the IAM console, in the navigation pane, choose Policies, and then choose Create Policy. This role gives AWS CodeDeploy permission to access the Amazon S3 buckets or GitHub repositories where our applications are stored. To launch Amazon EC2 instances that are compatible with AWS CodeDeploy, we must create an additional IAM role, an instance profile. Our Amazon EC2 instances need permission to access the Amazon S3 buckets or GitHub repositories where the applications that will be deployed by AWS CodeDeploy are stored.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |