AWS Writeup - Revision history

Admin: /* Advanced */

2018-03-05T23:12:08Z

Advanced

← Older revision		Revision as of 23:12, 5 March 2018
Line 17:		Line 17:
	Basic security tenets -		Basic security tenets -

	Machine tricks - if you want to attach an existing instance to a VPC, or run it on beefier hardware, or etc., create an AMI (image) from the machine (creates a snapshot); wait for the snapshot to complete; spin up a new AWS node from the snapshot, with the hardware/networks that you desire		Machine tricks - if you want to attach an existing instance to a VPC, or run it on beefier hardware, or change regions, or etc., create an AMI (image) from the machine (creates a snapshot); wait for the snapshot to complete; spin up a new AWS node from the snapshot, with the hardware/networks that you desire

	Scaling upward: how can I automate this process? (Quote: "if you're SSHing into a machine, your automation is broken.")		Scaling upward: how can I automate this process? (Quote: "if you're SSHing into a machine, your automation is broken.")

Admin: /* Advanced */

2018-03-05T23:10:32Z

Advanced

← Older revision		Revision as of 23:10, 5 March 2018
Line 23:		Line 23:
	Netdata for basic monitoring - bind to IP address, links in with networking		Netdata for basic monitoring - bind to IP address, links in with networking

	SSH keys ~~and~~ identity management - ~~how to share~~ a ~~network~~		SSH keys - identity management - sharing resources with others (i.e., a VPC)

Admin: /* Advanced */

2018-03-05T23:09:59Z

Advanced

← Older revision		Revision as of 23:09, 5 March 2018
Line 13:		Line 13:
	Nomenclature - elastic means scalable (absorbs big increase in traffic)		Nomenclature - elastic means scalable (absorbs big increase in traffic)

	Networking~~: vpc~~, subnets~~, etc.~~, connecting via VPN		Networking - VPCs, subnets, connecting via a VPN, can only attach at time of setup; networking patterns, single private/single public, single public, etc.

	~~Scale upward: how can I automate this process? (Quote: "if you're SSHing into a machine, your automation is broken.")~~		Basic security tenets -

	Netdata		Machine tricks - if you want to attach an existing instance to a VPC, or run it on beefier hardware, or etc., create an AMI (image) from the machine (creates a snapshot); wait for the snapshot to complete; spin up a new AWS node from the snapshot, with the hardware/networks that you desire

			Scaling upward: how can I automate this process? (Quote: "if you're SSHing into a machine, your automation is broken.")

			Netdata for basic monitoring - bind to IP address, links in with networking

	SSH keys and identity management - how to share a network		SSH keys and identity management - how to share a network

Admin: Created page with "==Basics== Costs, scheduling, and utilization Network, transfer of data, storage Storage hierarchies - saving and archiving Elastic file storage vs S3 ==Advanced== Nomen..."

2018-03-03T09:18:53Z

Created page with "==Basics== Costs, scheduling, and utilization Network, transfer of data, storage Storage hierarchies - saving and archiving Elastic file storage vs S3 ==Advanced== Nomen..."

New page

==Basics==

Costs, scheduling, and utilization

Network, transfer of data, storage

Storage hierarchies - saving and archiving

Elastic file storage vs S3

==Advanced==

Nomenclature - elastic means scalable (absorbs big increase in traffic)

Networking: vpc, subnets, etc., connecting via VPN

Scale upward: how can I automate this process? (Quote: "if you're SSHing into a machine, your automation is broken.")

Netdata

SSH keys and identity management - how to share a network