mozilla / awsboxen Goto Github PK

The way that defaults and profiles are merged together to produce the final CFN config is very ad-hoc and non-obvious. We should put together a couple of example use-cases and then re-think how the merging is done to make the results obvious in these cases.

Per mozilla/fxa-deployment#19 it's possible for our polling to trigger rate-limiting logic in the AWS API. We should transparently handle this with appropriate backoff etc.

Prerequisite is a per-Region base AMI.

Generally, it would be nice to be able to select a specific region in awsboxen.
Default is currently East, which is a bit overcrowded with Persona stuff.
So, either force it to US West (Oregon) or add the support for the region option (similar to what AWSBox does)

CFN generates a stream of events telling you about the progress of stack creation. We should read this and print out interesting events to the console, so the user has a better idea about what's going on.

This will also be useful for debugging errors, since e.g. ROLLBACK_IN_PROGRESS events come with an error description.

@warner can you please work whatever magic you did on the picl-deployment repo on this one as well, so that I can e.g. edit the project description and that sort of thing?

Automatically make it easy for ops to figure out who owns what, and what they should do with it.

AWS is chock-full of busted freezer instances, because they don't get torn down if something goes wrong during the build. They should be configured to self-terminated in, say, 24 hours after boot.

We currently assume that the user's awsbox deployment key is already uploaded to AWS. That's not guaranteed. We should add some logic to check for this and upload it if necessary.

E.g. exactly how do we freeze an AMI from awsbox?

awsboxen list
used to include the following:
scrypt-accounts-dev-lcip-org
scrypt-accounts-latest-dev-lcip-org
logs-dev-lcip-org

Now, it does not list them at all.
awsboxen info ETC
still works!

IRC clip for reference:

15:12 < jbonacci> rfkelly have you tried "awsboxen list" lately?
15:12 < jbonacci> defaulting to us-east-1 
15:12 < jbonacci> the Dev stacks no longer show up in the list
15:12 < jbonacci> although they do exist in AWS console
15:12 < jbonacci> fascinating
15:13 < rfkelly> jbonacci interesting; which dev stacks?
15:14 < jbonacci> scrypt-accounts-dev-lcip-org
15:14 < jbonacci> scrypt-accounts-latest-dev-lcip-org
15:14 < jbonacci> logs-dev-lcip-org
15:14 < jbonacci> oldsync-dev-lcip-org
15:14 < rfkelly> jbonacci oh, cloudformation webui has had a facelift
15:15 < jbonacci> rfkelly yep, although your "info" command still works
15:15 < rfkelly> jbonacci smells like a bug, maybe due to some small API tweak - please file a bug against awsboxen repo
15:20 < jbonacci> ok

I just tried to follow the instructions in the tutorial and I get the following error:

ERRORE FATALE: failed to describe security groups: An internal error has occurred

So that we don't leave orphansed snapshots or out-of-date AMIs lying around indefinitely