Travis CI is a pain in the arse! But the more important I've got a relatively up to day course which in fact hasn't been updated.
There is no AWSElasticBeanstalkFullAccess any longer. Use AdministratorAccess-AWSElasticBeanstalk
If you're experiencing the following error
The request signature we calculated does not match the signature you provided. Check your key and signing method. (Aws::S3::Errors::SignatureDoesNotMatch)
You mustn't use secure: key. Write it as follows in the .travis.yml file:
access_key_id: $AWS_ACCESS_KEY
secret_access_key: $AWS_SECRET_KEY
MIND When you add your environment variables to Travis CI, there is an annotation you may overlook:
If your secret variable has special characters like &, escape them by adding \ in front of each special character. For example, ma&w!doc would be entered as ma&w!doc.
For example: Secret access key: aaAXtldqugatcfiVMsSNq/jmmdZebbEy74tz4mAp
In my key is used a forward slash - I needed to escape it with a backslash:
AWS_SECRET_KEY aaAXtldqugatcfiVMsSNq\/jmmdZebbEy74tz4mAp
Stephen might think users will deal with the issues on their own - Yes, we do! However I spent an hour on those errors digging the Internet. Please, save our time Stephen!
Travis CI is a pain in the arse! But the more important I've got a relatively up to day course which in fact hasn't been updated.
There is no AWSElasticBeanstalkFullAccess any longer. Use AdministratorAccess-AWSElasticBeanstalk
If you're experiencing the following error
You mustn't use secure: key. Write it as follows in the .travis.yml file:
MIND When you add your environment variables to Travis CI, there is an annotation you may overlook:
For example:
Secret access key: aaAXtldqugatcfiVMsSNq/jmmdZebbEy74tz4mApIn my key is used a forward slash - I needed to escape it with a backslash:
AWS_SECRET_KEY aaAXtldqugatcfiVMsSNq\/jmmdZebbEy74tz4mApStephen might think users will deal with the issues on their own - Yes, we do! However I spent an hour on those errors digging the Internet. Please, save our time Stephen!