jairoglyph

:sunny: 
:zap: 
:leaves: 
:lipstick: 
:cop: 
:wheelchair: 
:fish: 
:hammer: 
:moneybag: 
:calling: 

chriseppstein

This gist is no longer valid. Please see Compass-Rails for instructions on how to install.

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": [
        {

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.

ryanshoover

# Continuous Integration to a WP Engine install
# PHP CircleCI 2.1 configuration file

# Requirements:
# 1. In CircleCI settings, add environment variables for your site's installs:
#     * WPE_PRODUCTION_INSTALL=thenameofyourproductioninstall
#     * WPE_STAGING_INSTALL=thenameofyourstaginginstall
#     * WPE_DEVELOPMENT_INSTALL=thenameofyourdevelopmentinstall
# 2. In your repo, have two files
#     * `./.gitignores/__default`    -- Excludes any compiled files