Can i redirect the storage path of my AGORA from AWS to a local server? - agora.io

As a startup, I am trying to cut down on my cost, and the smallest AWS package is about $1250/monthly, so Can I redirect the storage path of my AGORA from AWS to a local server?

Related

OpenStack Swift S3 object storage configuration in Kaltura community edition

Kaltura community edition support file remote storage including S3 object storage from Amazon AWS. Configuration settings in GUI are:
With Amazon AWS settings it works perfectly, but it doesn't work with custom storage endpoint like OpenStack Swift. Despite that storage url in configuration is different than AWS, server still using one of preconfigured regions of Amazon AWS endpoints.
Server is Ubunty 16, Kaltura community edition version - Propus - 16.06, installation from: Kaltura installation scripts
After installation there are different AWS configuration files for S3 endpoints on /opt/kaltura
One is in /opt/kaltura/app/vendor/aws/Aws/Common/Resources/public-endpoints.php
After adding custom endpoint in code
'newregion' => array(
'endpoint' => '100.100.XX.XX:8080'
)
and writing in GUI configuration new region, system still using Amazon AWS endpoints.
Expected configuration for S3 Non-AWS enpoint could be:
Storage URL: 100.100.XX.XX:8080 [OpenStack, not AWS endpoint]
Storage base Directory: bucketname/foldername
Path Manager: External Path
Storage username: Openstack S3 Access
Storage Password: Openstack S3 Secret

Running aws S3 locally to test saving of images

Hi everyone we implemented aws S3 for uploading images and generating pdfs through this images. However on our local testing server we cannot use the aws S3 locally and I am looking for ways to run aws S3 locally maybe using docker or another software.
Do you have any recommendations?
EDIT: I use docker for the local DB and Tomcat for the local server
You can NOT run S3 locally.
What you can do is to mimic the S3 API calls.
see https://github.com/spulec/moto
https://medium.com/#l.peppoloni/how-to-mock-s3-services-in-python-tests-dd5851842946

AWS S3 and AWS ELB instead of AWS Elastic beanstalk for SPA Angular 6 application

I am creating an Angular 6 frontend application. My backend api are created in DotNet. Assume the application is similar to https://www.amazon.com/.
My query is related to frontend portion deployment related only, on AWS. Large number of users with variable count pattern are expected on my portal. I thought of using AWS elastic beanstalk as PAAS web server.
Can AWS S3/ ELB be used instead of PAAS beanstalk without any limitations?
I'm not 100% sure what you mean by combining an Elastic Load Balancer with S3. I think you may be confused as to the purpose of the ELB, which is to distribute requests to multiple servers e.g. NodeJS servers, but cannot be used with S3 which is already highly available.
There are numerous options when serving an Angular app:
You could serve the files using a nodejs app, but unless you are doing server-side rendering (using Angular Universal), then I don't see the point because you are just serving static files (files that don't get stitched together by a server such as when you use PHP). It is more complicated to deploy and maintain a server, even using Elastic Beanstalk, and it is probably difficult to get the same performance as you could do with other setups (see below).
What I suspect most people would do is to configure an S3 bucket to host and serve the static files of your Angular app (https://docs.aws.amazon.com/AmazonS3/latest/dev/WebsiteHosting.html). You basically configure your domain name to resolve to the S3 bucket's url. This is extremely cheap, as you are not paying for a server which is running constantly, but rather only have to pay the small storage cost and plus a data transfer fee which would be directly proportional to your traffic.
You can further improve on the S3 setup by creating a CloudFront distribution that uses your S3 bucket as it's origin (the location that it get files from). When you configure your domain name to resolve to your CloudFront distribution, then instead of a user's request getting the files from the S3 bucket (which could be in a region on the other side of the world and so slower), the request will be directed to the closest "edge location" which will be much closer to your user, and check if files are cached there first. It is basically a global content delivery network for your files. This is a bit more expensive than S3 on it's own. See https://aws.amazon.com/premiumsupport/knowledge-center/cloudfront-serve-static-website/.

Is it possible to use Amazon S3 for folder in a .net site

Is it possible to use Amazon Simple Storage Service (S3) for folders & files on a .net site?
Background:
I have 200 websites sites and I would like to have a single common code base. Right now they are on a single dedicated server. I plan to move them to an EC2 server.
As you can see, some of the folders & files are not on S3 and some are.
Admin Panel - is a folder that requires authentication - is this an issue?
/Bin/ - contains DLL's - is this an issue?
EC2 is normal Windows Server like your current dedicated server. You remote desktop into it, install whatever you need, setup IIS etc.
S3 on the other hand is just a storage device. Think of it like a big NAS device. So you can use it to serve your static content (possible in conjunction with Cloudfront) but the actual website (Dlls, aspx pages etc) will have to be on EC2 in IIS.

404 redirect with cloud storage

I'm hoping to reach someone with some experience using a service like Amazon's S3 with this question. On my site we have a dedicated image server. And on this server, we have an automatic 404 redirect through Apapche so that, if a user tries to access an image that doesn't exist, they'll see a snazzy "Image Not Available" image.
We're looking to move the hosting of these images to a cloud storage solution (S3 or Rackspace's CloudFiles), and I'm wondering if anyone's had any success replicating this behavior on a cloud storage service and if so how they did it.
THe Amazon instances are just like normal hosted server instances once they are up and running so your Apache configuration could assumedly be identical to what you currently have.
Your only issue will be where to store the images. The new Amazon Elastic Block Store makes it easy to mount a drive based on S3 backed data. You could store all your images on such a volume and use it with your Apache instance.