AWS Access and Secret keys to use for this deployment. At minimum the keys must be allowed to execute
3 | codedeploy:*
and s3:Put*
. It's a best practice to have these keys be from an IAM role
4 | with limited scope.
7 | If your Jenkins install is running on an EC2 instance with an associate IAM role, you can leave these fields 8 | blank. You will just need to ensure that the role has the correct policies. 9 |
10 |AWS Access and Secret keys to use for this deployment. At minimum the keys must be allowed to execute
3 | codedeploy:*
and s3:Put*
. It's a best practice to have these keys be from an IAM role
4 | with limited scope.
7 | If your Jenkins install is running on an EC2 instance with an associate IAM role, you can leave these fields 8 | blank. You will just need to ensure that the role has the correct policies. 9 |
10 |If checked, the build will use a dedicated appspec.yml file per deployment group.
3 |The appspec file should be named "appspec.DEPLOYMENT_GROUP_NAME.yml" and must be present in the jenkins project workspace.
e.g.: appsec.staging.yml
5 |3 | In order to keep your application(s) more secure, this plugin only uses temporary credentials via STS, scoped to each application. To set this up: 4 |
5 | 6 |{"Version": "2012-10-17", "Statement": [{"Effect": "Allow", "Action": ["codedeploy:*", "s3:*"], "Resource": "*"}]}
Proxy host DNS name
3 |Proxy host port
3 |If checked, this build will wait for the AWS CodeDeploy deployment to finish (with either success or failure). Polling
3 | Timeout, below, sets the maximum amount of time to wait.
If unchecked, the deployment will be handed off
4 | to AWS CodeDeploy and the build will move on to the next step.
The build will be marked a failure if either the timeout is reached or the deployment fails. The 7 | build log will indicate which.
8 |