The Amazon Web Services (AWS) private key file and certificate file work together to allow Elastic Bamboo to securely access AWS. It is different to the security mechanism provided by the AWS Secret Access Key and is required to enable certain features, such as EBS for elastic instances and the Amazon command line tools.

• 証明書ファイルには、AWS アカウントに関連付けられた公開キーが含まれています。このファイルは、(Bamboo サーバーではなく) Amazon で保管されています。
• The private key file contains the private key that is used to authenticate requests to AWS. This file must be stored on your Bamboo server, if you are using EBS for elastic instances or the Amazon command line tools.
• これらのファイルに含まれる公開キーと非公開キーの組み合わせが X.509 証明書になります。

The first time you use Elastic Bamboo, Bamboo will automatically generate the private key file and certificate file for you. The certificate file will be kept by Amazon (to inject into your elastic instances) and the private key file will be downloaded to your Bamboo server in your Bamboo Home directory. If you are setting up Elastic Bamboo on multiple Bamboo servers using the same AWS account, you can simply copy the private key file across from the original Bamboo server. You should not need to regenerate the private key file and certificate file unless your private key file is lost or corrupted.

If you do need to regenerate the private key file and certificate file, please follow the instructions in the Amazon X.509 Certificates documentation. The Amazon documentation also contains instructions on using your own certificate, if you wish.

Once the files are generated, you will be able to download them (see screenshot below). We recommend that you store the files in the Home directory of your Bamboo server.

Screenshot above: Downloading the generated AWS private key file and certificate file