🛡️ AWS Elastic Beanstalk Environment uses a retired platform branch🟢

• Contextual name: 🛡️ Environment uses a retired platform branch🟢
• ID: /ce/ca/aws/elastic-beanstalk/environment-platform-support
• Tags:
  • 🟢 Policy with categories
  • 🟢 Policy with type
  • 🟢 Production policy
• Policy Type: BEST_PRACTICE
• Policy Categories: RELIABILITY

Stats

not available

Logic

• 🧠 prod.logic.yaml🟢
  • 📗 AWS Elastic Beanstalk Environment
  • 🔌 AWS Elastic Beanstalk Environment - object.extracts.yaml
  • 🧪 test-data.json

Description

Open File

Description

Identify Elastic Beanstalk environments running on a platform branch that AWS has retired. This policy evaluates branch support, using an explicit map of documented solution stack names and AWS retirement dates.

Retirement differs from a platform revision becoming superseded or from enabling managed updates. A newer revision on the same branch does not restore support after the branch retires. Managed updates apply eligible minor and patch updates within a branch; they do not migrate between branches, including after retirement. The platform's provisioning status, such as Ready, also does not establish support.

Rationale

AWS stops providing maintenance updates, security updates, and technical support for retired platform branches. An existing environment can continue running after retirement, but the lack of fixes increases security and operational risk.

Impact

Migrating to a supported branch can require changes to application code, dependencies, deployment configuration, and operating system assumptions. Test the replacement environment before moving production traffic.

... see more

Remediation

Open File

Remediation

Migrate the application to an Elastic Beanstalk platform branch that AWS currently supports. Updating the platform revision within a retired branch does not restore support.

1. Confirm the finding. In the environment's AWS account and Region, verify the deployed solution stack and platform branch against the AWS retirement schedule. Reconcile missing or stale CMDB data before making changes.
2. Plan the migration. Select a supported target branch and review changes to the operating system, runtime, application server, dependencies, and configuration. Back up application data and prepare a rollback plan before changing production.
3. Build and test the replacement. Create a separate environment on the target branch and deploy the application. Preserve the required environment variables, secret references, IAM roles, networking, certificates, scaling settings, and external database connections. Validate startup, health checks, application behavior, logging, security controls, scaling, and data access.

... see more

policy.yaml

Open File

Linked Framework Sections

Section	Sub Sections	Internal Rules	Policies	Flags	Compliance
💼 Cloudaware Framework → 💼 Infrastructure Modernization			39		no data