Good explanation regarding the integration of Jenkins and AWS credentials
@sagarahire96302 жыл бұрын
Sir..Don't u think it's bit risky to store such credentials in jenkins like the details of aws account
@oleksandrlytvyn532 Жыл бұрын
If Jenkins is deployed in AWS it would be much better to use IAM Role for that cause, instead of hardcoding (even via plugin) secret keys
@payloadpat7 ай бұрын
I know this is late but yes! That’s the best way to go. In your Jenkins pipeline, using the withAWS plugin without specifying any credentials, it automatically uses the credentials provided by the EC2 instance's role.
@prathapcharan3 ай бұрын
Yes it's better to use iam role instead of keys. Saving unencrypted keys outside of AWS is not recommended.
@ajayjohn1502 Жыл бұрын
Could you please explain how we can stop and start the ec2 instance using parameters..pls help
@sivajakka3199 Жыл бұрын
can u please explain from where do i need to take class name from the above explaination
@indianmovies34752 жыл бұрын
Superb sir
@princechandel5618 Жыл бұрын
good JOb Sir. kindly upload some more video related jenkins with Aws
@JavaHomeCloud Жыл бұрын
Will upload soon
@roeikeisar Жыл бұрын
Thank you very much my friend!
@deepakkumarsahoo4812 Жыл бұрын
Nice one.
@thulasiramrudrappa63212 жыл бұрын
Thanks you sir
@martinthong125 Жыл бұрын
where to key in aws_session_token?
@chetansharma-wl9vf2 жыл бұрын
Where to find this code?
@nat70522 жыл бұрын
Can you share your pipeline code ?
@ayex862 жыл бұрын
The most terrible idea! You shouldn't help people do such thing! You have AWS cloud native tools like Code suite !
@JavaHomeCloud2 жыл бұрын
Appreciate it, Can you please post full details
@prathapcharan3 ай бұрын
It's there mate. But clients I have worked with are more interested in running code in Jenkins only as it's free of cost