Verify mofosecure AWS account is production-ready

RESOLVED FIXED

Status

RESOLVED FIXED
4 years ago
3 years ago

People

(Reporter: johns, Assigned: johns)

Tracking

Details

(Assignee)

Description

4 years ago
Ensure all limits are acceptable. 
Ensure no traffic limitation exists.
Ensure AWS is aware of the purpose and ownership.
If possible, tie support to this account as well to ensure speedy service.

Emailed this to leo:
Hello Leo!

I'm checking in because this weekend, we're launching a failover component to Blue State Digital.  I'm doing so in a PCI-compliant AWS account to ensure scoping isn't applied to our typical apps.
(New account: 318526611700 owned by Devops@mozillafoundation.org)

I wanted to check in to see if we could verify that we're truly ready for production here.

1) Can you please verify that no traffic/bandwidth limits apply to this account?  We expect a ton of traffic, and absolutely cannot have it interrupted.
2) Is there a way to connect this to our normal mofo account, so as to allow for very fast support service?  Of all the accounts we'd want prompt responses on, it would be this one over the holidays.
3) How can I verify that Simon Wex and Jon Buckley, copied on this email, have administrator level access and are able to make account decisions?  Any shortcut or process there I should know about?
4) Can we please attach you as SA to this account?

Thanks Leo, I know this one is out of left field, but as a veteran of BSD, you know how it is.  :)

Thanks,
JP Schneider
(Assignee)

Comment 1

4 years ago
* Leo confirmed we would not hit any limits with usage.  The defaults for infra are fine.
* I've created AWS ticket, under MoFo but referencing mofosecure, so if we need it, they already have all the info pre-set: AWS Case: 1291072661
(Assignee)

Updated

4 years ago
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
(Assignee)

Comment 2

4 years ago
Well, this wasn't really ready, actually!  We are not yet able to use an SSL cert for all clients.  I expect this will be resolved in 24h.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(Assignee)

Comment 3

4 years ago
The limits have been raised, and the SSL work is being done behind the scenes at AWS.
Status: REOPENED → RESOLVED
Last Resolved: 4 years ago4 years ago
Resolution: --- → FIXED

Updated

3 years ago
See Also: → bug 1232126
You need to log in before you can comment on or make changes to this bug.