# Aws.yml layout and security of accesskey and secret key?

**URL:** <https://www.ruby-forum.com/t/aws-yml-layout-and-security-of-accesskey-and-secret-key/92877>\
**Category:** Rails\
**Created:** [April 25, 2007, 10:35am UTC](https://www.ruby-forum.com/t/aws-yml-layout-and-security-of-accesskey-and-secret-key/92877 "2007-04-25T10:35:59Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![adammontgomery](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/ce7236/32.png) [@adammontgomery](https://www.ruby-forum.com/u/adammontgomery)\
**Post date:** [April 25, 2007, 10:35am UTC](https://www.ruby-forum.com/t/aws-yml-layout-and-security-of-accesskey-and-secret-key/92877/1 "2007-04-25T10:35:59Z")

</div>

I have a aws.yml fill in a similar fashion to database.yml. There are  
staging, production areas, which include instance\_url, keypair\_name, see  
below. Im not storing this in svn, but copying across the file with cap  
on the after\_setup callback.

So the reason for the topic; I wanted to get some feedback on the  
security of this approach. Also, what is everyone else doing in the way  
of layout for their aws.yml files.

cheers  
adam

#-----------------------

# aws global settings

#-----------------------  
aws: &aws  
access\_key: ------  
secret\_access\_key: --------  
account: --------

#-----------------------

# environment settings

#-----------------------  
staging:  
keypair\_name: staging------keypair  
id\_rsa: “~/.ec2/id\_rsa-staging-------keypair”  
instance\_url: not-yet-defined  
s3:  
download\_bucket: -----  
static\_bucket: ----  
artwork\_bucket: ------  
\<\<: \*aws

production:  
keypair\_name: ------keypair  
id\_rsa: “~/.ec2/id\_rsa------”  
instance\_url: domU-------------  
s3:  
download\_bucket: -----  
static\_bucket: ----  
artwork\_bucket: ------  
\<\<: \*aws