Categorías: Todo - collaboration - communication

por Rodrigo Arem hace 1 año

81

AWS

In the evolving landscape of technology, both hard and soft skills are essential for success. Technical competencies, such as expertise in AWS services like S3, EC2, and Lambda, and familiarity with containerization tools like Docker and Kubernetes, are crucial.

AWS

Soft Skills

Atitude de Dono

Paixão por desafios

Engajamento

Trabalho em equipe

Comunicação Verbal e escrita

People

Colaboração

Ter atitude positiva diante dos desafios

Confiança

Empatia

Proatividade

Hard Skills

AWS

Type in your organization's name

ECS

Task Definition
Daemon Scheduling
NLB

EKS

Fargate
Node Group
ECR
AMI - Golden Images
Target Groups
CLI K8S

Databases

DynamoDB
Redshift
ElastiCache
RDS

Add a critical supplier for your organization

Where would failure in the supply chain cause significant problems?

These suppliers should be referenced in the risks section, and you should have a recovery strategy to cope with problems with your suppliers.

Storage

Glacier
EBS
Storage Gateway
S3

Add a core service or function

Core services are the ones that are critical to the survival of your organization - the ones without which you would not have customers or business.

These services or functions should be the first to be recovered in the event of a disaster.

Network and Content Delivery

Route 53
Cloud Front

Compute

EC2
ALB
SG
Launch Templates
ASG
ELB
Lambda

Add a team member

Ensure that you have representation for:

Management

CloudTrail
Cloud Watch

Add a milestone for your business continuity planning project, and set dates.

Think about:

Security and Identity

KMS
VPC

Add a critical staff member

Critical staff members are the ones on whom you will depend when a major incident occurs.

You will need to ensure that your critical staff members are trained and can be easily contacted.

Make sure that a copy of the contact list is kept off-site.

Route Tables
Shared Endpoints
VPC Endpoints
Subnetes
WAF
IAM

Who needs to be trained in your emergency procedures?

Consider:

Aplication Services

API GW

Add a communication audience

Who will you need to communicate parts of your plan to? Who needs to take action, stay informed or be reassured?

Consider:

VPC Link

What action will you take to communicate with 'API GW'? What will they need to know?

Think about:

Messagins

SNS
SQS

Add a location where you have people, assets, and operations that will be covered by your plan.

Jornada MicroService

CI/CD
Gitlab
Codebuild
CodePipeline
Argocd
API Swagger
ArgoRollouts
Logs | Event
Fluentd
Keda
Observability
Prometheus
AppDynamics
Kiali
Servicd Level Indicator
CloudWatch
Splunk
Kibana
Dynatrace
ElasticSearch / Opensearch
Grafana
IAC
Ansible
Helm
yaml | json
CloudFormation
Terraform

Add a operations' risk that may affect your business.

Think about:

Docker
Dockerfile
Compose

Add a IT risk that may affect your business.

Think about:

ServiceMesh
Istio - Objects

Add a physical risk that may affect your business.

Think about:

Istiod

Gateway

Virtual Services - Request Routing

DestionationRules - Traffic Shifting

Circuit Break

Authentication Policy ?

Retry Policy

Egress

Envoy Sidecar

Istio Operator

Chart/Istio

Add prevention measures

Kubernetes
Objects

Add a business risk that may originate from your staff.

Think about:

Deployments

Service

ConfigMap

Rbac

DaemonSet

StateFulset

Probe

Readiness

Liveness

What is the impact of "Objects" on your business? What level of resources is appropriate for dealing with it and recovering from it?

Rate the impact by clicking an icon:

Major- poses a critical risk to business

Survivable - causes problems that can be fixed

Minor - no recovery action needed

Namespace

Operator

HPA

Pod

Secret

Ingress