copilot svc deploy works fine, I just setup a default pipeline to automatically build and deploy after commit. I can see the pipeline getting triggered automatically on commit to main branch but the build is failing even though it builds fine when I run copilot svc deploy. Are the same env variables and secrets defined in my manifest used in the pipeline build? I don't see any env vars when poking around in CodePipeline admin.
It fails at this step COMMAND_EXECUTION_ERROR: Error while executing command: for workload in $WORKLOADS; do manifest but no useful error message just Reason: exit status 1 so I'm not sure how to proceed debugging, any ideas?
6 replies
Hi David,
I have tried to add this to addons:
Resources:
SSMAccessPolicy:
Type: AWS::IAM::ManagedPolicy
Properties:
PolicyDocument:
Version: 2012-10-17
Statement:
- Effect: Allow
Action:
- ssm:Describe*
- ssm:Get*
- ssm:List*
Resource: "{{ resource ARN }}"
Outputs:
SSMAccessPolicyArn:
Description: "The ARN of the ManagedPolicy to attach to the task role."
Value: !Ref SSMAccessPolicyand i get an error saying ResourceNotReady: failed waiting for successful resource state: Parameter values specified for a template which does not require them.
Heya @srikaransc !
Can you try this:
Parameters:
App:
Type: String
Description: Your application's name.
Env:
Type: String
Description: The environment name your service, job, or workflow is being deployed to.
Name:
Type: String
Description: The name of the service, job, or workflow being deployed.
Resources:
SSMAccessPolicy:
Type: AWS::IAM::ManagedPolicy
Properties:
PolicyDocument:
Version: 2012-10-17
Statement:
- Effect: Allow
Action:
- ssm:Describe*
- ssm:Get*
- ssm:List*
Resource: "{{ resource ARN }}"
Outputs:
SSMAccessPolicyArn:
Description: "The ARN of the ManagedPolicy to attach to the task role."
Value: !Ref SSMAccessPolicyCopilot always passes these parameters to the Addons stack so that you can build your own fancy names, or maybe import values from the environment or service stack
Hi everyone,
Please can someone tell me which directory does buildspec post_build execute in?
I want to upload file to newly created s3 bucket
- aws s3 sync public/assets/images s3://bucket-nameAlso is it possbile to get dynamic bucket name inside buildspec?
Thanks
6 replies
1 reply
9 replies
Hi, I'm trying to ship log from my container to Datadog with logging sidecars
Here is how my manifest.yml look like
logging:
image: amazon/aws-for-fluent-bit:latest
destination:
Name: datadog
TLS: on
apikey: <DD_API_KEY>
enableMetadata: true
configFile: /fluent-bit/configs/parse-json.confIs it possible to set this apikey from SSM?
Hi everyone, I am trying to apply a custom firelens config to make the Fargate logs work better with our Kinesis + Function Beat setup.
Our manifest.yml looks like:
logging:
image: 123456789.dkr.ecr.us-east-1.amazonaws.com/ns/firelens-custom:v0.2
destination:
Name: cloudwatch
region: us-east-1
log_group_name: /copilot/test-fargate-services
log_stream_prefix: copilot/
configFile: /extra.confThe Fargate service works well, however the custom configuration changes don't get applied to the generated logs.
I reckon its because of the service task definition generated by copilot. The custom config is missing from the firelensConfiguration :
"image": "123456789.dkr.ecr.us-east-1.amazonaws.com/ns/firelens-custom:v0.2",
"startTimeout": null,
"firelensConfiguration": {
"type": "fluentbit",
"options": {
"enable-ecs-log-metadata": "true"
}
},Any ideas on why copilot is not adding the custom config to task definition?
configFilePath instead.