LoginSignup
1
0

More than 5 years have passed since last update.

ElasticBeanstalkのデザイン変更の際に生じた問題

Last updated at Posted at 2018-04-26

概要

terraformでElasticBeanstalkの環境作成時にエラーが発生し、オーケストレーションが失敗したので、調べた。

経緯

  • Configurationはこんな感じで書いてた
elastic_beanstalk_environment.tf
/*************************/
/* worker Environment */
/*************************/
resource "aws_elastic_beanstalk_environment" "xxxxxxxxx" {
  name                 = "xxxxxxxxx"
  application          = "xxxxxxxxx"
  solution_stack_name  = "64bit Amazon Linux 2016.09 v2.3.2 running Ruby 2.3 (Puma)"
  tier                 = "Worker"
  tags {
    Service     = "xxxxxxxxx"
    Environment = "xxxxxxxxx"
    Description = "Managed by Terraform"
  }

  • ElasticBeanstalkのConfigurationの表示名が変更になってたので、terraformでもそれを指定

image.png

elastic_beanstalk_environment.tf
/*************************/
/* worker Environment */
/*************************/
resource "aws_elastic_beanstalk_environment" "xxxxxxxxx" {
  name                 = "xxxxxxxxx"
  application          = "xxxxxxxxx"
  solution_stack_name  = "Puma with Ruby 2.3 running on 64bit Amazon Linux/2.7.2"
  tier                 = "Worker"
  tags {
    Service     = "xxxxxxxxx"
    Environment = "xxxxxxxxx"
    Description = "Managed by Terraform"
  }

  • planは通ったけど、applyしたら失敗した...
* aws_elastic_beanstalk_environment.xxxxxxxxx: InvalidParameterValue: No Solution Stack named 'Puma with Ruby 2.3 running on 64bit Amazon Linux/2.7.2' found.

ドキュメント見たら、Solution Stack Nameの箇所は変更されてないので、以前の書き方でapplyすると成功しました。

所感

マネコンはデザインがよく変わるので、ドキュメントを参照しましょう(;・∀・)

1
0
0

Register as a new user and use Qiita more conveniently

  1. You get articles that match your needs
  2. You can efficiently read back useful information
  3. You can use dark theme
What you can do with signing up
1
0