DEV Community: Anto Online

NextCloud/S3/Latency for fellow chief information officers

Anto Online — Sun, 15 May 2022 23:00:03 +0000

As the chief information officer ;) for my self-hosted NextCloud instance, one of my primary responsibilities is to ensure that the network infrastructure is performant and cost-effective.

This is especially true if your use S3 storage with your NextCloud instance. In my case, I am using Wasabi S3.

Wasabi S3 provides reliable storage and a highly competitive rate. So I knew that I did well as the chief information officer of my one-person show.

However, my NextCloud instance is located in Sydney, and the Wasabi S3 bucket is hosted in the US. My users are based down-under, and Wasabi S3 did not have a data center in Australia. As you can imagine, this did not boast well for the performance side of things since the latency was not great. Even minor delays in transmission can cause significant reductions in usability.

Thankfully Wasabi S3 opened a new data center in Sydney, so I can fulfill my duty to ensure NextCloud is performant.

Read this post to see my test results from AWS and my local ISP:
https://anto.online/tips-and-tools/wasabi-s3-speed-test-results-from-sydney-australia/

I have now decided to move my data from the US and Australia. This is guaranteed to improve latency and help boost performance for all my users.

Hello fellow developers!

Anto Online — Sat, 14 May 2022 21:31:28 +0000

I'm so excited to be a part of the dev.to the community! There are some great people here. I love how everyone can share ideas and learn from each other.

Why not follow each other? It would be great to learn something new.

As an introduction:

I am a fan of Linux, serverless, and code. I work by day at a SaaS provider that uses lots of Cloud tech. During the night, I code to my heart's content on little side projects as a form of meditation.

The CORS specter...

Anto Online — Fri, 13 May 2022 21:30:53 +0000

I sat down at my computer to work on my new website. The task was simple! Connect the frontend with the backend API.

All was going well until suddenly my browser console said: "CORS errors whoo, haha!"

What? I already enabled CORS support, and I allowed any. (knowing this is bad practice) I rechecked everything and was sure everything was correct. So what's going on?

This is what I did to squash the CORS specter while trying to integrate two AWS Lambda Proxy REST API resources:
[https://anto.online/code/how-to-set-up-cors-for-an-aws-lambda-proxy-rest-api-resource/]

I hope this guide will save you the many hours of debugging I had to endure.