1 Answer
- Newest
- Most votes
- Most comments
0
johan at TTN discovered it was an error in the AWS documentation. It has been fixed.
answered 5 years ago
Relevant content
- asked 5 years ago
- asked 4 years ago
- AWS OFFICIALUpdated 25 days ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated a year ago