Incorrect Permissions and Security Settings Top Cloud Deployment Challenges

May 1, 2026 · Editor · 3 min read

Original source: GigamonTV

This video from GigamonTV covered a lot of ground. 2 segments stood out as worth your time. Everything below links directly to the timestamp in the original video.

Understanding these common missteps can help organizations prevent costly errors and downtime, ensuring smoother and more secure cloud operations from the outset.

Incorrect Permissions and Security Settings Top Cloud Deployment Challenges

Technical deployments in cloud environments frequently encounter issues due to misconfigured permissions and security policies. Common pitfalls include having the wrong personnel manage AWS tasks, improper Identity and Access Management (IAM) policies for virtual appliances, and inadequately configured security groups that block necessary traffic flow. These errors prevent crucial communication and operation within cloud infrastructure, underscoring the importance of precise setup.

Addressing these deployment challenges is critical for maintaining robust and secure cloud operations. The necessity of a load balancer for traffic management in AWS, particularly when monitoring more than 10 instances, highlights the scaling complexities that require careful architectural planning. An AWS document further reinforces this requirement, illustrating how traffic is routed through a load balancer to virtual network appliances when the instance count exceeds ten.

"It's going to be do I have the right permission or get the right person to do the work within AWS, do I have the proper IAM policy for to give the Gigamon virtual appliances the appropriate permissions to actually work within my environment, and third it's going to be the security policies or security groups, do I have the ports and protocols open to allow that traffic to flow?"

▶ Watch this segment — 34:04

Fabric Manager Deployment Flexible Across Cloud and On-Premises Environments

Fabric Manager, a key component for network monitoring, offers flexible deployment options, not requiring exclusive installation within AWS. It can be deployed on-premises as a physical Dell blade, as a virtual appliance on platforms like VMware or OpenStack, or in other cloud environments such as Azure. The critical factor for its functionality is possessing the correct permission sets to communicate effectively with the AWS environment, regardless of its deployment location.

This deployment flexibility is crucial for organizations with hybrid cloud strategies or those leveraging multiple cloud providers. Additionally, AWS imposes specific requirements for monitoring large-scale deployments, mandating a load balancer when more than 10 instances are being monitored via VPC mirroring. This ensures efficient aggregation and delivery of traffic to the monitoring toolset, preventing performance bottlenecks in extensive cloud infrastructures.

"I can have Fabric Manager deployed on-premise, like a physical Dell blade, which we call a Thunder blade. It can be a virtual appliance that's deployed on VMware, Nutanix, OpenStack. It can be deployed in Azure. Or in here, it boils down to, do I have the right permission sets for Fabric Manager to communicate into the AWS environment?"

▶ Watch this segment — 31:48