- \n
- We can have user data at EC2 instance launch through the console<\/li>\n
- We can also include it in CloudFormation<\/li>\n
- The important thing to pass is the entire script through the function
Fn::Base64<\/code><\/li>\n- Good to know: user data script log is in
\/var\/log\/cloud-init-output.log <\/code><\/li>\n<\/ul>\nLet’s see how to do this in CloudFormation. We have such an yml file:<\/p>\n
---\r\nParameters:\r\n SSHKey:\r\n Type: AWS::EC2::KeyPair::KeyName\r\n Description: Name of an existing EC2 KeyPair to enable SSH access to the instance\r\n\r\nResources:\r\n MyInstance:\r\n Type: AWS::EC2::Instance\r\n Properties:\r\n AvailabilityZone: eu-central-1a\r\n ImageId: ami-00a205cb8e06c3c4e\r\n InstanceType: t2.micro\r\n KeyName: !Ref SSHKey\r\n SecurityGroups:\r\n - !Ref SSHSecurityGroup\r\n # we install our web server with user data\r\n UserData: \r\n Fn::Base64: |\r\n #!\/bin\/bash -xe\r\n yum update -y\r\n yum install -y httpd\r\n systemctl start httpd\r\n systemctl enable httpd\r\n echo \"Hello World from user data\" > \/var\/www\/html\/index.html\r\n\r\n # our EC2 security group\r\n SSHSecurityGroup:\r\n Type: AWS::EC2::SecurityGroup\r\n Properties:\r\n GroupDescription: SSH and HTTP\r\n SecurityGroupIngress:\r\n - CidrIp: 0.0.0.0\/0\r\n FromPort: 22\r\n IpProtocol: tcp\r\n ToPort: 22\r\n - CidrIp: 0.0.0.0\/0\r\n FromPort: 80\r\n IpProtocol: tcp\r\n ToPort: 80<\/pre>\n
<\/p>\n
![\"\"](\"http:\/\/miro.borodziuk.eu\/wp-content\/uploads\/CloudFormation030.jpg\")
<\/p>\nNext-><\/code><\/p>\n![\"\"](\"http:\/\/miro.borodziuk.eu\/wp-content\/uploads\/CloudFormation029.jpg\")
<\/p>\nNext -> Create stack<\/code><\/p>\nAfter the EC2 instance has been created we can check the public DNS address of the EC2 and go to that adress in the browser:<\/p>\n
![\"\"](\"http:\/\/miro.borodziuk.eu\/wp-content\/uploads\/CloudFormation031.jpg\")
<\/p>\nWe can connect to the EC2 through SSH and check the output of user data:<\/p>\n
cat \/var\/log\/cloud-init-output.log<\/pre>\n
<\/p>\n
cfn init<\/span><\/p>\n
- \n
AWS::CloudFormation::Init<\/code> must be in the Metadata of a resource<\/li>\n- With the cfn-init script, it helps make complex EC2 configurations readable<\/li>\n
- The EC2 instance will query the CloudFormation service to get init data<\/li>\n
- Logs go to
\/var\/log\/cfn-init.log<\/code><\/li>\n<\/ul>\n![\"\"](\"http:\/\/miro.borodziuk.eu\/wp-content\/uploads\/CloudFormation033.jpg\")
<\/p>\nConsider such a tamplate:<\/p>\n
---\r\nParameters:\r\n SSHKey:\r\n Type: AWS::EC2::KeyPair::KeyName\r\n Description: Name of an existing EC2 KeyPair to enable SSH access to the instance\r\n\r\nResources:\r\n MyInstance:\r\n Type: AWS::EC2::Instance\r\n Properties:\r\n AvailabilityZone: eu-central-1a\r\n ImageId: ami-00a205cb8e06c3c4e\r\n InstanceType: t2.micro\r\n KeyName: !Ref SSHKey\r\n SecurityGroups:\r\n - !Ref SSHSecurityGroup\r\n # we install our web server with user data\r\n UserData: \r\n Fn::Base64:\r\n !Sub |\r\n #!\/bin\/bash -xe\r\n # Get the latest CloudFormation package\r\n yum update -y aws-cfn-bootstrap\r\n # Start cfn-init\r\n \/opt\/aws\/bin\/cfn-init -s ${AWS::StackId} -r MyInstance --region ${AWS::Region} || error_exit 'Failed to run cfn-init'\r\n Metadata:\r\n Comment: Install a simple Apache HTTP page\r\n AWS::CloudFormation::Init:\r\n config:\r\n packages:\r\n yum:\r\n httpd: []\r\n files:\r\n \"\/var\/www\/html\/index.html\":\r\n content: |\r\n <h1>Hello World from EC2 instance!<\/h1>\r\n <p>This was created using cfn-init<\/p>\r\n mode: '000644'\r\n commands:\r\n hello:\r\n command: \"echo 'hello world'\"\r\n services:\r\n sysvinit:\r\n httpd:\r\n enabled: 'true'\r\n ensureRunning: 'true'\r\n\r\n # our EC2 security group\r\n SSHSecurityGroup:\r\n Type: AWS::EC2::SecurityGroup\r\n Properties:\r\n GroupDescription: SSH and HTTP\r\n SecurityGroupIngress:\r\n - CidrIp: 0.0.0.0\/0\r\n FromPort: 22\r\n IpProtocol: tcp\r\n ToPort: 22\r\n - CidrIp: 0.0.0.0\/0\r\n FromPort: 80\r\n IpProtocol: tcp\r\n ToPort: 80<\/pre>\nCfn init is more readable way to install packages and modify the files on the system than user data way.<\/p>\n
Let’s create a CfnInitExample stack:<\/p>\n
![\"\"](\"http:\/\/miro.borodziuk.eu\/wp-content\/uploads\/CloudFormation035.jpg\")
<\/p>\nNext -><\/code><\/p>\n![\"\"](\"http:\/\/miro.borodziuk.eu\/wp-content\/uploads\/CloudFormation036.jpg\")
<\/p>\nNext -> Create stack<\/code><\/p>\nNow we can go to the url of the new EC2 instance:<\/p>\n
![\"\"](\"http:\/\/miro.borodziuk.eu\/wp-content\/uploads\/CloudFormation038.jpg\")
<\/p>\nNow let’s ssh to the EC2 instance:<\/p>\n
sudo cat \/var\/log\/cloud-init-output.log<\/pre>\n
![\"\"](\"http:\/\/miro.borodziuk.eu\/wp-content\/uploads\/CloudFormation039.jpg\")
<\/p>\nAnd<\/p>\n
[ec2-user@ip-172-31-24-120 ~]$ sudo cat \/var\/log\/cfn-init.log\r\n2021-06-01 12:50:36,880 [INFO] -----------------------Starting build-----------------------\r\n2021-06-01 12:50:36,881 [INFO] Running configSets: default\r\n2021-06-01 12:50:36,883 [INFO] Running configSet default\r\n2021-06-01 12:50:36,884 [INFO] Running config config\r\n2021-06-01 12:50:48,881 [INFO] Yum installed ['httpd']\r\n2021-06-01 12:50:48,888 [INFO] Command hello succeeded\r\n2021-06-01 12:50:49,012 [INFO] enabled service httpd\r\n2021-06-01 12:50:49,188 [INFO] Started httpd successfully\r\n2021-06-01 12:50:49,189 [INFO] ConfigSets completed\r\n2021-06-01 12:50:49,189 [INFO] -----------------------Build complete-----------------------<\/pre>\n
All the logs:<\/p>\n
[ec2-user@ip-172-31-24-120 ~]$ ls \/var\/log\r\namazon boot.log cfn-init-cmd.log cfn-wire.log cloud-init.log cron grubby_prune_debug journal maillog sa spooler wtmp\r\naudit btmp cfn-init.log chrony cloud-init-output.log dmesg httpd lastlog messages secure tallylog yum.log<\/pre>\n
If we need troubleshot:<\/p>\n
[ec2-user@ip-172-31-24-120 ~]$ sudo cat \/var\/log\/cfn-init.log\r\n2021-06-01 12:50:36,880 [INFO] -----------------------Starting build-----------------------\r\n2021-06-01 12:50:36,881 [INFO] Running configSets: default\r\n2021-06-01 12:50:36,883 [INFO] Running configSet default\r\n2021-06-01 12:50:36,884 [INFO] Running config config\r\n2021-06-01 12:50:48,881 [INFO] Yum installed ['httpd']\r\n2021-06-01 12:50:48,888 [INFO] Command hello succeeded\r\n2021-06-01 12:50:49,012 [INFO] enabled service httpd\r\n2021-06-01 12:50:49,188 [INFO] Started httpd successfully\r\n2021-06-01 12:50:49,189 [INFO] ConfigSets completed\r\n2021-06-01 12:50:49,189 [INFO] -----------------------Build complete-----------------------<\/pre>\n
<\/p>\n
cfn signal & wait conditions<\/span><\/p>\n
- \n
- We still don’t know how to tell CloudFormation that the EC2 instance got properly configured after a cfn-init<\/li>\n
- For this, we can use the cfn-signal script!\n
- \n
- We run cfn-signal right after cfn-init<\/li>\n
- Tell CloudFormation service to keep on going or fail<\/li>\n<\/ul>\n<\/li>\n
- We need to define WaitCondition:\n
- \n
- Block the template until it receives a signal from cfn-signal<\/li>\n
- We attach a CreationPolicy (also works on EC2, ASG)<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n
![\"\"](\"http:\/\/miro.borodziuk.eu\/wp-content\/uploads\/CloudFormation040.jpg\")
<\/p>\nConsider such a tamplate:<\/p>\n
---\r\nParameters:\r\n SSHKey:\r\n Type: AWS::EC2::KeyPair::KeyName\r\n Description: Name of an existing EC2 KeyPair to enable SSH access to the instance\r\n\r\nResources:\r\n MyInstance:\r\n Type: AWS::EC2::Instance\r\n Properties:\r\n AvailabilityZone: eu-central-1a\r\n ImageId: ami-00a205cb8e06c3c4e\r\n InstanceType: t2.micro\r\n KeyName: !Ref SSHKey\r\n SecurityGroups:\r\n - !Ref SSHSecurityGroup\r\n # we install our web server with user data\r\n UserData: \r\n Fn::Base64:\r\n !Sub |\r\n #!\/bin\/bash -xe\r\n # Get the latest CloudFormation package\r\n yum update -y aws-cfn-bootstrap\r\n # Start cfn-init\r\n \/opt\/aws\/bin\/cfn-init -s ${AWS::StackId} -r MyInstance --region ${AWS::Region}\r\n # Start cfn-signal to the wait condition\r\n \/opt\/aws\/bin\/cfn-signal -e $? --stack ${AWS::StackId} --resource SampleWaitCondition --region ${AWS::Region}\r\n Metadata:\r\n Comment: Install a simple Apache HTTP page\r\n AWS::CloudFormation::Init:\r\n config:\r\n packages:\r\n yum:\r\n httpd: []\r\n files:\r\n \"\/var\/www\/html\/index.html\":\r\n content: |\r\n <h1>Hello World from EC2 instance!<\/h1>\r\n <p>This was created using cfn-init<\/p>\r\n mode: '000644'\r\n commands:\r\n hello:\r\n command: \"echo 'hello world'\"\r\n services:\r\n sysvinit:\r\n httpd:\r\n enabled: 'true'\r\n ensureRunning: 'true'\r\n\r\n SampleWaitCondition:\r\n CreationPolicy:\r\n ResourceSignal:\r\n Timeout: PT2M\r\n Count: 1\r\n Type: AWS::CloudFormation::WaitCondition\r\n\r\n # our EC2 security group\r\n SSHSecurityGroup:\r\n Type: AWS::EC2::SecurityGroup\r\n Properties:\r\n GroupDescription: SSH and HTTP\r\n SecurityGroupIngress:\r\n - CidrIp: 0.0.0.0\/0\r\n FromPort: 22\r\n IpProtocol: tcp\r\n ToPort: 22\r\n - CidrIp: 0.0.0.0\/0\r\n FromPort: 80\r\n IpProtocol: tcp\r\n ToPort: 80\r\n\r\n<\/pre>\nUsing this template let’s create a stack:<\/p>\n
![\"\"](\"http:\/\/miro.borodziuk.eu\/wp-content\/uploads\/CloudFormation042.jpg\")
<\/p>\nNext -> Create stack<\/code><\/p>\n![\"\"](\"http:\/\/miro.borodziuk.eu\/wp-content\/uploads\/CloudFormation043-1.jpg\")
<\/p>\n<\/p>\n
cfn-signal failures troubleshooting<\/span><\/p>\n
Wait Condition Didn’t Receive the Required Number of Signals from an Amazon EC2 Instance<\/p>\n
- \n
- Ensure that the AMI you’re using has the AWS CloudFormation helper scripts installed. If the AMI doesn’t include the helper scripts, you can also cownload them to your instance.<\/li>\n
- Verify that the
cfn-init<\/code> &cfn-signal<\/code> command was successfully run on the instance. You can view logs, such as\/var\/log\/cloud-init.log<\/code> or\/var\/log\/cfn-init.log<\/code>, to help you debug the instance launch.<\/li>\n- You can retrieve the logs by logging in to your instance, but you must disable rollback on failure or else AWS-CloudFormation deletes the instance after your stack fails to create.<\/li>\n
- Verify that the instance has a connection to the Internet. If the instance is in a VPC, the instance should be able to connect to the Internet through a NAT device if it’s is in a private subnet or through an Internet gateway if it’s in a public subnet<\/li>\n
- For example, run:
curl -I https:\/\/aws.amazon.com<\/code><\/li>\n<\/ul>\nConsider a following yml tamplate:<\/p>\n
---\r\nParameters:\r\n SSHKey:\r\n Type: AWS::EC2::KeyPair::KeyName\r\n Description: Name of an existing EC2 KeyPair to enable SSH access to the instance\r\n\r\nResources:\r\n MyInstance:\r\n Type: AWS::EC2::Instance\r\n Properties:\r\n AvailabilityZone: eu-central-1a\r\n ImageId: ami-00a205cb8e06c3c4e\r\n InstanceType: t2.micro\r\n KeyName: !Ref SSHKey\r\n SecurityGroups:\r\n - !Ref SSHSecurityGroup\r\n # we install our web server with user data\r\n UserData: \r\n Fn::Base64:\r\n !Sub |\r\n #!\/bin\/bash -xe\r\n # Get the latest CloudFormation package\r\n yum update -y aws-cfn-bootstrap\r\n # Start cfn-init\r\n \/opt\/aws\/bin\/cfn-init -s ${AWS::StackId} -r MyInstance --region ${AWS::Region}\r\n # Start cfn-signal to the wait condition\r\n \/opt\/aws\/bin\/cfn-signal -e $? --stack ${AWS::StackId} --resource SampleWaitCondition --region ${AWS::Region}\r\n Metadata:\r\n Comment: Install a simple Apache HTTP page\r\n AWS::CloudFormation::Init:\r\n config:\r\n packages:\r\n yum:\r\n httpd: []\r\n files:\r\n \"\/var\/www\/html\/index.html\":\r\n content: |\r\n <h1>Hello World from EC2 instance!<\/h1>\r\n <p>This was created using cfn-init<\/p>\r\n mode: '000644'\r\n commands:\r\n hello:\r\n command: \"echo 'boom' && exit 1\"\r\n services:\r\n sysvinit:\r\n httpd:\r\n enabled: 'true'\r\n ensureRunning: 'true'\r\n\r\n SampleWaitCondition:\r\n CreationPolicy:\r\n ResourceSignal:\r\n Timeout: PT1M\r\n Count: 1\r\n Type: AWS::CloudFormation::WaitCondition\r\n\r\n # our EC2 security group\r\n SSHSecurityGroup:\r\n Type: AWS::EC2::SecurityGroup\r\n Properties:\r\n GroupDescription: SSH and HTTP\r\n SecurityGroupIngress:\r\n - CidrIp: 0.0.0.0\/0\r\n FromPort: 22\r\n IpProtocol: tcp\r\n ToPort: 22\r\n - CidrIp: 0.0.0.0\/0\r\n FromPort: 80\r\n IpProtocol: tcp\r\n ToPort: 80\r\n\r\n<\/pre>\nCommand<\/p>\n
hello: command: \"echo 'boom' && exit 1\"<\/pre>\n
will exit with error 1. 1 is bad exit code, good is 0.\u00a0 This will directly trigger cfn-init failure.<\/p>\n
Let’s create a stack:<\/p>\n
![\"\"](\"http:\/\/miro.borodziuk.eu\/wp-content\/uploads\/CloudFormation045.jpg\")
<\/p>\nNext<\/code><\/p>\n![\"\"](\"http:\/\/miro.borodziuk.eu\/wp-content\/uploads\/CloudFormation046.jpg\")
<\/p>\nNext -> Create stack<\/code><\/p>\nAnd we see “Failed to receive 1 resource signal(s) within the specified duration<\/span>”<\/p>\n
![\"\"](\"http:\/\/miro.borodziuk.eu\/wp-content\/uploads\/CloudFormation047.jpg\")
<\/p>\nAs the result all the stack has been roll backed.<\/p>\n
<\/p>\n
cfn-hup & cfn-metadata<\/span><\/p>\n
We have such a yaml template:<\/p>\n
AWSTemplateFormatVersion: '2010-09-09'\r\nDescription: AWS CloudFormation Sample Template for CFN Init\r\nParameters:\r\n KeyName:\r\n Description: Name of an existing EC2 KeyPair to enable SSH access to the instances\r\n Type: AWS::EC2::KeyPair::KeyName\r\n ConstraintDescription: must be the name of an existing EC2 KeyPair.\r\n \r\n LatestLinuxAmiId:\r\n Type: 'AWS::SSM::Parameter::Value<AWS::EC2::Image::Id>'\r\n Default: '\/aws\/service\/ami-amazon-linux-latest\/amzn2-ami-hvm-x86_64-gp2'\r\n\r\n WelcomeMessage:\r\n Type: String\r\n Default: \"Hello World\"\r\n \r\nResources:\r\n WebServerSecurityGroup:\r\n Type: AWS::EC2::SecurityGroup\r\n Properties:\r\n GroupDescription: Enable HTTP access via port 80 and SSH access via port 22\r\n SecurityGroupIngress:\r\n - IpProtocol: tcp\r\n FromPort: '80'\r\n ToPort: '80'\r\n CidrIp: 0.0.0.0\/0\r\n - IpProtocol: tcp\r\n FromPort: '22'\r\n ToPort: '22'\r\n CidrIp: 0.0.0.0\/0\r\n\r\n WebServerHost:\r\n Type: AWS::EC2::Instance\r\n Metadata:\r\n Comment: Install a simple PHP application\r\n AWS::CloudFormation::Init:\r\n config:\r\n packages:\r\n yum:\r\n httpd: []\r\n php: []\r\n groups:\r\n apache: {}\r\n users:\r\n \"apache\":\r\n groups:\r\n - \"apache\"\r\n sources:\r\n \"\/home\/ec2-user\/aws-cli\": \"https:\/\/github.com\/aws\/aws-cli\/tarball\/master\"\r\n files:\r\n \"\/var\/www\/html\/index.html\":\r\n content: !Sub |\r\n <h1>${WelcomeMessage} from ${AWS::StackName}<\/h1>\r\n mode: '000644'\r\n owner: apache\r\n group: apache\r\n # The cfn-hup.conf file stores the name of the stack and the AWS credentials that the cfn-hup daemon targets.\r\n \"\/etc\/cfn\/cfn-hup.conf\":\r\n content: !Sub |\r\n [main]\r\n stack=${AWS::StackId}\r\n region=${AWS::Region}\r\n # The interval used to check for changes to the resource metadata in minutes. Default is 15\r\n interval=2\r\n mode: \"000400\"\r\n owner: \"root\"\r\n group: \"root\"\r\n # The user actions that the cfn-hup daemon calls periodically are defined in the hooks.conf configuration file.\r\n # To support composition of several applications deploying change notification hooks, cfn-hup supports a directory named hooks.d that is located in the hooks configuration directory. You can place one or more additional hooks configuration files in the hooks.d directory. The additional hooks files must use the same layout as the hooks.conf file.\r\n \"\/etc\/cfn\/hooks.d\/cfn-auto-reloader.conf\":\r\n content: !Sub |\r\n [cfn-auto-reloader-hook]\r\n triggers=post.update\r\n path=Resources.WebServerHost.Metadata.AWS::CloudFormation::Init\r\n action=\/opt\/aws\/bin\/cfn-init -v --stack ${AWS::StackName} --resource WebServerHost --region ${AWS::Region}\r\n mode: \"000400\"\r\n owner: \"root\"\r\n group: \"root\"\r\n services:\r\n sysvinit:\r\n httpd:\r\n enabled: 'true'\r\n ensureRunning: 'true'\r\n CreationPolicy:\r\n ResourceSignal:\r\n Timeout: PT5M\r\n Properties:\r\n ImageId: !Ref LatestLinuxAmiId\r\n KeyName:\r\n Ref: KeyName\r\n InstanceType: t2.micro\r\n SecurityGroups:\r\n - Ref: WebServerSecurityGroup\r\n UserData:\r\n \"Fn::Base64\":\r\n !Sub |\r\n #!\/bin\/bash -xe\r\n # Get the latest CloudFormation package\r\n yum update -y aws-cfn-bootstrap\r\n # Start cfn-init\r\n \/opt\/aws\/bin\/cfn-init -s ${AWS::StackId} -r WebServerHost --region ${AWS::Region} || error_exit 'Failed to run cfn-init'\r\n # Start up the cfn-hup daemon to listen for changes to the EC2 instance metadata\r\n \/opt\/aws\/bin\/cfn-hup || error_exit 'Failed to start cfn-hup'\r\n # All done so signal success\r\n \/opt\/aws\/bin\/cfn-signal -e $? --stack ${AWS::StackId} --resource WebServerHost --region ${AWS::Region}\r\n\r\nOutputs:\r\n InstanceId:\r\n Description: The instance ID of the web server\r\n Value:\r\n Ref: WebServerHost\r\n WebsiteURL:\r\n Value:\r\n !Sub 'http:\/\/${WebServerHost.PublicDnsName}'\r\n Description: URL for newly created LAMP stack\r\n PublicIP:\r\n Description: Public IP address of the web server\r\n Value:\r\n !GetAtt WebServerHost.PublicIp\r\n\r\n\r\n# Get metadata (change the region accordingly)\r\n# \/opt\/aws\/bin\/cfn-get-metadata --stack CfnHupDemo --resource WebServerHost --region eu-west-1<\/pre>\nLet’s create a stack:<\/p>\n
![\"\"](\"http:\/\/miro.borodziuk.eu\/wp-content\/uploads\/CloudFormation67.jpg\")
<\/p>\nNext -><\/code><\/p>\n![\"\"](\"http:\/\/miro.borodziuk.eu\/wp-content\/uploads\/CloudFormation68-1.jpg\")
<\/p>\nNext -> Create stack<\/code><\/p>\nThe stack has successfully been created<\/p>\n
![\"\"](\"http:\/\/miro.borodziuk.eu\/wp-content\/uploads\/CloudFormation69.jpg\")
<\/p>\nThe http server on EC2 instance is up:<\/p>\n
![\"\"](\"http:\/\/miro.borodziuk.eu\/wp-content\/uploads\/CloudFormation70.jpg\")
<\/p>\nTo get metatdata from EC2 instance let’s connect to it and run command:<\/p>\n
\/opt\/aws\/bin\/cfn-get-metadata --stack CfnHupDemo --resource WebServerHost --region eu-central-1<\/pre>\n
The output:<\/p>\n
![\"\"](\"http:\/\/miro.borodziuk.eu\/wp-content\/uploads\/CloudFormation71.jpg\")
<\/p>\nNow let’s update the parameter of stack:<\/p>\n
![\"\"](\"http:\/\/miro.borodziuk.eu\/wp-content\/uploads\/CloudFormation72-1.jpg\")
<\/p>\nNext -> Next -> Update stack<\/code><\/p>\nThe meadata of EC2 instance has been changed:<\/p>\n
![\"\"](\"http:\/\/miro.borodziuk.eu\/wp-content\/uploads\/CloudFormation73.jpg\")
<\/p>\nBut the content of index.html bas been changed after 2 minutues:<\/p>\n
![\"\"](\"http:\/\/miro.borodziuk.eu\/wp-content\/uploads\/CloudFormation74.jpg\")
<\/p>\n<\/p>\n","protected":false},"excerpt":{"rendered":"","protected":false},"author":1,"featured_media":4218,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[89],"tags":[],"_links":{"self":[{"href":"http:\/\/miro.borodziuk.eu\/index.php\/wp-json\/wp\/v2\/posts\/4217"}],"collection":[{"href":"http:\/\/miro.borodziuk.eu\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/miro.borodziuk.eu\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/miro.borodziuk.eu\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/miro.borodziuk.eu\/index.php\/wp-json\/wp\/v2\/comments?post=4217"}],"version-history":[{"count":9,"href":"http:\/\/miro.borodziuk.eu\/index.php\/wp-json\/wp\/v2\/posts\/4217\/revisions"}],"predecessor-version":[{"id":4438,"href":"http:\/\/miro.borodziuk.eu\/index.php\/wp-json\/wp\/v2\/posts\/4217\/revisions\/4438"}],"wp:featuredmedia":[{"embeddable":true,"href":"http:\/\/miro.borodziuk.eu\/index.php\/wp-json\/wp\/v2\/media\/4218"}],"wp:attachment":[{"href":"http:\/\/miro.borodziuk.eu\/index.php\/wp-json\/wp\/v2\/media?parent=4217"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/miro.borodziuk.eu\/index.php\/wp-json\/wp\/v2\/categories?post=4217"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/miro.borodziuk.eu\/index.php\/wp-json\/wp\/v2\/tags?post=4217"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
- Good to know: user data script log is in