{"id":11357,"date":"2026-09-04T16:05:41","date_gmt":"2026-09-04T10:35:41","guid":{"rendered":"https:\/\/pheonixsolutions.com\/blog\/?p=11357"},"modified":"2026-09-04T16:10:07","modified_gmt":"2026-09-04T10:40:07","slug":"aws-cost-optimisation-checklist","status":"publish","type":"post","link":"https:\/\/pheonixsolutions.com\/blog\/aws-cost-optimisation-checklist\/","title":{"rendered":"AWS Cost Optimisation Checklist"},"content":{"rendered":"\n<h2 class=\"wp-block-heading\">Introduction<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Managing cloud costs is an important part of running workloads on AWS, especially for startups and growing businesses. As infrastructure expands, unused resources, oversized instances, unnecessary storage, and unexpected data-transfer charges can gradually increase the monthly AWS bill.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A regular cost review helps identify unnecessary spending while ensuring that applications continue to meet their performance, availability, and security requirements.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This checklist covers practical areas that can be reviewed to optimize AWS infrastructure costs without compromising business requirements.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Prerequisites<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Before starting an AWS cost optimization review, ensure that you have:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Access to the AWS account or required billing permissions.<\/li>\n\n\n\n<li>Access to AWS Cost Explorer.<\/li>\n\n\n\n<li>Knowledge of the AWS resources currently being used.<\/li>\n\n\n\n<li>Information about application workload and usage patterns.<\/li>\n\n\n\n<li>Understanding of production, staging, and development environments.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Implementation<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">1. Review AWS Spending<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Start by reviewing the current AWS bill and identifying the services contributing most to the overall cost.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Check:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Monthly AWS spending<\/li>\n\n\n\n<li>Service-wise costs<\/li>\n\n\n\n<li>Account-wise costs<\/li>\n\n\n\n<li>Region-wise costs<\/li>\n\n\n\n<li>Month-over-month cost changes<\/li>\n\n\n\n<li>Unexpected increases in spending<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Use <strong>AWS Cost Explorer<\/strong> to analyze spending trends and identify areas requiring further investigation.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">2. Identify Unused Resources<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Unused resources can continue generating charges even when they are no longer required.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Review resources such as:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>EC2 instances<\/li>\n\n\n\n<li>EBS volumes<\/li>\n\n\n\n<li>Elastic IP addresses<\/li>\n\n\n\n<li>Load balancers<\/li>\n\n\n\n<li>NAT Gateways<\/li>\n\n\n\n<li>RDS databases<\/li>\n\n\n\n<li>S3 storage<\/li>\n\n\n\n<li>Snapshots<\/li>\n\n\n\n<li>Unused development environments<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Remove resources that are no longer required after confirming that they are not needed for production, backup, or disaster recovery purposes.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">3. Right-Size EC2 Instances<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Check whether EC2 instances are appropriately sized for their actual workloads.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Review:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>CPU utilization<\/li>\n\n\n\n<li>Memory utilization<\/li>\n\n\n\n<li>Network usage<\/li>\n\n\n\n<li>Instance uptime<\/li>\n\n\n\n<li>Application workload patterns<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">If an instance consistently operates with significantly lower resource utilization, a smaller instance type may be sufficient.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Similarly, workloads that regularly experience resource constraints may require a more appropriate instance type.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">4. Use Auto Scaling<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">For applications with variable workloads, consider using Auto Scaling to adjust infrastructure capacity based on demand.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">Low Traffic\n    |\n    v\n2 Instances\n    |\nTraffic Increases\n    |\n    v\n4 Instances\n    |\nTraffic Decreases\n    |\n    v\n2 Instances<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">This avoids maintaining unnecessary application capacity during periods of low traffic.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">5. Review Instance Running Hours<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Check whether development, testing, or staging instances need to run continuously.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Where appropriate, schedule non-production resources to stop outside working hours.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">Working Hours\n     |\n     v\nInstance Running\n     |\n     v\nAfter Working Hours\n     |\n     v\nInstance Stopped<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">This can significantly reduce compute costs for environments that do not need to operate 24\/7.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">6. Review EBS Volumes and Snapshots<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Regularly review EBS volumes and snapshots.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Look for:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Unattached EBS volumes<\/li>\n\n\n\n<li>Old snapshots<\/li>\n\n\n\n<li>Unused volumes<\/li>\n\n\n\n<li>Excessive snapshot retention<\/li>\n\n\n\n<li>Over-provisioned storage<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Before deleting anything, verify that the resource is not required for backup or disaster recovery.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">7. Optimize S3 Storage<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Review S3 storage usage and identify objects that no longer require frequent access.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Consider appropriate S3 storage classes based on access patterns.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Also review:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Old objects<\/li>\n\n\n\n<li>Versioned objects<\/li>\n\n\n\n<li>Incomplete multipart uploads<\/li>\n\n\n\n<li>Object retention requirements<\/li>\n\n\n\n<li>Lifecycle policies<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">S3 Lifecycle rules can automatically transition or expire objects according to defined requirements.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">8. Review Database Resources<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Database resources can represent a significant portion of infrastructure costs.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Review:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>RDS instance size<\/li>\n\n\n\n<li>Database utilization<\/li>\n\n\n\n<li>Storage allocation<\/li>\n\n\n\n<li>Read replicas<\/li>\n\n\n\n<li>Multi-AZ requirements<\/li>\n\n\n\n<li>Backup retention<\/li>\n\n\n\n<li>Database uptime<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Avoid reducing database capacity or availability without first reviewing application and business requirements.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">9. Review NAT Gateway Costs<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">NAT Gateway charges can become significant in architectures with high outbound traffic from private subnets.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Review:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Data processed through NAT Gateways<\/li>\n\n\n\n<li>Number of NAT Gateways<\/li>\n\n\n\n<li>Cross-AZ traffic<\/li>\n\n\n\n<li>Services accessing AWS resources through NAT<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Where appropriate, AWS VPC endpoints can be considered for communication with supported AWS services.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">10. Monitor Data Transfer Costs<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Data transfer can contribute significantly to AWS costs.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Review:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Internet data transfer<\/li>\n\n\n\n<li>Cross-AZ traffic<\/li>\n\n\n\n<li>Cross-region traffic<\/li>\n\n\n\n<li>NAT Gateway traffic<\/li>\n\n\n\n<li>CDN usage<\/li>\n\n\n\n<li>Application-to-database traffic<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">The architecture should be reviewed if large volumes of unnecessary cross-region or cross-AZ traffic are identified.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">11. Review Elastic IP Addresses<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Check whether allocated public IPv4 addresses are actually required.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Release unused public IP addresses where they are no longer needed.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Public IPv4 usage can incur charges, so regularly reviewing allocated addresses can help avoid unnecessary costs.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">12. Use AWS Budgets and Alerts<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Set budgets for AWS spending and configure alerts when costs approach predefined thresholds.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">Monthly Budget\n     |\n     +-- 50%  \u2192 Monitor\n     |\n     +-- 80%  \u2192 Review\n     |\n     +-- 100% \u2192 Investigate<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">This helps identify unexpected spending before it becomes a larger issue.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">13. Use Resource Tagging<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Implement a consistent tagging strategy for AWS resources.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Useful tags can include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Environment<\/li>\n\n\n\n<li>Application<\/li>\n\n\n\n<li>Project<\/li>\n\n\n\n<li>Department<\/li>\n\n\n\n<li>Owner<\/li>\n\n\n\n<li>Cost Center<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">For example:<\/p>\n\n\n\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\" data-enlighter-theme=\"\" data-enlighter-highlight=\"\" data-enlighter-linenumbers=\"\" data-enlighter-lineoffset=\"\" data-enlighter-title=\"\" data-enlighter-group=\"\">Environment = Production\nApplication = WebApp\nOwner       = DevOps\nCostCenter  = Engineering<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Proper tagging makes it easier to understand where AWS spending is occurring.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">14. Review Savings Plans and Reserved Capacity<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">For workloads with predictable and consistent usage, evaluate pricing options such as:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>AWS Savings Plans<\/li>\n\n\n\n<li>Reserved Instances<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">These options can reduce costs compared with on-demand pricing when the workload is expected to remain consistent.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Do not commit to long-term pricing models until the workload and usage patterns are sufficiently understood.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">15. Review Non-Production Environments<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Development and staging environments should be reviewed separately from production infrastructure.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Consider:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Scheduling instances<\/li>\n\n\n\n<li>Reducing instance sizes<\/li>\n\n\n\n<li>Using smaller database resources<\/li>\n\n\n\n<li>Removing temporary resources<\/li>\n\n\n\n<li>Applying appropriate retention policies<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Non-production environments should provide the required functionality without unnecessarily matching the scale of production infrastructure.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">16. Review CloudWatch Logs<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">CloudWatch Logs can grow over time and increase storage costs.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Review:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Log retention periods<\/li>\n\n\n\n<li>High-volume log groups<\/li>\n\n\n\n<li>Duplicate logs<\/li>\n\n\n\n<li>Debug logging enabled in production<\/li>\n\n\n\n<li>Unnecessary historical logs<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Configure appropriate retention periods based on operational, security, and compliance requirements.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">17. Regularly Review AWS Cost Optimization<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Cost optimization should not be treated as a one-time activity.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A regular review should cover:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Monthly AWS spending<\/li>\n\n\n\n<li>Resource utilization<\/li>\n\n\n\n<li>Unused resources<\/li>\n\n\n\n<li>Storage growth<\/li>\n\n\n\n<li>Data transfer<\/li>\n\n\n\n<li>Database usage<\/li>\n\n\n\n<li>Compute requirements<\/li>\n\n\n\n<li>Savings opportunities<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">AWS Cost Optimization Checklist<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Area<\/th><th>Check<\/th><\/tr><\/thead><tbody><tr><td>AWS Billing<\/td><td>Review monthly spending<\/td><\/tr><tr><td>EC2<\/td><td>Right-size instances<\/td><\/tr><tr><td>Auto Scaling<\/td><td>Match capacity with demand<\/td><\/tr><tr><td>Non-Production<\/td><td>Stop unused resources<\/td><\/tr><tr><td>EBS<\/td><td>Remove unused volumes<\/td><\/tr><tr><td>Snapshots<\/td><td>Review retention<\/td><\/tr><tr><td>S3<\/td><td>Configure lifecycle policies<\/td><\/tr><tr><td>RDS<\/td><td>Review size and utilization<\/td><\/tr><tr><td>NAT Gateway<\/td><td>Monitor data processing<\/td><\/tr><tr><td>Data Transfer<\/td><td>Review cross-AZ and cross-region traffic<\/td><\/tr><tr><td>Public IPv4<\/td><td>Remove unnecessary addresses<\/td><\/tr><tr><td>CloudWatch<\/td><td>Review log retention<\/td><\/tr><tr><td>Tagging<\/td><td>Tag resources consistently<\/td><\/tr><tr><td>Savings Plans<\/td><td>Evaluate predictable workloads<\/td><\/tr><tr><td>AWS Budgets<\/td><td>Configure cost alerts<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">Conclusion<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">AWS cost optimization is an ongoing process that requires regular monitoring of infrastructure usage, resource utilization, storage, networking, and application requirements.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">By identifying unused resources, right-sizing workloads, optimizing storage, monitoring data transfer, scheduling non-production environments, and using appropriate AWS pricing options, organizations can reduce unnecessary cloud spending while maintaining the required performance and availability.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The objective of cost optimization should not simply be to reduce the AWS bill. It should be to <strong>use AWS resources efficiently while maintaining the security, reliability, performance, and availability required by the business<\/strong>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Frequently Asked Questions<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">1. What is the first step in AWS cost optimization?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The first step is to review current AWS spending using tools such as AWS Cost Explorer. Identify the services, regions, and resources contributing most to the monthly bill before making optimization changes.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">2. How can startups reduce AWS costs?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Startups can reduce AWS costs by right-sizing resources, removing unused infrastructure, scheduling non-production environments, optimizing S3 storage, monitoring data transfer, setting budgets and alerts, and evaluating Savings Plans when workloads become predictable.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">3. How often should AWS costs be reviewed?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">AWS costs should ideally be monitored continuously, with a detailed cost optimization review performed regularly, such as monthly. Significant changes in application traffic or infrastructure should also trigger an additional review.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Related Articles<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><a href=\"https:\/\/pheonixsolutions.com\/blog\/aws-infrastructure-architecture-for-startups\/\">AWS Infrastructure Architecture for Startups<\/a><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><a href=\"https:\/\/pheonixsolutions.com\/blog\/how-to-set-aws-billing-budget-email-notification\/\">How to Set AWS Billing Budget Email Notification<\/a><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Talk to Our Technology Experts<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Planning your AWS infrastructure or looking to improve an existing cloud environment? Our team can help with cloud architecture, infrastructure, DevOps, security, deployment, and ongoing optimization.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><a href=\"https:\/\/pheonixsolutions.com\/contact\">Connect with our technology experts.<\/a><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Introduction Managing cloud costs is an important part of running workloads on AWS, especially for startups and growing businesses. As [&hellip;]<\/p>\n","protected":false},"author":495,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[1019],"tags":[1076],"class_list":["post-11357","post","type-post","status-publish","format-standard","hentry","category-cloud-aws","tag-cost-optimisation","psol-cat-cloud-aws"],"jetpack_publicize_connections":[],"jetpack_shortlink":"https:\/\/wp.me\/phn2x7-2Xb","jetpack_sharing_enabled":true,"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/pheonixsolutions.com\/blog\/wp-json\/wp\/v2\/posts\/11357","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pheonixsolutions.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/pheonixsolutions.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/pheonixsolutions.com\/blog\/wp-json\/wp\/v2\/users\/495"}],"replies":[{"embeddable":true,"href":"https:\/\/pheonixsolutions.com\/blog\/wp-json\/wp\/v2\/comments?post=11357"}],"version-history":[{"count":1,"href":"https:\/\/pheonixsolutions.com\/blog\/wp-json\/wp\/v2\/posts\/11357\/revisions"}],"predecessor-version":[{"id":11358,"href":"https:\/\/pheonixsolutions.com\/blog\/wp-json\/wp\/v2\/posts\/11357\/revisions\/11358"}],"wp:attachment":[{"href":"https:\/\/pheonixsolutions.com\/blog\/wp-json\/wp\/v2\/media?parent=11357"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/pheonixsolutions.com\/blog\/wp-json\/wp\/v2\/categories?post=11357"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/pheonixsolutions.com\/blog\/wp-json\/wp\/v2\/tags?post=11357"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}