Module 5

All about AWS Compute Services

LogoModule 6 | AWS Cloud Foundations

Compute service Category differences

EC2 AMI's

LogoModule 6 | AWS Cloud Foundations

EC2 Image Builder

Essentially like a pipeline. Tell it that it will create a new image every Friday

EC2 Image Builder automates the creation, management, and deploymentof up-to-date and compliant golden VM images.

  • Provides a graphical interface to create image-building pipelines

  • Creates and maintains Amazon EC2 AMIs and on-premises VM images

  • Produces secure, validated, and up-to-date images

  • Enforces version control

EC2 Storage

  • Instance store is temporary. Just like memory it will be wiped once the instance is stopped

  • EBS is attached like a Hard Drive

  • EFS/FSx is used a like a network file share. It can be attached to multiple instances

LogoModule 6 | AWS Cloud Foundations

EFS/FSx

Amazon FSx for Windows

  • Provides fully managed shared file system storage for Microsoft Windows EC2 instances

  • •Native Microsoft Windows compatibility

  • New Technology File System (NTFS)

  • Uses Native Server Message Block (SMB) protocol version 2.0 to 3.1.1

  • Distributed File System (DFS) Namespaces and DFS Replication

  • Integrates with Microsoft Active Directory and supports Windows access control lists (ACLs)

User Scripts

You can place a script that will automatically install a webserver or specific packages on instance launch for example.

Best Practices

AMI Deployment Models

Placement Groups

Placement Benefits
Placement Limitations
Placement Strategies

Increase network performance between instances.

An instance can be launched in only one placement group at a time.

Cluster

Reduce correlated or simultaneous failure.

Instances with a tenancy of host can’t be launched in a placement group

Partition

Spread

  • Cluster: Packs instances close together inside an Availability Zone. This strategy helps workloads to achieve low-latency network performance.

  • Partition: Spreads your instances across logical partitions so that groups of instances in one partition do not share the underlying hardware with groups of instances in different partitions.

  • Spread: Strictly places a small group of instances across distinct underlying hardware to reduce correlated failures.

PreviousModule 4NextModule 6

Last updated

Was this helpful?