I'm attempting to use botocore entirely standalone - no reliance on configuration file

Exception initializing botocore session without any other config about botocore HOT 3 CLOSED

boto commented on June 2, 2024

Exception initializing botocore session without any other config

from botocore.

Comments (3)

mafrosis commented on June 2, 2024

Tellingly, I just discovered this (I am running from within an EC2 instance):

$ curl -v http://169.254.169.254/latest/meta-data/iam/ 
* About to connect() to 169.254.169.254 port 80 (#0)
*   Trying 169.254.169.254... connected
> GET /latest/meta-data/iam/ HTTP/1.1
> User-Agent: curl/7.22.0 (i686-pc-linux-gnu) libcurl/7.22.0 OpenSSL/1.0.1 zlib/1.2.3.4 libidn/1.23 librtmp/2.3
> Host: 169.254.169.254
> Accept: */*
> 
* HTTP 1.0, assume close after body
< HTTP/1.0 404 Not Found
< Content-Type: text/html
< Content-Length: 345
< Connection: close
< Date: Wed, 23 Jan 2013 02:04:10 GMT
< Server: EC2ws
< 
<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
         "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
 <head>
  <title>404 - Not Found</title>
 </head>
 <body>
  <h1>404 - Not Found</h1>
 </body>
</html>
* Closing connection #0

from botocore.

mafrosis commented on June 2, 2024

It appears my instance doesn't have IAM data included with the meta-data:

curl -v http://169.254.169.254/latest/meta-data/
* About to connect() to 169.254.169.254 port 80 (#0)
*   Trying 169.254.169.254... connected
> GET /latest/meta-data/ HTTP/1.1
> User-Agent: curl/7.22.0 (i686-pc-linux-gnu) libcurl/7.22.0 OpenSSL/1.0.1 zlib/1.2.3.4 libidn/1.23 librtmp/2.3
> Host: 169.254.169.254
> Accept: */*
> 
* HTTP 1.0, assume close after body
< HTTP/1.0 200 OK
< Content-Type: text/plain
< Accept-Ranges: bytes
< ETag: "-1351512713"
< Last-Modified: Fri, 04 Jan 2013 02:06:13 GMT
< Content-Length: 263
< Connection: close
< Date: Wed, 23 Jan 2013 02:07:26 GMT
< Server: EC2ws
< 
ami-id
ami-launch-index
ami-manifest-path
block-device-mapping/
hostname
instance-action
instance-id
instance-type
kernel-id
local-hostname
local-ipv4
mac
metrics/
network/
placement/
profile
public-hostname
public-ipv4
public-keys/
reservation-id
* Closing connection #0
security-groups%

from botocore.

mafrosis commented on June 2, 2024

I'm closing this as invalid. My original interpretation of the session constructor was wrong - I'll open another more specific issue.

from botocore.

Recommend Projects