Closed ljfranklin closed 8 years ago
Steps to reproduce at the unit level:
provider = AWS::Core::CredentialProviders::StaticProvider.new(:access_key_id => 'ACCESS_KEY', :secret_access_key => "SECRET_KEY")
client = AWS::EC2.new(:credential_provider => provider, :region => 'bogus')
client.regions.first
Output:
SocketError: getaddrinfo: nodename nor servname provided, or not known
+1 from the bosh mailing list. Search for "[cf-bosh] bosh-init on AWS failed"
I think this was improved in v52 and can be closed.
A user on the bosh slack specified "us-east" instead of "us-east-1" as the region in their manifest. Instead of a human-readable error (e.g. "Invalid region 'us-east'"), they received this: