Connecting and Monitoring AWS Hosted Application URL

Questions
1

Hello,

I have a n8n enviroment running in ECS and I have multiple AWS accounts running an application on a specific port.

I want to check the status of URL and trigger alert e-mails.

Is it possible to achieve this use case in N8N ?

1 Like
2

Hey @Vivek_Jain_Palvia Welcome to the n8n community!

Yep, totally doable in n8n. This is actually one of the more common things people use it for.

The simplest approach is to just let n8n do the checks itself. You set up a Schedule Trigger to run every few minutes, hit each URL with an HTTP Request node, and look at the response. If it comes back “Response code 200” then you’re all good. If it times out or returns something non-2xx, you treat it as down and fire off an email. That’s basically it. You can keep the list of URLs in a Set node, a database, or wherever you like and loop over them, even if they’re spread across different AWS accounts.

Let me know if this helps, Thanks

3

Hi Deepankar,

Thanks for your response, I tried the same approach and request is timing out.

I am trying to understand if we need to open firewall ports between N8N host and Application host/port or there is some other IAM consideration we need to be aware of ?

I see that there are 2 predefined credential type AWS(IAM) and AWS(Assume Role) which one amongst thes2 2 should be used if required ?

Thanks,

Vivek

1 Like
4

Hey @Vivek_Jain_Palvia I think in this case that would over-engineer the prob.

For n8n talking to your application, there’s no special IAM magic involved. n8n is just making outbound HTTP requests. As long as:

  1. the application endpoint is reachable from the n8n host, and
  2. outbound traffic from n8n isn’t blocked,

you don’t need to open any inbound firewall ports on the n8n side. If the app is behind a firewall or in a private VPC, then yes, you’d need network access (VPC peering, VPN, allowlisting the n8n IP, etc.), but that’s purely a network concern, not an n8n or agent one.

On the AWS credentials part:
AWS (IAM)
Use this when n8n itself has direct access to AWS APIs using an access key and secret. This is typical when n8n is outside AWS or you’re okay with static credentials.

AWS (Assume Role)
Use this when n8n is running inside AWS (EC2, ECS, EKS) or when you already have a base IAM identity and want n8n to assume another role via STS. This is generally the preferred and more secure option in AWS-native setups.

If your agent is just calling a REST API or webhook on your application, you don’t need either credential type at all. IAM only comes into play if n8n is calling AWS services directly S3 etc.

5

Hi @Vivek_Jain_Palvia

Welcome to the n8n community :tada: !

It would be a good idea to validate the Security Groups, NACLs, and routing, because a timeout only occurs when the network is blocking the connection; if any of these layers is misconfigured, the issue will appear exactly as you’re seeing now.