On Thu, Dec 12, 2019 at 6:29 AM Chris Kilding <[email protected]> wrote: > 1. Does it support storing the AWS Endpoint Configuration (service endpoint, > signing region)?
What is currently defined: https://javadoc.jenkins.io/plugin/aws-global-configuration/io/jenkins/plugins/aws/global_configuration/CredentialsAwsGlobalConfiguration.html > 2. Should plugins inherit their AWS SDK Maven dependency from the Global > Configuration plugin, or should they redefine their SDK dependency in their > own POMs? Inherit, optionally declaring an explicit dependency on a newer version of the `aws-java-sdk` plugin. > 3. Can it do anything that IAM instance profiles cannot? I am not sure I understand the question. `aws-global-configuration` does not “do” much of anything, it is just a common place to keep settings. For example, `artifact-manager-s3` defines its own settings for S3 buckets but relies on `aws-global-configuration` to define credentials. > I imagine that most Jenkins servers on AWS would inherit their AWS config > implicitly from the IAM instance profile. Yes, that is typical. Or in the case of EKS, I have not personally tried it but I presume via https://aws.amazon.com/blogs/opensource/introducing-fine-grained-iam-roles-service-accounts/ -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr0dE5rSPrkhxcRsTw%2B%3DPqdXXVOMQoGRCryDkDcQzxY1HQ%40mail.gmail.com.
