Issue Summary:
During my recent deployment attempt, I encountered a pipeline error stating: "The Elastic Beanstalk application casting-arabia does not exist." This error was unexpected, as the last successful deployment was conducted approximately 2 years ago, with no subsequent modifications to the Elastic Beanstalk configurations to my knowledge. The specific error message received when accessing the Beanstalk link through the pipeline is "Missing required key 'ResourceArn' in params (2)."
Impact:
This issue is a significant blocker for the project, as Elastic Beanstalk is critical for managing our environment variables for both the development and production servers. The absence of the Elastic Beanstalk application means we cannot proceed with deploying updates or new features to the live environment, affecting our service delivery and project timelines.
Investigative Details:
Request for AWS Support:
We need to understand what happened to the Elastic Beanstalk application and how we can restore access or reconstruct it without losing the critical environment configurations and deployment history. Specifically, we require assistance with the following:
- Investigation into the deletion or inaccessibility of the Elastic Beanstalk application "casting-arabia."
- Steps to recover or re-establish the Elastic Beanstalk application with all the existing configuration and environment variables.
- Guidance on ensuring the integrity and continuity of our deployment processes for future updates.
Thank you for your immediate attention to this matter.
I am available to provide any additional information or clarification required to assist with the resolution.
AWS 官方已更新 9 個月前
Hello,
I appreciate your quick response. Regrettably, I've encountered a limitation with CloudTrail, as it retains logs only for the last 90 days, and the issue at hand appears to have occurred a year or two ago. The last successful deployment of our application was 2 years ago, and it has remained unchanged since.
Upon reviewing the S3 buckets, I didn't find any backups available either.
My primary concern now is to retrieve the environment variables, particularly the AWS-related ones, which are crucial for our operations.
Thank you for your assistance.