Cloud Security, Reliability and Performance Efficiency Management

Ensure compliance and efficiency across all your resources and all your accounts

All of AWS’s key pillars & best practices in one place

Infrastructure Security

AWS Security Groups & encryption management

IAM visibility & control

Auto-remediation of security threats

Infrastructure Reliability

Zero down time 

Up-to-date & available resources

Automation & event-response 

Performance efficiency

Optimized resource usage

No human errors

Minimal anomaly resolution time

Scale continuous efficiency with TotalCloud’s solutions

Insights

Adopt ready-to-use insights to give you complete visibility into the security, reliability & performance of your cloud. These rule checks are compliant with the AWS security best practices.

View More

Auto-remediation

Set up event-based responses to deal with cloud anomalies and inefficiencies that are causing security threats, downtime or resource overruns. As soon as an event occurs, an auto-remediation workflow is triggered to fix issues in real-time.

View More

Automation Builder

You can create custom insights, reports and actions using workflows, with simple scaling and integration features, based on your security and monitoring needs.

View More

Ensure AWS compliance automation, from anywhere

Integrate with your management and ticketing softwares to directly perform reliability & high availability actions. Whether it’s EBS volume resize, EC2 rightsizing or Instance reboot, it can be triggered from anywhere.

Some of our powerful use cases

Access, edit and execute some of our commonly used templates to achieve specific best practice use cases. You can always create your own with our Automation Builder.

Security Group Management

Report & correct SGs that allow unrestricted access from public IPs to eliminate data breaches, leaks and DoS attacks.

NACL Management

Manage NACL rules being used by you and the state of your outbound and inbound rules to prevent unrestricted flow of traffic.

Utilization Reports

You can use TotalCloud’s workflows to access reports of over & under-utilized instances and clusters.

Send report of Security Groups which allow https access on public IP

It is AWS best practice to get aware of Security Groups which allows HTTPS access from public IP to reduce possibility of breach.

Send report of Security Groups which allows Oracle DB(TCP port 1521 ) access from public IP.

It is AWS best practice to get aware of Security Groups which allows Oracle DB access from public IP to reduce possibility of breach.

Send report of Security Groups which allows PostGreSql DB(TCP port 5432 ) access from public IP.

It is AWS best practice to get aware of Security Groups which allows PostGreSQL DB access from public IP to reduce possibility of breach.

Send report of Security Groups which allows SMTP (TCP port 25 ) access from public IP.

It is AWS best practice to get aware of Security Groups which allows SMTP access from public IP to reduce possibility of breach.

Send Report of Security Groups which allows MySQL(TCP port 3306 ) access from public IP.

It is AWS best practice to get aware of Security Groups which allows MySQL access from public IP to reduce possibility of breach.

Send report of security groups with empty descriptions

It is an AWS best practice to give a description for your security groups. It helps in quickly getting more insight into the configuration of your security group. You should define the purpose and identity of the IP address to each rule. This workflow sends a report of security groups which do not have descriptions to any of the rules.

Remove entries in security group which allows MongoDB(TCP port 27017) access from public IP.

It is AWS best practice to remove entries in security group which allows MongoDB access from public IP to reduce possibility of breach.

Send report of Security Groups which allows MSSQL(TCP port 1433) access from public IP.

It is AWS best practice to get aware of Security Groups which allows MSSQL access from public IP to reduce possibility of breach.

Send report of security group which allows FTP( TCP port 20 and 21) access from public IP.

It is AWS best practice to remove entries in security group which allows FTP access from public IP to reduce possibility of breach.

Apply new rules to AWS Security Group

Create or authorize a specific rule based on your security practice, to regulate inbound and outbound traffic effectively.

Remove entries in security group which allows PostGreSql DB(TCP port 5432 ) access from public IP.

It is AWS best practice to remove entries in security group which allows PostGreSQL DB access from public IP to reduce possibility of breach.

Remove entries in security group which allows RPC (TCP port 135 ) access from public IP.

It is AWS best practice to remove entries in security group which allows RPC access from public IP to reduce possibility of breach.

Report If High EC2 Instance Security Group Rules Count

A high number of security group rules for EC2 instances increases latency and impacts network performance when trying to access the instance. Reducing redundant and overlapping rules helps to ensure optimal performance.

Security Group internet accessibility report

Security Group internet accessibility report helps you view inbound and outbound traffic rules; Security Groups act as a virtual firewall for your instances.Our weekly/daily report helps users to ascertain the security posture of EC2 instances.

Send report of all Security Group change events.

Send report of all the Security Group changes in your AWS account i.e. if any operations like create/delete/edit any Inbound/Outbound rule is performed in your AWS account then this workflow will generate a report of it and send it to your email.

Remove entries in security group which allows SMTP (TCP port 25 ) access from public IP.

It is AWS best practice to remove entries in security group which allows SMTP access from public IP to reduce possibility of breach.

Remove entries in Security Groups which allow CIFS (TCP 445) on public IP.

It is AWS best practice to remove entries in security group which allows CIFS access from public IP to reduce possibility of breach.

Remove entries in security group which allows FTP( TCP port 20 and 21) access from public IP.

It is AWS best practice to remove entries in security group which allows FTP access from public IP to reduce possibility of breach.

Send report of security group which allows Elastic Search(TCP port 9200) access from public IP.

It is AWS best practice to remove entries in security group which allows Elastic Search access from public IP to reduce possibility of breach.

Remove entries in security group which allows DNS(TCP port 53 and UDP port 53 ) access from public IP.

It is AWS best practice to remove entries in security group which allows DNS access from public IP to reduce possibility of breach.

Send report of Security Groups which allows RDP (TCP port 3389) access from public IP.

It is AWS best practice to get aware of Security Groups which allows RDP access from public IP to reduce possibility of breach.

Remove entries in Security Group which allow https access on public ip

It is AWS best practice to remove entries in security group which allows HTTPS access from public IP to reduce possibility of breach.

Remove entries in security group which allows RDP (TCP port 3389) access from public IP.

It is AWS best practice to remove entries in security group which allows RDP access from public IP to reduce possibility of breach.

Remove entries in security group which allows MSSQL(TCP port 1433) access from public IP.

It is AWS best practice to remove entries in security group which allows MSSQL access from public IP to reduce possibility of breach.

Send report of Security Groups which allows RPC (TCP port 135 ) access from public IP.

It is AWS best practice to get aware of Security Groups which allows RPC access from public IP to reduce possibility of breach.

Report Subnets using default NACL

This template generates a report of the Subnets using default NACL, securing your AWS cloud infrastructure.

Report NACL rules

This template generates a report of all the NACL rules, helping you manage your resources efficiently.

Send report of network change events.

This workflow sends a report of all the network changes in your AWS account, in case actions like create/delete RouteTable/Routes are performed

Report Unrestricted Network ACL for Outbound Rules.

This workflow sends a report of AWS Network Access Control Lists (NACLs) for outbound rules that allow traffic from all ports.

Report Unrestricted Network ACL for Inbound Rules.

This workflow sends a report of AWS Network Access Control Lists (NACLs) for inbound rules that allow traffic from all ports.

Send report of Network ACL change events.

This workflow sends a report of all the Network ACL changes in your AWS account. In case actions like create/delete Network ACL or create/delete/replace Network ACL entry are performed.

Instance CPU utilization report

Workflow to send a report of Instances CPU utilization. It gives an overview of CPU utilization of your EC2 instances.

Elasticache clusters utilization report

This workflow gives an overview of CPU utilization of your Elasticache clusters through a simple report. 

Report EMR clusters with high CPU utilization.

Sends a report of EMR clusters if their HDFS utilization goes above than 90%. Instances with high HDFS utilization should be rebooted to improve the performance.

Report RDS instances with high CPU utilization.

Sends a report of RDS instances if their CPU utilization goes above than 90%. Rebooting such instances will improve the performance.

Report EC2 instances with high utilization.

Sends a report of EC2 instances if their CPU utilization goes above than 90%. Such instances should be rebooted or rightsized. 

Report Elasticache cluster with high CPU utilization.

Sends a report of Elasticache clusters whose CPU utilization is above 90%. Clusters with high CPU Utilization should be rebooted to improve the performance.

Redshift clusters utilization report

This workflow gives an overview of CPU utilization of your Redshift clusters through a simple report.  

RDS DB instance utilization report.

This workflow gives an overview of CPU utilization of your RDS DB instances through a simple report.  

Report Redshift clusters with high CPU utilization.

Sends a report of Redshift cluster if CPU utilization goes above than 90 %. Clusters with high CPU utilization should be rebooted this will improve the performance.
More Use Cases