How to fix the Service limit exceed error while launching an EC2 instance in AWS?

Here are the available CloudWatch metrics for EC2 instances in AWS:

• CPUUtilization
• DiskWriteOps
• DiskReadOps
• DiskWriteBytes
• DiskReadBytes
• NetworkIn
• MetadataNoToken
• NetworkPacketsIn
• NetworkPacketsOut
• NetworkOut

There are two types of volumes for EC2 instances in AWS:

• Amazon Elastic Block Store (EBS) Volumes: EBS volumes are storage units that can be attached to EC2 instances. They provide reliable and long-lasting storage, with features like encryption and snapshots. You can create and attach them independently, as they offer different performance options.
• Instance Store Volumes: Instance store volumes are stored directly on the physical server, hosting the EC2 instance. They provide temporary storage with high I/O performance. However, the data stored on these volumes is lost if the instance is stopped, terminated, or if there is a hardware failure.

EC2 instances in AWS have different pricing models based on various factors like type, region, pricing options (On-Demand, Reserved, or Spot), and usage duration.

After downloading your .pem file, set its permission to 400. This permission level only allows the owner to read the file while restricting any permissions for groups or other users. For a .pem file, these are the octal permissions that AWS recommends.

One can use Palo Alto Networks Prisma Access's SaaS Security Inline to detect and manage risks from unsanctioned SaaS apps.

SaaS Security Inline gives user’s visibility into software-as-a-service (SaaS) applications and helps them in identifying cloud-based threats.