Page Comparison

The AWS Security Credentials need to be specified for each task currently, which can be cumbersome quickly. Pending a more generic solution, it is already possible to ease this As of release 2.4, Tasks for AWS integrates with Identity Federation for AWS (Bamboo) to provide shared AWS Security Credentials management.

Include Page

	_IFAWSNoChargeNote
	_IFAWSNoChargeNote

Panel

bgColor	#eeeeee

On this page:

Table of Contents

AWS Credentials Sources

This results in two option for providing AWS Security Credentials:

Tip

title	Federated Amazon Web Services access

This is the recommended approach to share and manage AWS credentials:

It provides benefits like easy credentials sharing and reuse, fine grained access control for AWS resources, strong encryption and more (please refer to the Identity Federation for AWS Documentation for more information regarding the available features and implied advantages).

Image AddedPlease refer to the Identity Federation for AWS Administrator's Guide for details on how to configure the connectors.

this option requires at least one AWS Connector to be configured with System Scope to allow usage from Bamboo builds, where no user session is available
a connector yields a set of temporary credentials on task execution (optionally limiting the IAM permissions)
you can configure multiple connectors to provide credentials with different IAM permissions tailored for specific use cases

Note

title	No Real Encryption

This is not recommended, but easy to get started with:

The common pair of AWS security credentials (an AWS Access Key Id and an AWS Secret Key) is entered directly in each task and persisted after being processed with the Bamboo EncryptionService API.

Insert excerpt

	_BambooEncryptionServiceAPINote
	_BambooEncryptionServiceAPINote
nopanel	true

Image AddedIf you prefer this solution, you might still want to ease credentials reuse a bit via variable substitution as follows:

configure Access Key and Secret Key as e.g. ${bamboo.awsAccessKeyPassword} and ${bamboo.awsSecretKeyPassword}
define plan and/or global variables for the configured variable names (i.e. awsAccessKeyPassword and awsSecretKeyPassword given this example) with the actual credentials, which will then be substituted on task execution accordingly

Include Page

	_ChinaRegionsNote
	_

CNRegionsNote

ChinaRegionsNote

Include Page

	_GovCloudRegions
	_

CNRegionsNote

GovCloudRegions