cost-estimation-aws.pdf

AWS Cost Estimation

February 25, 2021 Version 3

Introduction

The objective of this document is to provide Mission System Owners with a basic understanding of how to leverage the AWS cost calculator to accurately project cloud hosting costs. Topics that will be covered include:

• How to access the AWS cost calculator tool

• Basic usage ‘best practices’ for estimating costs in Cloud One

• Baseline costs: Managed services that are required for all Cloud One hosted systems

• Mission System resource cost estimation

• Predicting and optimizing annual operational cost

• Other resources & relevant information (Intelink invoicing)

AWS Cost Calculator:

The Basics

AWS Cost Calculator: The Basics

The AWS Cost Calculator is a tool that provides the following:

• Web-based UI for estimating monthly costs and extrapolating to annual cost estimates.

• Up-to-date pricing rates for AWS services and their various cost models.

• Allows for estimating temporary usage of resources – estimating autoscaling and/or other resources that are not provisioned 100% of the time.

• Saving, exporting and sharing cost profiles - providing the capability to save progress, collaborate with other team members, and objectively evaluate the cost impact associated with changes to architecture or service consumption.

Key points to remember when using the Cost Calculator tool for a Cloud One hosted Mission System:

• The AWS Cost Calculator is located at: https://calculator.s3.amazonaws.com/index.html

• Costs vary between regions. Ensure the appropriate region is selected: AWS GovCloud (US West).

• Impact Level 5 systems are required to run on “Dedicated Instances” which have a different cost model. Ensure this option is selected if your Mission System is classified at IL-5.

• Ensure services being utilized or estimated are approved at the system’s Impact Level. AWS provides this information at https://aws.amazon.com/compliance/services-in-scope/ (under the DoD SRG sub-tab).

• Tool limitation to note: AWS Marketplace charges are not able to be estimated within the tool.

To estimate AWS Marketplace charges, the underlying EC2 charges can be estimated using the tool. Additional charges (software licenses, etc.) must be estimated separately (using the AWS marketplace provided pricing pages).

https://calculator.s3.amazonaws.com/index.html https://aws.amazon.com/compliance/services-in-scope/

Save/Share/Export is a powerful AWS cost calculator capability that allows a Mission System team to pre-configure a baseline configuration and share it with others. Many of the examples later in this presentation leverage save/share to provide reusable examples of common Cloud One configurations.

• “Save and Share” generates a URL that can be used in the future or shared. This URL brings the user to a cost calculator prefilled with the resources and values previously saved.

• ”Save and Share” is most useful for collaborating, sharing, and saving progress/estimates in the tool.

• “Export to CSV” generates a unique CSV file based on the resources defined within the calculator. This file can be downloaded, modified, shared, etc.

• ”Export to CSV” is most useful for reporting/saving data from the tool in an offline format.

Baseline Costs

AWS Cost Calculator: Baseline Costs Overview

Cloud One provisions several resources within every system’s AWS Account. AF-CCE maintains these services with no action required by the MSO, however the compute/store costs associated with these resources is the responsibility of the mission team. In the event these services are changed or updated in the future, MSO’s will be notified in advance so they can plan and budget accordingly.

• The services provisioned by the Cloud One team are:

• Bastion hosts

• Deployment Tooling

• Egress Firewalls

• AWS CloudTrail

• AWS GuardDuty

• AWS Config

• AWS Key Management Service

AWS Cost Calculator: Baseline Costs Overview

Not all of the Cloud One provisioned services are capable of being estimated in the AWS Cost Calculator. However, the services missing from the calculator typically have a negligible impact on over-all cost. Therefore, the templates provided will only include the major cost drivers.

To assist with estimations, the Cloud One baseline services are broken up into major cost drivers and minor cost drivers:

• Minor cost drivers:

• AWS CloudTrail

• AWS GuardDuty

• AWS Config

• AWS Key Management Service

• Major cost drivers:

• Bastion hosts

• Deployment Tooling

• Egress Firewalls

AWS Cost Calculator: Baseline Costs

• Major Cost Drivers (Major Impact on Cost):

• Bastion hosts – Each Mission System environment is provisioned with 2 bastion hosts. Bastion hosts are Windows servers accessed by the Common Gateway Service within Cloud One. These hosts are used for management plane traffic to securely access resources within the MSO’s AWS account. Estimated Cost:

$320/month

• Deployment Tooling – Jenkins is used to execute automation code to deploy resources and systems within the MSO’s AWS account. Jenkins is accessed by the MSO’s privileged users while logged into the Bastion Hosts. Estimated Cost: $117/month

• Egress Firewalls – The Egress Firewalls are virtual appliances that are purchased (with licensing included) in a metered, pay-as-you-go model. They filter network traffic leaving the Mission System’s network (as required by the Cloud One ATO). There are two firewall devices in Production and one each in Int and Test.

Estimated Cost: $842/month each for Dev/Int and Test; $1684/month for Production

AWS Cost Calculator: Baseline Costs

• Minor Cost Drivers (Minor Impact on Cost, and not estimated via cost calculator):

• AWS CloudTrail – CloudTrail provides event history of your AWS account activity, including actions taken through the AWS Management Console, AWS SDKs, command line tools, and other AWS services.

• AWS GuardDuty – GuardDuty is an AWS service to alert on suspicious activity leveraging VPC Flow Logs and CloudTrail logs.

• AWS Key Management Service (KMS) – AWS KMS is a service to manage encryption keys for AWS resources. This service is integrated with other AWS services.

• AWS Config – Config is a service that continuously monitors, records and validates compliance against pre- defined rule sets.

• For estimation purposes, the total cost of all these services is typically less than $150/month for Integration, Test and Production combined ($50/month/environment).

AWS Cost Calculator: Cost Calculator Templates

The following pre-built cost calculator templates can be used by mission teams to account for all ‘Cloud One-required’ hosting costs. They can be further extended to include Mission System specific costs.

Production Template URL:

https://calculator.s3.amazonaws.com/index.html#r=PDT&s=EC2&key=calc-2D3D8E72-5463-438E-A678-

C9FDDB578B22

Integration and Test Template URL:

https://calculator.s3.amazonaws.com/index.html#r=PDT&s=EC2&key=calc-DA94EE2C-2944-4CD6-BA5D- E25E66424F1F

Combined Integration/Test/Production Template URL:

https://calculator.s3.amazonaws.com/index.html#r=PDT&s=EC2&key=calc-30729E82-C3B2-4E5A-

9B57-D4CE2A1A3ABC

For licensing costs of the egress firewalls, the AWS Marketplace provides current software rates at the following URL: https://aws.amazon.com/marketplace/pp/B010GKMEKW?ref=cns_srchrow#pdp-pricing https://calculator.s3.amazonaws.com/index.html https://calculator.s3.amazonaws.com/index.html https://aws.amazon.com/marketplace/pp/B010GKMEKW?ref=cns_srchrow

Mission System Costs

AWS Cost Calculator: Mission System Costs Overview

Beyond the baseline services required for all Cloud One systems, MSOs must also account for the components that are specific to their system (application servers, databases, etc.). Leveraging the AWS Cost Calculator (and extending the baseline service templates), a MSO can accurately estimate annual costs. In this section, we will provide examples of how to account for these variable costs, including sample templates, considerations and instructions for estimation.

Major Cost Drivers:

• EC2/EBS,AutoScale Group (ASG), ELB, ElasticBeanstalk

• S3/Glacier

• Cloudwatch Logs

• RDS/DynamoDB/RedShift

• Kinesis

Minor Cost Drivers:

• Cloudwatch

• Simple Notification Service (SNS)

• Simple Queue Service (SQS)

• Simple Workflow Service (SWF)

No Cost Services:

• VPC

• Cloudformation

• IAM

• Management Console

AWS Cost Calculator: Introduction for EC2 and EBS

EC2 and EBS represent the primary building blocks for most AWS-hosted systems. EC2 is AWS’s service providing elastic compute capability. EBS is AWS’s service for persistent, scalable storage. These are the core services behind other services like Autoscale Groups and Elastic Beanstalk. Estimating these components is fairly straightforward (input the quantity and type of each instance used by the Mission System), but there are several considerations that must be taken into account:

• What is the system’s Impact Level? If it is Impact Level 5, dedicated instances will be required.

• Will the instances use EBS or ephemeral storage? If they use EBS volumes, then EBS needs to be included in the cost estimate.

• Will these instances be autoscaling? Will there be temporary resources only running periodically?

• Will some instances be running 24x7x365 for the next several years? If so, Reserved Instances should be explored to save up to 75% on the cost of those EC2 instances.

Major Cost Driver: EC2

Estimating cost for EC2 resources requires the following information:

• Instances: The number of instances in use by the Mission System.

• Usage: The amount of time these instances will be running. Modifying this field is the most effective way to estimate temporary resources and/or autoscaling. The options for units of measure include: % Utilized per Month, Hours per Day, Hours per Week, Hours per Month.

• For Elastic/Auto-scaling situations, leverage the metric that most closely matches your desired operating model. For example, if the resource is expected to be running 7 days a week, 9AM to 5PM, select ‘8 hours per day’. If it is available M-F, 9AM to 5PM, select 40 hours/week

• Type: The Operating System type and the EC2 instance size. Under “Advanced Options”, there is a checkbox for “Dedicated Instances” which is required for Impact Level 5 systems.

• Billing Option: On-Demand vs the various Reserved options. Reserved instances provide a discounted hourly rate with a commitment to pay for the instance for 1 or 3 years. These are great options for long term, predictable workloads.

Major Cost Driver: EBS

Estimating costs for EBS requires the following information:

• Description: A logical description of the EBS volumes. This gets saved when saving or exporting the template.

• Volumes: The number of volumes with these settings to estimate.

• Volume Type: What type of storage is required. This is typically going to be either “General Purpose SSD” or “Provisioned IOPS SSD”

• Storage: Amount of storage being provisioned for the EBS volume.

• IOPS: When selecting “Magnetic” or “Provisioned IOPS” Volume Types, this field is required. This field is not editable when selecting “General Purpose SSD”.

• Snapshot Storage: The amount of storage expected to change and be saved in a snapshot during the month.

Can be defined as a % of total volume storage or in GB/month

Major Cost Driver: Standalone EC2

The following is an example that represents a typical Mission System configuration. This system leverages 2 Linux EC2 instances on m5.large server sizes running 24x7x365 (for High Availability) with a single 10 GB EBS volume per host.

EC2/EBS Estimation Template: https://calculator.s3.amazonaws.com/index.html#r=PDT&s=EC2&key=calc-

12B5BDEF-E889-4FA3-B8F4-1693C31D5B78

Major Cost Driver: Autoscaling EC2

This example builds on the prior one – adding auto-scaling into the calculation. The following system has the same HA configuration as the previous example, but from 8am to 4pm, the system scales up with out 2 more instances in order to accommodate peak load.

Autoscaling EC2 Estimation Overview: https://calculator.s3.amazonaws.com/index.html#r=PDT&s=EC2&key=calc-

9D3D76AA-2C4F-4303-A817-DF41D0A5C129

Note: There is also one CloudWatch Metric and Alarm included in the template for completeness. Cloudwatch Metrics and Alarms are detailed in a later section.

Major Cost Driver: Elastic Beanstalk

Elastic Beanstalk is a fully managed service that orchestrates several underlying services, including:

• EC2 instances

• EBS volumes

• Autoscale Group (ASG)

• Elastic Load Balancer (ELB)

In order to estimate systems that are deployed via Beanstalk, the individual components must be added to the cost calculator.

Using the previous examples for Autoscaling EC2 and ELB, the following template is an Elastic Beanstalk stack: https://calculator.s3.amazonaws.com/index.html#r=PDT&key=calc-CB75F8E1-

E482-4821-BADF-628112565DCF

Major Cost Driver: S3

S3 is an object storage service that is extremely durable and infinitely scalable. Objects stored in S3 are accessed via HTTP verbs to the AWS service.

The details of how to estimate the cost of S3 include:

• Storage: The amount of storage being used.

• PUT/COPY/POST/LIST Requests: Number of requests to upload, modify or copy objects in S3.

• GET/SELECT and Other Requests: Number of requests to download or present objects in S3.

• Data Returned by S3 Select: Data returned by S3

• S3 example template:

https://calculator.s3.amazonaws.com/index.html#r =PDT&s=S3&key=calc-D78FC5D8-72DE-478D-

95E3-70800DED12DD

Major Cost Driver: Glacier

Glacier is a service used for archival purposes therefore data retrieval is not be expected to occur frequently.

Glacier’s cost is driven by how much data is being stored and how much it is being accessed.

The following template is making an assumption that the data in Glacier will need to be accessed once during the month via a standard retrieval request:

https://calculator.s3.amazonaws.com/index.html#r=PDT& s=Glacier&key=calc-1A6DCD95-219D-49DD-9A56-

3A28DA5C5F6F

Major Cost Driver: RDS

RDS is AWS’s fully managed RDBMS offering. Estimating RDS requires the following information:

• Instances: The number of instances in use.

• Usage: The amount of time these instances will be running. This field is most useful for estimating temporary resources.

The options for units of measure include: % Utilized per Month, Hours per Day, Hours per Week, Hours per Month

• DB Engine and License: The type of DB and the licensing scheme to be used. Note: USAF systems can leverage Oracle BYOL due to the USAF Enterprise Oracle License.

• Class and Deployment: The instance size and if it is a single Availability Zone (AZ) or a Multi-AZ deployment.

• Storage: The type of storage and the amount of storage allocated to the DB

• Production Oracle RDS template: https://calculator.s3.amazonaws.com/index.html#r=PDT&s=RDS&key=calc-C0FECABC-

9D61-40AE-9F86-149BF5D08D4B

Predict and Optimize

Overview

In the previous section, the key cost factors for each service have been identified and templates have been included for the various services.

Now we will exercise these templates to forecast budget requirements and optimize our costs in real-world scenarios. This allows for the ability to:

• Forecast budgetary requirements

• Determine Impact of modifying system capability on cost

• Determine Impacts of modifications to system architecture on cost

As a part of determining the impacts of system architecture on cost, we will explore ways to optimize costs around required availability of particular services or when services have varying levels of usage. For example, implementing autoscaling in Production or stopping Integration or Test environments when they are not in use.

Budget Forecasting for a System

As your system matures within the cloud, there are several operational models that should be considered when forecasting budget:

• Non-Autoscaling - All resources running 24x7x365 and no autoscaling being leveraged (not recommended).

• Autoscaling the system – Core resources running 24x7x365 with autoscaling enabled in Production.

• Further Optimizations – Minimum resources running in Production to maintain a highly available architecture. Autoscaling for peak demand is enabled in Production. Integration and Test environments are only running when needed (i.e. 8 hours per day).

• Adding new capability to the system requiring additional resources.

• Growing the system’s user base and estimating associated cost increases.

System Overview for Example Budget

The most straight-forward to estimate the cost for a Cloud One-migrated system is to simply take the pre-migration compute and store resources and enter them into the AWS cost calculator directly. This is the simplest approach, but does not take advantage of any cloud-based elasticity and subsequently has the highest operational cost. The following example demonstrates this configuration for a typical Cloud One system leveraging Beanstalk and Oracle RDS:

Elastic Beanstalk application:

• Application ELB

• Static set of 4 EC2 instances

•10 GBEBSVolume per instance

Several custom Cloudwatch metrics

Oracle RDS:

• Multi-AZin Prod

•SingleAZin Integration and Test

Several GBof application artifacts on S3

Cloudwatch Logs for application logs:

• 10 GBingested/month archiving for 1 year.

Non-Autoscaling Template URL:

https://calculator.s3.amazonaws.com/index.html#r=PDT&s=Glacier&key=calc-B285891B-D24D-4624-A7E6-1051AB88A193

Non-Autoscaling Budget Forecast

Reviewing the template for the Non-Autoscaling application, the monthly cost is estimated at $1,465.78/month. If this application is not expecting significant changes to usage or architecture over the next year, the annual estimate for application-specific components is:

12 months * $1,465.78 = $17,589.36 per year

Adding in the required Cloud One Baseline Services total cost from the template https://calculator.s3.amazonaws.com/index.html#r=PDT&s=EC2&key=calc-30729E82-C3B2-4E5A-9B57-D4CE2A1A3ABC (remember to add the AWS Marketplace costs for the egress firewalls:

https://aws.amazon.com/marketplace/pp/B010GKMEKW?ref=cns_srchrow#pdp-pricing in as well):

12 months * [$1794.53 + ($750 * 4)] = $57,534.36 per year

This gives a total annual budget estimate of a Non-Autoscaling application:

$17,589.36 + $57,534.36 = $75,123.66 per year

Autoscaling the Application Budget Forecast

One of the major benefits to cloud hosting is the ability to only pay for the resources you need. Taking the previous example, we can examine the cost impact of some simple autoscaling on over-all cost. By modifying the configuration to run 2 instances 24x7 (for HA) and 2 additional instances ONLY during peak load, we can slightly reduce operational costs.

The following are the required updates to the previous estimate to account for basic Autoscaling:

• Remove the static cluster of 4 EC2instances provisioned 24x7x365

• Replace with an Autoscale Group with a minimum size of 2 and a maximum of 4 instances – expecting the additional 2 instances to be running 12 hours per day.

Autoscaled system template: https://calculator.s3.amazonaws.com/index.html#r=PDT&s=Glacier&key=calc-

B5296176-D2A5-4CE4-BFA3-94A576E630E6

Autoscaling the Application Budget Forecast

Reviewing the template for the autoscaled application, the monthly cost is estimated at $1,377.20/month. If this system is not expecting significant changes to usage or architecture over the next year, the annual estimate wound be:

12 months * $1377.20 = $16,526.40 per year (9% savings realized)

Adding in the required Cloud One Baseline Services total cost from the template:

https://calculator.s3.amazonaws.com/index.html#r=PDT&s=EC2&key=calc-30729E82-C3B2-4E5A-9B57-D4CE2A1A3ABC (remember to add the AWS Marketplace costs for the egress firewalls:

https://aws.amazon.com/marketplace/pp/B010GKMEKW?ref=cns_srchrow#pdp-pricing in as well):

12 months * [$1794.53 + ($750 * 4)] = $57,534.36 per year

This gives a total annual budget estimate of:

$16,526.40 + $57,534.36 = $74,060.76 per year

Optimizing the System Budget Forecast

Further building upon the Autoscaling Application, we will examine the impact on cost if we turned off Integration and Test resources outside of business hours.

Required updates to the Autoscaling estimate to further optimize around Integration and Test environments lower utilization levels:

• Update Integration and Test EC2instances and RDSinstances to only run during regular business hours (8 hours per day)

Optimized system template: https://calculator.s3.amazonaws.com/index.html#r=PDT&s=Glacier&key=calc-

D4DEA6CF-B37B-4F49-BA2E-FAB506724C23

Optimizing the System Budget Forecast

Reviewing the template for the optimized system, the monthly cost is estimated at $936.04/month. If this system is not expecting significant changes to usage or architecture over the next year, it can be an annual estimate of:

12 months * $936.04 = $11,232.48 per year (36% savings realized)

Adding in the required Cloud One Baseline Services total cost from the template:

https://calculator.s3.amazonaws.com/index.html#r=PDT&s=EC2&key=calc-30729E82-C3B2-4E5A-9B57- D4CE2A1A3ABC (remember to add the AWS Marketplace costs for the egress firewalls:

https://aws.amazon.com/marketplace/pp/B010GKMEKW?ref=cns_srchrow#pdp-pricing in as well):

12 months * [$1794.53 + ($750 * 4)] = $57,534.36 / year

This gives a total annual budget estimate of:

$11,232.48 + $57,534.36 = $68,766.84 / year

Adding New Capability Budget Forecast

The cost calculator can also be used to estimate the cost impact on upcoming changes/improvements to the system.

Taking the previous example system, let’s assume that there is a new feature that requires the addition of a new database. The targeted release is in approximately 6 months.

Required updates to the optimized estimate to add this new database:

• Add new RDSinstance for each environment

Adding the new RDS to the system template: https://calculator.s3.amazonaws.com/index.html#r=PDT&key=calc- F840C4E4-6497-41F1-8524-398718B703F9&s=Glacier

Adding New Capability Budget Forecast

Reviewing the template for the optimized application, the new monthly cost is $1,357. Making the increase an estimated at $420.96/month for the new capability. If the capability is going to be released in 6 months, the increase required for the current Fiscal Year is: $2,525.76

The updated annual estimate of:

12 months * $1,357 = $16,284 per year (31% increase)

Adding in the required Cloud One Baseline Services total cost from the template:

https://calculator.s3.amazonaws.com/index.html#r=PDT&s=EC2&key=calc-30729E82-C3B2-4E5A-9B57- D4CE2A1A3ABC (remember to add the AWS Marketplace costs for the egress firewalls:

https://aws.amazon.com/marketplace/pp/B010GKMEKW?ref=cns_srchrow#pdp-pricing in as well):

12 months * [$1794.53 + ($750 * 4)] = $57,534.36 per year

This gives a total annual budget estimate of:$16,284 + $57,534.36 = $73,818.36 per year

Adding Additional Users Budget Forecast

• The cost calculator can also be useful for estimating the impact of increased traffic/load on annual operating cost.

Continuing with the previous example, assume that the new feature release is expected to lead to a 50% increase in user traffic. Performance testing has determined the application will need to scale out an additional 3 instances to support this, but only during peak hours.

• Required updates to the new capability estimate to accommodate the larger user base:

• Add 3 Production EC2instances for 8 hours/day

• Add 3 EBSvolumesfor the new instances

Adding the new user base requirements to the template:

https://calculator.s3.amazonaws.com/index.html#r=PDT&key=calc-6679EFD2-7A9E-40F7-982B-BC19CD576E2A&s=Glacier

Adding Additional Users Budget Forecast

The updated annual estimate of:

12 months * $1,449.19 = $17,390.28 per year (6% increase)

Adding in the required Cloud One Baseline Services total cost from the template:

https://calculator.s3.amazonaws.com/index.html#r=PDT&s=EC2&key=calc-30729E82-C3B2-4E5A-9B57- D4CE2A1A3ABC (remember to add the AWS Marketplace costs for the egress firewalls:

https://aws.amazon.com/marketplace/pp/B010GKMEKW?ref=cns_srchrow#pdp-pricing in as well):

12 months * [$1794.53 + ($750 * 4) ] = $57,534.36 / year

This gives a total annual budget estimate of:

$17,390.28 + $57,534.36 = $74,924.64 / year

Other Resources & Information

Monthly Invoices

If a system is running for longer than a month in AWS, Cloud One provides a monthly invoice via Intelink as a service to the MSOs. The monthly invoice is a great tool for getting more detail into cost estimations. Noting the estimation templates and descriptions previously discussed, some metrics that are cost drivers may be difficult to estimate without the aid of an actual AWS invoice.

Monthly invoices are delivered for MSOs at: https://intelshare.intelink.gov/sites/afcce/Invoices/Forms/AllItems.aspx

To request access, a request is sent from the MSO to the Cloud One PMO with a list of users that need access. The Cloud One PMO will ensure those users get access to the application’s invoices.

https://intelshare.intelink.gov/sites/afcce/Invoices/Forms/AllItems.aspx

Using Monthly Invoice Data

The following example illustrates how data from an invoice can be used to add accuracy to cost calculator templates. Examining actual billing data for S3:

The actual data from the invoice can be loaded into the AWS Cost Calculator tool:

As more monthly invoices are available, the estimates can be further refined to allow for more accurate estimating of resource consumption over time.

Current Pricing Details for AWS Services

AWS Service Pricing URL AWS CloudTrail https://aws.amazon.com/cloudtrail/pricing/

AWS GuardDuty https://aws.amazon.com/guardduty/pricing/

AWS Config https://aws.amazon.com/config/pricing/

AWS KMS https://aws.amazon.com/kms/pricing/

Cloudformation https://aws.amazon.com/cloudformation/pricing/

Elastic Beanstalk https://aws.amazon.com/elasticbeanstalk/pricing/

EC2 https://aws.amazon.com/ec2/pricing/

EBS https://aws.amazon.com/ebs/pricing/

ELB https://aws.amazon.com/elasticloadbalancing/pricing/

S3 https://aws.amazon.com/s3/pricing/

RDS https://aws.amazon.com/rds/pricing/

DynamoDB https://aws.amazon.com/dynamodb/pricing/

RedShift https://aws.amazon.com/redshift/pricing/

Kinesis https://aws.amazon.com/kinesis/data-streams/pricing/

SNS https://aws.amazon.com/sns/pricing/

SQS https://aws.amazon.com/sqs/pricing/

SWF https://aws.amazon.com/swf/pricing/ https://aws.amazon.com/cloudtrail/pricing/ https://aws.amazon.com/guardduty/pricing/ https://aws.amazon.com/config/pricing/ https://aws.amazon.com/kms/pricing/ https://aws.amazon.com/cloudformation/pricing/ https://aws.amazon.com/elasticbeanstalk/pricing/ https://aws.amazon.com/ec2/pricing/ https://aws.amazon.com/ebs/pricing/ https://aws.amazon.com/elasticloadbalancing/pricing/ https://aws.amazon.com/s3/pricing/ https://aws.amazon.com/rds/pricing/ https://aws.amazon.com/dynamodb/pricing/ https://aws.amazon.com/redshift/pricing/ https://aws.amazon.com/kinesis/data-streams/pricing/ https://aws.amazon.com/sns/pricing/ https://aws.amazon.com/sqs/pricing/ https://aws.amazon.com/swf/pricing/