src/main/resources/com/amazonaws/codedeploy/AWSCodeDeployPublisher/help-awsAccessKey.html [1:8]:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
<div>
  <p>AWS Access and Secret keys to use for this deployment. At minimum the keys must be allowed to execute
  <code>codedeploy:*</code> and <code>s3:Put*</code>. It's a best practice to have these keys be from an IAM role
  with limited scope.</p>

  <p>
    If your Jenkins install is running on an EC2 instance with an associate IAM role, you can leave these fields
    blank. You will just need to ensure that the role has the correct policies.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -



src/main/resources/com/amazonaws/codedeploy/AWSCodeDeployPublisher/help-awsSecretKey.html [1:8]:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
<div>
  <p>AWS Access and Secret keys to use for this deployment. At minimum the keys must be allowed to execute
  <code>codedeploy:*</code> and <code>s3:Put*</code>. It's a best practice to have these keys be from an IAM role
  with limited scope.</p>

  <p>
    If your Jenkins install is running on an EC2 instance with an associate IAM role, you can leave these fields
    blank. You will just need to ensure that the role has the correct policies.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -