{"id":908,"date":"2025-09-30T10:23:53","date_gmt":"2025-09-30T07:23:53","guid":{"rendered":"https:\/\/www.pubconcierge.com\/blog\/?p=908"},"modified":"2025-09-30T10:37:39","modified_gmt":"2025-09-30T07:37:39","slug":"leased-ips-aws-azure-gcp-2025-multi-cloud-guide","status":"publish","type":"post","link":"https:\/\/www.pubconcierge.com\/blog\/leased-ips-aws-azure-gcp-2025-multi-cloud-guide\/","title":{"rendered":"Integrating Leased IPs with Cloud Services: A Practical Playbook for AWS, Azure, and GCP"},"content":{"rendered":"\n<p>If you run a multi-cloud stack, you already know the pain: hard-coded allowlists, vendor IP churn, rising public IPv4 fees, and the constant dance between compliance and velocity. The clean way to keep your reputation, preserve partner allowlists, and control costs is to standardize on <strong>leased IPs<\/strong> that you can route consistently across AWS, Azure, and Google Cloud.<\/p>\n\n\n\n<p>This guide walks you through how <strong>leased IPs<\/strong> fit into each cloud\u2019s Bring-Your-Own-IP feature, common patterns that actually scale, the guardrails legal teams expect, and fresh market numbers so your business case is solid.<\/p>\n\n\n<div class=\"ub_table-of-contents\" data-showtext=\"show\" data-hidetext=\"hide\" data-scrolltype=\"auto\" id=\"ub_table-of-contents-fb750db1-5393-476e-a8f0-36b7e64e1284\" data-initiallyhideonmobile=\"false\"\n                    data-initiallyshow=\"true\"><div class=\"ub_table-of-contents-header-container\"><div class=\"ub_table-of-contents-header\">\n                    <div class=\"ub_table-of-contents-title\">Content:<\/div><\/div><\/div><div class=\"ub_table-of-contents-extra-container\"><div class=\"ub_table-of-contents-container ub_table-of-contents-1-column \"><ul><li><a href=https:\/\/www.pubconcierge.com\/blog\/leased-ips-aws-azure-gcp-2025-multi-cloud-guide\/#0-how-byoip-works-in-each-cloud->\u2022 How BYOIP works in each cloud<\/a><\/li><li><a href=https:\/\/www.pubconcierge.com\/blog\/leased-ips-aws-azure-gcp-2025-multi-cloud-guide\/#1-architecture-patterns-that-scale->\u2022 Architecture patterns that scale<\/a><\/li><li><a href=https:\/\/www.pubconcierge.com\/blog\/leased-ips-aws-azure-gcp-2025-multi-cloud-guide\/#2-step-by-step-integrating-leased-ips-on-aws->\u2022 Step-by-step: Integrating leased IPs on AWS<\/a><\/li><li><a href=https:\/\/www.pubconcierge.com\/blog\/leased-ips-aws-azure-gcp-2025-multi-cloud-guide\/#3-step-by-step-integrating-leased-ips-on-azure->\u2022 Step-by-step: Integrating leased IPs on Azure<\/a><\/li><li><a href=https:\/\/www.pubconcierge.com\/blog\/leased-ips-aws-azure-gcp-2025-multi-cloud-guide\/#4-step-by-step-integrating-leased-ips-on-google-cloud->\u2022 Step-by-step: Integrating leased IPs on Google Cloud<\/a><\/li><li><a href=https:\/\/www.pubconcierge.com\/blog\/leased-ips-aws-azure-gcp-2025-multi-cloud-guide\/#5-security-and-reliability-tips->\u2022 Security and reliability tips<\/a><\/li><li><a href=https:\/\/www.pubconcierge.com\/blog\/leased-ips-aws-azure-gcp-2025-multi-cloud-guide\/#6-compliance-and-policy-guardrails->\u2022 Compliance and policy guardrails<\/a><\/li><li><a href=https:\/\/www.pubconcierge.com\/blog\/leased-ips-aws-azure-gcp-2025-multi-cloud-guide\/#7-cost-modeling-for-the-cfo->\u2022 Cost modeling for the CFO<\/a><\/li><li><a href=https:\/\/www.pubconcierge.com\/blog\/leased-ips-aws-azure-gcp-2025-multi-cloud-guide\/#8-implementation-checklist->\u2022 Implementation checklist<\/a><\/li><li><a href=https:\/\/www.pubconcierge.com\/blog\/leased-ips-aws-azure-gcp-2025-multi-cloud-guide\/#9-faqs->\u2022 FAQs <\/a><\/li><\/ul><\/div><\/div><\/div>\n\n\n<h2 class=\"wp-block-heading\" id=\"0-how-byoip-works-in-each-cloud-\"><strong>How BYOIP works in each cloud<\/strong><\/h2>\n\n\n\n<p><strong>BYOIP<\/strong> stands for <strong>Bring Your Own IP<\/strong>. It\u2019s a cloud feature that lets you use <strong>your own public IP address ranges<\/strong>, including <strong>leased IPs<\/strong>, inside a cloud provider\u2019s network (AWS, Azure, or Google Cloud) instead of using IPs the provider assigns.<\/p>\n\n\n\n<p>Every provider supports some version of BYOIP. The through line: clouds need to verify you control the prefix, and they may require RPKI Route Origin Authorizations and specific RDAP or LOA steps.<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>\u2022 <strong>AWS<\/strong>: You import your range into EC2 as a BYOIP pool, prove control, and optionally announce via AWS. AWS documentation outlines prerequisites like adding RDAP comments and creating a ROA at your RIR.<\/li><li>\u2022 <strong>Azure<\/strong>: Use <strong>Custom IP Address Prefix<\/strong> to bring a contiguous range that Microsoft is permitted to advertise, then allocate those IPs to public resources.<\/li><li>\u2022 <strong>Google Cloud<\/strong>: Create a <strong>Public Advertised Prefix<\/strong> and import your range. Google warns against overlapping announcements, which matters when your lessor also advertises parts of the same space.<\/li><\/ul>\n\n\n\n<p>If you use <strong>leased IPs<\/strong>, make sure your provider supplies a current <strong>Letter of Authorization<\/strong> and supports RPKI so you can create ROAs that allow the cloud\u2019s ASN to originate the route. ARIN also notes providers monitor ROA repositories, and some platforms require valid ROAs.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"1-architecture-patterns-that-scale-\"><strong>Architecture patterns that scale<\/strong><\/h2>\n\n\n\n<p>Here are patterns we see succeed across teams using <strong>leased IPs<\/strong> in multi-cloud.<\/p>\n\n\n\n<p><strong>1. Static egress IPs for APIs and partner allowlists<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>\u2022 Allocate <strong>leased IPs<\/strong> to managed NAT or load balancers per region.<\/li><li>\u2022 Keep the same IPs across clouds so partners only manage one allowlist.<\/li><li>\u2022 Prefer regional segmentation so an incident on one prefix does not impact global traffic.<\/li><\/ul>\n\n\n\n<p><strong>2. Blue-green cloud cutovers<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>\u2022 Announce your <strong>leased IPs<\/strong> via Cloud A while pre-provisioned in Cloud B.<\/li><li>\u2022 Shift BGP advertisement to Cloud B during cutover with minimum DNS changes.<\/li><li>\u2022 Maintain TLS certs and allowlists bound to the <strong>leased IPs<\/strong> rather than provider IPs.<\/li><\/ul>\n\n\n\n<p><strong>3. Reputation control for outbound messaging and scraping<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>\u2022 Assign unique <strong>leased IPs<\/strong> per tenant or per workload class.<\/li><li>\u2022 Track deliverability or block-list signals per IP, rotate methodically, and use RPKI to prevent route hijack that could poison reputation.<\/li><\/ul>\n\n\n\n<p><strong>4. Centralized IP lifecycle with IPAM<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>\u2022 Treat <strong>leased IPs<\/strong> as first-class inventory in IPAM.<\/li><li>\u2022 Track cloud attachment, lease end dates, RPKI status, ROA expirations, and abuse tickets.<\/li><\/ul>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"2-step-by-step-integrating-leased-ips-on-aws-\"><strong>Step-by-step: Integrating leased IPs on AWS<\/strong><\/h2>\n\n\n\n<p><strong>1.Gather docs from your lessor<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>\u2022 LOA authorizing you and the cloud ASN to originate the prefix.<\/li><li>\u2022 Confirmation of RIR allocation and who manages RPKI.<\/li><\/ul>\n\n\n\n<p><strong>2.Prepare RPKI and RDAP<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>\u2022 Add the self-signed certificate to RDAP comments, create a ROA at the RIR to include the AWS ASN you will use. Follow AWS prerequisites closely.<\/li><\/ul>\n\n\n\n<p><strong>3.Provision BYOIP<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>\u2022 Import the range into EC2 BYOIP. After validation, it shows as an address pool.<\/li><\/ul>\n\n\n\n<p><strong>4.Attach to services<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>\u2022 Allocate addresses to Elastic IPs, NLBs, or Global Accelerator. Keep one-to-one mapping for critical APIs to avoid churn during failover.<\/li><\/ul>\n\n\n\n<p><strong>5.Optimize cost and controls<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>\u2022 You will not pay the AWS public IPv4 hourly fee for addresses you bring, which helps your business case. Build guardrails to avoid accidental use of billed cloud-owned IPs.<\/li><\/ul>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"3-step-by-step-integrating-leased-ips-on-azure-\"><strong>Step-by-step: Integrating leased IPs on Azure<\/strong><\/h2>\n\n\n\n<p>1.<strong>Validate ownership and authorization<\/strong><\/p>\n\n\n\n<p>\u2022  Confirm your lessor\u2019s LOA allows Microsoft to advertise the range.<\/p>\n\n\n\n<p>\u2022  Ensure RPKI ROAs cover Microsoft\u2019s required origin ASN. Azure monitors ROA state.<\/p>\n\n\n\n<p>2. <strong>Create a Custom IP Address Prefix<\/strong><\/p>\n\n\n\n<p>\u2022  Import the prefix into your subscription. After approval, you can use it like Azure-owned space.<\/p>\n\n\n\n<p>3. <strong>Bind to public endpoints<\/strong><\/p>\n\n\n\n<p>\u2022  Assign addresses to Public IP resources, Application Gateways, or Front Door as needed.<\/p>\n\n\n\n<p>\u2022  Standardize on Standard SKU Public IP for consistency across regions. Note that some services have moved pricing and SKU defaults in 2025.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"4-step-by-step-integrating-leased-ips-on-google-cloud-\"><strong>Step-by-step: Integrating leased IPs on Google Cloud<\/strong><\/h2>\n\n\n\n<p>1. <strong>Plan your PAP architecture<\/strong><\/p>\n\n\n\n<p>\u2022  Use a dedicated project and organization folder for BYOIP. Google recommends planning ahead.<\/p>\n\n\n\n<p>2. <strong>Import your range<\/strong><\/p>\n\n\n\n<p>\u2022  Create a <strong>Public Advertised Prefix<\/strong> and import the <strong>leased IPs<\/strong>.<\/p>\n\n\n\n<p>\u2022  Avoid overlap. Google does not support overlapping announcements of the same prefix from outside Google if you import it.<\/p>\n\n\n\n<p>3.<strong>Attach to workloads<\/strong><\/p>\n\n\n\n<p>\u2022  Assign addresses to load balancers or as persistent pod IPs with GKE if you need sticky egress identity.<\/p>\n\n\n\n<p>4.<strong>Watch the math<\/strong><\/p>\n\n\n\n<p>\u2022  External IPv4 pricing on Google Cloud increased in 2024 for in-use addresses. BYOIP helps with control, yet you still need to model egress.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"5-security-and-reliability-tips-\"><strong>Security and reliability tips<\/strong><\/h2>\n\n\n\n<ul class=\"wp-block-list\"><li>\u2022 <strong>RPKI first<\/strong>: Keep ROAs current, track expirations, and align maxLength with the subnets you will actually advertise. AWS, Azure, and some networks monitor ROAs and will flag gaps. (read more: <a href=\"https:\/\/www.pubconcierge.com\/blog\/rpki-in-ip-leasing-secure-routing\/\">RPKI in IP Leasing: 7 Steps for Secure Routing<\/a>)<\/li><li>\u2022 <strong>No overlap<\/strong>: If the lessor announces the prefix from their ASN while you try importing the same block, GCP will reject it, and any cloud may see routing instability.<\/li><li>\u2022 <strong>Abuse desk readiness<\/strong>: Document an abuse workflow. Cloud providers provide channels and expect quick responses when something looks off.<\/li><li><strong>\u2022<\/strong> <strong>IP hygiene<\/strong>: Warm up new <strong>leased IPs<\/strong> gradually, segment by workload risk, and keep reverse DNS aligned with use cases to protect reputation.<\/li><\/ul>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"6-compliance-and-policy-guardrails-\"><strong>Compliance and policy guardrails<\/strong><\/h2>\n\n\n\n<p>Using <strong>leased IPs<\/strong> does not exempt you from platform rules or laws. Bake these into your SOPs.<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>\u2022 <strong>Cloud AUPs<\/strong>: AWS, Azure, and GCP all prohibit spam, abuse, or unlawful activity. Keep runbooks that map violative behaviors to enforcement steps on your side.<\/li><li>\u2022 <strong>Privacy laws<\/strong>: For the EU\/UK, apply <strong>GDPR<\/strong> (lawful basis, transparency, DSRs) and appropriate transfer tools for cross-border data. In the U.S., align to <strong>CPRA\/CCPA<\/strong> and track emerging state laws with differing consent\/opt-out standards.<\/li><li>\u2022 <strong>Email rules<\/strong>: For commercial email, follow FTC CAN-SPAM guidance, including clear opt-outs and accurate sender info. Tie this to IP reputation tracking.<\/li><li>\u2022 <strong>Sanctions and export<\/strong>: Check partners and destinations against OFAC and similar lists before you route traffic from <strong>leased IPs<\/strong> into restricted regions.<\/li><li>\u2022 <strong>Contract terms<\/strong>: Make sure your lease agreement clearly states routing rights, ROA delegation, LOA format, abuse handling, and indemnity.<\/li><\/ul>\n\n\n\n<p>None of this is legal advice. Work with your counsel to adapt these controls for your industry and jurisdictions.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"7-cost-modeling-for-the-cfo-\"><strong>Cost modeling for the CFO<\/strong><\/h2>\n\n\n\n<p>A simple model we see adopted:<\/p>\n\n\n\n<ol class=\"wp-block-list\" type=\"1\"><li><strong>Inventory<\/strong>: Count all public IPv4s you consume per cloud and per region.<\/li><li><strong>Compare<\/strong>: Cloud-owned public IPv4 fees vs the monthly rate for <strong>leased IPs<\/strong>, plus any BYOIP administrative overhead. On AWS alone, BYOIP avoids the $0.005 per hour public IPv4 charge.<\/li><li><strong>Right-size<\/strong>: Use smaller blocks for bursty workloads and larger blocks for steady, allowlist-sensitive traffic.<\/li><li><strong>Scenario test<\/strong>: Add multi-cloud failover events, where the same <strong>leased IPs<\/strong> follow the traffic.<\/li><\/ol>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"8-implementation-checklist-\"><strong>Implementation checklist<\/strong><\/h2>\n\n\n\n<p>Use this as your internal runbook when you standardize on <strong>leased IPs<\/strong>.<\/p>\n\n\n\n<p><strong>Vendor and range readiness<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>\u2022 Confirm lease terms allow cloud advertising and sub-allocations.<\/li><li>\u2022 Get LOA naming your org and the cloud ASNs.<\/li><li>\u2022 Create or update ROAs for each cloud and region.<\/li><\/ul>\n\n\n\n<p><strong>Cloud import<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>\u2022 AWS: Prepare RDAP comment, ROA, then create BYOIP pool in EC2.<\/li><li>\u2022 Azure: Create Custom IP Address Prefix, then provision Public IPs from it.<\/li><li>\u2022 GCP: Create Public Advertised Prefix, avoid overlapping external announcements, then assign to LBs or GKE.<\/li><\/ul>\n\n\n\n<p><strong>Networking and controls<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>\u2022 Assign <strong>leased IPs<\/strong> to NAT or load balancers.<\/li><li>\u2022 Add monitoring for ROA validity and route reachability.<\/li><li>\u2022 Implement IPAM records with owner, lease end date, and usage tags.<\/li><\/ul>\n\n\n\n<p><strong>Compliance and abuse<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>\u2022 Map cloud AUPs to internal policies.<\/li><li>\u2022 Add CAN-SPAM and privacy checks to workflows where relevant.<\/li><li>\u2022 Publish an abuse contact and escalate within defined SLAs.<\/li><\/ul>\n\n\n\n<p class=\"has-large-font-size\"><strong>Make it real with PubConcierge<\/strong><\/p>\n\n\n\n<p>If your roadmap includes standardizing on <strong>leased IPs<\/strong> across clouds, we can help with BYOIP-ready ranges, LOAs, RPKI support, and monitoring so your team spends less time chasing routing edge cases and more time shipping.<\/p>\n\n\n\n<p>We design allocation plans that match partner allowlists, compliance requirements, and cost targets.<\/p>\n\n\n\n<p class=\"nav-contact has-background has-large-font-size\" style=\"background-color:#e60100; text-align:center\"><a href=\"javascript:;\" class=\"has-white-color has-text-color nav-contact\"><strong> No-Risk! TEST FOR FREE &#8211; Get Started Now!\n<\/strong><\/a><\/p>\n\n\n\n<p><\/p>\n\n\n\n<div class=\"wp-block-group\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n<h2 class=\"wp-block-heading\" id=\"9-faqs-\"><strong>FAQs <\/strong><\/h2>\n\n\n\n<p><strong>Q1: Can I use leased IPs if I do not \u201cown\u201d the prefix?<\/strong><br>\u2022 Yes, if your lessor grants explicit authorization and you can satisfy cloud prerequisites like ROAs and RDAP updates that prove control. Many providers offer BYOIP-ready ranges with documentation.<\/p>\n\n\n\n<p><strong>Q2: Do leased IPs save money on every cloud?<\/strong><br>\u2022 They often do on AWS because BYOIP avoids the public IPv4 hourly fee, and they can simplify allowlists everywhere. You still pay for network egress and related services, so run the numbers for your traffic profile.<\/p>\n\n\n\n<p><strong>Q3: What breaks most often in multi-cloud BYOIP?<\/strong><br>\u2022 Overlapping or duplicate announcements, expired ROAs, and missing LOAs. GCP explicitly disallows overlapping announcements for imported prefixes.<\/p>\n\n\n\n<p><strong>Q4: How long does BYOIP validation usually take?<\/strong><br>\u2022 Plan for a few business days for LOA review, RDAP checks, and ROA propagation. Many teams finish faster when the lessor provides a BYOIP-ready pack with templated LOAs and RPKI instructions.<\/p>\n\n\n\n<p><strong>Q5: Can I bring only part of a leased block into a cloud?<\/strong><br>\u2022 Yes, if your lease permits sub-allocation and the cloud\u2019s BYOIP supports your desired prefix length. Keep ROAs aligned to the exact subnets you plan to announce and avoid overlaps in any other network.<\/p>\n\n\n\n<p><strong>Q6: Will leased IPs reduce my AWS public IPv4 charges?<\/strong><br>\u2022 Yes. Addresses you bring to AWS via BYOIP are not billed the public IPv4 hourly fee. You still pay for standard services like load balancers and data transfer<\/p>\n\n\n\n<p><strong>Q7: Do I need RPKI for all clouds?<\/strong><br>\u2022 It is strongly recommended. Valid ROAs help prove authorization and prevent hijacks. Track ROA expirations the same way you track TLS certs.<\/p>\n\n\n\n<p><strong>Q8: Can I use leased IPs for both egress and inbound traffic?<\/strong><br>\u2022 Yes. Common patterns include egress through NAT or proxies and inbound on load balancers or global accelerators. Keep separate pools for noisy workloads to protect reputation.<\/p>\n\n\n\n<p><\/p>\n<\/div><\/div>\n\n\n\n<p><strong>Disclaimer<\/strong>: This article is general information and not legal advice. Work with counsel to adapt controls for your jurisdictions and industry.<\/p>\n\n\n\n<p class=\"has-large-font-size\">Stay up to date on growth infrastructure, email best practices, and startup scaling strategies by<strong> <\/strong><a href=\"https:\/\/www.linkedin.com\/company\/pubconcierge\" target=\"_blank\" rel=\"noopener\"><strong>following PubConcierge on LinkedIn<\/strong><\/a><em><strong>.<\/strong><\/em><\/p>\n","protected":false},"excerpt":{"rendered":"<p>If you run a multi-cloud stack, you already know the pain: hard-coded allowlists, vendor IP churn, rising public IPv4 fees, and the constant dance between compliance and velocity. The clean way to keep your reputation, preserve partner allowlists, and control costs is to standardize on leased IPs that you can route consistently across AWS, Azure,&hellip; <a class=\"more-link\" href=\"https:\/\/www.pubconcierge.com\/blog\/leased-ips-aws-azure-gcp-2025-multi-cloud-guide\/\">Continue reading <span class=\"screen-reader-text\">Integrating Leased IPs with Cloud Services: A Practical Playbook for AWS, Azure, and GCP<\/span><\/a><\/p>\n","protected":false},"author":7,"featured_media":909,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"ub_ctt_via":"","footnotes":""},"categories":[5,39,38],"tags":[],"class_list":["post-908","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ip-leasing","category-ipv4-ipv6","category-proxy","entry"],"featured_image_src":"https:\/\/www.pubconcierge.com\/blog\/wp-content\/uploads\/2025\/09\/PUBCONCIERGE-Integrating-Leased-IPs-with-Cloud-Services-A-Practical-Playbook-for-AWS-Azure-and-GCP.jpg","author_info":{"display_name":"Raluca Sima","author_link":"https:\/\/www.pubconcierge.com\/blog\/author\/raluca-sima\/"},"authors":[],"_links":{"self":[{"href":"https:\/\/www.pubconcierge.com\/blog\/wp-json\/wp\/v2\/posts\/908","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.pubconcierge.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.pubconcierge.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.pubconcierge.com\/blog\/wp-json\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"https:\/\/www.pubconcierge.com\/blog\/wp-json\/wp\/v2\/comments?post=908"}],"version-history":[{"count":4,"href":"https:\/\/www.pubconcierge.com\/blog\/wp-json\/wp\/v2\/posts\/908\/revisions"}],"predecessor-version":[{"id":916,"href":"https:\/\/www.pubconcierge.com\/blog\/wp-json\/wp\/v2\/posts\/908\/revisions\/916"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.pubconcierge.com\/blog\/wp-json\/wp\/v2\/media\/909"}],"wp:attachment":[{"href":"https:\/\/www.pubconcierge.com\/blog\/wp-json\/wp\/v2\/media?parent=908"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.pubconcierge.com\/blog\/wp-json\/wp\/v2\/categories?post=908"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.pubconcierge.com\/blog\/wp-json\/wp\/v2\/tags?post=908"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}