Azure has a robust CI/CD pipeline which is much easier to use than CodeDeploy on AWS. It is called Build/Release pipelines under Azure DevOps. It allows you to configure multiple environments with build and release (deployment) stages for each. It also allows for easy configuration and interoperability with Azure Webapps/VMs and other resources available on ...
It may be helpful to look at the different AWS developer services as you are trying to achieve your goal in the wrong services:
Running the specific dotnet testing and publish steps are not done in CodeDeploy. Rather, they would be done in AWS CodeBuild, in the AWS Pipeline, or directly on your Jenkins Server.
AWS CodeDeploy is for taking your build ...
Yes. AWS CodeDeploy bundletype is specified separately from the revision location, so you could upload a .nupkg to Amazon S3, set the bundle type to 'zip', and since a nupkg is simply an archive CodeDeploy will treat it as such and upload it to your EC2 instance.
In your nuspec, make sure your appspec.yml gets placed in the root of your .nupkg. My project ...
got this answer from aws support
Andrew from AWS Support here.
I understand that you would like to know if there is a way to speed up
Code Deploy as currently it takes 7 minutes to complete. Please
correct me if needed.
After examining the link and the Code Deploy environment I can see
that the step which involves rerouting ...
bitbucket deploy: 45 seconds
This seems correct. Not sure of your repo size, but if it is hosted outside of your region, that's not out of the ordinary.
bitbucket deploy: 45 seconds
Again, seems correct. Not much room for optimization here.
provisioning a new ec2 instance: 3:40 minutes
What size of instance are you provisioning? Are you ...
Both are excellent tools, but it depends on your use cases for which is better. I would highly recommend using the entire AWS Ci/Cd suite (CodeBuild/CodePipeline/CodeDeploy) to gain the full benefit of using your resources in AWS. Here are pros for both:
Multitude of customizability plugins
Integration with all cloud providers (GCP, Azure, etc.)
The way I handled this in the past was to have a separate repository that contains the scripts, as most of them ended up shared across multiple projects anyway. Then your appspec.yml file just contains references to the scripts and imports them via a submodule. It's not perfect because a developer could change the appspec.yml to call his own scripts ...
I know a good amount about Jenkins so I can give you specific information about that, but I know virtually nothing about AWS code deploy, that being said using my general AWS knowledge, there are a few things I think I can safely tell you to get started.
Jenkins is open source however you can get hosted Jenkins if you prefer a managed solution. CodeDeploy ...
i got the answer from aws support:
he reason why you are seeing that notification is because it is in accordance to your launch configuration (staging-1-deploy) settings. During the creation of a launch configuration, the assignment of public IP addresses to EC2 instances defaults to Only assign a public IP address to instances launched in the default VPC ...