Their pricing presumes familiarity with how I'll use it, but the original pain that's driving me in this direction is "I want to make sense of my @awscloud CloudTrail logs." I think not having an explicit "contact us for Enterprise Pricing" CTA is a misstep.
I think detecting the region from which a customer is signing up would be a nice feature, but they may have a reason to prioritize the Europe region.
I click the button and nothing happened. I barely noticed an "email sent" popup at the bottom of the screen. This is a questionable UX decision.
I bias for "make the customer happy as soon as possible, get the rest of their contact info later." I also don't sell SaaS so what do I know?
Security is critically important for things like "my audit logs," so "your password is too strong" erodes confidence.
Having removed any periods and @ signs, I come up with a password that meets the unstated requirements. Onwards!
...and the wheels kinda fall off here. "Use a node runtime that started the deprecation process back in July, and click all this stuff in the console" vs. "deploy this CloudFormation stack" suddenly makes me question how committed to this I really am.
I'm going to soldier onward, but with my "shitposting" @awscloud account that contains no sensitive information whatsoever instead of the account I actually want CloudTrail analysis for.
Okay, this is the way to go, clearly. I do think including it in the onboarding flow is a bit more scalable than "the CEO tweets along with your shenanigans" but again, I do not sell SaaS so what do I know?
The "click here to get to the Serverless Application Repository" link takes me to eu-central-1. I blithely change it back to the Sad Region (Ohio) and solidier onward.
I assure you @coralogix that I am remarkably authentic.
This presupposes a model in which CloudTrail isn't a holistic thing but rather specific to a component of an application. I don't think I agree because that can get spendy on the AWS side.
I click the "Deploy" button (ClickOps for the win!) and Lambda console go brrrrrr.
Looks like the runtime is sensible, the docs in the onboarding just lag. I get it.
And a cup of coffee later, we've got logs in @coralogix!
Let's go exploring.
#awswishlist I'd like to apply a tag to an existing CloudFormation stack, preferably via ClickOps.
Hmm. Got logged out, it didn't like the password I'd painstakingly handcrafted, so I whacked the password reset link. It has been ~5 minutes and no email yet.
Emailed the CSE who emailed me. I'll pick this back up once I can get back into @coralogix...
It got reset, and I got back in. Then I picked up my iPad to continue this thread and... password invalid.
Either 1Password is messing with me or there's something very "odd" about the @coralogix login flow.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
Despite a weird transient Google SSO error, I'm now logged in and staring at an empty dashboard.
I have to google a bit to find the CloudTrail story and it's... well, half marks.
So from a bit of digging it looks like it's great at the ingestion nonsense. It'll reduce noise I don't care about (AWS Config checks and such), then shunt the now quieter stream to something I can use to visualize / work with the events.
Since a lot of friends seem to be getting MacBooks Pro, I will dump some of the things I do to set mine up as a former Grumpy *nix Admin(tm).
A thread...
I've been using vcsh (github.com/RichiH/vcsh) for years to manage my dotfiles. I'm redoing my zsh config this break to remove over a decade of cruft. Early returns are looking promising.
# This function means `cdf` changes directory to that of your frontmost Finder window.
cdf() {
target=`osascript -e 'tell application "Finder" to get POSIX path of (target of front Finder window as text)'`
cd "$target"
}
Dave Brown is the VP of EC2 at AWS, which is too many acronyms. He declines to address the platypus in the room.
"So you run all of @awscloud EC2. I'm not saying that's a high stress job, but you *are* only 22 years old. How do you live with that kind of pressure?"
@primitivetype: "Maybe in hex. The trick is to have an amazing team."
Here's an unexpected thread from me; I never expected to write one quite like it...
A while back I had @ajyawn on the podcast, where he talked about @bytechek with me. It was a great episode, and I came away impressed by what AJ was doing. buff.ly/3pYnCGO
When I saw this tweet from him, I reached out to AJ with a "sounds like someone raised a funding round, and congratulations are in order." This isn't my first rodeo when it comes to reading the tea leaves.
I was excited enough about what @bytechek does (helps companies get to SOC2 compliance quickly, because I am a nerd as well as a former SOC2 control owner) and about @AjYawn as a person that I asked whether I could invest as well.
Because this is incredibly dense and technical, let me try to simplify it. I'm sure I will be condescendingly corrected if I get this wrong...
"We made a change internally that caused a bunch of internal things to become extremely chatty, like AWS employees defending the company if someone says something even slightly unflattering on Twitter."
So a question I posed in slack.lastweekinaws.com led to an unfortunate realization on my part:
@awscloud is too big, and has too many customers for the overall good of society.
"Well were things more reliable before @awscloud?" No! Good lord no! The difference is that I could have a bad day and take down a hospital. AWS has a bad day and takes down all the hospitals.
It's the simultaneous outage of everything that's the problem.
The worst part is that I don't even have the slightest clue how to fix it. You can plan and plan and plan around this. You can build out multi-region or multi-cloud until the cows come home.
And then one of your third parties did none of this and you're just as down.