instance metadata API unstable
ActivePublic
Actions

Authored by Krenair on Apr 3 2019, 1:56 PM.

Tags

Referenced Files

	F28570489: raw.txt
	Apr 3 2019, 1:56 PM

Subscribers

None

	krenair@deployment-puppetmaster03:~$ curl 'http://169.254.169.254/latest/meta-data/' -vvv
	* Trying 169.254.169.254...
	* TCP_NODELAY set
	* Connected to 169.254.169.254 (169.254.169.254) port 80 (#0)
	> GET /latest/meta-data/ HTTP/1.1
	> Host: 169.254.169.254
	> User-Agent: curl/7.52.1
	> Accept: /
	>
	< HTTP/1.1 200 OK
	< Content-Type: text/plain; charset=UTF-8
	< Content-Length: 210
	< Date: Wed, 03 Apr 2019 13:54:23 GMT
	<
	ami-id
	ami-launch-index
	ami-manifest-path
	block-device-mapping/
	hostname
	instance-action
	instance-id
	instance-type
	local-hostname
	local-ipv4
	placement/
	public-hostname
	public-ipv4
	reservation-id
	* Curl_http_done: called premature == 0
	* Connection #0 to host 169.254.169.254 left intact
	security-groupskrenair@deployment-puppetmaster03:~$ curl 'http://169.254.169.254/latest/meta-data/' -vvv
	* Trying 169.254.169.254...
	* TCP_NODELAY set
	* Connected to 169.254.169.254 (169.254.169.254) port 80 (#0)
	> GET /latest/meta-data/ HTTP/1.1
	> Host: 169.254.169.254
	> User-Agent: curl/7.52.1
	> Accept: /
	>
	< HTTP/1.1 500 Internal Server Error
	< Content-Length: 92
	< Content-Type: text/plain; charset=UTF-8
	< Date: Wed, 03 Apr 2019 13:55:17 GMT
	<
	500 Internal Server Error

	Remote metadata server experienced an internal server error.

	* Curl_http_done: called premature == 0
	* Connection #0 to host 169.254.169.254 left intact

instance metadata API unstableActivePublicActions