pand-app

option_settings:
    - namespace: aws:elasticbeanstalk:container:nodejs
      option_name: NodeCommand
      value: "npm start"

    - namespace: aws:elasticbeanstalk:container:nodejs
      option_name: NodeVersion
      value: "4.4.3"
commands:
  050-node-script-installer:

yefim

{
  "AWSEBDockerrunVersion": "1",
  "Image": {
    "Name": "<AWS_ACCOUNT_ID>.dkr.ecr.us-east-1.amazonaws.com/<NAME>:<TAG>",
    "Update": "true"
  },
  "Ports": [
    {
      "ContainerPort": "443"
    }

mkubenka

#!/bin/sh

apt-get -y install git bc
git clone https://github.com/letsencrypt/letsencrypt /opt/letsencrypt
mkdir /etc/letsencrypt

tonysneed

- Open Automator 
- File -> New -> Service 
- Change "Service Receives" to "files or folders" in "Finder" 
- Add a "Run Shell Script" action 
- Change "Pass input" to "as arguments" 
- Paste the following in the shell script box: open -n -b "com.microsoft.VSCode" --args "$*" 
- Save it as something like "Open in Visual Studio Code"

igorescobar

#!/bin/bash
# .ebextensions/scripts/db_migrate.sh
. /opt/elasticbeanstalk/hooks/common.sh

EB_SUPPORT_FILES=$(/opt/elasticbeanstalk/bin/get-config container -k support_files_dir)

EB_CONFIG_DOCKER_ENV_ARGS=()

while read -r ENV_VAR; do
EB_CONFIG_DOCKER_ENV_ARGS+=(--env "$ENV_VAR")

RobertoSchneiders

This is how I configured the deploy of my rails apps to AWS Elastic Beanstalk through CircleCI 1.0.

If you are using the Circle CI 2.0, take a look at this article from ryansimms

Configure Environments Variables

On Project Settings > Environment Variables add this keys:

• AWS_ACCESS_KEY_ID
• AWS_SECRET_ACCESS_KEY
  The aws user must have the right permissions. This can be hard, maybe, this can help you.

RobertoSchneiders

I am deploying with this IAM using Codeship and Circle CI to Elastic Beanstalk. I had a lot of trouble with this config. I talked to the aws support for about 6 hours until this worked properly, so, I guess it is worth to share.

UPDATE: In the end, I have to use the AWSElasticBeanstalkFullAccess policy. My custom policy keep breaking every week with some new added permission or some EB internal change. Anyway, the IAM I was using is below.

This works for me with CircleCI and EB Cli.

{
    "Version": "2012-10-17",
    "Statement": [
        {

ryanfitz

var AWS = require('aws-sdk');

exports.handler = function(event, context) {
    var cloudsearchdomain = new AWS.CloudSearchDomain({endpoint: 'doc-dev-cinch-accounts-ltmqj5gt5mjb5hg5eyqaf2v5hu.us-east-1.cloudsearch.amazonaws.com'});

    var documents = event.Records.map(function(record) {
        var data = {id : record.dynamodb.Keys.id.S};
        
        if (record.eventName === 'REMOVE') {
            data.type = 'delete'

timothyhutz

#!/bin/bash
# chkconfig: 2345 95 20
# description: This application was developed by me and is tested on this server
# processname: my_app
#
# Tomcat 8 start/stop/status init.d script
# Initially forked from: https://gist.github.com/valotas/1000094
# @author: Miglen Evlogiev <[email protected]>
#
# Release updates:

vrivellino

console.log('Loading function');

var AWS = require('aws-sdk'),
    s3 = new AWS.S3(),
    s3Bucket = 'archive-bucket',
    s3Prefix = 'kinesis-archive-test',
    s3Partitions = 2;

exports.handler = function (event, context) {
  //console.log(JSON.stringify(event, null, 2));