Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
i also use amazon, and i watch the costs like a hawk. it can explode quickly.
if youre cost concerned, i would not recommend amazon. although a mature environment, youre paying for it.
that said, the cost explorer is your friend. sorting by 'usage type' over time is what made it start working for me.
i was also able to throw that metric into a default cloudfront dashboard.
if you want serious details, you may need to do as they say and create the user, to access the required metrics.
from recollection you need to create a user who can access the API required to grab the metrics you want. Even in their own system, this user needs to exist before they can show you metrics using their own api.
i ran into similar security accessing my s3 bucket proceduraly.
created new account in https://us-east-1.console.aws.amazon.com/organizations/v2/home/accounts
for some reason got another 12 months of free usage (which was expired on my account)
waited 3 minutes to get the aws account id, before it wasn't appearing
delegated new account in https://s3.console.aws.amazon.com/s3/lens/organization-settings/add-account?region=us-east-1
had no idea about the password, tried to get details on user, it complained that "AWS Account Management trusted access is not enabled"
enabled it here https://us-east-1.console.aws.amazon.com/organizations/v2/home/services/AWS%20Account%20Management
still have no idea how to access this new account, i don't know the password, they only sent me a welcome email
If you create a new account you should have configured a root email address for it. That one should have received an email to login and set the initial password IIRC.
You can get an estimate of what it's going to cost by going to https://calculator.aws
Upload to AWS shouldn't really cost much, unless you're sending a lot of API put requests. Since they are backups I'm going to guess the files are large and will be uploaded as Multi-Part and will probably invoke multiple API calls to do the upload.
My suggestion would be to upload it to s3 and have it automatically transition to glacier for you using a lifecycle rule.
Cost explorer would be your best bet to get an idea of what it'll cost you at the end of the month as it can do a prediction. There is (unfortunately) not a way to see how many API requests you've already done IIRC.
Going by the s3 pricing page, PUT requests are $ 0.005 per 1000 requests( N. Virginia ).
Going by a docs example
https://docs.aws.amazon.com/AmazonS3/latest/userguide/mpuoverview.html
Assuming you're uploading 10x 100gb according to the upload scheme mentioned above you'd make 10.020 API calls which would cost you 10 * 0.005= 0.05$.
Then there would be the storage cost on glacier itself and the 1 day storage on s3 before it transitioned to glacier.
Retrieving the data will also cost you, as well as downloading the retrieved data from s3 back to your device. If we're talking about a lot of small files you might incur some additional costs of the KMS key you used to encrypt the bucket.
I typed all this on my phone and it's not very practical to research like this. I don't think I'd be able to give you a 100% accurate answer if I was on my pc.
There's some hidden costs which aren't Hidden if you know they exist.
Note that (imo) AWS is mostly aimed at larger organisations and a lot of things ( like VMs ) are often cheaper elsewhere. It's the combination or everything AWS does and can do so that makes it worth the while. Once you have your data uploaded to s3 you should be able to see a decent estimate in cost explorer.
Note that extracting all that data back from s3 to your onprem or anywhere or you decide to leave AWS will cost you a lot more than what it cost you to put it there.
Hope this helps!