AWS Copilot CLI を使って AWS App Runner にデプロイしてみた

$ aws configure
AWS Access Key ID [None]: <アクセスキーID>
AWS Secret Access Key [None]: <シークレットアクセスキー>
Default region name [None]: <使用するリージョン>
Default output format [None]: json

$ aws sts get-caller-identity
{
    "Account": <アカウントID>, 
    "UserId": <ユーザーID>, 
    "Arn": "arn:aws:iam::<アカウントID>:user/copilot-user"
}

$ curl -Lo copilot https://github.com/aws/copilot-cli/releases/download/v1.24.0/copilot-darwin && chmod +x copilot && sudo mv copilot /usr/local/bin/copilot &&  copilot --help

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 41.1M  100 41.1M    0     0   105M      0 --:--:-- --:--:-- --:--:--  105M
👩✈️ Launch and manage containerized applications on AWS.

Commands 
  Getting Started 🌱
    init        Create a new ECS or App Runner application.
    docs        Open the copilot docs.
 
  Develop ✨
    app         Commands for applications.
                Applications are a collection of services and environments.
    env         Commands for environments.
                Environments are deployment stages shared between services.
    svc         Commands for services.
                Services are long-running ECS or App Runner services.
    job         Commands for jobs.
                Jobs are tasks that are triggered by events.
    task        Commands for tasks.
                One-off Amazon ECS tasks that terminate once their work is done.
 
  Release 🚀
    pipeline    Commands for pipelines.
                Continuous delivery pipelines to release services.
    deploy      Deploy a Copilot job or service.
 
  Extend 
    storage     Commands for working with storage and databases.
    secret      Commands for secrets.
                Secrets are sensitive information that you need in your application.
 
  Settings ⚙️
    version     Print the version number.
    completion  Output shell completion code.

Flags
  -h, --help      help for copilot
  -v, --version   version for copilot

Examples
  Displays the help menu for the "init" command.
  `$ copilot init --help`

$ git clone https://github.com/aws-containers/hello-app-runner.git
$ cd hello-app-runner

$ copilot app init
Application name: my-app-runner-application
✔ Proposing infrastructure changes for stack my-app-runner-application-infrastructure-roles
- Creating the infrastructure for stack my-app-runner-application-infrastructure-roles          [create complete]  [52.1s]
  - A StackSet admin role assumed by CloudFormation to manage regional stacks                   [create complete]  [21.7s]
  - An IAM role assumed by the admin role to create ECR repositories, KMS keys, and S3 buckets  [create complete]  [20.7s]
✔ The directory copilot will hold service manifests for application my-app-runner-application.

Recommended follow-up action:
  - Run `copilot init` to add a new service or job to your application.

$ copilot env init --help
Creates a new environment in your application.

Usage
  copilot env init [flags]

Common Flags
  -a, --app string                     Name of the application. (default "my-app-runner-application")
      --aws-access-key-id string       Optional. An AWS access key.
      --aws-secret-access-key string   Optional. An AWS secret access key.
      --aws-session-token string       Optional. An AWS session token for temporary credentials.
      --default-config                 Optional. Skip prompting and use default environment configuration.
  -n, --name string                    Name of the environment.
      --profile string                 Name of the profile.
      --region string                  Optional. An AWS region where the environment will be created.

Import Existing Resources Flags
      --import-cert-arns strings         Optional. Apply existing ACM certificates to the internet-facing load balancer.
      --import-private-subnets strings   Optional. Use existing private subnet IDs.
      --import-public-subnets strings    Optional. Use existing public subnet IDs.
      --import-vpc-id string             Optional. Use an existing VPC ID.

Configure Default Resources Flags
      --internal-alb-allow-vpc-ingress   Optional. Allow internal ALB ingress from port 80 and/or port 443.
      --internal-alb-subnets strings     Optional. Specify subnet IDs for an internal load balancer.
                                         By default, the load balancer will be placed in your private subnets.
                                         Cannot be specified with --default-config or any of the --override flags.
      --override-az-names strings        Optional. Availability Zone names.
                                         (default 2 random AZs)
      --override-private-cidrs strings   Optional. CIDR to use for private subnets.
                                         (default 10.0.2.0/24,10.0.3.0/24)
      --override-public-cidrs strings    Optional. CIDR to use for public subnets. 
                                         (default 10.0.0.0/24,10.0.1.0/24)
      --override-vpc-cidr ipNet          Optional. Global CIDR to use for VPC.
                                         (default 10.0.0.0/16)

Telemetry Flags
      --container-insights   Optional. Enable CloudWatch Container Insights.

Examples
  Creates a test environment using your "default" AWS profile and default configuration.
  `$ copilot env init --name test --profile default --default-config`

  Creates a prod-iad environment using your "prod-admin" AWS profile and enables container insights.
  `$ copilot env init --name prod-iad --profile prod-admin --container-insights`

  Creates an environment with imported resources.
  `$ copilot env init --import-vpc-id vpc-099c32d2b98cdcf47 \`
  `--import-public-subnets subnet-013e8b691862966cf,subnet-014661ebb7ab8681a \`
  `--import-private-subnets subnet-055fafef48fb3c547,subnet-00c9e76f288363e7f \`
  `--import-cert-arns arn:aws:acm:us-east-1:123456789012:certificate/12345678-1234-1234-1234-123456789012`

  Creates an environment with overridden CIDRs and AZs.
  `$ copilot env init --override-vpc-cidr 10.1.0.0/16 \`
  `--override-az-names us-west-2b,us-west-2c \`
  `--override-public-cidrs 10.1.0.0/24,10.1.1.0/24 \`
  `--override-private-cidrs 10.1.2.0/24,10.1.3.0/24`

$ copilot env init
Environment name: dev
Credential source: [profile default]
Default environment configuration? Yes, use default.
✔ Wrote the manifest for environment dev at copilot/environments/dev/manifest.yml
- Update regional resources with stack set "my-app-runner-application-infrastructure"  [succeeded]  [0.0s]
- Update regional resources with stack set "my-app-runner-application-infrastructure"  [succeeded]        [131.5s]
  - Update resources in region "us-east-1"                                             [create complete]  [128.0s]
    - KMS key to encrypt pipeline artifacts between stages                             [create complete]  [121.4s]
    - S3 Bucket to store local artifacts                                               [create complete]  [2.1s]
✔ Proposing infrastructure changes for the my-app-runner-application-dev environment.
- Creating the infrastructure for the my-app-runner-application-dev environment.  [create complete]  [51.9s]
  - An IAM Role for AWS CloudFormation to manage resources                        [create complete]  [20.1s]
  - An IAM Role to describe resources in your environment                         [create complete]  [19.9s]
✔ Provisioned bootstrap resources for environment dev in region us-east-1 under application my-app-runner-application.
Recommended follow-up actions:
  - Update your manifest copilot/environments/dev/manifest.yml to change the defaults.
  - Run `copilot env deploy --name dev` to deploy your environment.

$ copilot env deploy

$ copilot svc init
Note: It's best to run this command in the root of your workspace.
Service type: Request-Driven Web Service
Service name: frontend
Reachable from: Internet
Dockerfile: ./Dockerfile
✔ Wrote the manifest for service hello-app-runner-service at copilot/hello-app-runner-service/manifest.yml
Your manifest contains configurations like your container size and port (:8000).

- Update regional resources with stack set "my-app-runner-application-infrastructure"  [succeeded]        [15.5s]
  - Update resources in region "us-east-1"                                             [update complete]  [11.2s]
    - ECR container image repository for "hello-app-runner-service"                    [create complete]  [2.6s]
Recommended follow-up actions:
  - Update your manifest copilot/hello-app-runner-service/manifest.yml to change the defaults.
  - Run `copilot svc deploy --name hello-app-runner-service --env test` to deploy your service to a test environment.

$ copilot svc deploy
(省略)
✔ Deployed service frontend.
Recommended follow-up action:
  - You can access your service at <App Runner のエンドポイント> over the internet.

$ copilot app delete
Are you sure ~ ?: Y