1091235 - Provide AWS Credentials In Support Of MasterFirefox OS Account

Status: RESOLVED FIXED

(Infrastructure & Operations :: Infrastructure: Other, task)

Description

[Ben (:bensternthal)]

As discussed in our meeting today please provide AWS keys in support of the MasterFirefox OS project. These would be a sub account of Air Moz

We would also like some guidance on billing/costs, for example we need guidelines on instances and/or how much usage.

Comment 1

[Ben (:bensternthal)]

Can we get an ETA on these. Development is blocked by this task.

Comment 2

[Philippe M. Chiasson (:gozer)]

Wrong bucket, AWS credentials are provided by Infra

Comment 3

[Philippe M. Chiasson (:gozer)]

I need to know which GPG key to use to send this to you.

(1)     Benjamin Sternthal <[e-mail]>
          2048 bit RSA key 0x502BF8973F1CB48A, created: 2014-01-10, expires: 2018-01-10
(2)     Benjamin Sternthal <[e-mail]>
          4096 bit RSA key 0x88A755188C0B4009, created: 2013-10-17, expires: 2017-10-17

Comment 4

[Ben (:bensternthal)]

Please use the Jan 10th one. Also include Josh Mize.

Comment 5

[Philippe M. Chiasson (:gozer)]

(1)     Josh Mize <[e-mail]>
          2048 bit RSA key 0x1270D0FA485BDE07, created: 2013-07-29
(1)     Benjamin Sternthal <[e-mail]>
          2048 bit RSA key 0x502BF8973F1CB48A, created: 2014-01-10, expires: 2018-01-10

You should seriously consider getting your keys verified and signed by other Mozillians, would have made the discovery process easier.

Delivered via e-mail:

Message-ID: <[e-mail]>
Date: Tue, 11 Nov 2014 13:30:23 -0500
From: "Philippe M. Chiasson" <[e-mail]>
To: [e-mail], [e-mail]
Subject: Bug 1091235

Comment 6

[Josh Mize [:jgmize]]

(In reply to Philippe M. Chiasson (:gozer) from comment #5)
> (1)     Josh Mize <[e-mail]>
>           2048 bit RSA key 0x1270D0FA485BDE07, created: 2013-07-29
> (1)     Benjamin Sternthal <[e-mail]>
>           2048 bit RSA key 0x502BF8973F1CB48A, created: 2014-01-10, expires:
> 2018-01-10
> 
> You should seriously consider getting your keys verified and signed by other
> Mozillians, would have made the discovery process easier.
> 
> Delivered via e-mail:
> 
> Message-ID: <[e-mail]>
> Date: Tue, 11 Nov 2014 13:30:23 -0500
> From: "Philippe M. Chiasson" <[e-mail]>
> To: [e-mail], [e-mail]
> Subject: Bug 1091235

:gozer, I've lost the private key associate with the message you sent. Would you mind resending to my Mozilla email account using the public key I have registered on https://keybase.io/jgmize and tell me where I should go to register it so that it's more easily discovered by Mozillians?

Comment 7

[Philippe M. Chiasson (:gozer)]

$> gpg --keyserver gpg.mozilla.org --send-key 0xDBB176AA98945BFE
gpg: sending key 0xDBB176AA98945BFE to hkp server gpg.mozilla.org

Comment 8

[Josh Mize [:jgmize]]

:gozer,

Thanks, I was able to decrypt your attachment, but when I attempted to log in to the mozilla-infra aws console with the credentials provided, I got a message that I needed to change the password before I could continue, but when I attempted to do so I got the following error message:

User is not authorized to perform iam:ChangePassword.

Can you either remove the need for me to change the password (preferred) or grant the account the iam:ChangePassword permission?

Comment 9

[Ben (:bensternthal)]

Is this still outstanding, if so can you work with Gozer to resolve.

Comment 10

[Josh Mize [:jgmize]]

(In reply to Ben (:bensternthal) from comment #9)
> Is this still outstanding, if so can you work with Gozer to resolve.

Yes, I just verified that the situation is the same as I described in comment #8. :gozer can you help with this?

Comment 11

[Brian Hourigan [:digi]]

> Yes, I just verified that the situation is the same as I described in
> comment #8. :gozer can you help with this?

Hi Josh

I checked and 'Allow users to reset their own password' is enabled, but your policy seems to forbid access to iam:*. I'd rather not changing it without understanding why.

I edited your account and removed the requirement for you to reset your password on the next login, so you should effectively be able to access your account immediately.

Comment 12

[Josh Mize [:jgmize]]

Thanks :digi, I can log in to the AWS console now.