Questions tagged with DevOps
Content language: English
Sort by most recent
Hello,
I am working on deploying an application that is packaged using Docker onto Elastic Beanstalk with a single EC2 instance currently.
I have a multi-stage Dockerfile that is as small as I could possibly make it. Initially, I tried to deploy it to Elastic Beanstalk by deploying my Dockerfile, but the builds took too long so it would fail.
So currently, I am building my image locally, pushing it to an AWS ECR repository, then deploying to elastic beanstalk using a Dockerrun.aws.json file. This, however, still gets timeout errors on deployment! When looking at the logs, it appears the build gets stopped because the command used to pull my pre-built image takes too long to download for some reason. So is there any way to increase this timeout?
I have already tried running eb deploy with the --timeout flag, but it doesn't seem to change anything. I have also tried making a config file to increase the timeout:
.ebextensions/increase-timeout.config
```
option_settings:
- namespace: aws:elasticbeanstalk:command
option_name: Timeout
value: 1800
```
But that also fails to change the 300 second timeout.
Does anyone have any idea of how I could fix this? Thanks!
We are trying to build and deploy dotnet application on windows platform in elastic beanstalk environment but deployment is getting failed with an error "Deployment completed, but with errors: During an aborted deployment, some instances may have deployed the new application version. To ensure all instances are running the same version, re-deploy the appropriate application version. Failed to deploy application. Unsuccessful command execution on instance id(s) 'i-0031f3decb3972a8f'. Aborting the operation. [Instance: i-0031f3decb3972a8f ConfigSet: Infra-WriteRuntimeConfig, Infra-EmbeddedPreBuild, Hook-PreAppDeploy, Infra-EmbeddedPostBuild, Hook-EnactAppDeploy, Hook-PostAppDeploy] Command failed on instance. Return code: 1 Output: null. Deployment Failed: Unexpected Exception Error occurred during build: Command hooks failed"
* below CF stack is failing with this error "Resource handler returned message: Error occurred during operation 'CreateApplication'." (RequestToken: <some-token-id>, HandlerErrorCode: GeneralServiceException)"
* Region: eu-weat-1
* anyone knows what could be possible reasons for this error?
```
AWSTemplateFormatVersion: 2010-09-09
Description: EMR serverless cluster
Resources:
EmrSparkApp:
Type: AWS::EMRServerless::Application
Properties:
Type: Spark
ReleaseLabel: emr-6.9.0
Outputs:
EmrSparkAppId:
Description: Application ID of the EMR Serverless Spark App
Value: !Ref EmrSparkApp
```
I want to read data from Databricks output and format the data for SageMaker training
Im trying to create a nested stack on a cloudformation template, i have declared in the parent application a reference to the http api we are using, and use this api in the child template. When i try to do the build with sam, it throws this error:
**"E0001 Error transforming template:ApiId must be a valid reference to an 'AWS::Serverless::HttpApi' resource in same template."**
**Parent template declaration:**
```
childStack:
Type: "AWS::Serverless::Application"
Properties:
Location: ./child.yaml
Parameters:
ApiId: !Ref ApiReference
```
**Child template declaration:**
```
AWSTemplateFormatVersion: '2010-09-09'
Transform: AWS::Serverless-2016-10-31
Parameters:
ApiId:
Type: string
Globals:
Function:
Runtime: !Ref "AWS::NoValue"
Handler: !Ref "AWS::NoValue"
Layers: !Ref "AWS::NoValue"
Resources:
lambdaFunctionLogGroup:
Type: 'AWS::Logs::LogGroup'
Properties:
Location: ./parent.yaml
LogGroupName: !Join
- '/'
- - '/aws/lambda'
- !Ref 'TournamentSubscriptionFunction'
RetentionInDays:
!FindInMap [Service, !Ref EnvironmentName, LogRetentionInDays]
lambdaFunction:
Location: ./parent.yaml
Type: AWS::Serverless::Function
Properties:
Description: Image validation for identity verification
FunctionName: !Sub '${EnvironmentName}-lambda'
PackageType: Image
Architectures: ['arm64']
Environment:
Variables:
ExampleVariable
Policies:
- CloudWatchLambdaInsightsExecutionRolePolicy
Events:
Name:
Type: HttpApi
Properties:
Path: /event-client/api/lambda
Method: POST
ApiId: !Ref ApiReference
Auth:
Authorizer: OAuth2Authorizer
VpcConfig:
SubnetIds: !Split
- ','
- Fn::ImportValue: !Sub '${EnvironmentName}-PrivateSubnets'
Tags:
Environment: !Sub '${EnvironmentName}'
Metadata:
DockerTag: nodejs16.x-v1
DockerContext: ../dist/src/client/lambda-route
Dockerfile: Dockerfile
```
Hi team,
my org relies on Azure devops Pipeline
we want to deploy from Azure to our ECS fargate cluster
but we have some consideration
- we cannot create long-lived credentials in AWS
- we don't have outbound internet connectivity in AWS from within our VPC
how can we deploy the built artifact from Azure to ECS without using AWS long-lived credentials?
i saw the solution of using a build agent [build agents](https://medium.com/hashmapinc/automate-code-deployment-with-aws-ec2-build-agents-for-your-azure-devops-pipelines-6636fe1c8e21)
can Azure assume a role in AWS without using build agents?
how can Azure Assume a role in AWS
but still, need AWS credentials
I am trying to cut down the cost of container insights, so I want to delete some metrics, that I am not using at any time. Please let me know if there is any way to delete default metrics.
I am deploying using codedeploy through Jenkins.
In Jenkins, I created a shell to query codedeploy's deployment-id with aws-cli.
Here is the corresponding command.
```
aws deploy list-deployments --application-name [my-application-name] --deployment-group-name [my-deployment-group-name] --query "deployments[0]" --output text
```
In the case of other distribution groups, only one distribution id was normally output, but in the case of a specific distribution group, two were output.
One was the most recent one, but the second output was the deployment-id that was deployed 4 months ago.
What could be the cause of this output?
Additionally, how can I delete the Deployment history in codedeploy?
root [ERROR]: An error occurred (AccessDeniedException) when calling the GetDeployablePatchSnapshotForInstance operation: Instance Id i-009da1237dec531ad doesn't match the credentials
I am using aws system patch manager to update system patches, but getting above error, when I run any command they run successfully, means no issue related drier or connectivity
Is turborepo supported as a template in Amplify?
If so - could you share a template from one of the basic examples? It looks like amplify-ui is using turborepo but from online research, its not straightforward and there are a lot of red herrings regarding error messages. There are also errors found in the turborepo [basic](https://github.com/vercel/turbo/tree/main/examples/basic) template when. building in amplify that don't appear in local development.
Hi team,
in my team, we have our code and pipelines in AWS code commit and codePipeline,
**our AWS account doesn't allow creating IAM users nor long-lived credentials. also, outbound connections are blocked in our ASEA AWS account (no internet access)**
we need to integrate with other teams using AzureDevops (ADO),
in this case, how can we allow to deploy to AWS from ADO?
is there a specific AWS role to allow another cloud vendor to deploy to AWS (ADO --> AWS)
Thank you!!
Hello all! I am investigating an issue happening with recent API Gateway deployments that have resulting warnings in the Jenkins console output resembling the following:
```
"warnings": [
"More than one server provided. Ignoring all but the first for defining endpoint configuration",
"More than one server provided. Ignoring all but the first for defining endpoint configuration",
"Ignoring response model for 200 response on method 'GET /providers/{id}/identity/children' because a model with the same name already exists. Please reference the defined model/schema, rather than redefine it on this method.",
"Ignoring request model for 'PUT /providers/{id}/admin_settings' because a model with the same name already exists. Please reference the defined model/schema, rather than redefine it on this method.",
"Ignoring response model for 200 response on method 'GET /providers/{id}/profile/addresses/{address_id}' because a model with the same name already exists. Please reference the defined model/schema, rather than redefine it on this method.",
"Ignoring response model for 200 response on method 'GET /providers/{id}/profile/anecdotes/{anecdote_id}' because a model with the same name already exists. Please reference the defined model/schema, rather than redefine it on this method.",
"Ignoring request model for 'POST /providers/{id}/routes' because a model with the same name already exists. Please reference the defined model/schema, rather than redefine it on this method.",
"Ignoring response model for 200 response on method 'GET /providers/{id}/routes/{route_id}' because a model with the same name already exists. Please reference the defined model/schema, rather than redefine it on this method.",
"Ignoring response model for 200 response on method 'GET /service_type_groups/{id}' because a model with the same name already exists. Please reference the defined model/schema, rather than redefine it on this method.",
"Ignoring response model for 200 response on method 'GET /service_types/{id}' because a model with the same name already exists. Please reference the defined model/schema, rather than redefine it on this method."
]
```
Here is an example of the 200 response for an effected method in the OAS doc:
```
responses:
'200':
description: Array of Provider Identities that are children of this Provider
content:
'application/json':
schema:
description: Array of children provider identities
type: array
items:
$ref: '#/components/schemas/providerIdentityExpansion'
'404':
$ref: '#/components/responses/not_found'
'500':
$ref: '#/components/responses/server_error'
```
Based on the language in the warnings text, my understanding is that there is some kind of default request/200 response model defined, and it is somehow being overwritten in the API methods themselves. But when comparing some other (seemingly) non-warning methods they look identical in how they are implemented. I have tried a few potential fixes with removing adding attributes, but none have worked so far.
Would anyone be able to help me in finding what exactly is going wrong here in the OAS doc?