Security is a critical part of managing workloads in AWS. AWS Key Management Service (AWS KMS) makes it easier to create and manage cryptographic keys that can be used to protect data across AWS services.

AWS KMS Key Creation at a Glance

Create an AWS KMS Key through the AWS KMS console by selecting the key type, configuring administrators and key users, reviewing the key policy, and creating the key. The KMS key can then be used to protect data across supported AWS services.

What is AWS KMS?

AWS Key Management Service (KMS) is a managed service that allows you to create and control cryptographic keys used to protect data. AWS services can use KMS keys to encrypt data at rest, while KMS handles the underlying cryptographic operations and access control.

KMS keys can be used with services such as:

• Amazon EC2 / EBS
• Amazon S3
• Amazon RDS
• Amazon EFS

Prerequisites

Before creating the KMS key, make sure you have:

1. An AWS account
2. Access to the required AWS region
3. IAM permissions to create and manage KMS keys

Create a KMS Key Using AWS Console

Log in to the AWS Management Console and open:

AWS KMS → Customer managed keys

Click: Create key

Select Key Type

Under Key type, select: Symmetric

Under Key usage, select: Encrypt and decrypt

Then click: Next

Add Key Details

Provide a meaningful alias. For example: alias/prod-data-encryption

Click: Next

Configure Key Administrators

AWS KMS allows you to specify which IAM users or roles can administer the key. Typical administrative permissions include:

• Enable key
• Disable key
• Schedule key deletion
• Change key policy
• Configure rotation
• Manage aliases

Configure Key Users

Next, select the IAM users or roles that should be allowed to use the key. The exact permissions required depend on how the key will be used. For an application that needs encryption and decryption, permissions may include:

kms:Encrypt

kms:Decrypt

kms:GenerateDataKey

kms:DescribeKey

For AWS services, the required permissions can vary depending on the service.

Review the Key Policy

AWS KMS uses a key policy to control access to a KMS key. A simplified example looks like:

The root principal in a KMS key policy does not mean that the AWS account root user is the only person who can use the key. It establishes account-level control that can allow IAM policies to grant access. However, KMS policies should be designed carefully according to the principle of least privilege.

Click: Finish

The KMS key is now created.

Find the KMS Key ID

After creating the key, open:

AWS KMS → Customer managed keys

You should see something similar to:

Alias

alias/prod-data-encryption

Key ID

12345678-abcd-1234-abcd-123456789012

Key ARN

arn:aws:kms:ap-south-1:123456789012:key/12345678-abcd-1234-abcd-123456789012

The Key ID or Key ARN can be used when configuring AWS services.

Test the KMS Key

Before attaching the key to production resources, you can verify that it is enabled. Run: 

Look for: “KeyState”: “Enabled”

You can also test encryption directly. Generate a data key:

AWS will return an encrypted data key and plaintext data key. Do not store or expose the plaintext data key unnecessarily.

Conclusion

AWS KMS provides a centralized way to manage encryption keys and control access to encrypted data.

A typical implementation involves:

Create KMS Key

       ↓

Create Alias

       ↓

Configure Key Administrators

       ↓

Configure Key Users

       ↓

Configure Key Policy

       ↓

Enable Rotation

       ↓

Attach KMS Key to AWS Resource

       ↓

Test Encryption

       ↓

Monitor Usage with CloudTrail

The important point is that creating a KMS key is only the first step. The key must also be correctly integrated with the AWS service and the IAM/KMS policies must allow the required operations.

Need Help With AWS KMS Configuration?

AWS KMS requires careful configuration of encryption keys, permissions, and key policies. If you need help setting up or managing AWS encryption and security, Skynats can assist with AWS infrastructure management and support.

Explore AWS Cloud Management Services

The post How to Create and Use an AWS KMS Key for Encryption in AWS appeared first on Server Management Services | Cloud Management | Skynats.

Install Node Exporter on Linux to collect system-level metrics for effective server monitoring with Prometheus. Prometheus is a monitoring platform that collects metrics from configured targets. For Linux servers, Node Exporter is a monitoring agent installed on each server to collect system-level metrics such as CPU usage, memory utilization, disk space, filesystem statistics, network traffic, and system load. It exposes system metrics over TCP port 9100, which the Prometheus server can access and scrape.

This guide explains how to install and configure Node Exporter on a Linux server and verify its connectivity from the Prometheus server.

If you need assistance with Linux server monitoring, Node Exporter installation, or ongoing server management, a managed server provider can handle the setup and monitoring for you.

Node Exporter Installation at a Glance

Node Exporter is installed on a Linux server to collect system metrics such as CPU, memory, disk, and network usage for Prometheus. The basic setup involves installing Node Exporter, configuring it as a systemd service, allowing secure access to TCP port 9100, and verifying connectivity with the Prometheus server.

Prerequisites

To proceed with the setup, we need:

• root or sudo access to the Linux server.
• Ensure that the server has network connectivity to the Prometheus server.
• TCP port 9100 is allowed between the Linux server and Prometheus server.

For security, port 9100 should preferably be accessible only from the Prometheus server or trusted monitoring network rather than being exposed publicly.

Step 1: Download Node Exporter

Download the Node Exporter package to a temporary directory:

Extract the downloaded archive:

Copy the binary file to /usr/local/bin/:

Verify the installation using:

The command should return the installed Node Exporter version.

Step 2: Create a Dedicated Node Exporter User

For security, run Node Exporter under a dedicated system user instead of the root user.

Create the user:

Set the ownership for the binary:

Step 3: Create a Systemd Service

Create a systemd service for Node Exporter to start automatically when the server boots and to provide standard service management through systemctl.

Create the service file:

Add the following:

Save the file using wq! and reload the systemd configuration:

Enable the service to start automatically after reboot:

Start the service:

Check the service status:

The service should show:

Active: active (running)

Step 4: Verify Node Exporter Is Listening

Node Exporter listens on TCP port 9100 by default.

Check whether the port is listening:

A typical output will look similar to:

LISTEN 0 4096 *:9100 *:* users:((“node_exporter”,pid=1234,fd=3))

Step 5: Test Node Exporter Locally

Before testing connectivity from the Prometheus server, verify that Node Exporter is working locally.

Run:

If Node Exporter is working correctly, the command will return a large set of metrics.

For example:

node_cpu_seconds_total

node_memory_MemTotal_bytes

node_memory_MemAvailable_bytes

node_filesystem_size_bytes

node_network_receive_bytes_total

This response means that Node Exporter is installed and functioning correctly on the server.

Step 6: Configure the Server Firewall

The Prometheus server needs to access the TCP port on the monitored server.

For security reasons, port 9100 should not normally be exposed to the public internet. Access should preferably be restricted to the private IP address of the Prometheus server or the trusted monitoring network.

UFW

If the server uses UFW and the Prometheus server has the private IP 10.0.1.23:

You can verify the rule using: 

Firewalld

For servers using firewalld:

Reload the firewall:

Verify the configuration:

CSF

If the server uses CSF, TCP port 9100 needs to be permitted appropriately.

However, instead of allowing the port globally, access should preferably be restricted to the Prometheus server’s private IP.

You can do this by adding the following lines at the bottom of the /etc/csf/csf.allow file:

Note: CSF configuration can vary depending on how the server’s firewall policies are structured.

Step 7: Configure the AWS Security Group

If the Linux server is hosted on AWS EC2, the Security Group attached to the instance must also permit TCP port 9100.

Add an inbound rule similar to:

Type:        Custom TCP

Port:        9100

Protocol:    TCP

Source:      10.0.1.23/32

If the Prometheus and monitored servers are located in different VPCs, through VPC peering, the appropriate VPC routes must also be configured between the two networks.

Step 8: Test Connectivity from the Prometheus Server

Once Node Exporter is running and the required firewall/network settings are configured, test connectivity from the Prometheus server.

For example, if the monitored server has the private IP 10.26.3.21

Run the following command from the Prometheus server:

If the connection is successful, Prometheus should be able to retrieve the Node Exporter metrics.

A successful connection should return a message similar to: 

Connection to 10.26.3.21 9100 port [tcp/*] succeeded!

Troubleshooting Connection Failures

If the connection times out, You can check whether connection attempts are reaching the monitored server using:

If no packets are observed, the issue is likely somewhere in the network path, such as routing, Security Groups, or NACLs. If packets reach the server but the connection is not established, investigate the local firewall or service configuration. 

After checking everything, run the curl test again from the Prometheus server.

Conclusion

Node Exporter provides the system-level metrics required for monitoring Linux servers through Prometheus. The installation involves deploying the Node Exporter binary, creating a dedicated system user, configuring a systemd service verifying that the exporter is listening on TCP port 9100, and configure the local server to allow the  the Prometheus server to access the Node Exporter endpoint securely.

With the right configuration, Node Exporter can be an important component of a reliable Linux server monitoring setup.

Need Help With Linux Server Monitoring?

Setting up and maintaining server monitoring across multiple Linux servers can require ongoing configuration, security, and maintenance. Skynats can help with Linux Server Support, monitoring, and infrastructure support.

Learn More About Linux Server Services

The post How to Install and Configure Node Exporter on a Linux Server appeared first on Server Management Services | Cloud Management | Skynats.

What is SOC 2?

SOC 2 is an attestation examination and report rather than an ISO-style certification. An independent auditor examines a service organization’s controls against the AICPA Trust Services Criteria. These criteria cover security and, when included in the engagement, availability, processing integrity, confidentiality, and privacy.

SOC 2 is commonly used by SaaS, cloud, technology, and other service organizations to provide customers and business partners with information about their controls and security practices.

SOC 2 engagements may be Type I or Type II. A Type I examination evaluates whether relevant controls are suitably designed and implemented at a specific point in time, while a Type II examination also evaluates the operating effectiveness of relevant controls over a defined period.

Organizations preparing for security assessments can also strengthen their infrastructure through Managed Security Solutions

What is ISO 27001?

ISO 27001 is an internationally recognized standard that specifies requirements for establishing, implementing, maintaining, and continually improving an Information Security Management System (ISMS). Organizations can also choose to undergo an independent certification process to demonstrate conformity with the standard.

ISO 27001 takes a structured, risk-based approach to information security. It can be applied by organizations of different sizes and across different industries, making it relevant for businesses that want to establish a formal information security management framework.

Organizations working toward stronger information security can also consider compliance services to help address security policies, risk management, controls, and ongoing monitoring.

What is HIPAA?

Unlike the other two, HIPAA is a U.S. federal law rather than a voluntary security standard or certification.

HIPAA applies to covered entities and business associates that are subject to the HIPAA Rules. These requirements address areas such as privacy, security, and breach notification involving protected health information (PHI). Business Associate Agreements (BAAs) may also be required when a business associate relationship exists.

Healthcare organizations and technology providers handling sensitive workloads should also consider appropriate managed security services to support ongoing security monitoring and infrastructure protection.

Which One Do You Need?

The right framework or regulatory requirement depends on your customers, market, industry, services, contractual obligations, and the type of data your organization handles.

• Selling to US enterprises: SOC 2 may be requested by customers as evidence of relevant security controls.
• Expanding globally: ISO 27001 can provide a structured and internationally recognized approach to information security management.
• Handling health data: If your organization is subject to HIPAA as a covered entity or business associate, the applicable HIPAA requirements need to be addressed.
• Serving multiple markets or customer types: Your organization may need to address more than one framework or regulatory requirement.

Many growing companies eventually pursue more than one, since the underlying security practices — such as access management, encryption, monitoring, risk management, and incident response — can overlap significantly.

Organizations operating cloud workloads can also review their cloud security services to strengthen infrastructure protection and security management.

Can You Have SOC 2, ISO 27001, and HIPAA Together?

Yes. An organization can work toward SOC 2, ISO 27001, and applicable HIPAA requirements at the same time. These frameworks and requirements address different areas, although some security practices may overlap.

For example, access management, security monitoring, risk management, incident response, encryption, and security policies may be relevant across multiple compliance programs.

However, meeting one framework or requirement does not automatically mean that an organization meets the requirements of another. Businesses should evaluate their specific obligations and customer requirements separately.

Side-by-Side Comparison

Aspect	SOC 2	ISO 27001	HIPAA
Type	Audit report (attestation)	Certification	Legal requirement (US federal law)
Governing body	AICPA	ISO/IEC	U.S. Dept. of Health & Human Services (HHS)
Mandatory or voluntary	Voluntary (market-driven)	Voluntary	Mandatory for covered entities/business associates
Who typically needs it	SaaS & cloud service companies	Any organization, especially global/enterprise	Healthcare providers, insurers, and their vendors
What it covers	Security, availability, processing integrity, confidentiality, privacy	Full Information Security Management System (ISMS)	Protected Health Information (PHI)
Geographic relevance	Mainly US, globally accepted	International	US only
Proof of compliance	Auditor’s report (Type I/II)	3-year certificate + surveillance audits	Self-attested via risk assessments & BAAs
Typical timeline	3–12 months	6–18 months	3–6+ months (ongoing)
Non-compliance consequence	Lost deals, reputational damage	Loss of certification, lost trust	Legal penalties, fines, criminal charges (severe cases)

Conclusion

SOC 2, ISO 27001, and HIPAA aren’t competing standards; they serve different purposes for different situations.

SOC 2 can provide customers with assurance about relevant controls at a service organization. ISO 27001 provides a structured framework for managing information security through an ISMS. HIPAA establishes legal requirements for covered entities and business associates that fall within its scope.

Knowing your customers, your market, your contractual requirements, and the type of data you handle makes the compliance landscape clearer. In some cases, the right approach may involve more than one framework or regulatory requirement working together.

If you’re unsure which security or compliance requirements may apply to your infrastructure, contact us  to discuss your requirements with our team.

The post SOC 2 vs ISO 27001 vs HIPAA: Which Compliance Do You Need? appeared first on Server Management Services | Cloud Management | Skynats.

Cloud services have become an important part of modern businesses. Employees use applications such as cloud storage, email, collaboration tools, and other online services every day.Using cloud services makes work easier and more flexible, but it also creates new security challenges. Sensitive company information can be exposed if employees use unauthorized applications or if an account is compromised.

This is where Cloud Access Security Broker (CASB) comes in. A CASB helps organizations monitor and secure the way users access cloud applications and data. That is, it acts as a security layer between users and cloud service providers. 

What Is CASB? Quick Answer

CASB (Cloud Access Security Broker) is a security solution that helps organizations monitor, control, and protect access to cloud applications and services. It acts as a security layer between users and cloud service providers, helping organizations enforce security policies as cloud services are accessed.

A CASB provides visibility into cloud usage, controls user access, protects sensitive data, and helps detect potential security threats. It can also help organizations manage Shadow IT, data loss, compliance requirements, and risky cloud activities.

In simple terms, CASB helps organizations maintain visibility and control over how employees use cloud services while protecting company data and applications.

How Does CASB Work?

CASB works between users and cloud service providers to enforce an organization’s security rules. It can discover which cloud applications employees are using, identify risky applications or activities, and apply appropriate security policies. For example, if an employee tries to upload confidential company information to an unauthorized cloud storage service, a CASB can detect the activity and take action based on the organization’s policy. Depending on the configuration, it may block the activity, generate an alert, or apply other security controls.

Four Key Pillars of CASB

According to Netskope, CASB is built around four major areas: visibility, compliance, data security, and threat protection. 

• Visibility: Helps organizations understand which cloud services, users, and devices are being used.
• Compliance: Helps businesses follow industry and data protection requirements.
• Data Security: Helps protect sensitive information using controls such as Data Loss Prevention (DLP).
• Threat Protection: Helps detect and prevent malware, ransomware, unauthorized access, and other cloud-based threats.

Benefits of CASB

One of the biggest advantages of CASB is better visibility and control over cloud usage. It can help organizations identify Shadow IT, which refers to cloud applications being used without proper approval from the IT team. 

CASB can also help prevent data leaks, improve cloud security, support compliance, and detect suspicious activities. These benefits are especially useful for organizations with remote employees, multiple cloud applications, and employees using personal devices. 

Conclusion

As businesses increasingly rely on cloud applications and services, managing cloud security has become more complex. Employees may access multiple SaaS applications, share sensitive information across cloud platforms, or use applications that have not been approved by the IT team.

A Cloud Access Security Broker (CASB) helps organizations gain greater visibility and control over these activities. It can help identify Shadow IT, protect sensitive data, enforce access and security policies, support compliance requirements, and detect potential cloud-based threats.

However, CASB should be considered as part of a broader cybersecurity strategy rather than as a standalone security solution. Organizations should evaluate their cloud environment, security requirements, compliance needs, and existing security tools before choosing a CASB solution.

Secure Your Cloud Environment with the Right Cybersecurity Strategy

Whether you’re using SaaS applications, cloud infrastructure, or remote-work environments, having the right security controls in place is essential.

Explore our cybersecurity solutions to learn how you can strengthen your organization’s security, protect critical data, and reduce cloud-related security risks.

The post What Is CASB and How Does It Work? A Simple Guide to Cloud Security appeared first on Server Management Services | Cloud Management | Skynats.

This is where Monitorix can help.

Monitorix is a free and open-source monitoring tool designed to collect system and network information from Linux and UNIX-based systems. It presents the collected information through easy-to-understand graphs, making it much easier to see what is happening on your server.Monitorix is designed for monitoring Linux/UNIX servers and includes a built-in HTTP server for viewing monitoring graphs.

Why Use Monitorix for Linux Server Monitoring?

One of the biggest advantages of Monitorix is its simplicity.

Monitorix can help you:

• Monitor CPU and memory usage.
• Check system load and running processes.
• Monitor disk usage and I/O activity.
• Track network traffic.
• Monitor disk temperatures and health.
• Keep an eye on services such as SSH, FTP, SMTP, and others.
• Monitor Apache and MySQL statistics.
• View Fail2ban statistics.
• Monitor multiple remote servers.
• View historical data by day, week, month, or year.
• Zoom into graphs when you need more detail.

Installing Monitorix on Almalinux

Let’s look at a basic installation process. Monitorix packages and dependencies may be available through the EPEL repository.
First, install EPEL.

Note: RHEL/CentOS package availability changes over time. For newer distributions, always check the current Monitorix and EPEL documentation before using an older installation command.

How to Install Monitorix and Its Required Packages?

After enabling EPEL, install the required dependencies:

Now install Monitorix:

If the installation completes successfully, Monitorix should now be available on your server.

Configure Monitorix

The main configuration file is: /etc/monitorix/monitorix.conf

The configuration file allows you to control different parts of Monitorix.

For example, you can enable or disable specific monitoring graphs and adjust settings according to your environment.

Before making changes, it is a good idea to keep a backup of the original configuration:

That way, you can easily restore the original configuration if something goes wrong.

How to Start and Enable the Monitorix Service?

Once the configuration is ready, enable and start Monitorix to start automatically when the server boots:

If everything is working correctly, you should see the service in an active state.

Monitorix will then begin collecting system information based on its configuration.

Access the Monitorix Dashboard

Once Monitorix has started collecting data, open a web browser and visit:

Keep in mind that it can take some time before meaningful graphs appear because Monitorix needs to collect data first.

Monitoring Multiple Servers

Another useful feature is Multihost monitoring. If you manage several Linux servers, you can configure Monitorix to monitor remote systems and view their statistics from a central location.

Monitor Multiple Linux Servers with Monitorix

Another useful feature is Multihost monitoring. If you manage several Linux servers, you can configure Monitorix to monitor remote systems and view their statistics from a central location.

This can be useful for administrators who need visibility into the performance of multiple servers.

When Do You Need Professional Server Management?

Monitorix can help you identify issues such as high CPU usage, memory pressure, disk activity, network traffic changes, and service-related problems.

However, monitoring a problem and resolving the underlying cause are two different things. Server performance issues may require detailed investigation, configuration changes, security checks, or ongoing server administration.

If your Linux server is experiencing performance issues, resource problems, security concerns, or service failures, Professional server support can help identify and resolve the underlying issues.

Final Thoughts

Monitorix is a simple, lightweight, and open-source solution for Linux server monitoring. It provides useful graphs for CPU, memory, disk, network activity, and other system and service statistics.

For small and medium-sized environments, test servers, personal infrastructure, and Linux administration labs, Monitorix can provide a useful overview of server health without requiring a complicated monitoring stack.

If you need help with Linux server monitoring, troubleshooting, security, optimization, or ongoing server management, Skynats can provide expert server management and technical support.

The post Monitorix: Linux Server Monitoring, Setup and Configuration Guide appeared first on Server Management Services | Cloud Management | Skynats.

What Does VAPT Stand For?

VAPT stands for Vulnerability Assessment and Penetration Testing. This is in fact two different but complementary approaches to security testing rolled into one process:

• Vulnerability Assessment (VA): A systematic review of systems, networks, and applications to identify, classify, and prioritize security weaknesses.
• Penetration Testing (PT): A simulated cyberattack carried out by ethical hackers to actively exploit those weaknesses and determine how much damage a real attacker could cause.

Together, VAPT provides organizations with a complete picture of their security posture—not a list of potential flaws, but real evidence of which ones are exploitable.

Vulnerability Assessment vs. Penetration Testing

People tend to use these terms interchangeably, but they serve different purposes:

A vulnerability assessment might reveal that a server has a known vulnerability in an old version of software. A penetration test goes one step further—it attempts to actually get inside with that vulnerability, giving you a clear picture of what an attacker could access, steal, or damage.

Why is VAPT important?

• Identifies security holes before hackers do. Proactive testing identifies vulnerabilities before they become breaches.
• Secures sensitive data. Customer data, financial records, and intellectual property are protected.
• Ensures compliance with regulations. Security testing is often a requirement for standards like ISO 27001, PCI-DSS, HIPAA, GDPR, and SOC 2.
• Builds customer confidence. A strong security posture builds confidence in customers and partners.
• Lowers financial risk. A VAPT engagement is far less expensive than the potential fines, downtime, and lost reputation resulting from a data breach.
• Tests existing security controls. Ensures that firewalls, intrusion detection systems, and access control systems are working as intended.

Types of VAPT

VAPT is not a uniform process. It usually covers several areas of testing, depending on what needs to be tested:

• Network VAPT: It tests the network infrastructure, both internal and external, such as firewalls, routers, and servers. 
• Web Application VAPT: Tests web apps and websites for vulnerabilities like SQL injection, cross-site scripting (XSS), and broken authentication.
• Mobile Application VAPT: Tests Android and iOS apps for insecure data storage, weak encryption, and API vulnerabilities.
• Cloud VAPT: Tests cloud environments (AWS, Azure, GCP) for misconfigurations and access control issues.
• API VAPT: Testing APIs for authentication weakness, data exposure, and improper input validation.
• Wireless Network VAPT: Checks Wi-Fi networks for rogue access points and encryption flaws.
• Social Engineering Testing: Tests human susceptibility through phishing tests and pretexting exercises.

 How Does the VAPT Process Work?

The phases of a typical VAPT engagement are

1. Scoping & Planning: Identifying the systems, applications, and goals of the assessment.
2. Information Gathering (Reconnaissance): Collecting data on the target environment.
3. Vulnerability Scanning: This is the use of automated tools to identify known vulnerabilities.
4. Manual Penetration Testing: Ethical hackers try to exploit the vulnerabilities they find.
5. Risk Analysis and Prioritization: Prioritize vulnerabilities according to severity and potential impact on the business.
6. Reporting: Providing a full report of the findings, evidence, and recommendations for remediation.
7. Remediation Support: Helping the organization remediate identified issues.
8. Re-testing: Confirming that the defects have been fixed correctly.

How Often Should You Conduct VAPT?

Most security experts recommend a VAPT:

• At least once or twice a year as a baseline.
• After major infrastructure or application changes.
• Following any security incident.
• Before launching a new product or service.
• As required by compliance frameworks.

Conclusion

VAPT is not just a tick in the box for compliance. It is a critical, ongoing investment in your organization’s resilience to cyber assaults. The combined reach of vulnerability assessment and the depth of penetration testing provide businesses with a realistic view of their actual security posture and the confidence to defend against evolving attacks.

At Skynats, our professional VAPT services help businesses assess web applications, mobile applications, APIs, internal and external networks, and cloud environments. Our assessments are tailored to your environment and security requirements, helping identify potential vulnerabilities and providing recommendations to strengthen your overall security.

If you haven’t done a VAPT assessment in a while, it’s time to get to work. Cybercriminals are constantly looking for vulnerabilities; find them before they do.

Want to safeguard your business with a professional VAPT assessment? Contact our security experts today. 

The post What is VAPT in Cyber Security? A Complete Guide appeared first on Server Management Services | Cloud Management | Skynats.

cPanel Disk Space Issues can disrupt your website’s normal operation by preventing file uploads, email delivery, backups, and other essential hosting tasks. One common cause is the “Other Usage” section in cPanel, which may show a significant amount of storage being used without clearly indicating what is consuming the space. This often makes it difficult for website owners to identify the root cause of the problem.

The “Other Usage” category typically includes hidden files, log files, temporary cache, system-generated files, and items stored in the Trash that may not be immediately visible through the File Manager. Understanding what contributes to this storage usage is the first step toward managing your hosting account more effectively. In this guide, we’ll explain what “Other Usage” means, explore the common reasons behind cPanel Disk Space Issues, and discuss what to look for before making any changes to your hosting environment.

Common Signs of cPanel Disk Space Issues

Explain symptoms like:

• Unable to upload files
• Emails not being delivered
• Backup failures
• WordPress update errors
• “Disk quota exceeded” messages
• Website performance issues

Prerequisites

Before you begin, make sure you have:

• Access to your cPanel account to review storage usage.
• A recent backup to prevent accidental data loss.
• SSH access (if provided by your hosting provider) for advanced investigation.
• Appropriate permissions to manage hosting files.

What Causes “Other Usage”?

The Other Usage section may include:

• Large log files generated by applications or websites.
• Files stored in the Trash folder.
• Temporary application files
• Failed backup archives
• Website migration files
• Session files
• Cache generated by CMS applications
• Large archived log files
• Hidden files (also known as dotfiles).
• Temporary cache files.
• System-managed user files located in directories such as /var and /usr (depending on your hosting environment).
• Old backup files that are no longer needed.

Since these files are not always visible in the Disk Usage interface, they can consume a significant amount of storage without user noticing.

Steps to Resolve Disk Space Issues

Step 1: Clear Unnecessary Log Files

Log files can grow over time and occupy a large amount of storage. Review old or unnecessary logs and remove them if they are no longer required for troubleshooting.

Step 2: Empty the Trash

Files moved to the Trash still consume disk space until they are permanently deleted. Open the File Manager, review the Trash folder, and empty it to free up storage.

Step 3: Check Hidden Files

Enable Show Hidden Files (dotfiles) in File Manager. Review hidden files carefully and remove only those that are safe to delete.

Step 4: Review System-Managed User Files

Some hosting environments store user-related files in directories such as /var and /usr. If you have the required permissions, review these locations and remove unnecessary files with caution. If you don’t have necessary permissions then ask your hosting provider to do it. Avoid deleting system files unless you are certain they are no longer needed.

Step 5: Remove Old Backups and Cache Files

Delete outdated backup archives and clear unnecessary cache files created by your applications. This can free a significant amount of disk space.

Step 6: Verify Disk Usage

After cleaning up, revisit the Disk Usage page in cPanel to confirm that the available storage has increased and the “Other Usage” value has decreased.

Conclusion

The “Other Usage” section in cPanel can sometimes hide the actual cause of high disk consumption, but resolving the issue is usually straightforward. Clearing old logs, emptying the Trash, checking hidden files, removing outdated backups, and reviewing system-managed files can help reclaim valuable storage space. Regularly monitoring disk usage and cleaning unnecessary files will help keep your hosting account running smoothly and prevent future storage-related problems.

Need Help Resolving cPanel Disk Space Issues?

If your hosting account continues to experience storage issues or the “Other Usage” category keeps growing without a clear reason, our experienced engineers can help identify the underlying cause and recommend the right solution. From ongoing server monitoring to complete cPanel Infrastructure Management, Skynats provides 24/7 expert support to keep your hosting environment running smoothly.

👉 Explore our Professional cPanel Management or Contact Us to speak with our server management experts.

The post How to Resolve cPanel Disk Space Issues: Understanding “Other Usage” appeared first on Server Management Services | Cloud Management | Skynats.

Quick Answer

AWS CloudFormation Setup is the process of creating, deploying, and managing AWS infrastructure using reusable YAML or JSON templates.CloudFormation is widely used by organizations offering managed cloud infrastructure services to automate scalable and repeatable cloud deployments. Instead of manually configuring AWS resources, CloudFormation automates provisioning, updates, and deletions while maintaining consistency, reducing human error, and simplifying infrastructure management.

What Is AWS CloudFormation?

AWS CloudFormation is Amazon Web Services’ Infrastructure as Code (IaC) service that automates cloud infrastructure deployment. Organizations using AWS cloud management can leverage CloudFormation to standardize, provision, and manage AWS resources efficiently.. It enables developers and system administrators to define cloud infrastructure using code rather than configuring resources manually through the AWS Management Console.

A CloudFormation template acts as a blueprint that describes the AWS resources your application requires. When you deploy the template, AWS automatically creates the resources in the correct order while resolving dependencies between them.

This approach makes deployments:

• Faster
• Consistent
• Repeatable
• Version-controlled
• Easier to scale

Whether you’re deploying a single Amazon S3 bucket or an entire production environment, CloudFormation helps automate the entire process.

Why Use AWS CloudFormation?

Managing AWS infrastructure manually becomes increasingly difficult as environments grow.

CloudFormation simplifies infrastructure management by offering:

• Infrastructure as Code (IaC)
• Automated resource provisioning
• Consistent deployments across environments
• Easy rollback during failures
• Version-controlled infrastructure
• Simplified disaster recovery
• Reduced operational errors

For organizations managing multiple AWS environments, CloudFormation significantly improves operational efficiency and deployment reliability.

How AWS CloudFormation Works

CloudFormation follows a simple workflow:

1. Write a YAML or JSON template.
2. Upload the template to AWS.
3. Create a CloudFormation Stack.
4. AWS provisions resources automatically.
5. Monitor deployment progress.
6. Update infrastructure when needed.
7. Delete the stack when resources are no longer required.

This workflow ensures infrastructure remains reproducible and easy to manage throughout its lifecycle.

Step 1: Sign In to the AWS Management Console

Log in to your AWS account.

1. Open the AWS Management Console.
2. Enter your credentials.
3. In the search bar, type CloudFormation.
4. Select AWS CloudFormation from the services list.

You’ll be redirected to the CloudFormation dashboard, where you can create and manage infrastructure stacks.

Step 2: Create a CloudFormation Template

A template defines the infrastructure you want AWS to deploy.

Create a file named:

s3-bucket.yaml

AWSTemplateFormatVersion: '2010-09-09'
Description: Create an Amazon S3 Bucket

Resources:
  DemoBucket:
    Type: AWS::S3::Bucket

Save the file locally.

Understanding the Template

This template contains:

• AWSTemplateFormatVersion – Specifies the template version.
• Description – Explains the purpose of the template.
• Resources – Lists the AWS resources to create.
• AWS::S3::Bucket – Creates a new Amazon S3 bucket.

Although simple, this demonstrates the core concept of Infrastructure as Code.

Step 3: Create a CloudFormation Stack

A Stack is a collection of AWS resources managed together.

To create one:

1. Open the CloudFormation console.
2. Click Create Stack.
3. Choose With new resources (Standard).
4. Under Specify template, select Upload a template file.
5. Upload s3-bucket.yaml.
6. Click Next.

For beginners, uploading a template file is the easiest approach.

Step 4: Specify Stack Details

Provide the required configuration.

Example:

Leave the remaining options unchanged for this tutorial.

Click Next.

Step 5: Configure Stack Options

CloudFormation offers several optional settings, including:

• Tags
• IAM permissions
• Rollback configuration
• Notifications
• Stack policies
• Monitoring options

For a basic deployment, you can keep the default values.

Click Next.

Step 6: Review and Create the Stack

Review all configuration settings carefully before deployment.

Once verified:

1. Review the template.
2. Confirm the stack settings.
3. Click Submit.

CloudFormation immediately begins provisioning your infrastructure.

Step 7: Monitor Stack Creation

You can monitor deployment progress from the Stacks page.

Select your stack to view:

• Events
• Resources
• Outputs
• Template
• Parameters

The Events tab displays every action CloudFormation performs during deployment.

Deployment completes successfully when the status changes to:

CREATE_COMPLETE

After deployment:

1. Open the Resources tab.
2. Locate the Amazon S3 bucket.
3. Open the Amazon S3 Console.
4. Verify that the bucket has been created successfully.

This confirms that CloudFormation deployed the infrastructure defined in your template.

Updating a CloudFormation Stack

One of CloudFormation’s biggest advantages is that infrastructure updates are automated.

To update a stack:

1. Modify your template.
2. Select the existing stack.
3. Click Update.
4. Upload the revised template.
5. Review the proposed changes.
6. Submit the update.

CloudFormation only modifies the resources that require changes, minimizing downtime and reducing unnecessary updates.

Deleting a CloudFormation Stack

When infrastructure is no longer needed, CloudFormation can clean it up automatically.

Steps:

1. Select the stack.
2. Click Delete.
3. Confirm deletion.

CloudFormation removes all associated resources unless a resource has a retention policy configured.

Automatic cleanup helps prevent unused resources from generating unnecessary AWS costs.

CloudFormation Best Practices

To build reliable and maintainable infrastructure, follow these best practices:

Use Version Control

Store CloudFormation templates in Git to track changes and collaborate effectively.

Organize Templates

Break large deployments into nested stacks or reusable modules for easier management.

Validate Templates

Use AWS template validation tools before deployment to detect syntax issues early.

Implement Change Sets

Review infrastructure changes before applying them to production environments.

Apply Least Privilege Access

Grant only the IAM permissions required to deploy and manage CloudFormation stacks.

Add Parameters and Outputs

Parameters make templates reusable, while Outputs simplify integration with other AWS services.

Monitor Stack Events

Regularly review deployment events to identify errors and troubleshoot failed deployments quickly.

Common CloudFormation Issues and Troubleshooting

Understanding these common issues can significantly reduce deployment time and improve operational reliability.

Real-World Example

Imagine your development team needs identical environments for development, testing, and production.

Instead of manually configuring hundreds of AWS resources each time, you create one CloudFormation template and deploy it across all environments. This ensures consistency, reduces configuration drift, and allows infrastructure changes to be version-controlled alongside application code.

This Infrastructure as Code approach is widely adopted by DevOps teams to improve scalability and operational efficiency.

Conclusion

AWS CloudFormation Setup provides a reliable and repeatable way to deploy AWS infrastructure using Infrastructure as Code. By defining resources in YAML or JSON templates, organizations can automate deployments, maintain consistent environments, reduce manual errors, and simplify ongoing infrastructure management.

Whether you’re provisioning a single Amazon S3 bucket or deploying a complex cloud architecture, CloudFormation helps standardize deployments and supports modern DevOps practices through automation and version control.

The post AWS CloudFormation Setup Guide: Create & Manage Stacks appeared first on Server Management Services | Cloud Management | Skynats.

In this guide, you’ll learn how to install Dokploy on Ubuntu Server, configure the dashboard, and secure your deployment environment for production use.

Quick Answer

Dokploy can be installed on an Ubuntu server using a single installation script. The installer automatically sets up Docker, Docker Swarm, and Traefik, allowing you to manage and deploy applications through an easy-to-use web dashb

Installation command:

curl -sSL https://dokploy.com/install.sh | sh

http://YOUR_SERVER_IP:3000

Dokploy is an open-source application deployment platform designed for developers and DevOps teams who want complete control over their infrastructure.

It simplifies application deployment by providing a web-based interface that integrates with:

• Docker
• Docker Swarm
• Traefik
• Git repositories
• SSL certificate automation

Many developers consider Dokploy a self-hosted alternative to:

• Heroku
• Vercel
• Netlify

Unlike managed platforms, Dokploy allows you to host applications on your own VPS while maintaining full infrastructure control.

Why Use Dokploy?

Dokploy offers several advantages for developers and businesses:

Benefits of Dokploy

• Simple installation process
• Open-source and self-hosted
• Docker-native deployment
• Built-in reverse proxy management
• Automated SSL certificate support
• Multi-application management
• Resource-efficient architecture
• Beginner-friendly dashboard

For teams looking to reduce hosting costs while maintaining deployment flexibility, Dokploy can be an excellent choice.

Prerequisites

Before installing Dokploy, make sure you have the following:

• A Linux VPS server (Ubuntu, Debian, Fedora, or CentOS)
• Minimum 2GB RAM and 30GB storage recommended
• Root or sudo access
• Open ports:
  • 80 (HTTP)
  • 443 (HTTPS)
  • 3000 (Dokploy dashboard)
• Basic knowledge of Linux terminal commands

Dokploy supports several Linux distributions, here we are using Ubuntu 24 for installing.

How to Install Dokploy on Ubuntu Server

Step 1: Connect to Your Server

Log in to your Ubuntu VPS using SSH.

ssh root@your-server-ip

your-server-ip

with your actual server IP address.

Step 2: Update the Server

Before installing any software, update your system packages.

apt update && apt upgrade -y

curl -sSL https://dokploy.com/install.sh | sh

http://your-server-ip:3000

docker ps

http://your-server-ip:3000

systemctl status docker

ss -tulpn

docker --version

http://your-server-ip:3000

https://deploy.example.com

The post How to Install Dokploy on Ubuntu Server appeared first on Server Management Services | Cloud Management | Skynats.

This happens because CentOS 7 End of Life (EOL) was reached on July 1, 2024. The good news is that the issue can still be fixed temporarily by switching to the CentOS Vault repositories.

Quick Answer

The error occurs because CentOS 7 reached End of Life (EOL) on July 1, 2024, and the official mirror repositories are no longer maintained. To restore package management functionality, update your repository configuration to use CentOS Vault repositories hosted on vault.centos.org.

While this solution allows yum to function again, it is only a temporary workaround. Migrating to a supported operating system such as AlmaLinux or Rocky Linux is strongly recommended.
If your applications are hosted on dedicated infrastructure, a managed dedicated server environment can simplify migration and long-term maintenance.

What Is the CentOS 7 Mirrorlist Error?

The CentOS 7 mirrorlist error occurs when the system attempts to retrieve package information from the official CentOS mirror network.

Since CentOS 7 is now EOL, the standard repositories hosted through mirrorlist.centos.org are no longer available, causing package installation and update operations to fail.

Common symptoms include:

• yum update failures
• Package installation errors
• cPanel update issues
• MultiPHP Manager repository errors
• Failed dependency checks

Why This Error Happens

CentOS 7 repositories are no longer hosted on mirrorlist.centos.org. Since the operating system is now unsupported, package updates and validations stop working unless the repository configuration is changed to use vault.centos.org.
Unsupported operating systems often require additional monitoring, patch management, and server optimization to maintain stability.

Expert Insight

In managed server environments, this issue has become one of the most common support requests for legacy CentOS 7 systems. While switching to Vault repositories restores package access, it does not provide new security patches. Organizations running production workloads should plan a migration strategy immediately.

Prerequisites

Before starting, make sure you have:

• Root or sudo access to the server
• A CentOS 7 system
• Basic knowledge of Linux commands
• Internet connectivity

Step-by-Step Fix

Step 1: Backup the Existing Repository File

Run the following command to create a backup:

This allows you to restore the original configuration if needed.

Step 2: Edit the Repository File

Open the repository file using a text editor:

Replace the existing content with the following:

Save the file and exit.

Step 3: Clean and Rebuild Yum Cache

Run:

This refreshes the repository cache and allows yum to work again.

Verify the Repository

Test whether the fix worked:

If no mirrorlist errors appear, the repository issue has been resolved successfully.

Common Issues After Applying the Fix

Repository Still Not Working

Check DNS connectivity:

ping vault.centos.org

Update CA certificates:

yum update ca-certificates

Run:

scripts/upcp --force

Best Practices for Servers Still Running CentOS 7

Although Vault repositories restore package availability, they should only be considered a short-term solution.

Recommended actions:

1. Audit all CentOS 7 servers.
2. Identify critical applications and dependencies.
3. Create full system backups.
4. Test migration in a staging environment.
5. Migrate to a supported operating system.

Popular alternatives include:

• AlmaLinux
• Rocky Linux
• CloudLinux
• Enterprise Linux distributions

Should You Continue Using CentOS 7?

Only temporarily.
Because CentOS 7 no longer receives security updates, running it in production increases security and compliance risks.

Recommended Approach

Use the Vault repository fix to regain package management functionality, then schedule a migration to a supported operating system as soon as possible.

Conclusion

The CentOS 7 mirrorlist error occurs because CentOS 7 has reached End of Life and the standard repositories are no longer available through mirrorlist.centos.org.

By updating your repository configuration to use vault.centos.org, you can restore yum update functionality and continue managing packages. However, this is only a temporary workaround. For long-term security, stability, and compliance, migrating from CentOS 7 to a supported operating system such as AlmaLinux or Rocky Linux should be your next priority.

The post How to Fix “Could not retrieve mirrorlist” Error on CentOS 7 appeared first on Server Management Services | Cloud Management | Skynats.