1 Answer
- Newest
- Most votes
- Most comments
0
Never mind. I figured it out. Apparently, I had set up another service a long time ago that I didn't realize was still running and it was firing up. Problem solved.
answered a year ago
Relevant content
- Accepted Answerasked 2 years ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 9 months ago