Aws Codepipeline

Aws Codepipeline

AWS CodePipeline is a fully managed continuous delivery solution that assists you in automating your release pipelines for quick and reliable application and infrastructure upgrades. Third-party services like GitHub or your own custom plugin may be simply connected with AWS CodePipeline.

You can use any of the following interfaces to create, access, and administer your pipelines:

  • The AWS Management Console is a web-based interface for accessing AWS Data Pipeline.
  • AWS Command Line Interface (AWS CLI) – Supports Windows, macOS, and Linux and provides commands for a wide range of AWS services, including AWS Data Pipeline. See AWS Command Line Interface for additional information on installing the AWS CLI.
  • AWS SDKs – Provides language-specific APIs and handles many of the connection intricacies, such as computing signatures, retrying requests, and resolving errors.
  • Query API – Provides low-level APIs that may be accessed using HTTPS requests. The Query API is the quickest way to get started with AWS Data Pipeline, but it requires your application to handle low-level functionality like hash creation and error handling.

Amazon EC2 Container Service

The Amazon EC2 Container Solution is a highly scalable, high-performance container management service that supports Docker containers and allows you to run distributed applications on Amazon EC2 instances in a cluster.

Benefits

  • Role-based access control is integrated across all AWS services (IAM)
  • Audit logging and security for APIs across all services (CloudTrail)
  • Integration with other Amazon Web Services (AWS) services (24x7 support and consolidated billing)
  • Architectural patterns/guidance and training (well architected)
  • Removes the requirement for cluster management software and the creation of fault-tolerant designs.
  • Schedule batch operations and long-running apps.
  • Simple APIs allow for easy integration and expansion.
  • Thousands of Docker containers may be launched in seconds with no added complexity.
  • You'll have a high level of isolation thanks to security features.

You'll need to provide the cloud-config file for the User Data.

#cloud-config
rancher:
    environment:
      ECS_CLUSTER: your-ecs-cluster-name
      ECS_AVAILABLE_LOGGING_DRIVERS: |-
         ["json-file","awslogs"]
# If you have selected a RancherOS AMI that does not have ECS enabled by default,
# you'll need to enable the system service for the ECS agent.
   services_include:
    amazon-ecs-agent: true