The blue/green deployment is still connected to both the old and new blue instances, which is expected behavior after a successful upgrade. The deployment controls the replication and switchover process between the environments.
You can safely delete the old blue instance since the new blue instance is now the primary. However, it's best to leave the blue/green deployment in place for a period of time in case you need to rollback.
To delete the old resources, you would first set deletion protection on the new blue instance. Then delete the old blue instance. Finally, delete the blue/green deployment once you're confident the upgrade was successful.
Deleting the blue/green deployment will remove the "blue/green" badge from the new blue instance and it will appear as a standalone instance again. However, replication between the old green and new blue will continue unless you manually stop it.
Thank you, it worked like you said.
- Accepted Answerasked a year ago
- Accepted Answerasked 2 months ago
- AWS OFFICIALUpdated 6 months ago
- How do I upgrade my Elastic Beanstalk environment platform from a deprecated or retired version to the latest version?AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago