{"id":70012,"date":"2024-06-20T03:19:31","date_gmt":"2024-06-20T03:19:31","guid":{"rendered":"https:\/\/logmeonce.com\/resources\/2023\/08\/13\/aws-assume-role-with-mfa\/"},"modified":"2024-07-01T06:43:16","modified_gmt":"2024-07-01T06:43:16","slug":"aws-assume-role-with-mfa","status":"publish","type":"post","link":"https:\/\/logmeonce.com\/resources\/aws-assume-role-with-mfa\/","title":{"rendered":"Unlock the Power of AWS Assume Role With MFA: Secure Your Cloud Setup!"},"content":{"rendered":"<div class=\"336cb5b64765e27a1a6c1bb71b941f1a\" data-index=\"1\" style=\"float: none; margin:10px 0 10px 0; text-align:center;\">\n<script async src=\"https:\/\/pagead2.googlesyndication.com\/pagead\/js\/adsbygoogle.js?client=ca-pub-4830628043307652\"\r\n     crossorigin=\"anonymous\"><\/script>\r\n<!-- above content -->\r\n<ins class=\"adsbygoogle\"\r\n     style=\"display:block\"\r\n     data-ad-client=\"ca-pub-4830628043307652\"\r\n     data-ad-slot=\"5864845439\"\r\n     data-ad-format=\"auto\"\r\n     data-full-width-responsive=\"true\"><\/ins>\r\n<script>\r\n     (adsbygoogle = window.adsbygoogle || []).push({});\r\n<\/script>\n<\/div>\n<p>Do you want to \u200charness the power of AWS and\u2064 AWS Assume Role\u2063 with \u2062MFA? If \u2062so, you\u2019ve come to \u2064the right place. Using \u2062Multi-Factor\u200d Authentication (MFA), AWS users can assume cross-account roles\u2062 and\u200d execute \u2062actions in one\u200b AWS account from another account. This process helps \u2063ensure the safety and security of resources by adding a layer of authentication. In \u2063this article, we\u2019ll\u2064 discuss the basics of AWS Assume Role with \u2062MFA\u2062 and \u200clook at how you can begin using this service to maximize the potential of your cloud setup.\u200c So get ready to\u200d make the most of\u200c your AWS\u2062 with a secure,\u200c cost-effective\u200c MFA \u200bService.<\/p>\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_77 counter-hierarchy ez-toc-counter ez-toc-grey ez-toc-container-direction\">\n<div class=\"ez-toc-title-container\">\n<p class=\"ez-toc-title\" style=\"cursor:inherit\">Table of Contents<\/p>\n<span class=\"ez-toc-title-toggle\"><a href=\"#\" class=\"ez-toc-pull-right ez-toc-btn ez-toc-btn-xs ez-toc-btn-default ez-toc-toggle\" aria-label=\"Toggle Table of Content\"><span class=\"ez-toc-js-icon-con\"><span class=\"\"><span class=\"eztoc-hide\" style=\"display:none;\">Toggle<\/span><span class=\"ez-toc-icon-toggle-span\"><svg style=\"fill: #999;color:#999\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" class=\"list-377408\" width=\"20px\" height=\"20px\" viewBox=\"0 0 24 24\" fill=\"none\"><path d=\"M6 6H4v2h2V6zm14 0H8v2h12V6zM4 11h2v2H4v-2zm16 0H8v2h12v-2zM4 16h2v2H4v-2zm16 0H8v2h12v-2z\" fill=\"currentColor\"><\/path><\/svg><svg style=\"fill: #999;color:#999\" class=\"arrow-unsorted-368013\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"10px\" height=\"10px\" viewBox=\"0 0 24 24\" version=\"1.2\" baseProfile=\"tiny\"><path d=\"M18.2 9.3l-6.2-6.3-6.2 6.3c-.2.2-.3.4-.3.7s.1.5.3.7c.2.2.4.3.7.3h11c.3 0 .5-.1.7-.3.2-.2.3-.5.3-.7s-.1-.5-.3-.7zM5.8 14.7l6.2 6.3 6.2-6.3c.2-.2.3-.5.3-.7s-.1-.5-.3-.7c-.2-.2-.4-.3-.7-.3h-11c-.3 0-.5.1-.7.3-.2.2-.3.5-.3.7s.1.5.3.7z\"\/><\/svg><\/span><\/span><\/span><\/a><\/span><\/div>\n<nav><ul class='ez-toc-list ez-toc-list-level-1 ' ><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/logmeonce.com\/resources\/aws-assume-role-with-mfa\/#1_Step_up_Security_with_Multi-Factor_Authentication_for%E2%80%8D_AWS_Assume_%E2%81%A3Role\" >1. Step up Security with Multi-Factor Authentication for\u200d AWS Assume \u2063Role<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/logmeonce.com\/resources\/aws-assume-role-with-mfa\/#2_Keep_Your_Data_Safer_with_AWS_Assume%E2%81%A3_Role_and_MFA\" >2. Keep Your Data Safer with AWS Assume\u2063 Role and MFA<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/logmeonce.com\/resources\/aws-assume-role-with-mfa\/#3_%E2%80%8DMake_the_Most_%E2%80%8Bof_Your_AWS%E2%81%A3_Account_with_%E2%81%A2Enhanced_Security_using%E2%80%8B_MFA_and_Assume_%E2%81%A4Role\" >3. \u200dMake the Most \u200bof Your AWS\u2063 Account with \u2062Enhanced Security using\u200b MFA and Assume \u2064Role<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/logmeonce.com\/resources\/aws-assume-role-with-mfa\/#4_Strengthen_%E2%80%8CSecurity%E2%80%8B_Around_Your_Data%E2%81%A2_with_AWS_Assume_Role_and_MFA\" >4. Strengthen \u200cSecurity\u200b Around Your Data\u2062 with AWS Assume Role and MFA<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/logmeonce.com\/resources\/aws-assume-role-with-mfa\/#IAM_User_Policy_Details\" >IAM User Policy Details<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/logmeonce.com\/resources\/aws-assume-role-with-mfa\/#Q_A\" >Q&amp;A<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-7\" href=\"https:\/\/logmeonce.com\/resources\/aws-assume-role-with-mfa\/#Conclusion\" >Conclusion<\/a><\/li><\/ul><\/nav><\/div>\n<h2 id=\"1-step-up-security-with-multi-factor-authentication-for-aws-assume-role\"><span class=\"ez-toc-section\" id=\"1_Step_up_Security_with_Multi-Factor_Authentication_for%E2%80%8D_AWS_Assume_%E2%81%A3Role\"><\/span>1. Step up Security with Multi-Factor Authentication for\u200d AWS Assume \u2063Role<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><b>Multi-Factor authentication is\u200b a powerful way to \u2062step up your AWS security<\/b>. \u2064Setting\u2062 up\u2062 the authentication security doesn\u2019t have to be\u200c complicated \u200ceither. Here\u2019s what you \u2062need to do:<\/p>\n<ul>\n<li>Go\u200d to the IAM console in AWS \u200cand\u200d select \u200cUsers in the left side navigation.<\/li>\n<li>Select an existing user and\u200d choose the\u200c Security \u2064Credentials Tab.<\/li>\n<li>Click \u200bon the \u200b\u201cActivate \u200dMFA\u201d button.<\/li>\n<li>Choose a \u2062hardware or virtual MFA \u2062device to use.<\/li>\n<li>Follow \u200bthe setup instructions \u200bto assign an \u2064MFA\u200c device \u2063to a\u200b user.<\/li>\n<\/ul>\n<p>Once \u2063this process is \u2062complete, \u2062the\u2064 user \u200cis now required to enter a\u200b one-time password generated by the MFA device as part of \u2064the login \u200cprocess. This substantially strengthens\u2064 the security of your AWS\u200b account\u2063 and helps protect you \u2062from malicious attempts\u2064 to gain access to your resources. Additionally, \u2063AWS lets you\u200d use MFA-based authentication for\u2063 Assumed Roles from the Security Credentials section of the IAM console for more\u200b streamlined,\u200d secure access control.<\/p>\n<h2 id=\"2-keep-your-data-safer-with-aws-assume-role-and-mfa\"><span class=\"ez-toc-section\" id=\"2_Keep_Your_Data_Safer_with_AWS_Assume%E2%81%A3_Role_and_MFA\"><\/span>2. Keep Your Data Safer with AWS Assume\u2063 Role and MFA<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Security is one \u200cof\u200b the \u200bbiggest concerns for companies \u200cand\u200d individuals today. As \u200bdata\u2063 breaches become more frequent\u2062 and sophisticated, businesses rely on Amazon\u2019s <a href=\"https:\/\/logmeonce.com\/consumer-password-manager-and-password-recovery\/pricing-and-comparison\/\">renowned \u2063cloud-based \u2064security solutions<\/a> to protect\u2063 their valuable assets.<\/p>\n<p>The AWS\u2063 Assume Role \u2063and Multi-Factor Authentication \u200c(MFA) \u200dare two of the most \u2063popular\u2064 security features \u2063offered by AWS. Assume Role enhances \u2063your system security by allowing you\u200d to grant temporary access to your applications. MFA adds an extra layer of \u2064security by requiring \u200cusers to \u200center a one-time\u200c code \u200bin \u200corder\u200b to access services.\u200b Here\u2019s how \u200dthese two features work:<\/p>\n<ul>\n<li><strong>Assume Role:<\/strong> Assume Role securely grants temporary access\u200c to your\u200c applications\u200d and systems without exposing \u200dyour AWS credentials. This feature requires users to input their existing \u2063AWS \u2062credentials \u2062and define a specific\u2063 set of permissions and time frames for access privileges.<\/li>\n<li><strong>MFA:<\/strong> \u200cMFA adds \u2064an additional \u2062layer of authentication to your \u200blogin process. When enabled, \u2063users are required \u2062to input a one-time code to gain access. This feature\u200c can\u2062 be used in conjunction \u200cwith a variety of authentication methods,\u2062 including SMS,\u2062 physical\u2064 token devices,\u200d or biometrics.<\/li>\n<\/ul>\n<p>By leveraging the\u200c Assume Role and MFA features, \u2063you can drastically reduce the risks of data breaches and \u2064ensure better security for your organization.<\/p>\n<h2 id=\"3-make-the-most-of-your-aws-account-with-enhanced-security-using-mfa-and-assume-role\"><span class=\"ez-toc-section\" id=\"3_%E2%80%8DMake_the_Most_%E2%80%8Bof_Your_AWS%E2%81%A3_Account_with_%E2%81%A2Enhanced_Security_using%E2%80%8B_MFA_and_Assume_%E2%81%A4Role\"><\/span>3. \u200dMake the Most \u200bof Your AWS\u2063 Account with \u2062Enhanced Security using\u200b MFA and Assume \u2064Role<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><b>Protect\u2063 Your \u2062Data with \u200cMulti-Factor \u200dAuthentication<\/b><\/p>\n<p>Ensuring the security \u2063of your AWS account\u200c starts \u200bwith using multi-fator authentication \u2063(MFA). This requires\u200d a user to sign in with two different\u200d factors, such as \u2063a password and a \u2064second verification code. MFA\u200d verifies \u2063the identity of the person signing in and provides an extra\u2064 layer of security.<\/p>\n<p>You can \u200bsecure access \u200dto your\u2064 AWS resources by setting up\u200b MFA. This way, you can require all users who have\u200d been assigned an IAM role to \u2063authenticate\u2064 with MFA. Furthermore,\u2064 you can require MFA for\u2063 administration access to \u2062specific AWS \u2062services, such as \u200bAmazon EC2 and\u200c Amazon S3, as well as\u200d for individual API requests.<\/p>\n<p><b>Simplify User Access Using Assume \u2064Role<\/b><\/p>\n<p>Using Amazon Identity and Access\u2063 Management (IAM) with Assume Role allows\u200b you \u200bto\u200c control which\u200d users\u2064 can\u200b access \u2062your\u200b AWS environment and the resources within \u2063it.\u2063 Assume Role \u200bis an AWS feature that enables you to grant\u2064 users\u200d temporary access to AWS resources\u200d with limited \u200bprivileges. This \u200bway, users can access the AWS resources they need while\u2063 you maintain full \u200bcontrol over who accesses what.<\/p>\n<p>The process is simple: a user authenticates, then you enter the user\u2019s IAM \u200daccount \u2063and\u200c create an IAM\u200b role that\u200d controls the\u2063 access the user is entitled \u2063to. You then grant \u200ccertain permissions to \u2064the user within the role. With Assume \u2062Role,\u2064 you\u200d can \u2064set the duration of the\u2062 user\u2019s \u2062access, as well \u200bas\u200c specify which\u2063 IP addresses the user\u2063 has \u200daccess from. \u2064This\u2063 way, you can\u200d ensure users are accessing AWS resources\u2062 securely and \u200bwith \u200dthe minimum level of access required.<\/p>\n<h2 id=\"4-strengthen-security-around-your-data-with-aws-assume-role-and-mfa\"><span class=\"ez-toc-section\" id=\"4_Strengthen_%E2%80%8CSecurity%E2%80%8B_Around_Your_Data%E2%81%A2_with_AWS_Assume_Role_and_MFA\"><\/span>4. Strengthen \u200cSecurity\u200b Around Your Data\u2062 with AWS Assume Role and MFA<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><b>Multi-Factor Authentication<\/b><\/p>\n<p>Multi-factor authentication (MFA)\u200c is \u200can important security\u2064 practice that\u200b helps \u200cguard your data\u200c from unauthorized access. With MFA, you verify\u2062 your identity \u200cwith two or more pieces of evidence,\u200c such as a password, fingerprint, or code sent to \u200cyour mobile phone.\u200c This \u200dextra layer\u200c of protection\u200d can help keep your \u2064data \u2064secure and \u2062reduce the \u2062risk of\u2062 malicious\u2064 attacks.<\/p>\n<p><b>Assume\u2064 Role for AWS<\/b><\/p>\n<p>An \u200dAssume Role for AWS is a powerful tool\u2062 that allows you to securely access AWS resources without \u200chaving to use your \u2062own \u200dcredentials. With Assume Role, \u200byou can grant temporary access to\u2064 your AWS resources and limit the permissions \u2062of the users. This way, you\u2062 can ensure that data\u200c stored\u200b in AWS is only accessed by those who are authorized, while the\u200d risk of malicious\u2062 attack on your data\u2062 is\u200b minimized.<\/p>\n<p>Assume Role also makes it easier to administer\u200d large\u200d numbers\u200b of users. It helps you create and manage \u200duser roles,\u2062 set access levels, and \u200bexpire credentials easily with \u2063a single API call. By combining Assume Role\u2063 with MFA, you can ensure a stronger security posture and protect your\u2062 data from malicious activity.<\/p>\n<p>When using AWS assume role with MFA (Multi-Factor Authentication), temporary credentials are generated to provide an additional layer of security. This process requires the use of a hardware device or Authenticator app to generate a time-based one-time password for authentication. These temporary credentials are used to access resources within Amazon Web Services using the Amazon Resource Name (ARN) of the role. The role trust policy defines the trust relationship between the role and the identity provider, such as Cognito User or IAM User. Within the configuration file, role permissions and profiles are specified to control access to users and devices for users. Cross-account access can be granted through policy grants, while MFA-Protected API Access ensures a strong security posture for sensitive API operations. The maximum session duration setting limits the time a role session can be active, providing an additional layer of protection. It is important to follow best practices for access control, such as least-privilege access and using Role MFA for role assumption. Sources: AWS Assume Role and MFA documentation, AWS IAM User Guide.<\/p>\n<p>AWS Assume Role With MFA is a secure way to access resources in an AWS account by assuming a specific role with Multi-Factor Authentication (MFA) enabled. The process involves using a config file to define role profiles with resource-based policies and trust relationships. This allows users to obtain short-term credentials for role chains, ensuring additional security for role principals. The role ARN is used to grant access with policy permissions, while the sts get-session-token AWS CLI command is used to generate temporary session tokens for subsequent cross-account API requests. Session tags and inline policies can be used to further restrict access and enforce security measures. The IAM User Guide provides detailed information on user access permissions, limits, and best practices for securely managing identities within the AWS environment. By implementing MFA and assuming roles with strict policies, users can ensure the security and integrity of their AWS resources. Sources: AWS documentation and IAM User Guide.<\/p>\n<p>AWS Assume Role With MFA is a feature that allows users to assume a role in AWS using long-term credentials while adding an additional layer of security through multi-factor authentication (MFA). This process involves establishing a trust relationship between the role and the source identity, granting access based on the policies set for the role. Multi-factor authentication requires the user to provide two forms of verification, such as a password and a one-time authentication token from a device like the LogMeOnce Authenticator. The process of assuming a role also involves setting session tags, which define the session&#8217;s permissions and limits. Users can obtain information about their current credentials by using the &#8220;aws sts get-caller-identity&#8221; command, which provides details like the caller identity and source credentials. By understanding the various components and limitations of assuming roles in AWS, users can enhance the security of their accounts and access resources more securely and efficiently.<\/p>\n<p><a href=\"https:\/\/docs.aws.amazon.com\/IAM\/latest\/UserGuide\/id_credentials_mfa.html\" target=\"_blank\" rel=\"noopener nofollow\">Sources<\/a>:<br \/>\n&#8211; AWS Documentation: Assume a Role with MFA docs.aws.amazon.com<\/p>\n<p>In AWS, assuming a role with multi-factor authentication (MFA) involves establishing a trust relationship between the role and the root user credentials. A policy is then defined that grants access to the role, requiring an additional authentication factor such as a token code from an MFA device. This extra layer of security is crucial for protecting sensitive resources, especially when using services like Amazon Elastic Container Service (ECS) that have separate limits for role sessions. Role sessions have upper size limits for character types, including alphanumeric characters, spaces, and other specified characters from a valid character list. The session also includes context assertions and condition keys to ensure secure access. For more information on assuming roles and MFA in AWS, refer to the AWS documentation and IAM User Guide for detailed guidelines and best practices.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"IAM_User_Policy_Details\"><\/span>IAM User Policy Details<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<table>\n<tbody>\n<tr>\n<th>Policy Name<\/th>\n<th>Access Type<\/th>\n<th>MFA Required<\/th>\n<\/tr>\n<tr>\n<td>Inline User Policy<\/td>\n<td>Programmatic<\/td>\n<td>No<\/td>\n<\/tr>\n<tr>\n<td>Assume Role Profile<\/td>\n<td>Console<\/td>\n<td>Yes<\/td>\n<\/tr>\n<tr>\n<td>Role A<\/td>\n<td>Permanent<\/td>\n<td>No<\/td>\n<\/tr>\n<tr>\n<td>Param User<\/td>\n<td>Programmatic<\/td>\n<td>Yes<\/td>\n<\/tr>\n<tr>\n<td>Demo Role<\/td>\n<td>Console<\/td>\n<td>No<\/td>\n<\/tr>\n<tr>\n<td>Inline Session Policy<\/td>\n<td>Console<\/td>\n<td>No<\/td>\n<\/tr>\n<tr>\n<td>Role Demo<\/td>\n<td>Permanent<\/td>\n<td>No<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2 id=\"qa\"><span class=\"ez-toc-section\" id=\"Q_A\"><\/span>Q&amp;A<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Q: What \u200dis \u200dAWS Assume Role with \u2063MFA?<\/p>\n<p>A: AWS Assume\u2063 Role with MFA is a feature of Amazon Web\u200b Services (AWS) that allows\u2062 users to log into their AWS account from any device\u2063 with an additional layer of security. This extra layer is called Multi-Factor Authentication (MFA), \u200dwhich requires users to input a code\u200b from\u2064 an approved \u2063device in addition to their password. This \u2064makes it more difficult for malicious \u2063actors to gain\u2062 access \u2062to an AWS account.<\/p>\n<p>Q: What is AWS Assume Role with MFA?<br \/>\nA: AWS Assume Role with MFA is a security feature that allows users to assume temporary security credentials to access AWS resources by using Multi-Factor Authentication (MFA) for an additional layer of security.<\/p>\n<p>Q: How does AWS Assume Role with MFA work?<br \/>\nA: When a user attempts to assume a role with MFA, they must provide their access key, secret access key, MFA device serial number, and MFA token code. Once authenticated, AWS generates temporary security credentials, including a security token, to grant access to the specified role.<\/p>\n<p>Q: What is role chaining in the context of AWS Assume Role with MFA?<br \/>\nA: Role chaining refers to the ability to assume multiple roles in a sequence, with each role having its own trust policy and granular permissions. This allows for a more complex access control strategy within an AWS environment.<\/p>\n<p>Q: What is the &#8211;profile option in AWS Assume Role with MFA?<br \/>\nA: The &#8211;profile option allows users to specify a named profile in a credentials file to assume a role with MFA. This simplifies the process of assuming roles with MFA in the AWS CLI.<\/p>\n<p>Q: How does AWS Assume Role with MFA enhance security in an AWS environment?<br \/>\nA: By requiring users to authenticate with an additional factor (MFA) before assuming a role, AWS Assume Role with MFA adds an extra layer of security to prevent unauthorized access to sensitive resources. This helps to protect against identity theft and unauthorized access to AWS resources.<\/p>\n<p>Sources:<br \/>\n&#8211; AWS Documentation: Assume Role with MFA docs.aws.amazon.com<\/p>\n<h2 id=\"outro\"><span class=\"ez-toc-section\" id=\"Conclusion\"><\/span>Conclusion<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>If you\u2019re looking for an easier \u200dand more \u200dsecure way to \u200bAws Assume Role\u200d With MFA for your business, creating a\u2063 FREE LogMeOnce account\u2064 is the way to go. LogMeOnce provides a comprehensive, <a href=\"https:\/\/logmeonce.com\/passwordless-mfa\/\">multi-factor authentication solution<\/a> for your business\u200b that allows secure access to AWS cloud applications and services without hindering \u2062productivity. With <a href=\"https:\/\/logmeonce.com\/\">LogMeOnce<\/a>, you can \u200densure safe access to your \u200cAWS console or services with\u2064 MFA authentication and secure your accounts using\u2062 strong, unique passwords.<\/p>\n\n<div style=\"font-size: 0px; height: 0px; line-height: 0px; margin: 0; padding: 0; clear: both;\"><\/div>","protected":false},"excerpt":{"rendered":"<p>Do you want to \u200charness the power of AWS and\u2064 AWS Assume Role\u2063 with \u2062MFA? If \u2062so, you\u2019ve come to \u2064the right place. Using \u2062Multi-Factor\u200d Authentication (MFA), AWS users can assume cross-account roles\u2062 and\u200d execute \u2062actions in one\u200b AWS account from another account. This process helps \u2063ensure the safety and security of resources by adding [&hellip;]<\/p>\n","protected":false},"author":27,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[19737],"tags":[7232,20648,20649,11055,10933,781],"class_list":["post-70012","post","type-post","status-publish","format-standard","hentry","category-two-factor-authentication","tag-aws-2","tag-assume-role","tag-aws-access-tokens","tag-mfa","tag-multi-factor-authentication","tag-security"],"acf":[],"_links":{"self":[{"href":"https:\/\/logmeonce.com\/resources\/wp-json\/wp\/v2\/posts\/70012","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/logmeonce.com\/resources\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/logmeonce.com\/resources\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/logmeonce.com\/resources\/wp-json\/wp\/v2\/users\/27"}],"replies":[{"embeddable":true,"href":"https:\/\/logmeonce.com\/resources\/wp-json\/wp\/v2\/comments?post=70012"}],"version-history":[{"count":0,"href":"https:\/\/logmeonce.com\/resources\/wp-json\/wp\/v2\/posts\/70012\/revisions"}],"wp:attachment":[{"href":"https:\/\/logmeonce.com\/resources\/wp-json\/wp\/v2\/media?parent=70012"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/logmeonce.com\/resources\/wp-json\/wp\/v2\/categories?post=70012"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/logmeonce.com\/resources\/wp-json\/wp\/v2\/tags?post=70012"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}