When you launch an instance, you can specify a key pair . If you specify a key pair at launch, when your instance boots for the first time, the public key material is placed on your Linux instance in an entry within ~/.ssh/authorized_keys .

To verify the fingerprint of your key pair, compare the fingerprint displayed on the Key pairs page in the Amazon EC2 console, or returned by the describe-key-pairs command, with the fingerprint that you generate using the private key on your local computer. These fingerprints should match.

Amazon EC2 provides different purchasing options that enable you to optimize your costs.

The rules of a security group control the inbound traffic that's allowed to reach the instances that are associated with the security group. The rules also control the outbound traffic that's allowed to leave them.

Add an instance store volume to an Amazon EC2 instance at launch and then prepare it for use.

The following tools can help you select the optimal instance types for your new or existing workloads:

You can use SageMaker JumpStart to learn about SageMaker features and capabilities through curated one-step solutions and pretrained models.

Use Amazon Elastic Inference (EI) to speed up the throughput and decrease latency for inference in Amazon SageMaker

Learn about creating and managing Amazon EMR clusters from Amazon SageMaker Studio Classic to process large-scale data for machine learning workloads.

Learn about Amazon SageMaker capabilities to build, train, and deploy geospatial models.