# COG - Cloud Access S3/Swift/
**URL:** https://community.qfield.org/t/cog-cloud-access-s3-swift/357
**Category:** Ask the Community
**Tags:** gh-import
**Created:** [14 May 2025 02:09 UTC](https://community.qfield.org/t/cog-cloud-access-s3-swift/357 "2025-05-14T02:09:00Z")
**Posts on this page:** 9
**Page:** 1
### Author:  [@system](https://community.qfield.org/u/system)
#### Post date: [14 May 2025 02:09 UTC](https://community.qfield.org/t/cog-cloud-access-s3-swift/357/1 "2025-05-14T02:09:00Z")
Is there the possiblity to access a CloudOptimized Geotiff somewhere in an Object storage, with authentification.
I tried arrount with COG in the cloud a bit. A Layer without auth. works in QField on my mac desktop, but on the Android tablet the error (picture) comes. So my first intention was to ask here what is possible and implemented in QField?
* * *
_Imported from [GitHub discussion](https://github.com/opengisch/qfield/discussions/4412) by @EulenspiegelTill on 2023-07-03T07:22:40Z_
---
### Author:  [@system](https://community.qfield.org/u/system)
#### Post date: [14 May 2025 02:09 UTC](https://community.qfield.org/t/cog-cloud-access-s3-swift/357/2 "2025-05-14T02:09:02Z")
EulenspiegelTill , we fixed an issue on Android which unlocked this very functionality. You can confirm it works using an APK provided here: [Package CAs for curl by nirvn · Pull Request #4415 · opengisch/QField · GitHub](https://github.com/opengisch/QField/pull/4415)
* * *
_Imported from [GitHub comment](https://github.com/opengisch/QField/discussions/4412#discussioncomment-6357777) by @nirvn on 2023-07-05T01:39:16Z_
---
### Author:  [@system](https://community.qfield.org/u/system)
#### Post date: [14 May 2025 02:09 UTC](https://community.qfield.org/t/cog-cloud-access-s3-swift/357/3 "2025-05-14T02:09:05Z")
Work’s perfect! I will try arround a bit with compression and see whats working smooth. Also try out authentification (enviroment variables 🙃 ) on QGiS side with gdal, and will be back at you with that. but need some spare time first to try arround.
Thank’s!
* * *
_Imported from [GitHub comment](https://github.com/opengisch/QField/discussions/4412#discussioncomment-6359129) by @EulenspiegelTill on 2023-07-05T06:26:21Z_
---
### Author:  [@system](https://community.qfield.org/u/system)
#### Post date: [14 May 2025 02:09 UTC](https://community.qfield.org/t/cog-cloud-access-s3-swift/357/4 "2025-05-14T02:09:07Z")
Since the newest version (3.4.7 - Ebo) I face this problem again. I can not access a public s3 COG from within QField but I have no problem accessing it with QGis.
On another note, is there a way to set AWS credentidals in QField?
* * *
_Imported from [GitHub comment](https://github.com/opengisch/QField/discussions/4412#discussioncomment-12277880) by @SilvioMueller on 2025-02-21T15:27:06Z_
---
### Author:  [@system](https://community.qfield.org/u/system)
#### Post date: [14 May 2025 02:09 UTC](https://community.qfield.org/t/cog-cloud-access-s3-swift/357/5 "2025-05-14T02:09:08Z")
SilvioMueller , could you attach a sample project here with that public S3 cog layer? It’ll be hard to look into this possible regression otherwise.
The latest version is now 3.5.0, have you tested there?
* * *
_Imported from [GitHub comment](https://github.com/opengisch/QField/discussions/4412#discussioncomment-12283083) by @nirvn on 2025-02-22T01:57:12Z_
---
### Author:  [@system](https://community.qfield.org/u/system)
#### Post date: [14 May 2025 02:09 UTC](https://community.qfield.org/t/cog-cloud-access-s3-swift/357/6 "2025-05-14T02:09:10Z")
Thanks for looking into this.
I tried it in this project: silviom/AWS\_Test2/. One important point I forgot to add, the COG is only accessible for some whitelisted IP’s. I am trying to avoid to have my AWS objects completely public. It seems the problem is with QGIS Cloud:
```auto
08:46:27.882 QGSMSGLOG WARNING Layer "Basel_4_2" cannot be packaged and will be removed because "PackagePreventionReason.INVALID".
08:46:27.882 libqfieldsync WARNING Layer "Basel_4_2" cannot be packaged and will be removed because "PackagePreventionReason.INVALID".
```
* * *
_Imported from [GitHub comment](https://github.com/opengisch/QField/discussions/4412#discussioncomment-12297863) by @SilvioMueller on 2025-02-24T08:53:10Z_
---
### Author:  [@system](https://community.qfield.org/u/system)
#### Post date: [14 May 2025 02:09 UTC](https://community.qfield.org/t/cog-cloud-access-s3-swift/357/7 "2025-05-14T02:09:11Z")
SilvioMueller , ah, so, if you import your project into QField through other means (USB cable, import zipped project URL, etc.), does it work?
* * *
_Imported from [GitHub comment](https://github.com/opengisch/QField/discussions/4412#discussioncomment-12297897) by @nirvn on 2025-02-24T08:56:59Z_
---
### Author:  [@system](https://community.qfield.org/u/system)
#### Post date: [14 May 2025 02:09 UTC](https://community.qfield.org/t/cog-cloud-access-s3-swift/357/8 "2025-05-14T02:09:13Z")
SilvioMueller thank you for these two key lines from the log! This is a `libqfieldsync` issue, tbh it was never tested directly with Object storage provider.
* * *
_Imported from [GitHub comment](https://github.com/opengisch/QField/discussions/4412#discussioncomment-12297959) by @suricactus on 2025-02-24T09:02:49Z_
---
### Author:  [@system](https://community.qfield.org/u/system)
#### Post date: [14 May 2025 02:09 UTC](https://community.qfield.org/t/cog-cloud-access-s3-swift/357/9 "2025-05-14T02:09:14Z")
Ah I see! just for completeness, i exported the project directly to QField by plugging the Tablet. This also did not work
* * *
_Imported from [GitHub comment](https://github.com/opengisch/QField/discussions/4412#discussioncomment-12298450) by @SilvioMueller on 2025-02-24T09:47:32Z_