surajkota

import kfp
from kfp import components
from kfp import dsl
from kfp.aws import use_aws_secret

# Replace the argument with path to the component file or use load_component_from_url() method
sagemaker_model_op = components.load_component_from_file("../../model/component.yaml")

# Replace the argument with path to the component file or use load_component_from_url() method
sagemaker_deploy_op = components.load_component_from_file("../../deploy/component.yaml")

cloudbow

function first_names() {

### Pass the paramters before you execute 
export CLUSTER_NAME=${CLUSTER_NAME}
export AWS_REGION=${REGION}
export AWS_DEFAULT_REGION=${AWS_REGION}
}

## Set account id settings
function aws_account_id_settings(){

kislayverma

I was at Amazon for about six and a half years, and now I've been at Google for that long. One thing that struck me immediately about the two companies -- an impression that has been reinforced almost daily -- is that Amazon does everything wrong, and Google does everything right. Sure, it's a sweeping generalization, but a surprisingly accurate one. It's pretty crazy. There are probably a hundred or even two hundred different ways you can compare the two companies, and Google is superior in all but three of them, if I recall correctly. I actually did a spreadsheet at one point but Legal wouldn't let me show it to anyone, even though recruiting loved it.

I mean, just to give you a very brief taste: Amazon's recruiting process is fundamentally flawed by having teams hire for themselves, so their hiring bar is incredibly inconsistent across teams, despite various efforts they've made to level it out. And their operations are a mess; they don't really have SREs and they make engineers pretty much do everything,

lizthegrey

default['sshd']['sshd_config']['AuthenticationMethods'] = 'publickey,keyboard-interactive:pam'
default['sshd']['sshd_config']['ChallengeResponseAuthentication'] = 'yes'
default['sshd']['sshd_config']['PasswordAuthentication'] = 'no'