Skip to main content

AWS Pricing


The Price Is….

Varied. How it works is more important than how it’s priced at this point, so this will be brief(er).

E2 and RDS have Reserved Capacity, save up to 75% over the equivalent of on-demand capacity.

Instances are;



  • All Up Front (AURI)
  • Partial Up Front (PURI)
  • No Upfront (NURI)

Bigger the upfront payment, bigger the discount.

Minimize risk, manage budget, comply with longer-term commitments.

There are volume-based discounts.
S3 and transfer out from EC2 has tired prizing, most you use, less you pay per gigabite. (Inbound data transfer is always free).

Storage Services Portfolio can help lower your pricing based on how frequently you access data and what it takes to retrieve it.

And there is custom pricing for your projects if you need it.

With AWS, you pay for
  • Compute
    • By the hour with On-Demand Instances.
    • No minimum requirements
  • Data transfer Out (Not In)
    • Aggregated across EC2, S3, RDS, SimpleDB, SQS, SNS, VPC.
    • Charged at outbound data transfer rate.
  • Storage
    • Standard has 11 9s of durability
    • Standard Infrequent Access reduces cost by storing less frequently accessed data (cool data) with slightly less redundancy in place.
    • What’s in your buckets and the size and amount.
    • Volume storage - Amt provisioned in GBs per month
    • Your active Database Instance is fully backed up with no additional charge, if you delete your DBI, then you’re charged per GB per month.

Comments

Popular posts from this blog

Connecting IoT Devices to a Registration Server (Packet Tracer, Cisco)

In Packet Tracer, a demo software made by Cisco Systems. It certainly has changed a lot since 2016. It's almost an Olympic feat to even get started with it now, but it does look snazzy. This is for the new CCNA, that integrates, among other things, IoT and Automation, which I've worked on here before. Instructions here . I don't know if this is an aspect of "Let's make sure people are paying attention and not simply following blindly", or an oversight - The instructions indicate a Meraki Server, when a regular one is the working option here. I have to enable the IoT service on this server. Also, we assign the server an IPv4 address from a DHCP pool instead of giving it a static one. For something that handles our IoT business, perhaps that's safer; Getting a new IPv4 address every week or so is a minimal step against an intruder, but it is a step. There are no devices associated with this new server; In an earlier lab (not shown), I attached them to 'H

What Do You Need? [List of Offered Services]

2023 Version is here, at this handy Notion Page.

Building, Breaking, and Building A CRM with Retool

 I like no- or low-code solutions to things. I've often wanted to simply push a button or move some GUI around and have the code implement itself.  I've thought about building something that's like a customer relationship management (CRM) system for keeping up with my network better than my little spreadsheet where I click links and then go like something. The general idea in this CRM Development is:  To have a GUI to add people to a NRM (Network Relationship Management).       Attach it to a database (MySQL is what I went with eventually using Amazon Relational Database service, but you can use PostGRES, and probably others).     Make sure components are connected to each other in the retool interface. This video is a good start. Watching the tutorial video, heard some SQL commands and went 'Oh no 😳" before going "Wait I know basic SQL", which is good, because you'll see.  When you get set up, there's a plethora of resources you can use -- Incl