# Issues with AWS CDN and S3
**URL:** https://meta.discourse.org/t/issues-with-aws-cdn-and-s3/391132
**Category:** Self-hosting
**Tags:** cdn, s3
**Created:** [10 בדצמבר, 2025, 3:15am UTC](https://meta.discourse.org/t/issues-with-aws-cdn-and-s3/391132 "2025-12-10T03:15:44Z")
**Posts on this page:** 4
**Page:** 2
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [20 בדצמבר, 2025, 9:44pm UTC](https://meta.discourse.org/t/issues-with-aws-cdn-and-s3/391132/21 "2025-12-20T21:44:29Z")
Nice work! So glad you figured it out.
Now you should be able to spin up a new server with just your `app.yml` file. You can even try it if you want (change the hostname on the test site before you build the container).
---
### Author:  [@philh](https://meta.discourse.org/u/philh)
#### Post date: [20 בדצמבר, 2025, 11:46pm UTC](https://meta.discourse.org/t/issues-with-aws-cdn-and-s3/391132/22 "2025-12-20T23:46:58Z")
Tried that and saw the message when proceeding with setup without a valid domain.
```plaintext
Checking your domain name . . .
WARNING: Port 443 of computer does not appear to be accessible using hostname: discourse.example.com.
WARNING: Connection to http://discourse.example.com (port 80) also fails.
This suggests that discourse.example.com resolves to some IP address that does not reach this
machine where you are installing discourse.
The first thing to do is confirm that discourse.example.com resolves to the IP address of this server.
You usually do this at the same place you purchased the domain.
If you are sure that the IP address resolves correctly, it could be a firewall issue.
A web search for "open ports YOUR CLOUD SERVICE" might help.
This tool is designed only for the most standard installations. If you cannot resolve
the issue above, you will need to edit containers/app.yml yourself and then type
./launcher rebuild app
```
Gave it a go but probly messed up on
> [@pfaffman](#):
>
> (change the hostname on the test site before you build the container)
---
### Author:  [@philh](https://meta.discourse.org/u/philh)
#### Post date: [30 בדצמבר, 2025, 4:20am UTC](https://meta.discourse.org/t/issues-with-aws-cdn-and-s3/391132/23 "2025-12-30T04:20:27Z")
> [@philh](#):
>
> I may write things up but a few notes for now:
Applying the lessons learned was/is a bit of an undertaking. It is a work in progress but hopefully if will help others.
> [@Configuring AWS's Amazon S3 for storage and Cloudfront for CDNs](https://meta.discourse.org/t/configuring-awss-amazon-s3-for-storage-and-cloudfront-for-cdns/392369):
>
> [Getting Started](#heading--getting-started) You will need: A Discourse instance with app.yml access AWS account [Naming Strategy](#naming-strategy) There are many places to make mistakes. Using a naming convention strategy that makes sense to you and perhaps others will help you with troubleshooting especially if you are configuring multiple Discourse instances. IAM user: your-iam-user Policy: s3-discourse-policy-your-iam-user Backups bucket: yourdomain-subdomain-backups Uploads bucket: yourdomain-subdomain-uploads Distribution CDNs: cdn…
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [29 בינואר, 2026, 4:20am UTC](https://meta.discourse.org/t/issues-with-aws-cdn-and-s3/391132/24 "2026-01-29T04:20:55Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
[Previous page](https://meta.discourse.org/t/issues-with-aws-cdn-and-s3/391132.md?page=1)