You have successfully transfered the domain to Gandi, but your domain is still configured with GD nameservers. Check this: Log in to your AWS web console Select Route53 service Select Hosted Zones in the left pane Select verticeinteractive.co.uk (but do not click on the domain name, just select the radio button) Notice the 4 name … Read more
API Gateway does not currently support multipart form data. This is being considered for future development. In the meantime, you will need to modify your client to use multiple requests or a single one-part request. Update: API Gateway now supports binary payloads. Simply define multipart/form-data as a binary media type for your API and proxy … Read more
As a heads up to anyone who uses the .ebextensions/*.config way: nowadays you can add, edit and remove environment variables in the Elastic Beanstalk web interface. The variables are under Configuration → Software Configuration: Creating the vars in .ebextensions like in Onema’s answer still works. It can even be preferable, e.g. if you will deploy … Read more
This is actually really easy: Go to the “Network & Security” -> Security Group settings in the left hand navigation Find the Security Group that your instance is apart of Click on Inbound Rules Use the drop down and add HTTP (port 80) Click Apply and enjoy
This is how I added a cron job to Elastic Beanstalk: Create a folder at the root of your application called .ebextensions if it doesn’t exist already. Then create a config file inside the .ebextensions folder. I’ll use example.config for illustration purposes. Then add this to example.config container_commands: 01_some_cron_job: command: “cat .ebextensions/some_cron_job.txt > /etc/cron.d/some_cron_job && … Read more
A fix for this problem is to add swap (i.e. paging) space to the instance. Paging works by creating an area on your hard drive and using it for extra memory, this memory is much slower than normal memory however much more of it is available. To add this extra space to your instance you … Read more
I’ll go out on a limb and say that the specified key doesn’t technically exist, so the error message is technically accurate but doesn’t tell the whole story. This should be an easy fix. S3 buckets have two¹ endpoints, “REST” and “website.” They have two different feature sets. The web site endpoint provides magical resolution … Read more
Update: in late December, 2015, AWS announced a new feature, a Managed NAT Gateway for VPC. This optional service provides an alternative mechanism for VPC instances in a private subnet to access the Internet, where previously, the common solution was an EC2 instance on a public subnet within the VPC, functioning as a “NAT instance,” … Read more
I found a way using the aws-sdk. var aws = require(‘aws-sdk’); var lambda = new aws.Lambda({ region: ‘us-west-2’ //change to your region }); lambda.invoke({ FunctionName: ‘name_of_your_lambda_function’, Payload: JSON.stringify(event, null, 2) // pass params }, function(error, data) { if (error) { context.done(‘error’, error); } if(data.Payload){ context.succeed(data.Payload) } }); You can find the doc here: http://docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/Lambda.html
See the EC2 documentation on the subject. Run: wget -q -O – http://169.254.169.254/latest/meta-data/instance-id If you need programmatic access to the instance ID from within a script, die() { status=$1; shift; echo “FATAL: $*”; exit $status; } EC2_INSTANCE_ID=”`wget -q -O – http://169.254.169.254/latest/meta-data/instance-id || die \”wget instance-id has failed: $?\”`” Here is an example of a more … Read more