anarquias

MySQL

Getting started

AWS ECS setup

aws ecs help

echo $AWS_DEFAULT_PROFILE aws configure --profile andrew aws ec2 describe-instance-status --profile andrew --instance-ids i-81c24938

AWS CLI Cheatsheet

http://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html https://www.youtube.com/watch?v=_wiGpBQGCjU

Setup

A few tips for OSCP

Doing all of the exercises is important since you will discover low-hanging fruit from the labs based on the recon you do with the different tools in the exercises.
Be wary of doing full /24 range port scans, especially for anything more than a few TCP ports. The machines might be in all sorts of broken states left by students etc.
When starting to recon a specific machine:

Revert
Port scan
Try to identify services

Those steps in that order are important. You want a fresh state for the machine and you want to do just simple port scanning first because doing nmap's service scanning or nse scripts might send payloads that actually crash services. So be careful.

0.1. References
0.2. Other cheatsheets
0.3. Manage multiple gcloud config configurations
- 0.3.1. Switch gcloud context with gcloud config
0.4. Credentials
0.5. info
0.6. projects
0.7. zones & regions
0.8. Organization
0.9. billing

	#!/bin/bash
	yum install -y aws-cli
	aws s3 cp s3://yours-ecs-config/ecs.config /etc/ecs/ecs.config
	echo ECS_CLUSTER= cluster-name-demo >> /etc/ecs/ecs.config

	CI & CD:
	========
	2 core software development processes
	CI process of automating regular code commits followed by an automated build and test process designed to highlight intergration issues early.
	Additional tooling and functionality provided by Bamboo, CruiseControl, Jenkins, Go and TeamCity etc.
	workflow based
	CD takes the form of a workflow based process which accepts a tested software build payload from a CI server. Automates the deployment into a working QA, Pre-prod or Prod environment.
	AWS CodeDeploy and CodePipeline provide CI/CD services
	Elasticbeanstalk and CFN provide functionality which can be utilized by CI/CD servers.

	1. In AWS batch, you are able to specify minimum, maximum and desired number of CPU's.
	2. Amazon EBS-backed EC2 instances boot faster than instance store-backed instances.
	3. The operating system offered in Amazon Light sail are Amazon Linux and Ubuntu.
	4. AWS Elastic beanstalk is used to spin up infrastructure that is both externally facing and internally facing.
	5. SSD-backed Amazon EBS gives you low latency.
	6. AWS can only create latency record sets in the AWS region, not in customer location.
	7. The only routing protocol that AWS Direct Connect supports is BGP.
	8. A private VIF is the logical interface between your on-premises network and AWS resource located in VPC.
	9. Cloud front will forward a file to a user as soon as it get it's first bytes. It does no error checking.
	10. Origin access identity (OAI) is used to restrict access to your Amazon S3 content.

	Autoscaling.
	◾Understand autoscaling inside and out.
	◾Make sure you know the differences between deploying with and without Cloudformation (as there are some deployment methods you can do with Cloudformation that you can’t without) and the command or JSON syntax to perform them.
	◾Understand lifecycle hooks and the autoscaling stages they run in
	◾Understand launch configurations and how they work and are updated (hint: You must replace them)
	◾Understand why you may need to place an instance into STANDBY state

	•Elastic Beanstalk.
	◾You’ll need to know this to an advanced level.
	◾Understand what stacks Beanstalk supports natively and how you would deploy a stack it doesn’t (hint: Use Docker).