[JIRA] (JENKINS-37164) ECS plugin does not use InstanceProfileCredentialsProvider, and cannot use IAM profile
Title: Message Title Evan Borgstrom closed an issue as Not A Defect Sorry, this is NOT a bug. It turned out to be because of: https://bugs.launchpad.net/ubuntu/+source/ca-certificates-java/+bug/1396760 The IAM profile does indeed work as expected. Jenkins / JENKINS-37164 ECS plugin does not use InstanceProfileCredentialsProvider, and cannot use IAM profile Change By: Evan Borgstrom Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
[JIRA] (JENKINS-37164) ECS plugin does not use InstanceProfileCredentialsProvider, and cannot use IAM profile
Title: Message Title Evan Borgstrom updated an issue Jenkins / JENKINS-37164 ECS plugin does not use InstanceProfileCredentialsProvider, and cannot use IAM profile Change By: Evan Borgstrom Attachment: Screen Shot 2016-08-03 at 9.49.47 PM.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37164) ECS plugin does not use InstanceProfileCredentialsProvider, and cannot use IAM profile
Title: Message Title
Evan Borgstrom created an issue
Jenkins / JENKINS-37164
ECS plugin does not use InstanceProfileCredentialsProvider, and cannot use IAM profile
Issue Type:
Bug
Assignee:
Jan Roehrich
Components:
amazon-ecs-plugin
Created:
2016/Aug/04 4:48 AM
Environment:
Jenkins 2.7.1 amazon-ecs 1.4 aws-credentials 1.16 aws-java-sdk 1.10.50
Priority:
Major
Reporter:
Evan Borgstrom
When adding a cloud it says: "AWS IAM Access Key used to connect to ECS. If not specified, implicit authentication mechanisms are used (IAM roles...)" This does not actually work. My instance has the correct policy and is confirmed from the cli:
$ aws --region us-east-1 ecs list-clusters
{
"clusterArns": [
"arn:aws:ecs:us-east-1::cluster/jenkins"
]
}
Looking through the github repos it appears that only the EC2 Cloud plugin actually uses InstanceProfileCredentialsProvider. (https://github.com/search?q=org%3Ajenkinsci+InstanceProfileCredentialsProvider=Code)
