--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/fc046bdc-e7ff-4457-9b16-2ba81f52dafc%40googlegroups.com.
Please follow below steps:
Configure Systems,
Amazon S3 profile,
S3 profiles name : same name as "IAM role"
Instead of given credentials, we can select "Use IAM Role", then apply and save
Publish artifacts to S3 Bucket,
S3 profile name: name same as "IAM role",
Files to upload: Source : Files name
Destination bucket : Bucket path
Bucket Region : Select bucket region
Then Apply and Save
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/
On Thu, Aug 2, 2018 at 8:46 AM, <seshadri...@gmail.com> wrote:
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 hiding AWS credentials in Jenkins jobs
On Monday, 30 July 2018 17:03:22 UTC+5:30, gil wrote:what about writing your job to upload files to s3?
On Friday, 27 July 2018 14:44:13 UTC+3, seshadri...@gmail.com wrote:Hi,My self Jai,Am currently facing problem with "how to hide aws access key and secrete key in S3 plugin while uploading artifacts from jenkins job to AWS S3 ??? Need help soon, Can any body please??Thanks and RegardsJai
--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.