1 Answer
- Newest
- Most votes
- Most comments
2
These issues was caused due to possible user error in launching the instance as a mac2-m2.metal instance from a mac2.metal AMI and placing it on a mac2-m2 dedicated host.
The reported issues no longer occur when the instance is launched as a mac2.metal instance and placed on a mac2 dedicated host.
answered 18 days ago
Relevant content
- asked 2 years ago
- asked 2 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 10 months ago