Lately, we figured out how this will work. Steps to configure this correctly.
1. Create a new credential in Jenkins of a kind "AWS Credentials". 2. Add "IAM Role to use" as the IAM role that needs to be assumed. 3. Create a new Amazon EC2 configuration in "Configure Clouds". Use the credential created in step 2 in the "Amazon EC2 Credentials" field. 4. Configure EC2 general instance configuration. Thanks On Friday, 18 December 2020 at 18:24:36 UTC+5:30 Paritosh Anand wrote: > Hi, > > Lately, I have been trying to figure out how to configure EC2 cloud to > launch slave nodes in another AWS account. > > Seems the plugin is unable to successfully locate the AMI and security > groups from the other account. > > Why am I doing this ? > Recently our organisation got merged with another, and we are trying to > unify the Jenkins platform to support CI for all the projects. > We do use the EC2 plugin to dynamically launch nodes based on the > workload. Hence, wish to extend the same for the sister organisation. > > Any help will be much appreciated. :) > > Thanks. > Paritosh > -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/9797f13f-d0bd-4f77-bed3-39c03323d26an%40googlegroups.com.
