Before rolling out an instance of beetmover, that's supposed to transfer our nightly builds artifacts to S3, we need some staging bucket to push to while we work on date branch. Please let me know if there's any other information you need from our side. Thanks!

Just to be clear, this is supposed to be a staging bucket, as our nightly builds from date are still in the testing phase. This is particularly useful for us in order to flip that bit eventually and compare our newly TC-migrated nightly builds against our currently BB ones. I expect once we have a full migration and we're moving to inbound/central out of date branch, this bucket can be decommissioned.

Do you want this bucket to live in our production AWS account, where we manage it or do you want access to our dev account where you can manage it yourself? Are these artifacts served to end users in this iteration or is this just for testing?

(In reply to Jeremy Orem [:oremj] from comment #2) > Do you want this bucket to live in our production AWS account, where we > manage it or do you want access to our dev account where you can manage it > yourself? Dev account would be the best for now since we're planning on ditching it later. > Are these artifacts served to end users in this iteration or is this just > for testing? this is just for testing, no artifacts are to to be served to end users from this bucket. Once testing is over, we'll most likely request a separate production bucket and ditch this one.

In that case, check out https://mana.mozilla.org/wiki/display/SVCOPS/Requesting+A+Dev+IAM+account+from+Cloud+Operations Once you are issued an account, you will be able to generate an S3 bucket and API credentials.