<p>We have two ec2 instances and a private IP db instance along with a Amazon Load Balancer.</p>
<p>Is there a way to upload images on CraftCMS domain pointing to a load balancer?</p>
<p>Right now the assets image upload hangs.</p>
<p>The images are uploaded successfully if we disable the load balancer or when we create multiple A records pointing to the IPs resolved by querying the load balancer.</p>
<p>Is there a plugin or an effective way to resolve this?</p>

CC BY-SA 4.0
2022-11-14T18:30:57.883Z
"Right now the assets image upload hangs." - I'd check logs - either the ALB logs in Cloudwatch, wherever Craft's logs are configured to write to (in case the request is actually making it to the server), etc. and look for the underlying error to figure out where to debug.
Brad Bell
CC BY-SA 4.0
2022-11-29T17:31:20.703Z
I figured that the loadbalancer is causing the issue. When you point several A records to the IPs which the loadbalancer is resolving and removing the CNAME record, it works. This is not ideal when a load balancer is in place.
Noor M
<craft3><assets><assets-field><aws><load-balancer>
AWS Load Balancer - Assets Uploads
# AWS Load Balancer - Assets Uploads

(Asked by: username_0 on 2022-11-13)

We have two ec2 instances and a private IP db instance along with a Amazon Load Balancer.

Is there a way to upload images on CraftCMS domain pointing to a load balancer?

Right now the assets image upload hangs.

The images are uploaded successfully if we disable the load balancer or when we create multiple A records pointing to the IPs resolved by querying the load balancer.

Is there a plugin or an effective way to resolve this?

**Tags:** craft3, assets, assets-field, aws, load-balancer
> **Comments:**
> **username_1**: "Right now the assets image upload hangs." - I'd check logs - either the ALB logs in Cloudwatch, wherever Craft's logs are configured to write to (in case the request is actually making it to the server), etc. and look for the underlying error to figure out where to debug.  
> **username_0**: I figured that the loadbalancer is causing the issue. When you point several A records to the IPs which the loadbalancer is resolving and removing the CNAME record, it works. This is not ideal when a load balancer is in place.  

---

## 0 answers

