Diagram with a central green circle featuring a gear and lock icon, connected by arrows to eight orange circles with lambda and chain link icons. The heading reads Upwind.

Ensure Security for AWS EC2 Instances & Lambda Functions with Upwind’s Non-Human Identity Security 

Joshua Burgin July 09, 2024

Ensure Security for AWS EC2 Instances & Lambda Functions with Upwind’s Non-Human Identity Security 

Using Upwind’s Non-Human Identity Security, you can easily monitor and secure AWS execution roles and ensure best practices for non-human identities (NHIs).

Execution roles are important for granting permissions to AWS EC2 instances and AWS Lambda functions. However, it can be difficult to enforce best practices that allow only known resources to assume and use permissions within the role. Upwind’s Identity Security simplifies this process, providing full visibility and monitoring for all the execution roles in your AWS environment.

Screenshot-2024-07-02-at-12.35.50%E2%80%AFPM-1024x799

What is an Execution Role?

In an AWS cloud environment, an execution role grants permissions to AWS EC2 instances and AWS Lambda functions, to perform actions on behalf of a user or another service. Execution role permissions are IAM permissions that allow EC2 instance or Lambda function permissions to access specific services and resources, and they cannot access any services or resources that are not specified in the permissions. An execution role consists of permissions defined by IAM policies and a trust policy specifying which entity is allowed to assume the role, allowing services to securely access resources without needing permanent credentials.

Screenshot-2024-07-03-at-5.26.29%E2%80%AFAM-1024x661

It’s important to note that Lambda functions and EC2 instances do not have permissions by default, and they rely entirely on the permissions that are granted to them by the execution role. This is designed to follow the Principle of Least Privilege, which grants only the necessary permissions required for a function to perform needed tasks.

Screenshot-2024-07-03-at-5.25.45%E2%80%AFAM-1024x471

How do you secure Execution Roles?

In order to ensure security for your Lambda functions and EC2 instances, you must carefully monitor execution roles and their associated permissions. By controlling the execution role’s permissions and ensuring that it adheres to best practices, you can also ensure your non-human identity security.

Upwind empowers you to do this by providing you with:

  • Execution Role Details: Discover the name of the role, the associated account, and when it was created.
  • An Authorization Graph: Visually understand who can assume a role and what permissions they have on which resources.
  • A list of Trusted Entities: Including the entities that are allowed to assume a particular IAM role
  • A Resources overview: View all resources currently assuming a given role 
  • Highly Privileged Permissions: Automatic identification if a cross-account role’s permissions include highly privileged permissions.

Use Upwind’s Non-Human Identity Security to monitor, track and manage your execution roles and easily understand which resources are currently assuming the role, who can assume a role, and what role permissions they have on EC2 instances and Lambda functions.
To learn more about Upwind’s Non-Human Identity Security, visit the Upwind Documentation Center (login required) or schedule a demo.

Contents

Further Reading

Upwind-Sentinel

Upwind for Microsoft Sentinel – Available on Marketplace and Security Store

Security teams should not have to switch between tools to understand what is happening across their cloud environments. That’s why we’re excited to announce that the Upwind solution for Microsoft Sentinel is now available through the Microsoft Marketplace and the Microsoft Security Store. The integration brings Upwind security data directly into Microsoft Sentinel, helping security…
You Can't Crowdsource Your Way to a Live Adversary

You Can’t Crowdsource Your Way to a Live Adversary

Bug bounty programs were built on a single assumption: that finding a vulnerability was the hard, scarce, expensive part worth paying for. That assumption held for about a decade, then AI erased it. When anyone can point a model at your code and receive a plausible-looking finding back in seconds, a crowd of finders stops…
arrayref Supply Chain Attack

arrayref Supply Chain Attack: A One-Line Build Dependency Ran a Backdoor During cargo build

Key Takeaways Executive Summary arrayref 0.3.10 is a hijacked release of a widely used Rust utility crate that added one dependency, proc-macro1, whose build script downloaded and executed a remote binary at compile time. The release was live on crates.io for 86 minutes on August 20, 2026, alongside [email protected] and [email protected] published from the same…
Add the Upwind RSS Feed to Slack
Connect the Upwind RSS Feed to your Slack.
Follow the how-to here.
Threat RSS
Add the Upwind RSS Feed to Slack
Connect the Upwind RSS Feed to your Slack.
Follow the how-to here.
Main RSS