Never mind. I got it to work. I assigned an instance profile to my slaves
and created an S3 profile with "Use IAM role" checked. It again unchecked
it but it worked nonetheless. Also, the S3 profile didn't have to bear the
same name as the IAM role assigned to the slaves.
On Wednesday, August 2
I can't see the screenshots. Would you please post them again? I tried to
follow your instructions but Jenkins automatically unchecks "use IAM role"
after I save it with the name or ARN of the role. What am I doing wrong?
On Thursday, August 2, 2018 at 9:48:38 PM UTC+5:30 seshadri...@gmail.com
Hi Aldrin Leal,
Thanks for your information, my problem got solved with other way
like instead of using IAM user credentials in Jenkins, we can create IAM
role with S3 full permission and attach that role in to the Jenkins server,
then in Jenkins at the S3 publisher profile instead of p
Why not restrict the key to allow only uploading from a given IP Address?
Is it way safer
https://aws.amazon.com/blogs/security/writing-iam-policies-
how-to-grant-access-to-an-amazon-s3-bucket/
https://docs.aws.amazon.com/IAM/latest/UserGuide/
reference_policies_examples_aws_deny-ip.html
--
-- A
Jenkins deployments will need to upload artifacts to S3; Jenkins can't
write to S3 by default, so we'll need to specify AWS credentials to upload.
We'd prefer to not expose these credentials in build scripts or
configuration options.
Goal is to provide best practices for properly using and hidin
