Fork me on GitHub
Slack Archive

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

2016-05-31

Channels

#aws
<
2016-05-31
>
onetom08:05:37

does anyone knows why amazonica "0.3.58" doesnt pick up the region settings from .aws/config? 

(describe-availability-zones)
=>
{:availability-zones [{:state "available", :region-name "us-east-1", :messages [], :zone-name "us-east-1a"}
                      {:state "available", :region-name "us-east-1", :messages [], :zone-name "us-east-1b"}
                      {:state "available", :region-name "us-east-1", :messages [], :zone-name "us-east-1c"}
                      {:state "available", :region-name "us-east-1", :messages [], :zone-name "us-east-1e"}]}
but it works with explicit endpoint spec: 
(describe-availability-zones  {:endpoint "ap-southeast-1"})
=>
{:availability-zones [{:state "available", :region-name "ap-southeast-1", :zone-name "ap-southeast-1a", :messages []}
                      {:state "available", :region-name "ap-southeast-1", :zone-name "ap-southeast-1b", :messages []}]}
my config file looks like: 
> cat ~/.aws/config
[default]
region=ap-southeast-1
and awscli understands it: 
aws ec2 describe-availability-zones
{
    "AvailabilityZones": [
        {
            "State": "available",
            "RegionName": "ap-southeast-1",
            "Messages": [],
            "ZoneName": "ap-southeast-1a"
        },
        {
            "State": "available",
            "RegionName": "ap-southeast-1",
            "Messages": [],
            "ZoneName": "ap-southeast-1b"
        }
    ]
}