- Newest
- Most votes
- Most comments
AWS CloudShell is just a web-based SSH environment. I would be surprised if there is a need to do anything prior to the migration.
@PGearman Full transparency, I'm still a bit of a rookie, so don't take my words as gospel. Having said that, how recent is this notification? If it's not recent, I wouldn't worry about it.
The most recent notification was this week. Again, I don't think we have anything on there. I certainly didn't write any scripts or anything for CloudShell that we would need to back-up, so my only concern at this point is the affected resource (by ARN) matching our RDS DB. But the DB has back-ups, and is running on MySQL 8.0, while CloudShell is saying it's still on MySQL 5.5.
So I'm pretty sure I have nothing to worry about, I just wanted to make sure of that.
Relevant content
- Accepted Answerasked a year ago
- asked a year ago
- asked 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
Just to be clear, when I click on the affected resource, it gives an ARN which appears to be the same ARN for our DB instances. But it doesn't appear that the DB instances are on there (they're on Amazon RDS). It still shouldn't be a problem?