Okay.
There are a lot of "Ask the @awscloud expert" options at the #AWSsummit today.
In this thread, it's "ask the @awscloud incompetent" instead.
Hit me with your cloud questions, and I will answer them poorly.
There are a lot of "Ask the @awscloud expert" options at the #AWSsummit today.
In this thread, it's "ask the @awscloud incompetent" instead.
Hit me with your cloud questions, and I will answer them poorly.
You secure Kubernetes by running it on AWS. Since EKS supports Fargate, there's no infrastructure for you to manage, and thus absolutely nothing left for you to secure. Your days are free and easy unless you're in infosec; in that case you're starving to death instead.
You should only use Lambda when AWS has overshot its revenue goal for the quarter. Otherwise, it's EC2 all the way, and don't skimp on the instance sizing.
It's a near certainty that your "app" is a bunch of crappy npm libraries spackled together, so don't worry; you already have.
The Lambda can modify itself. It can use a database like Route 53. Or you can use RDS as a queue to maintain your state.
Grab the first thing you can find off of Stack Overflow. Next, post that to Twitter asking how to secure it.
Lastly, post with a second account something like "that's all you need to do!" The enraged answers will tell you what to do next.
Lastly, post with a second account something like "that's all you need to do!" The enraged answers will tell you what to do next.
If you're doing this on a budget, you round-robin deploy everything into a rotating array of fresh free-tier accounts.
If you're doing this with money to burn, I'd like to sell you my Enterprise Kubernetes offering called OpenShift.
If you're doing this with money to burn, I'd like to sell you my Enterprise Kubernetes offering called OpenShift.
Ghosts, obviously.
Whichever has the most posts on HackerNews that day; in reality you're just using the console and lying about it anyway like the rest of us.
It means AWS makes $40 billion of revenue a year.
You run your dangerous experiments in other people's unsecured AWS accounts.
For your existing account, the answer is a credit card chargeback. You may need to do this for several months.
For your existing account, the answer is a credit card chargeback. You may need to do this for several months.
There was a hit movie about this called jAWS.
You have summoned a demon. Because the summoning is done via CloudTrail, you may wish to go grab a snack first. Maybe watch a few episodes of something on Netflix before the demon gets here.
Two shakes of a CloudFront distribution update!
AWS has pre-removed them for you with their latest enhancement to Lambda.
It's now your duty to ooh and aah over this in countless tweets, Medium posts, and lines at Starbucks.
It's now your duty to ooh and aah over this in countless tweets, Medium posts, and lines at Starbucks.
That's a good start, but you should also make sure to pass messages via Pinpoint, Chime, Route 53, RDS, EC2 instance tags, CloudTrail logs, Keyspaces, EventBridge, an AppSync subscription, and IoT Events as well.
Start off running it on EC2. Have a pod running on EKS, and make sure that some of those workloads run on Fargate too.
Then, whenever people ask if you run with X architecture, the answer is a smug "Yes I do."
Then, whenever people ask if you run with X architecture, the answer is a smug "Yes I do."
For truly asynchronous tasks, I prefer TaskRabbit.
Roughly two months ago when their regions filled up and you couldn't get servers anymore.
This is the kind of thought-follower question that tells me that his resume isn't just a list of technologies and an 8x10 glamour shot as the cover letter.
You should already know your access patterns when using DynamoDB.
A bulk update implies you didn't know them, and thus the pain serves as an instructive teacher so you make better choices next time.
A bulk update implies you didn't know them, and thus the pain serves as an instructive teacher so you make better choices next time.
The Database Migration Service. You might think it doesn't support SimpleDB as a destination, but present AWS with this use case and let their blinding hatred for Oracle do the rest of the work for you.
Have a cron job run every minute that generates a random number. 1 time out of 1000 it does a `shutdown -h now`.
The default limit is 500 per account, but it can be raised.
The power play is to have the limit raised in multiple accounts. As long as you move the zone to a new account less than 12 hours from creating it, you won't get charged the 50¢ fee per zone per month.
This works.
The power play is to have the limit raised in multiple accounts. As long as you move the zone to a new account less than 12 hours from creating it, you won't get charged the 50¢ fee per zone per month.
This works.
If they're good at naming, "VMhere."
But they're AWS so probably "AmazonVMware Cloud on AWS by AWS Elastic Enterprise Container Service for Fargate on Kubernetes."
But they're AWS so probably "AmazonVMware Cloud on AWS by AWS Elastic Enterprise Container Service for Fargate on Kubernetes."
Lying on your resume that you have whichever one seems handy because honestly, nobody can be bothered to check.
For having the temerity to ask that question the CNCF has already put a bounty on your head.
Neal Stephenson made up a bunch of jargon in "Anathem" that almost makes perfect sense by the time the book was finished; the CNCF did that with project names.
Neal Stephenson made up a bunch of jargon in "Anathem" that almost makes perfect sense by the time the book was finished; the CNCF did that with project names.
It's Kubernetes because when you call a Large Successful Company's technology "legacy," they feel the chill of their own mortality working its way down their spine, and they hurl that Large Successful Checkbook at whatever they think will make it stop.
Because even though it won't solve the real problem, "the vendor screwed up" is always a better line than "I screwed up."
Via the magic of realizing that "autoscaling" is a term with no fixed definition, and success is just a better narrative away. You're probably already doing it!
The answer is of course IBM Cloud. They clearly think it's still the late 1980s; by the time they get around to invoicing for things you use in 2020 you'll be happily retired and long gone.
The one that I just uploaded. Its only difference from the community version is the surcharge I tack on.
I don't recognize the term, so I can only assume it's a new Javascript framework. Don't worry; Lambda has you covered.
Customer obsession, impressive scale, eternal APIs, sarcastic number of services, management via horsewhip, otherworldly durability, terrible naming, a surprise in your bill every month, solving hard problems, ignoring easy problems, twerking backwards, pushing the envelope.
Sticking them with the bill.
Because when every query you run is a full table scan, you need another knob to turn that won't fix the problem.
