"What I know about AWS wouldn't fill the back of a postage stamp"
Recently one of our Team resigned and went off to pastures new. He was the "AWS" guy. As a long term Windows / Microsoft and Azure guy, being lumbered with problems in AWS fills me with fear (and a bit of hatred)
"There's an issue pushing data from redshift to an S3 bucket"
I have no idea what this means. I barely know my around the console. So it's time to draw on good ol' fashioned IT Troubleshooting experience. Has it ever worked? Is it working for anyone else? What's changed??
Well then I racked my brains. The user insisted it was an IAM issue. But nothing has changed in IAM because no one left on the team touches AWS. What has changed?
The only thing that came to mind was that we upgraded the Redshift Cluster from 2 nodes to 4 last Friday. A simple click a button job. That wouldn't effect permissions.... would it?
Well, after much clicking and expanding and tabs and the like - turns out, the permissions on the bucket had indeed been locked down to IP addresses. Two new nodes = two new IP addresses. Can that be it?
Added the IP's to the bucket policy. Bosh. Works. I'm an AWS Troubleshooting hero.
The tl;dr is this...
Don't doubt yourself. Draw on your experience. You are an IT Professional - don't be scared off by terms like "buckets, redshift, AWS glue (glue??)" etc.
If there's no one else to turn to you, you have to fix it and you can fix it!
JV
"There's an issue pushing data from redshift to an S3 bucket"
I have no idea what this means. I barely know my around the console. So it's time to draw on good ol' fashioned IT Troubleshooting experience. Has it ever worked? Is it working for anyone else? What's changed??
Well then I racked my brains. The user insisted it was an IAM issue. But nothing has changed in IAM because no one left on the team touches AWS. What has changed?
The only thing that came to mind was that we upgraded the Redshift Cluster from 2 nodes to 4 last Friday. A simple click a button job. That wouldn't effect permissions.... would it?
Well, after much clicking and expanding and tabs and the like - turns out, the permissions on the bucket had indeed been locked down to IP addresses. Two new nodes = two new IP addresses. Can that be it?
Added the IP's to the bucket policy. Bosh. Works. I'm an AWS Troubleshooting hero.
The tl;dr is this...
Don't doubt yourself. Draw on your experience. You are an IT Professional - don't be scared off by terms like "buckets, redshift, AWS glue (glue??)" etc.
If there's no one else to turn to you, you have to fix it and you can fix it!
JV