aws-opsworks

问题 I am using Amazon linux AMI in Opsworks and the Amazon linux AMI are the latest one (OS Amazon Linux 2017.03). The issue is that this AMI comes with docker version 17.03.2-ce , however I need to install version 17.05 or later (because I want to modify "ingress" network in docker swarm which is only possible in the latest docker versions.) Looks like Amazon officially supports version only till 17.03. If I try to upgrade the docker manually from the centos rpm/repository, I get the following

问题 According to AWS documentation you can create a Custom AMI two different ways. http://docs.aws.amazon.com/opsworks/latest/userguide/workinginstances-custom-ami.html I'm creating my AMI directly from an EC2 instance so the OPworks Agent should NOT be there. Nevertheless instances created with my AMI would NOT get pass the setup stage. Does anyone knows why this is? Update: Here's some more information. If you look at the article above it says to stop the OPworks agent etc. Well I logged into

问题 The Problem When running custom cookbooks on AWS OpsWorks a setup_failed status appears against the instance and the following in the failure log: [2016-03-26T22:53:48+00:00] INFO: Started chef-zero at chefzero://localhost:8889 with repository at /var/chef One version per cookbook data_bags at /var/chef/runs/62832572-cb67-421a-8309-d831140d7b98/data_bags nodes at /var/chef/runs/62832572-cb67-421a-8309-d831140d7b98/nodes [2016-03-26T22:53:48+00:00] INFO: Forking chef instance to converge...

问题 I would like to know how to prevent this type of error. So far I tried disabling prepared statements via the database configuration at AWS Opsworks: Eg: Database Configuration }, "deploy": { "app_name": { "database": { "adapter": "postgresql", "prepared_statements": false, "username": "username", "database": "db_name_production", "host": "cool_host.com", "password": "easy" }, Error Log PG::DuplicatePstatement: ERROR: prepared statement "a6" already exists : INSERT INTO "polls" ("answer_type",

问题 I am trying to run congnito via cloudformation and everything works but there is section in cognito as follows: As you see there is section "Enable identity providers" and I can not find where I can set it to my cognito user pool in cloudformation! I tried this attributes but it says not supported. SupportedIdentityProviders Here is my code for user pool client: UserPoolClient: Type: "AWS::Cognito::UserPoolClient" Properties: ClientName: !Sub ${project}-client ExplicitAuthFlows: - ADMIN_NO

问题 I have a fairly complex deployment of dynamically configured instances of a rail apps on nginx using passenger that I currently use Capistrano for. I am trying to automate the entire process on Opsworks from creating the stack, layers, instances and dynamic app deployment. None of the existing Opsworks recipes come close to what I need so I started my own custom cookbooks. I am trying to test them using test-kitchen and vagrant but the Opsworks cookbooks have too many custom dependancies to

问题 I'm new to Opsworks, so hopefully this is a very easy question! My setup is a custom PHP/Apache AMI (Amazon Linux) server layer, an RDS layer, and a PHP app named "abc_app" in an S3 bundle. I tried to deploy the app to a server instance. It deployment finished successfully, but the code is not anywhere on the server, and nothing was in the /var/www/html directory where I expected it to be. The deploy log was not very helpful except that there was no mention of "abc-app" in it. I'm not sure if

问题 I have my stack on opsworks and app is deploying fine (cake php). Now I have to configure some things like chmod, php versions, etc etc... I'm reading about this but don't know exactly whats the best way to do this. Question 1 - Should I do this with custom deploy JSON or via custom cookbooks? Question 2 - Whats the correctly way to work with custom cookbooks? Fork original AWS repositories, update recipes and then use it in my stack? 回答1: depends on what you would like to achieve, you may

问题 I am trying to set up Redis instance/layer in the Amazon OpsWorks environment for caching purposes and Sidekiq, but cannot make the Rails application communicate with Redis. Do I need a Chef recipe for it no matter what? I've tried to create Redis on a separated layer, added an instance to this layer, but cannot find a way to make communicate Rails and Redis between each other. Any advice how to make it? Thank you 回答1: A possible way to do it is create a "ElastiCache cluster" on AWS and tell

问题 I'm new to chef and AWS OpsWorks. I want to create a custom cookbook in order to precompile assets in production and set cron jobs with the whenever gem. I found something about precompiling assets and I'll figure the cron part out as well, but I am confused how my custom chef project should look like. Is it a full chef solo project that will replace the standard cookbook(s) of AWS OpsWorks, thus I'll have to copy stuff from their github repo? Or will our and their cookbooks be merged? If so,