aws

EBS Volumes Storage volumes you can attach to your EC2 instances. Mission Critical 🟢 production workloads. designed for mission critical workloads 🟢 highly available. automatically replicated within a single AZ to protect against hardware failures. 🟢 scalable. dynamically increase capacity and chnage the volume type with no downtime or performance impact to your live systems. EBS Volume Types: Solid State Disk General Purpose SSD (gp2) - legacy 3 IOPS per GiB, up to maximum of 16,000 IOPS per volume regardless of how large the volume is, the maximum number of input/output operations the storage system can handle for that volume is 16,000 per second....

S3 is Object-Based Storage Manages data as objects rather then in file systmes or data blocks. Upload any file type you can think of to S3. Examples include photos, videos, code, documents, and text files. Cannot be used to run an OS or DB. S3 Basics Unlimited storage. The total amount of data and the number of objects you can store is unlimited. Objects up to 5 TB in Size. S3 objects can range in size from a minimum of 0 bytes to a maximum of 5 TB....

Virtualization The technology that lies at the core of all cloud operations is virtualization. Virtualization lets you divide the hardware resources of a single physical server into smaller units. That physical server could therefore host multiple virtual machines (VMs) running their own complete operating systems, each with its own memory, storage, and network access. a virtual machine host Cloud Computing Major cloud providers like AWS have enormous server farms where hundreds of thousands of servers and disk drives are maintained along with the network cabling necessary to connect them....

Traefik v1.7 is running within a Docker Swarm, functioning as a global service. Consequently, an instance of Traefik is deployed for each host within our Docker Swarm cluster. It is important to note that the Swarm’s routing mesh is not employed in this setup. Instead, the port mode is configured as “host,” allowing the port to be attached to the host’s network. traefik: image: ${REGISTRY}/traefik:1.6 build: ./traefik volumes: - /var/run/docker.sock:/var/run/docker.sock networks: - traefik environment: - AWS_ACCESS_KEY_ID=${AWS_ACCESS_KEY_ID} - AWS_SECRET_ACCESS_KEY=${AWS_SECRET_ACCESS_KEY} - AWS_REGION=${AWS_REGION} - AWS_HOSTED_ZONE_ID=${AWS_HOSTED_ZONE_ID} ports: - target: 80 published: 80 protocol: tcp mode: host - target: 443 published: 443 mode: host protocol: tcp - target: 8080 published: 8080 mode: host protocol: tcp deploy: mode: global restart_policy: condition: on-failure Docker Swarm deployed to AWS and lives behind internal/external load balancers (Classic type)....