15 things to reduce AWS cost.

#1 Identify Amazon EC2 instances with low-utilization and reduce cost by stopping or rightsizing.

Use AWS Instance Scheduler to automatically stop instances. Use AWS Operations Conductor

to automatically resize the EC2 instances (based on the recommendations report from Cost Explorer).

#2 Identify Amazon EBS volumes with low-utilization and reduce cost by snapshotting then deleting them

#3 Analyze Amazon S3 usage and reduce cost by leveraging lower cost storage tiers

Use S3 Analytics to analyze storage access patterns on the object data set for 30 days or longer. It makes recommendations on where you can leverage S3 Infrequently Accessed (S3 IA) to reduce costs. You can automate moving these objects into lower cost storage tier using Life Cycle Policies. Alternately, you can also use S3 Intelligent-Tiering, which automatically analyzes and moves your objects to the appropriate storage tier.

#4 Identify Amazon RDS, Amazon Redshift instances with low utilization and reduce cost by stopping (RDS) and pausing (Redshift)

K8S PROBES

#Kubernetes probes

Kubernetes probes are health checks that are used to monitor the health of applications and services in a Kubernetes cluster. Kubernetes probes are typically implemented using the Kubernetes API, which allows them to query the application or service for information. This information can then be used to determine the application's or service's health. Kubernetes probes can also be used to detect changes in the application or service and send a notification to the Kubernetes control plane, which can then take corrective action. Kubernetes probes are an important part of the Kubernetes platform, as they help ensure that applications and services run smoothly. They can be used to detect potential problems before they become serious, allowing you to take corrective action quickly.

There are 3 types of Probes available.

• Liveness Probe—indicates if the container is operating. If so, no action is taken. ...
• Readiness Probe—indicates whether the application running in the container is ready to accept requests. ...
• Startup Probe—indicates whether the application running in the container has started.

A successful message for a readiness probe indicates that the container is ready to receive traffic. If a readiness probe is successful, the container is considered ready and can begin receiving requests from other containers, services, or external clients.

A successful message for a liveness probe indicates that the container is still running and functioning properly. If a liveness probe succeeds, the container is considered alive and healthy. If a liveness probe fails, the container is considered to be in a failed state, and Kubernetes will attempt to restart the container to restore its functionality. Both readiness and liveness probes return a successful message with an HTTP response code of 200-399 or a TCP socket connection is successful. If the probe fails, it will return a non-2xx HTTP response code or a failed TCP connection, indicating that the container is not ready or alive.