by Anil Jalela | Nov 28, 2022 | Linux
Ec2 Instance Purchasing Options
There are four ways to pay for amazon EC2 Instances ie:- On-Demand, Reserved Instance, and Spot Instance.
You can also Ply for Dedicated Host which provides you with EC2 Instance Capacity on Physical servers dedicated for your Use.
1 |
On-demand |
→ AWS on-demand Instances are Virtual servers that run in AWS or AWS Relational Database Service (RDS) and are purchased on a fixed Rode per Hour.
→ AWS Recommends using On-demand Instances for applications with Short term irregular workloads that Cannot be interrupted.
→ They are also Suitable for use during the testing and development of applications on EC2.
→ With On-demand instances, you only pay for the EC2 instances you use.
→ The Use of on-demand instances frees you from the Cost and Complexities of planning, purchasing, and maintaining hardware and transforms what are commonly Large Fixed Costs into much Smaller Variable Costs.
→ Pricing is per instance-hour Consumed for each instance from the time an instance is launched until it is terminated or stopped.
→ Each partial instance hour consumed will be billed per second for Linux Instances and as a full Hour for all Other Instance types. |
2 |
Dedicated Instance |
→ Dedicated instances are run in a VPC on Hardware that is dedicated to a Single Customer.
→ Your dedicated instances are physically isolated at the host hardware level from instances that belong to other AWS Accounts.
→ Dedicated instances may share Hardware with other instances from the Same AWS Account that is not a dedicated instance.
→ Pay for dedicated Instances On-demand Save up to 70% by purchasing Reserved instances or save up to 90% by purchasing Spot Instances. |
3 |
Dedicated Host |
→ An Amazon EC2 Dedicated Host is a
physical server with EC2 Instance Capacity fully Dedicated to your Use.
→ Dedicated Host can help you address Compliance requirements and Reduce costs by allowing you to use your existing Server Bound Software licenses.
→ Pay for a Physical Host that is fully dedicated to Running Your Instances, and bring your existing per-Socket, per-Core per-VM Software license to Reduce Cost. |
4 |
Schedule Instance |
→ Schedule Reserve Instances enable you to purchase Capacity Reservations that recur on a daily, weekly, or monthly basis, with a specified Start time and Duration, for a One-Year term.
→ You Reserve the capacity in advance So that you know it is available When you need it. You pay for the time that the instances are Scheduled, even if You do not use them.
→ Schedule instances are a good choice for Workloads that do not run Continuously, but do run on a regular Schedule.
→ Purchase instances that are always available on the Specified Recurring Schedule, for a one-year term.
for eg:- You Can use Schedule instances for an application that runs during business hours or for Batch Processing that Runs at the end of the Week. |
5 |
Reserved Instance |
→ Amazon EC2 RI provides a significant discount (up to 75%) Compared to On-demand pricing and provides a Capacity Reservation when Used in a Specific Availability Zone.
→ Reserved instances give you the option to Reserve a DB instance for a one or three-year term and in turn receive a significant discount Compared to the On-demand Instance pricing for the DB instances.
→ Standard RI:- These provide the most significant discount (up to 75% of on-demand) and are Best Suited for steady-state – State Usage.
→ Convertible RI:- These provide a discount up to 54%) and the Capability to change the attributes of the RI as long as the Exchange Results in the Creation of Reserved instances of greater or equal value.
Schedule RI:- These are available to launch within the time window you Reserve. |
6 |
Sot Instance |
→ Amazon EC2 Spot Instances let you take advantage of unused Ec2 Capacity in the AWS Cloud Spot Instances are available at up to 90% discount Compared to On-demand prices
→ You Can use Spot – Instances for various test & Development Workloads.
→ You also have the Options to hibernate, Stop or terminate your Spot instances when EC2 Reclaims the Capacity Back with two minutes of notice.
→ When Would my Spot Instance get interrupted?
The primary reason would be Amazon EC2 Capacity Requirement (eg-On-demand or Reserved instances) Secondarily if you have chosen to set a ‘max. spot price and the spot price rises above this |
by Anil Jalela | Nov 28, 2022 | Linux
EC2:-
→ Amazon Ec2 provides Scalable Computing Capacity in the Aws Cloud.
→ You Can Use Amazon EC2 to launch as many or as few Virtual Servers as you need, Configure Security and networking, and manage Storage.
→ Amazon EC2 enables you to scale up or – Scale down the instance.
→ Amazon EC2 is having two storage options ie EBS & instance store.
→ Pre Configured templates are available known as Amazon Machine Image.
→ By default, when you create an EC2 account with amazon, your account is limited to a maximum of 20 instances per EC2 Region with two default High Iso instances.
Types of EC2 Instances :-
General Purpose:-
1 |
General Purpose
Available in four sizes:- Nano, Small, medium, and Large but not all.
A-Series:-(A1) medium and large only
M-Series:-(M4, M5, M5a, M5ad, M5d)
T-Series:-(T2,T3,T3a)
|
Balanced Memory & CPU
|
General-purpose instances provide a balance of computing memory and networking resources and can be used for a variety of workloads.
A1–Instances:- Al-instances are ideally suited for Scale-Out Workloads that are supported by the Arm Ecosystem. These instances are well-suited for the following Application Webserver.
Containerized micro Services.
Caching fleets.
Distributed data Stores.
An application that requires Arm Instruction Set.
IM4, M5, M5a, M5ad and M50.
M4 Instance: – The New My instances feature a Custom Intel Xeon E5-2676 v3 Haswell processor Optimized Specifically for EC2
VCPU 2 to 40 (Max.).
RAM 8GB to 160 GB (Max.).
Instance Storage EBS Only.
M5, M5a, M5ad, and M5d Instances: These instances provide an ideal Cloud infra, offering a Balance of Compute, memory, and Networking Resources for a Broad Range of applications Used in – Gaming Servers, Web Server Small and Medium databases
VCPU 2 to 96 (max.).
RAM – 8 to 384 (Max.).
Storage EBS & NVMe, SSD.
T2, T3 and T3a Instances
1 These instances provide a baseline level of CPU Performance with the ability to burst to a higher level When Required by Your Workload!
→ An Unlimited Instances Can Sustain high CPU Performance for any period of time Whenever Required
Used for :
1) Website and Web App.
2) Code Repositories.
3) Development, build test.
4) Microservices
VCPU 2 to 8 (max.).
RAM – 0.5 to 32 (Max.)
|
Compute Optimized:-
2 |
Compute Optimized
Three types are Available C4, C5, C5n (C3 Previous Instance )
|
More CPU than RAM |
Compute Optimized Instances (C-Series)
Compute Optimized Instances are Ideal for Compute-bound application’s that benefit from high-performance processors.
Three types are Available C4, C5, C5n (C3 Previous Instance )
C4-instances:- C4 instances are optimized for Compute intensive Workloads and deliver Very Cost effective high performance at a low price per Compute Ratio.
VCPU 2 to 136
RAM – 3.75 to Go GB
Storage – EBS Only
Network BW – 10 Gbps
Use Cases –Web Server, Batch Processing, MMO Gaming, Video Encoding
C5 instances:- C5 is Optimized for compute-intensive Workloads and delivers Cost-effective high performance at
a low price per Compute Ratio.
Powered by AWS Nitro System.
VCPU 2 to 72
RAM + 4 to 192 GB
Network B.W → Up to 25 Gbps
Instance Storage – EBS Only & NVMe SSD.
High-performance Web Server, Gaming, and Video Encoding.
Note:-
C5 supports a max of 25 EBS volume.
C5 uses an Elastic Network Adapter.
C5 uses a new EC2 Hypervisor. |
Memory Optimized:-
3 |
Memory Optimized
Memory Optimized
R Series.
X-Series.
Z-Series.
Memory Optimized instances are designed to deliver fast performance for Workloads that process large data sets in Memory |
More RAM |
R4, RS, R5a, Road and R50d
→ High Performance, Relational (MySQL), and NoSQL (MongoDB, Cassandra) databases.
→ Distributed Web Scale Cache Stores that provide in-memory caching of key-value type data
→ Used in Financial Services, Hadoop.
VCPU – 2 t. 96
RAM = 1648 768GB
Instance Storage – EBS Only & Nume SSD
X1, Xle Instances
→ Well suited for High-Performance databases and Memory intensive enterprise applications, Relational Database Workload, SAP HANA.
→ Electronic Design Automation
VCPU – 4 to 128.
RAM – 122 to 3904 GB.
Instance Storage – SSD.
Zld Instance
→ High-Frequency Zid delivers a sustained all Core frequency of up to 4.0 GHz, the fastest of any cloud instances
→ AWS Nitro System, Xeon Processor, up to 1.8T8 of instances Storage
VCPU – 2 to 48
RAM → 16 to 384 GB
Storage – NVM SSD
use Cases:- Electronic Design Automation and Certain databases Workloads with high per-Core Licensing Cost |
Accelerated Computing / GPU:-
|
|
|
|
4 |
Accelerated Computing / GPU
Accelerated Computing
P Series.
G Series.
F Series
|
Graphics Optimized |
Accelerated Computing instance families use Hardware accelerators, or Co-processors to perform Some functions such as floating point number calculation, graphics processing, or data pattern Matching more efficiently than is possible in Software Running on CPUs
F1 Instance
→ F1 Instances offer Customizable Hardware acceleration with field Programmable Gate arrays (FPGA).
→ Each FPGA Contains 2.5 million Logic Elements and 6800 DSP engines.
→ Designed to accelerate Computationally intensive algorithms, such as data flow or highly parallel Operations.
→ F1 provider Local NVM SSD Storage.
VCPU – 8 to 64.
FPGA – 1 to 8.
RAM – 122 to 476 GB.
Storage- NUMe SSD
Used in = Genomics Research, Financial Analytics, Real-time Video Processing & Big data Search
P2 & P3 Instances
It Uses NVIDIA Tesla GPUs.
→ Provide High Bandwidth Networking.
→ Up to 32 GB of memory Per GPU which makes them Ideal for deep Learning & Computational Fluid Dynamics.
P2 Instance
VCPU + 4 to 64.
GPU 1 to 16.
RAM + 61-768GB.
GPU RAM – 12-192GB.
Network BW – 25 Gbps
Storage – SSD & EBS.
P3 Instance
VCPU – 8 to 96.
GPU – 1 to 8.
RAM 61-73298.
Storage SSD & EBS.
Used in Machine Learning, Databases Seismic Analysis, Genomics, Molecular Modeling, AI, and Deep Learning.
Note:- p3 Support CUDA9 & Open GL Apis.
P2 Supports CUDA8 and Open CL 12 G2 & G3 Instances
Optimized for Graphics Intensive application
→ Well suited for apps like 3D Visualisation
→ G3 Instances use NVIDIA Tesla M60 GPU and provide a Cost Effective, high-performance platform for Graphics applications
VCPU – 4 to 64.
GPU – 1 to 4.
RAM – 30.5 to 488GB.
GPU Memory 8 to 32 GB.
Network Performance – 25 Gbps
Used in – Video Creation Services, 3D Visualisation, and Streaming Graphics-intensive applications. |
5 |
Storage Optimized
I Series.
D Series.
H Series.
Storage Optimized instances are designed for Workloads that Require’ high, sequential Read and write access to very large data sets on local Storage
They are Optimized to deliver tens of thousands of Low Latency, Random I/O Operations per second CIOPS) to application
|
Low latency |
D2 instances
Well suited for the following
→ Massive Parallel Processing (MPP) data warehouse.
→ Map Reduce and Hadoop distributed Computing.
→ Log or data Processing app
VCPU — + 4 to 36.
RAM — 30.5 to 244 GB.
storage — SSD.
H1 Instances
This family features up to 16 TB of HDD Based local storage, high disk throughput, and a balance of computing & Memory.
→ Well suited for App Requiring Sequential access to large amounts of data on direct-attached instance storage.
→ Application that requires high throughput access to large quantities of data
vCPU – 8 to 64.
RAM – 32 to 256GB.
Storage – HDD.
I3 and I3en Instances
Well suited for=>
→ High-frequency online transaction process-ing System COLTP).
→ Relational Databases.
→ No SQL Databases.
→ Distributed File System.
→ Data Warehousing application.
VCPU 2 to 96.
RAM – 16 to 768 GB.
Local Storage – NVMe SSD.
Networking Performance – 25 Gbps to l00 Gbps.
Sequential Throughout Read – 16 GB/s Write – 6.4GB/S (I3), 8GB/S (I3en). |
6 |
High Memory Optimized
U Series
|
High RAM, Nitro System |
High Memory Instances
→ High Memory Instances are bare metal’ Instances and do not Run on a Hypervisor
→ Only available under Dedicate Host Purchasing Category (for 3 yr. Term)
→ OS directly on Hardware
High Memory Instances are purchased and built to run large-in-memory databases, including production developments of SAP HANA in the cloud.
Features :
Latest Generation Intel Xeon Pentium 8176M Processor
# 6, 9, 12 TB of instance Memory, the largest of any of the EC2 Instance
Powered by the AWS Nitro System, a combination of dedicated Hardware & Lightweight Hypervisor
Bare Metal Performance with direct access to host Hardware.
EBS Optimized by default at no additional Cost.
model :- U-6tb 1 metal, U-9th metal & U-12tb1 metal
Network Performance – 25 Gbps.
Dedicated EBS Bandwidth – 14 Gbps.
Each Instance offers 448 logical Processors. |
7 |
Previous Generation |
|
T1, M1,C1, CC2,M2, CR1, CG1, I2.Hs1, M3,C3 and R3 |
EC2 Bare Metal Instances:-
EC2 Bare Metal Instances |
→ Non-Virtualised Environment
→ Operating System runs directly on Hardware
→ Suitable for Licensing Restricted tier-1 Business Critical Applications.
eg:- i3 metal, 15-metal, r5-metal, z1d-metal, u-6ti metal |
by Anil Jalela | Nov 28, 2022 | Linux
AWS Solution Architect & Sysops
==============================
Cloud Computing is the On-demand delivery of Compute power, database, storage & applications, and Other IT Resources through a Cloud Service platform via the Internet with pay-as-you-go.
Characteristics of Cloud
1 |
On-demand self-service |
2 |
Broad Network Access |
3 |
Scalability |
4 |
Resource Pooling |
5 |
Measured services |
Service in cloud
IAAS:- infrastructure as a services
PAAS:- Platform as a service
SAAS:- Software as a service
Model:-
9 |
Application |
|
|
SAAS |
8 |
Data |
|
|
SAAS |
7 |
Runtime |
|
PAAS |
SAAS |
6 |
Middleware |
|
PAAS |
SAAS |
5 |
os |
IAAS |
PAAS |
SAAS |
4 |
Virtualization |
IAAS |
PAAS |
SAAS |
3 |
Server |
IAAS |
PAAS |
SAAS |
2 |
storage |
IAAS |
PAAS |
SAAS |
1 |
Network |
IAAS |
PAAS |
SAAS |
Deployment of cloud
(1) public cloud
(2) Private cloud
(3) Hybrid cloud
by Anil Jalela | Nov 15, 2022 | Linux
Best Practices to Improve Yahoo, AOL, and Cox.net Deliverability and Sender Reputation.
Yahoo, AOL, and Cox.net, operated by Apollo Global Management, Inc., utilize a unified spam filtering system. Beginning February 2024, these providers will implement stricter requirements for senders, emphasizing the need for email marketers to refine their practices to align with these new standards. This guide provides detailed insights into the factors influencing deliverability and actionable strategies to optimize sender reputation.
How Yahoo, AOL, and Cox.net Determine Sender Reputation
The sender’s reputation plays a crucial role in determining email deliverability. The spam filtering system employed by Yahoo, AOL, and Cox.net evaluates reputation based on several key factors:
Authentication: Email authentication protocols, including DKIM, SPF, and DMARC, are essential for building trust and combating spoofing or phishing attempts. Properly configuring these protocols ensures emails are verified as originating from a legitimate source.
Spam Complaint Rates: Maintaining a low spam complaint rate is critical. Complaint rates exceeding 0.3% indicate dissatisfaction with your emails and can damage your sender reputation. Clear subscription processes and easy-to-use unsubscribe options help mitigate this risk.
IP Address Reputation: The historical performance of the sending IP is closely monitored. A consistent record of low complaints and clean email lists strengthens the reputation of the IP address.
Domain Reputation: ISPs evaluate the sending domain over time. If the domain frequently sends spam or exhibits other negative behaviors, it will harm the deliverability of future campaigns.
Content Quality: Email content is scrutinized for spam triggers such as excessive use of keywords like “free” or “discount,” misleading subject lines, and suspicious links. High-quality content that aligns with user expectations is less likely to be flagged.
Engagement Metrics: ISPs rely heavily on engagement metrics, such as open rates, click-through rates, and responses, to assess the quality of emails. Low engagement indicates poor relevance and can lead to emails being routed to the spam folder.
Bounce and Block Rates: High bounce rates suggest poor list hygiene or sending to invalid addresses, negatively affecting reputation. Similarly, being blocked by recipients or ISPs signals issues with the sender’s practices.
Spam Trap Hits: Sending emails to spam traps, which are set up to catch senders with poor practices, is a serious indicator of poor list management. Frequent hits can lead to blacklisting.
ASN Reputation: The reputation of the sender’s Autonomous System Number (ASN), particularly for bulk senders, is also a factor. Poor ASN practices can lead to reduced deliverability.
To maintain a strong sender reputation, it is crucial to regularly monitor domain and IP performance through feedback tools and address any issues promptly.
Factors Impacting Deliverability
Several controllable and uncontrollable factors influence email deliverability. Below are some of the most impactful considerations and how to address them:
High Complaint Rates: User complaints occur when recipients mark emails as spam. To minimize complaints, clearly communicate what subscribers can expect when signing up, and include a prominent and easy-to-use unsubscribe link in every email.
Inactive Subscribers: Continuously sending to inactive recipients, who neither open nor engage with emails, signals poor list management. Regularly segment your audience and remove or re-engage inactive subscribers to maintain high engagement metrics.
Sudden Changes in Sending Volume: Abrupt increases in email volume can trigger ISP suspicion, especially with Yahoo’s spam filters. For new IPs or campaigns, gradually increase sending volume to establish trust with ISPs.
Unverified Emails: Sending to invalid or unverified email addresses increases bounce rates and can damage sender reputation. Use email validation services to clean your list before sending.
Invalid Authentication Records: Yahoo, AOL, and Cox.net depend on properly configured SPF, DKIM, and DMARC records for authentication. Ensure these records are accurate to prevent deliverability issues.
Key Actions to Improve Deliverability
To enhance email deliverability across Yahoo, AOL, and Cox.net, adhere to the following best practices:
Implement Feedback Loops: Yahoo provides feedback loop (FBL) services that allow you to monitor and address spam complaints effectively. Regularly review FBL data and take corrective action where necessary.
Segment and Target Audiences: Tailoring content to specific audience segments improves engagement and reduces complaints. Send personalized, relevant emails based on user behavior and preferences.
Warm Up New IPs: For new IP addresses, start by sending small volumes of email and gradually increase as trust with ISPs is established. This process helps avoid triggering spam filters.
Separate Sending Domains: Use distinct IPs or domains for transactional and marketing emails to isolate potential reputation issues.
Monitor Blacklists: Regularly check whether your domain or IP has been blacklisted, particularly by AOL, which often collaborates with third-party blacklists.
Optimize Email Content: Avoid excessive use of spammy keywords, test emails for readability across devices, and ensure all links are functional. Including a clear sender name and unsubscribe link also improves compliance and user trust.
Advanced Tactics for Better Inbox Placement
Leverage Analytics: Use analytics tools to monitor engagement metrics such as open rates, click rates, and complaints. Use these insights to optimize future campaigns.
Dynamic Content and Personalization: Tailor your emails to recipients based on their behavior, preferences, or demographics. Dynamic content significantly improves engagement and reduces spam complaints.
Warm-Up Campaigns: For new domains or IPs, conduct gradual warm-up campaigns to build a positive reputation before ramping up sending volumes.
Use Feedback Data: Analyze feedback loop reports to identify problematic addresses and remove them from your list to prevent further complaints.
Updated Email Sender Requirements (Effective February 2024)
To meet the updated standards, email senders must comply with the following requirements:
General Requirements
Authenticate Emails: Implement SPF, DKIM, and DMARC. A valid DMARC policy, even at p=none, is strongly recommended.
Maintain Low Complaint Rates: Ensure complaint rates stay below 0.3%.
Follow Compliance Standards: Adhere to RFC 5321, RFC 5322, and CAN-SPAM Act requirements.
DNS Configuration: Use valid forward and reverse DNS records (PTR) for sending IPs.
Bulk Senders
List Hygiene: Remove invalid and inactive recipients from your lists regularly.
Visible Unsubscribe Options: Include List-Unsubscribe headers and clearly visible unsubscribe links in all emails.
Authentication: Both SPF and DKIM are mandatory, and a valid DMARC policy must be published.
Updated Resources for Yahoo, AOL, and Cox.net
To address deliverability issues or seek support, utilize these updated resources:
Contact Support: Access the Yahoo/AOL/Cox.net sender support portal at Yahoo Sender Support.
Error Codes: Review updated SMTP error codes at Yahoo SMTP Error Codes.
Feedback Loop Registration: Register for Yahoo’s feedback loop services to manage complaints effectively.
By focusing on authentication, segmentation, compliance, and high-quality email practices, senders can navigate these updated standards effectively. Staying informed about ESP updates and leveraging available tools will ensure better inbox placement and maintain a strong sender reputation.